• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

S1 Keeps Resetting Universal Control Sample Rate

imacken

New member
I have Universal Control set to 48kHz, yet whenever I load a song in S1 that is set to 44kHz, then Universal Control resets to that value as well.
Is there a way to stop this happening?
 
No one? I guess I should open a support ticket then.
 
Studio One will want to have the interface use the same sample rate as the song. Universal Control will display the sample rate of the interface. Something has to give: Set your song to 48kHz, or keep your interface on 44.1kHz.
 
Thanks for that. So it is correct behaviour that UC will always be set to whatever the song is set to? And keep it set to that?
If that is the case, then what's the point of UC if it is commanded by S1? I would have thought it was the other way round, so that, for example, if UC was set to 48kHz and then a song at 44.1 was loaded into S1, then I would have expected UC to revert to the set 48, and not be permanently set to 44.1.
 
UC is software to control the settings inside the interface, not only the sample rate but also various other settings and the onboard DSP if any, like a remote control. It also shows you the current status of all those settings. UC also installs the driver for the interface and is used to check for and perform driver and interface firmware updates.

Studio One can also control some if not all parameters inside the interface including the sample rate, like a second remote control. If Studio One changes an interface setting then UC will show that change too.

So the truth is in the interface so to speak. When you select a PreSonus interface in Studio One then Studio One knows its driver and controls and uses those to select the sample rate that goes with the song. And at the same time you can use UC to control say the interface's onboard mixer/DSP if present.
 
Thanks again. I'm kind of surprised by that. I would have expected UC to be the controlling factor here, not S1. I can't really see the logic in a song determining what the interface is set to, outside the context of the song, of course.
 
Maybe that is your misconception: there‘s no „controlling“ factor. Both applications (UC and S1) can manage the interface. And whenever you open either one, it simply shows the actual setting of the interface.
 
For sure, it is my misconception. As I said, I can't see the logic of whatever a song is set to determining the settings on the interface for all other software. IMO, the song settings should be temporary, and the UC settings regarded as default for other software and new songs to use.
But, hey ho... what do I know???
 
As I said, I can't see the logic of whatever a song is set to determining the settings on the interface for all other software. IMO, the song settings should be temporary, and the UC settings regarded as default for other software and new songs to use.

If that was the case - users would be flooding the forums with other questions - like why does my song sound garbled? Or slowed down? Or sped up?

S1 (and it's built in sample rate traffic cop vibe) ensure your song is going to play back - and I would think that is exactly what %99.99 of users would want.

Same thing happens here with something like J.River Media Center and my RME UCX-II. One minute I am playing a 44khz/16bit FLAC file and the next I am rocking a 96khz/24 bit FLAC file within a 5 hour playlist.

The last thing I need is the RME driver jumping into the middle of this trying to enforce it's own rules when it comes to encountering different Sample Rate/Bit depths. I want my play list to play uninterrupted regardless of its track make up and I expect JRMC to tell the RME exactly what to do and when to it.

VP
 
Last edited:
I think maybe you're misunderstanding what I am saying. The song should, of course retain all its settings when it is being used so the scenario you describe would not happen, but when it is closed, the interface should revert to what UC is set to. Like a default setting. To me, it isn't logical that all following new songs/software should have to accept what any particular, previous song is set to. Song settings should surely be individual to them?
 
I think maybe you're misunderstanding what I am saying. The song should, of course retain all its settings when it is being used so the scenario you describe would not happen, but when it is closed, the interface should revert to what UC is set to. Like a default setting. To me, it isn't logical that all following new songs/software should have to accept what any particular, previous song is set to. Song settings should surely be individual to them?

My RME reverts back to what I tell it to - but that is based on the OS direction - and never the driver.

I have Windows 10 tell the RME that I expect standard 44.1/16bit operation (at a baseline) when I am not using S1 - say for watching YouTube or listening to Spotify etc.

But the RME ASIO driver - which is industry standard - has no say over what "it" might think is default. It reacts to anything it gets (regardless of the source) and switches on the fly without hesitation. But it calls no shots - so to speak.

If you want to save your sanity - pick a baseline sample rate and bit depth (ideally identical to what you use 99.99% of the time in S1, stick with it and do not spend too much time watching sample rate and bit meters. As long as the sound is coming out to your speakers and phones and sounds good (and normal) - that means the driver is rolling with the punches and doing exactly what it should - which is all that matters.

VP
 
Thanks. TBH, I have just set all my songs in S1 to 48, so that the issue doesn't arise any more. A manual exercise that took a while, but all good now.
where it becomes even more confusing is when there are 2 songs open in S1 with different sample rates. Swapping between them is fun! And then there is the whole 'do you want to save changes' prompt when the sample rates have changed because a song with a different rate has been opened thing, but... let's not go there!
 
Thanks. TBH, I have just set all my songs in S1 to 48, so that the issue doesn't arise any more. A manual exercise that took a while, but all good now.
where it becomes even more confusing is when there are 2 songs open in S1 with different sample rates. Swapping between them is fun! And then there is the whole 'do you want to save changes' prompt when the sample rates have changed because a song with a different rate has been opened thing, but... let's not go there!

Been an S1 user since 2011 and ever since then my standard baseline for everything audio related in 44.1khz/16bit. The only time I ever see the RME change it's sample rate is when I fire up a 88/24 or 96/24 FLAC download. But again - as long as I can hear it - it's good :)

VP
 
Back
Top