• 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!

Sample Rate Mismatch - PSO unable to adjust sound card

D

DrLloyd

New member
I have a new problem that has popped up recently. It may or may not be due to the recent PSO update.
Now, when I open a project with a 96kHz sample rate, I get an error message that the sample rate doesn't match my sound card settings (card is set to 44.1kHz, etc.).
This never happened before until recently.
Shouldn't PSO adjust the sound card settings for each project automatically?
Anyone know why this is happening?
Thanks!
 
Windows? MacOS? Which SO version? Which audio interface?

Adding specs to your sig will make sure the details are always there. See the link in my sig
 
DrLloyd said:
Anyone know why this is happening?
Thanks!
Click to expand...
Hard to say without knowing any details. There should be a notice asking you to put your specs in your signature when posting in the Community Support forum. Don’t ignore it if you want help ;-)

BTW, PSO is typically used as the abbreviation for PreSonus Symphonic Orchestra.
 
I don’t see any specs in anyone’s signature? Not everyone is using a computer to view this website. Signatures don’t seem to show on cell phones.
On a PC we are told that best practices is to set everything to the same sample rate. Windows sound settings, audio interface and the default setting for projects in your daw.
If you do video editing then 48 is the standard to use. I can see that trying to use 96 might result in your system having problems. It probably why not many people use it.
 
Regarding sample rates I have 3 remarks to add to James's post:
  1. The advantage of 48kHz (or 96kHz) for video is to have exactly the same number of audio samples for each frame, which helps the editing process.
  2. A part of latency is sample rate related. A higher sample rate results in a somewhat lower latency.
  3. That infamous xiph video isn't telling the whole truth. As Monty states he chose his examples "carefully", to make his point. Nyquist assumes perfect sample value precision. Lower bit depth means less precision means poorer reconstruction. Steady sinewaves (Monty's demonstration) are nicely repetitive and it's that repetition (oversampling if you like) which sneakily improves the precision needed for a good reconstruction. But real audio can be wildly irregular, lacking that repetition. Which makes for sketchy reconstruction from low bit depth samples.
 
Last edited:
Surf.Whammy said:
It doesn't help that Studio One uses "resolution" instead of "bit-depth"; but that's the way it works with terminology. As I read and understand, "process resolution" is the way Studio One handles audio internally as a software engineering activity; and "export resolution" is similar but is not such confusing terminology, since it's the way you specify how you want exported audio to be done. Additionally, the software engineering perspective and terminology is that "Single 32-bit" and "Double 64-bit" refer "Single-Precision Floating Point" and "Double-Precision Floating Point" arithmetic, respectively.
Click to expand...
Yeah, floating point can be a bit confusing. With 32 bits you could have 32-bit fixed point precision, where (single precision) 32-bit FP uses those same 32 bits for 'only' 24-bit precision but with an 8-bit exponent for way more dynamic range than the fixed point option. The advantage of FP is that you get that 24-bit precision at every practical signal level, where with fixed point effective precision gets less with weaker signals (using fewer bits). So bit depth and precision can be different things I guess, depending on definitions.

Edit: Corrected 11-bit to 8-bit
 
Last edited:
SwitchBack said:
Yeah, floating point can be a bit confusing. With 32 bits you could have 32-bit fixed point precision, where (single precision) 32-bit FP uses those same 32 bits for 'only' 24-bit precision but with an (11-bit) exponent for way more dynamic range than the fixed point option. The advantage of FP is that you get that 24-bit precision at every practical signal level, where with fixed point effective precision gets less with weaker signals (using fewer bits). So bit depth and precision can be different things I guess, depending on definitions.
Click to expand...
Studio One uses 32-bit floating point arithmetic internally but can be configured to use 64-bit floating point arithmetic internally.

It's the IEEE 754 standard, now called "binary32", but it also can be the "binary64", which maps to double-precision floating point rather than single-precision floating point.

It's unlikely that Studio One modifies floating point arithmetic, because that's done at the processor level and would not be easy to change.
 
Last edited:
We've gotten away from the topic. Perhaps the Lounge would be a better place for lengthy discussions about various standards and implementations. Don't get me wrong - these discussions are sometimes interesting, but they are providing no information the OP can use to solve the issue this post was created for.

Thanks
 
BobF said:
We've gotten away from the topic. Perhaps the Lounge would be a better place for lengthy discussions about various standards and implementations. Don't get me wrong - these discussions are sometimes interesting, but they are providing no information the OP can use to solve the issue this post was created for.

Thanks
Click to expand...
The problem the OP experienced is caused by the sample rates being inconsistent (in other words, not being the same).

Studio One is flexible for specifying the desired sample rate; and PSO keys off the sample rate specified in Studio One.

The OP just needs to set the sample rate consistently for Studio One, sound card, VSTI virtual instrument engines (if any); and perhaps Windows, although I do everything on the Mac and cannot verify how anything on a Windows machine works.

If there is an external digital audio and MIDI interface, then it probably has a way to set its sample rate; and if so, then all of them should match (operating system, Studio One, VSTi virtual instrument engines like Kontakt, and if present a separate sound card or an external digital audio and MIDI interface like the MOTU 828mk3 Hybrid or PreSonus Quantum 2626 and Quantum HD 8 USB-C Audio Interface).

To be precise, the OP should select a sample rate and then use it for each relevant software and hardware component (Studio One, sound card, and so forth).

Since the OP indicated the sound card is set top 44.1-kHz, one solution is to set Studio One to 44.1-kHz, and if applicable to Windows and any VSTi virtual instrument engines like Kontakt. Set all of them top 44.1-kHz or if 96-kHz is preferred, then set all of them to 96-kHz.

The sample rates need to match.

If you like, I can delete my posts about sample rates and move it to the Lounge. :)
 
Last edited:
Surf.Whammy said:
The problem the OP has is caused by the sample rates being inconsistent (in other words, not being the same).

Studio One is flexible for specifying the desired sample rate; and PSO keys off the sample rate specified in Studio One.

The OP just needs to set the sample rate consistently for Studio One, sound card, VSTI virtual instrument engines (if any); and perhaps Windows, although I do everything on the Mac and cannot verify how anything on a Windows machine works.

If there is an external digital audio and MIDI interface, then it probably has a way to set its sample rate; and if so, then all of them should match (operating system, Studio One, VSTi virtual instrument engines like Kontakt, and if present a separate sound card or an external digital audio and MIDI interface like the MOTU 828mk3 Hybrid or PreSonus Quantum 2626 and Quantum HD 8 USB-C Audio Interface).

To be precise, the OP should select a sample rate and then use it for each relevant software and hardware component (Studio One, sound card, and so forth).

Since the OP indicated the sound card is set top 44.1-kHz, one solution is to set Studio One to 44.1-kHz, and if applicable to Windows and any VSTi virtual instrument engines like Kontakt. Set all of them top 44.1-kHz or if 96-kHz is preferred, then set all of them to 96-kHz.

The sample rates need to match.

If you like, I can delete my posts about sample rates and move it to the Lounge. :)
Click to expand...

Yes, matching rates across devices and apps is essential.

I'll see if I can move your sample rate thesis and related posts to a new thread in the Lounge ... though not immediately.
Thank you for understanding.
 
I moved the sample rate thesis posts to the Lounge--via copy, paste, and delete . . . . :):)
 
Last edited:
You must log in or register to reply here.
Back
Top