Hi,
 
Yesterday I installed my UR44 but I noticed some strange behviour in Sonar X3.
When I set the samplerate in Sonar, let's say 192 kHz and then I open the ASIO control panel to acces the Yamaha Steinberg driver I adjust the buffersize (say 128 but any) and then look at the samplerate under the tab 'Steinberg' it reads 44.1 kHz.

I then adjust this to 192 kHz (as this is also the setting I choose in Sonar) and I click OK and close the settings panel.

Now when I open the ASIO panel again and go to the Steinberg tab it is back at 44.1 kHz and this is always the case.

Has anyone noticed this behaviour, is it normal and/or what is the correlation between setting samplerate in your DAW and in the driver settings from Steinberg?
 
PS. I don't have this behaviour in Live 9 and Steinberg support couldn't give me an answer since they didn't have a copy of Sonar X3 to replicate.

am using a similar setup.
 
if i can rem correctly, there is a minimum sample buffer for different sample rates. 
 
the unit will somehow set the buffers to match the latency times as closely as possible to the last good latency settings based on the last selected sample rate.

Hi, thanks for your reply.
I realise there is a dependecy between samplerate/buffersize but in my case whichever samplerate I select, it always jumps back to 44.1 kHz.
 
I noticed your signature mentions you use 1.0 driver. There's a 1.8.5 update: http://www.steinberg.net/...re/downloads_ur44.html

hi, just a quick question... do you have the onboard sound device enabled? i suspect that Windows may be hoarding the ASIO config.... due to the so called internal Windows sounds etc... even if you disabled that, somehow, somewhere, something may be the hog. the most effective solution is to disable the sound device from BIOS, just before the system boots into Windows.
 
yeah... thanks for noticing. i have had the original install and have never updated even though i have download the latest updates and firmware. Since day one i had the UR44, it has worked for me exceptionally well; besides, i had some issues with the included plugins.... i have never used them in work anyway. during my initial test, they acted up so i quickly gave them the boot and never looked back. honestly this unit is rock solid since initial install; i guess i wouldnt make the install unless something is not right. thanks again friend.

Hi, thanks for your suggestion. I am saving up for a DAW-only PC but for now I'm still working on my main PC so disabling the onboard device is somewhat unpractical since I'd have to make a dual-boot systeem while having no extra HDD-slots available. Also with my older soundcard (Edirol UA-25) I didn't have this issue (though granted that ASIO panel didn't have the extra samplerate select option).
 
I suppose you're right about not fixing anything that isn't broken ;)

hmm.... 
 
i'm not sure of the outcome on your end however, if you try the following and observe the UR44:
 
1. close off every other programme leaving just the Win Desktop. 
2. open the UR44 control panel and set, for eg, 96k & 192 buffers. (latency is about 10sec)
3. restart the pc and observe that after the boot up, open up the UR44 control panel. the setting should stay. - if not some this else has already grabbed the driver and locked the sample rate.
 
4. if all is well, open a programme that doesnt use ASIO. For me its Media Monkey. when playing the songs, the UR44 jumps to the sample rate of the media being played. - if so thats good. (from 96k to 44k; buffers should be higher at 44k - notice the latency is almost the same)
 
5. next, open up an audio editor - empty work area. (UR44 should still hold at 44k rate) - here's the trick, if you open up a Wave File recorded at any other sample rate, you should observe that the UR44 will jump to THAT new rate. Opening a second file of yet another different sample rate, the UR44 should follow suite.  
(a word of caution though, if you press play immediately there is about a 1sec delay before the unit kicks in the new calculations. after that all is well)
 
if all is working so far, try again in Sonar. All should be well. 
 
Good luck friend... hope you can resolve this... 

Thank you so much for your elaborate testscenario!
Have to attend to some other things now but will check this evening and do some more testing.

Life took over (always does) so had to delay my testing. Short version: I'm an idiot and the problem's solved ;)
 
Longer version: I didn't realise Sonar's samplerate setting in preferences was for new projects (unlike in Live).
So everytime I loaded an existing project it was ofcourse automatically set back to it's chosen values and when creating a new project I adjusted the samplerate and kept wondering why it jumped back in the driver settings, not realising the samplerate was already set as default.
 
Sorry for the wild goosechase. Enthusiasm and haste rarely sit well with sub par knowledge.
Anyway, thanks again!

it all worked out...
 
cheers!!!