Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
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!
sorry, did not read properly.
you are right, when there is no buss, timestretching, or tuning involved, the "mixdown selection" of one audio track should null indeed.
Checked it in FSP8, and the Mixdown Selection result nulls perfectly with the original. Even a meter that goes down to -300dBFS shows -infinity.
This has been driving me mad and it's taken me a few days to track down the issue but I have finally got to the bottom of it and there seems to be a bug in v6.6. I was going to contact support and tell them but they won't care if it's been fixed in a later version so I wonder if somebody can try this (it won't take long) to see if the issue persists in later version.
The reason that the render isn't quite right is that under certain (very normal) circumstances (see below) any render is 1 sample out. And while that may not seem to be an issue then anybody who's spent time trying to get tracks to be in phase (e.g. multi-mic stuff) then 1 sample can make quite a difference. If your mixdowns don't quite sound like you expected then this could possibly be the reason why.
I'm still trying to pin down the circumstances where it happens but the easiest one to replicate is quite simple
1. Drag a wave file onto a blank project
2. Cut out a section in the middle (don't move anything, just cut it by selecting a range and double clicking the track)
3. Do a "mixdown selection" on the section you've cut out and tick import so it brings it back into the song on the next track.
4. Unmute the original track and flip phase on one of them.
5. See if they null (mine don't)
Now there are lots of other circumstances which cause this issue but I don't have a definitive list and, in some ways, it doesn't matter. What I really want to know is whether this is fixed in later versions because, if not, I'll report it as a bug to Presonus Fender.
Unhelpfully, this doesn't always cause the issue (I have no idea why) so if it does null then you may want to close that open up a new song and test again. It only takes a couple of minutes.
Tried your Test, plus all the other Bounce and Mixdown Options available in FSP8, but did not get any offset with one single audio track/event.
Also there is no pop up window (anymore?), where I could tick "import" with the "mixdown selection" method. It does it by default.
In FSP8 "Import to Track" Ticks only exist in Export Mixdown or Export Stems as far as I know.
That is not to say that FSP8 has fixed something.. there might be other factors to be discovered.
Maybe something stupid like "Ignore Audio Device Timestamps" or "Sync To external Devices" somehow screws with render timing. Maybe it's the old "depends on where you start playback/render issue" or the "delayed get-back-in-sync loop playback issue" where stuff is out of sync a few seconds after a loop return that then gets shifted back in sync with a sometimes noticable click...
I'm saying all that to keep you from getting angry at me, if you update to v8 and the issue is still present for you.
Thanks for testing @FMN-Music, that's really helpful. Just to confirm, you did cut out a section in the middle of the track and just did the mixdown selection on that piece?
(Sorry, I was doing so many tests that I got myself confused, mixdown selection doesn't have any options)
Don't worry about "misleading" me as I'm going to wait for the demo for v8 and I'll test it on that before updating but I have to confess I am really concerned about what this means for my mixes. There are too many variables to know exactly what impact this would have but just knowing the mixdowns may not be rendered accurately is a concern because even one sample makes a difference..
