Hmm how are you changing the buffer size? If you are using ASIO and you change it from the ASIO control panel (opened from SONAR) then the ASIO driver sends back a notification to SONAR and we adjust to the new buffer size.
This definitely works for most interfaces including other RME devices. Not sure about the Hammerfall.
Are you using ASIO drivers? If SONAR Isn't responding to changing the buffer size it would imply that we never got a notification that the size changed.
One thing you can try is open preferences | configuration file and click "reload configuration". That should force SONAR to reload the driver without having to restart.

tlw
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.

Oops. Good pull, Tim I looked at the RME download page but didn't click the link before posting. Now I wonder why the OP would use ASIO4ALL when the manufacturer has a driver available?
 
[EDIT: I didn't mean to address my ASIO4ALL comments to the original poster.]

Thanks for the input guys.
 
I always use the latest and greatest RME drivers, always. And always ASIO (is there any other type?!?! :O) Personally, I dabbled with ASIO4ALL a few times long ago with little success. RME cards want their dedicated drivers - it's why people buy that brand.
 
In the past (older Sonar versions), it has sometimes been fine, but mostly I have to close Sonar to change buffers properly.
I click on hidden icons, bottom right of the Windows desktop, open the RME driver box, and change the buffer size. It's the fastest way to do it AFAIK.
 
Should I rather be opening the RME driver box from Sonar Prefs?
 
L.

AHA, OK - I just tried changing it from the Sonar Prefs and that works perfectly. So Sonar has to change the RME driver, not the other way around. Glad that's sorted.
 
Can we get little floating buffer toggle menu now? :o)  I'm the KING of shortcuts, ya know...

LJB
 
Should I rather be opening the RME driver box from Sonar Prefs?
 

I really think you should. I always do it from Sonar Prefs and it works fine (using Roland interfaces) ... and it did not like me fiddling with settings externally ...
 
BTW, hitting "P" to get to the Sonar preferences is much quicker than opening anything external ...

LJB
AHA, OK - I just tried changing it from the Sonar Prefs and that works perfectly. So Sonar has to change the RME driver, not the other way around. Glad that's sorted.
 
Can we get little floating buffer toggle menu now? :o)  I'm the KING of shortcuts, ya know...

You could try the new voice command thingy in win10 ;-) ... try saying something "increase that bl**dy buffer, you d*rk"

Thanks bro - I'll be sure to scream it out loud while looking up at some spot on the ceiling. Can't wait to see my clients' faces!

LJB
AHA, OK - I just tried changing it from the Sonar Prefs and that works perfectly. So Sonar has to change the RME driver, not the other way around. Glad that's sorted.
Can we get little floating buffer toggle menu now? :o)  I'm the KING of shortcuts, ya know...

Yes you should do it from SONAR since the ASIO dll is loaded by SONAR. ASIO drivers are handled by an ASIO dll and each client for the device loads its own instance of the dll. If you change it from another place probably the device fails to notify all clients. I will tell RME about it - I would assume that a driver should notify all its clients if one of them changes the global buffer size. Either that or it would need to support per client buffer sizes (which is a lot harder)