I run an RME HDSP9652 card on Win 7x64 and when composing and final-mixing for film I am constantly changing between my composing project and my mixing project. I find in S-Plat I have to quit Sonar entirely and re-open the program in order for the buffers to clear. If I just close the project, change the buffer and then open the next project the sound is totally garbled.
 
Is that something that the Bakers can address, or do the driver manufacturers have to handle this issue?
 
Nice work on GlassCow or whatever it's called, BTW. It runs well! :O)
 
L.

Historically if I change the asio buffers on my aging Terratec EWS88D card (We're goin' down together btw)
I experience buffer issues too. When I press space, I get a short growl then a drop out.
 
No point in trying to make Cakewalk care about an interface the Terratec denies is their child so I restart and soldier on.
 

It sounds strange for me. I use Focusrite Scarlett 8i6. When I change buffer I have dropout, and I only have to start Audio Engine again and all is working fine.

Disabling audio engine, change latency, then re-enabling audio engine doesn't work?
 
I did a quick test and works ok: no dropout and strange sounds with asio4all.
 
Latency from 128 to 1024 samples, and back to 128.

Thanks for posting this LJB - it's my biggest gripe!
I have the Hammerfall AIO card. I'm a guitarist so when I'm using a plugin like S-Gear or GuitarRig I change to 64 but then if I want to mix or use Melodyne I need to switch to 1024. Surely with all the 'whizz-bangery' software techniques around these days we should be able to simply click and toggle between the two rather than pulling up Preferences, etc. I also have to exit and reload Sonar to make the changed buffers take affect, although I hadn't twigged the above re. switching off/on the audio engine and need to give it a try.
All VERY primitive in terms of workflow though. 

I guess a bit of this is on both sides of the fence. Although SONAR can handshake with interfaces, it is up to the interface to accept it (when locked) and respond appropriately. SONAR has no ability to "force" the interface to do anything it is not designed for (purge buffers, etc.). In the case of ASIO, the handshake comes from the interface, but similar, and again what is happening inside the interface is mostly its territory.
 
In my case, Focusrite recommends disengaging (i.e. closing any application using it) when adjusting buffers; but I do this quite often with SONAR open and a project loaded. SONAR's audio engine will drop out occasionally when doing so, but has been a simple "turn the audio engine back on" scenario. I think that SONAR is intercepting the "disengaging" part by doing so when required, but saves me any forced close/reopen of SONAR by doing so.

I can change buffers for my UFX without problems. Sonar just stops and re-starts the audio engine.

ChazEd
Disabling audio engine, change latency, then re-enabling audio engine doesn't work?
 
I did a quick test and works ok: no dropout and strange sounds with asio4all.
 
Latency from 128 to 1024 samples, and back to 128.

ASIO4all is a wrapper that uses the Windows driver such as WDM or even MME. It is not an ASIO driver it just looks as if it is to a host. There is no good reason to use it with Sonar.

I see there are no ASIO drivers for your card. RME does have a WDM driver download. Have you tried that? Many users have had many problems with ASIO4ALL.
 
On my M-Audio PCI card I experienced a ~30 second delay when changing buffer size with Sonar running, but after that everything was fine. On my Scarlett 6i6 there are inconsistent delays/dropouts/stutters, but it rights itself without having to close Sonar. Sometimes I manually stop and start the Sonar audio engine.
 
I think your problem might be ASIO4ALL.

Are you using the RME ASIO driver with the HDSP?

If not, the ASIO driver for HDSP cards can be downloaded from here:

http://www.rme-audio.de/e...loads/driver/hdspe.php

The page says it's a WDM driver but if you click on the link the text that comes up says there's WDM, WDM-KS and ASIO drivers in the package. It might be a good idea to do a firmware uograde if there's one available.

If you are using the RME ASIO driver it might be worth while contacting RME support about the problem. They usually seem helpful.