alogie


There are some beta drivers for the Liquid Saffire 56 at beta.focusrite.com, but unfortunately they didn't fix the issue with the audio engine error popping up.
Does rolling back to X1a = uninstalling everything and then installing again, or is there a way to back out the X1b update?

musicman100

alogie


There are some beta drivers for the Liquid Saffire 56 at beta.focusrite.com, but unfortunately they didn't fix the issue with the audio engine error popping up.
Does rolling back to X1a = uninstalling everything and then installing again, or is there a way to back out the X1b update?

if you had a bacup pre update you could do that, but I had to do an un-install of X1 (it deletes A,B, and quickfixes  and go back and re-install from the original DVDs then aapply the updates one a ta time testing along the way.

HOWEVER!!!!!! try the buffer sizes first.

Does your audio quit ? dropout light? can you re-enable the audio engine?

brundlefly

the only way I seem to be able to re-enable the engine is to go into Prefs, changes something in the audio driver settings e.g. 64-bit engine, and save the change.

I have similar issues because the clock source for my interface is external via ADAT, and X1 can't control the rate the way it wants. What I've found is that I have to have the "Default [sample] rate for new projects" set to match the current project rate. This really shouldn't matter, and didn't used to, but SONAR now attempts to set the clock rate on the interface to the Default rate as soon as it starts (even before a project is opened), and again if you open a project that does not match the Default rate.


If you are changing sample rates from one project to another, or if Windows or other multi-media applications are being allowed to use your interface, and change the sample rate, this could be part of the problem. It also depends on how the interface driver reports status to SONAR, and whether it responds properly to SONAR's request to change the rate.


The Bakers are aware of these issues from another thread (http://forum.cakewalk.com/tm.aspx?high=&m=2291325&mpage=1#2292302) and problem reports, and are looking into it. In the mean time, I suggest making sure the Default rate in driver settings always matches the project rate, and no other apps are trying to use the driver at the same time as SONAR, or even in between SONAR sessions if possible. I do this by leaving my onboard sound enabled a the default device for Windows (though I have Windows sounds turned off of course) and other multi-media apps, reserving my E-MU 1820m for use only by SONAR.

BTW, I personally doubt disk space has anything to do with it. I run a very small partition on my audio drive that I use for active projects, archiving stuff off to a larger partition when it gets full. I've had the active partition get down to 1GB, and still be working fine. A twenty-track, 5-minute project recorded at 24x48 is about 1.6GB of audio; you don't need 100-500 times that much free space to avoid disk problems.

25GB free is plenty. If you're not getting disk-based dropouts, it's of no concern.

brundlefly

chuckebaby
leaving your onboard soundcard kinda goes against everything ive been taught..but i know you are a very smart guy bundle..so i might just take your advise on this..is this something everyone should do?

 It's definitely more common to disable onboard sound, and there are valid arguments for it, but I'm not the only one to recommend doing it this way.


If your DAW is truly dedicated to music, and you never run a browser, CD player or other media player on it, I could see disabling the onboard sound. But if your DAW is also your all-purpose PC as mine is, I think it makes sense to dedicate the audio interface to SONAR, and make the onboard sound available to Windows so it keeps its mitts off your interface.

In XP, you could actually tell Windows to only use the default audio device. Win7 did away with this option, but I've not had any trouble with any other app trying to use my audio interface unless I specifically configure it to.

Another advantage of this setup is that you can be watching and listening to a tutorial or some other online audio source and following/playing along with SONAR with no driver sharing problems between the two.

musicman100

alogie

musicman100

alogie


There are some beta drivers for the Liquid Saffire 56 at beta.focusrite.com, but unfortunately they didn't fix the issue with the audio engine error popping up.
Does rolling back to X1a = uninstalling everything and then installing again, or is there a way to back out the X1b update?

if you had a bacup pre update you could do that, but I had to do an un-install of X1 (it deletes A,B, and quickfixes  and go back and re-install from the original DVDs then aapply the updates one a ta time testing along the way.

HOWEVER!!!!!! try the buffer sizes first.

Does your audio quit ? dropout light? can you re-enable the audio engine?

I get the window popping up which says "Unable to open audio playback device. Device may not support the current project's audio format or may be in use." I don't see a dropout light, and the only way I seem to be able to re-enable the engine is to go into Prefs, changes something in the audio driver settings e.g. 64-bit engine, and save the change.

THAT is EXACTLY what I had to do until I rolled back to X1A, my sample rates were locked in and I didnt change them . I could not click on the audio engine to re-enable
I am still at X1A until there is a fix