• SONAR
  • Help please - is it possible updating to X2a has caused these problems?
2013/04/14 13:54:53
SteveStrummerUK
Computer Specs:
  • Intel Core i7-2600 CPU @ 3.40 GHz; 16GB RAM
  • Windows 7 Home Premium 64bit
Sound Card:
  • Line 6 TonePort UX2
  • ASIO Drivers
SONAR:
  • X2a 64bit

 
As you may have seen in my other thread, I updated X2 yesterday to version X2a. The only other update I'd done was the 'Hotfix' that came out just after it was launched.
 
Since then, I've experienced a couple of problems, and I'm just wondering if this could be anything to do with the update, or whether something else has caused it.
 
First off, the only other change I've made to my PC in the last week was to download the trial version of Adobe Lightroom about 5 days ago. Since I first installed X2 (the day it was released), I've never had a problem with it, and certainly nothing like what has happened today and yesterday.
 
I noticed yesterday that after using X2a for a while, and having closed it, I was unable to play any sound files, either on my computer, or on any website. I reopened X2a and it played the project perfectly. I checked to see if I'd inadvertently unchecked the 'Share Drivers' option in SONAR, but I hadn't. I closed X2a again, and still couldn't get any audio from any source (I tried Windows Media Player, Foobar, WinAmp and RealPlayer).
 
The only way I could restore sound to everything else except SONAR was to restart my PC.
 
And now this afternoon, exactly the same thing has happened since I closed X2a. I definitely had audio before I opened it (I checked deliberately) but again, after I closed it, no other audio will play.
 
I've been to the Line 6 website and reinstalled the latest drivers for my UX2 but this still hasn't altered the situation.
 
In desperation, I've tried using System Restore to return X2a to X2, but that keeps hanging for some reason. On one restart, Windows failed to open altogether, so I retried in Safe Mode and again tried to restore. When my PC rebooted, it went straight to the 'Repair' screen, which also failed.
 
After having to physically unplug the thing to turn it off, my PC has eventually restarted and loaded Windows. As my last back-up ran last Tuesday, I'm now in the process of manually saving everything to a removable drive, just in case everything goes pear shaped.
 
So, is this a massive coincidence or does it seem possible that installing and running X2a has caused this?
 
If so, any advice would be very gratefully received. I'm guessing the first thing I should do is to uninstall/roll back X2a to see if that clears it. Which is the best way to accomplish this seeing as System Restore doesn't want to play ball?
 
Thanks in advance guys
 
 
2013/04/14 15:04:22
dlion16
this sounds more systemic than an x2a update.

do you have windows on automatic updates? if not, have you installed any windows updates? i heard that some were problematic and had to be uninstalled.

[link=http://arstechnica.com/security/2013/04/microsoft-tells-windows-7-users-to-uninstall-faulty-security-update/]

also, have you updated your graphics card driver? i use vegas as well as sonar, and that forum is filled with discussions about drivers and performance. bottom line, the latest may not be the best for your system and what you do. not related to audio? imho the weakest part of sonar is the gui and how it interacts with windows ...

i believe you can just reinstall x2, but i'm not 100% sure.
2013/04/14 15:12:05
The Maillard Reaction


Two quick things to check.

1) Can you minimize SONAR and use some other Audio App while SONAR is still running?

2) When you exit SONAR are you sure it is really shutting down? Can you check services and make sure it isn't stuck and has actually shut down?


Good Luck.

best regards,
mike
2013/04/14 15:47:07
tKx5050
When you did the x2a update Sonar saved the original sonarpdr.exe in a folder called "backup" under prog files->cakewalk->x2 producer. I believe you can just replace the current sonarpdr.exe with the backup to uninstall the x2a update. 

Save the current one just in case and someone chime in if I'm wrong about this. I don't think your problems are from the update. 

Steve
2013/04/14 18:42:47
SteveStrummerUK

Hi guys, many thanks to all who have replied.

I'm still backing everything up at the moment and so I probably won't get chance to try out anything tonight.



2013/04/14 18:47:39
jb101
tKx5050


When you did the x2a update Sonar saved the original sonarpdr.exe in a folder called "backup" under prog files->cakewalk->x2 producer. I believe you can just replace the current sonarpdr.exe with the backup to uninstall the x2a update. 

Save the current one just in case and someone chime in if I'm wrong about this. I don't think your problems are from the update. 

Steve

I seem to remember someone from Cake explaining that this only worked for quickfixes, not updates.  I did it when a quickfix seemed to cause problems with X1.
 
I also don't think the X2a update caused your issues.
2013/04/14 20:59:12
tKx5050
jb101 - I think you're probably right. Just hot-fixes save a backup.
2013/04/14 21:49:56
Tom Riggs
I think sonar is changing the sample rate of your sound card and it is not resetting to 44.1 when you close. That would cause othe programs not to playback. 
2013/04/14 23:59:34
jaws44
I agree with Tom Riggs.
It happens to me when I open a project in sonar set at 96k.
So if I want to play another source I close sonar and open my sound card menu from Windows and I change the sample rate to 48k or 44.1k and it will work. 
2013/04/15 07:09:19
The Maillard Reaction
Tom Riggs


I think sonar is changing the sample rate of your sound card and it is not resetting to 44.1 when you close. That would cause othe programs not to playback. 



+2


I had the same thought.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account