-
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!
Automatic Normalization Occurs Upon Exporting
- Thread starter Seamus
- Start date
More info needed:
1. when you import the files yourself, do they work as expected or do they look normalised and peaking? (normalised and peaking would be kind of a contradiction as the highest possible normalisation would be 0dBFS and that would not peak any DAW)
2. what's your export process?
3. how does your producer import the files
4. what DAW do they use?
It could be the metering of what your producer uses is different from the metering in Studio One but that should not affect the sound in any way.
BTW: make sure to gain stage your tracks/stems properly in any case.
1. when you import the files yourself, do they work as expected or do they look normalised and peaking? (normalised and peaking would be kind of a contradiction as the highest possible normalisation would be 0dBFS and that would not peak any DAW)
2. what's your export process?
3. how does your producer import the files
4. what DAW do they use?
It could be the metering of what your producer uses is different from the metering in Studio One but that should not affect the sound in any way.
BTW: make sure to gain stage your tracks/stems properly in any case.
SwitchBack
Well-known member
Also check the export format. Studio One's internal dynamic range can be much wider than your chosen export format (e.g. 32-bit floating point vs. 16-bit WAV export format), so what looks good inside Studio One may not 'fit' in the chosen export format and needs turning down first (or a different export format).
yeah, totally: if you work with 32 bit floating point you have a huge amount of dynamic values (±1,18 × 10⁻³⁸ to ±3,4 × 10³⁸) while exporting to 16 bit will shrink it down to just 65,536. So I think my comment about gain staging would help in bit-chopping scenario as well.
1. when you import the files yourself, do they work as expected or do they look normalised and peaking? (normalised and peaking would be kind of a contradiction as the highest possible normalisation would be 0dBFS and that would not peak any DAW)
So the tracks on my end do not appear to be peaking. These are the tracks that were originally recorded in my Studio One DAW.
My producer uses Luna and simply drags and drops them in. When he sees is the WAV files on the tracks are huge and the sound
is peaking.
2. what's your export process?
I just do a normal exporting of tracks.
3. how does your producer import the files
Drag and drop
4. what DAW do they use?
Luna
Also, both of us keep are sessions at 48kHz/24bits.
So the tracks on my end do not appear to be peaking. These are the tracks that were originally recorded in my Studio One DAW.
My producer uses Luna and simply drags and drops them in. When he sees is the WAV files on the tracks are huge and the sound
is peaking.
2. what's your export process?
I just do a normal exporting of tracks.
3. how does your producer import the files
Drag and drop
4. what DAW do they use?
Luna
Also, both of us keep are sessions at 48kHz/24bits.
Well, some of your answers need more clarification:
A) what is „a normal exporting of tracks” include in your case, meaning: what sample rate, what but depth, do you export tracks or channels? Is a limiter on any of those?
B) Ok, your producer drags them into Luna. But Luna needs to have some definition for what happens to files it gets presented.
SwitchBack
Well-known member
Another thought:
Luna is capable of importing AAF containers, which is a fast way of transferring complete songs (tracks, events, names, fades, ...) to another DAW.
Have a look at this video how to prepare your Studio One song for AAF export. The video does a transfer to ProTools but it's the same for any DAW capable of importing AAF containers. Word of warning: The video moves through the process at breakneck speed so be prepared to pause and rewind a lot
Luna is capable of importing AAF containers, which is a fast way of transferring complete songs (tracks, events, names, fades, ...) to another DAW.
Have a look at this video how to prepare your Studio One song for AAF export. The video does a transfer to ProTools but it's the same for any DAW capable of importing AAF containers. Word of warning: The video moves through the process at breakneck speed so be prepared to pause and rewind a lot
Hi SwitchBack,Another thought:
Luna is capable of importing AAF containers, which is a fast way of transferring complete songs (tracks, events, names, fades, ...) to another DAW.
Have a look at this video how to prepare your Studio One song for AAF export. The video does a transfer to ProTools but it's the same for any DAW capable of importing AAF containers. Word of warning: The video moves through the process at breakneck speed so be prepared to pause and rewind a lot
There's no option to save as an AAF file.
Watch the video
I did. There's no option to save as an AAF file for me.
Crossinger
Active member
Which version of Studio One / Studio Pro are you using? AAF export is possible since v4.0
I believe I have v3.
SwitchBack
Well-known member
Then I'd say it's time to upgrade.
Okay. When upgrading, how do you secure your files from the old version and transfer to the new?
SwitchBack
Well-known member
Songs created in older versions open in newer versions. The other way around there are limitations, so make copies before you make changes (you do get a warning before saving a song from an older version in a newer version).
Also note that you don't have to remove v3 to install a newer version. Multiple S1/SP versions can live side by side and they even can share resource directories.
Also note that you don't have to remove v3 to install a newer version. Multiple S1/SP versions can live side by side and they even can share resource directories.