• Hi and welcome to the Studio One & Studio Pro User Forum!

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

Rendering in Studio One (sic)

SUMMARY

I think it's probably worth summarising this thread because it's got long and complicated and if you've not been following it post by post then it's probably quite difficult to ascertain what's been established and what is conjecture.

What is established is that under certain circumstances, when Studio One/Pro mixes down audio it moves it by 1 sample. The circumstances are when you move the start point of an event, either by moving the event, trimming it, or cutting it. If you got to post #26 then @FMN-Music has posted a video demonstrating this. This is without any re-sampling, without any plugins, it's just a feature/bug of the Studio One/Pro engine and exists (for sure) in v6-8.

The reasons for it doing this are, doubtless complex, but in essence it's because the start of the bounce/mixdown falls between two sample points and the engine can't cope with that without shifting the whole audio event to begin bang on at a sample point. I'm speculating here but it seems that the playback and mixdown engine seem to choose different sample points (one shifts it back, one shift if forward) so that's why you end up with the 1 sample difference. That explanation may be wrong but it seems to fit the facts and the facts are that there's a 1 sample difference when you mix/bounce something.

What is also established is that other DAWs (notably Cubase and Reaper) can cope with audio events which start between sample points and don't shift the audio to a sample point.

I did work out a way (in post 33) of moving/trimming/cutting audio events without causing the issue but that was slightly hit and miss. But it works most of the time.

Everything I've said above is established fact except for the speculation about why Studio One/Pro does this. But the fact it does it isn't up for debate any more.

--------------------------------------------------------------------------------------------------------------------------------------------------------------

What I've been trying to do since that point is try and work out whether it matters and that's still very much an open question. I hate the fact that my mixdowns may not be true to what I hear in my listening sessions and I don't actually know what other things are compromised by this limitation in the audio engine.

But it may not matter in the grand scheme of things.

In trying to answer this question (in my post 54 just above) I discovered that my mixdown of an actual song is not just different to what I'm hearing in the mixing session but every mixdown is different. Probably, speculating again, because plugins introduce their own randomness which means that no two mixdowns are going to be identical.

My suspicion is that it doesn't matter but I'm not ready to put this to bed without more testing (when time allows).
 
I had a thought about the established problem and wondered what those of you who have a better understanding of coding and DSP think about it?

The issue, as I've described above, is when you move the start point of an event, either by moving the event, trimming it, or cutting it and the start of the event then falls between two samples. The audio engine shifts the whole even either backwards or forward to the next sample and chooses different options depending on whether it's playing back or bouncing/mixing down.

I imagine it's a massive job to overhaul the audio engine to be able to cope (like Cubase and Reaper) but how about a simpler solution whereby Studio OnePro makes sure when you move/edit/trim that the event always starts exactly on a sample? That way there's be no shifting (except when you're moving) so the playback and bounce/mixdown would always be the same?

I know there's quite a lot of assumptions in here but that would seem to be a relatively easy and reliable solution?
 
My guess is that you'll always be chopping right at a sample, a sample being the smallest time unit in the material used in the song (from the start, or resampled at import). That would be a 1/44100th part of a second for a 44.1kHz song. So the rounding would be in the chopping position, not in the resampling after chopping between two samples.
 
My guess is that you'll always be chopping right at a sample, a sample being the smallest time unit in the material used in the song (from the start, or resampled at import). That would be a 1/44100th part of a second for a 44.1kHz song. So the rounding would be in the chopping position, not in the resampling after chopping between two samples.

But I'm asking whether it would be possible for S1 to simply shift the start of the event, trim, chop to the nearest sample? In my workaround in post 33 I'm assuming that's effectively what I've forced S1 to do ... just in a really clumsy way.
 
@FMN-Music, I see you've been testing the rendering of instrument tracks in the other thread but did you get a chance to test general audio rendering and the issue discussed in this thread?
 
yes, last post in the thread.



Song to test yourself (Don't change Samplerate or Tempo!):

How to test:
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 
Back
Top