OP
OP
darren
Member
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 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).