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.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.
Well, some of your answers need more clarification: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.
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![]()
Watch the videoHi SwitchBack,
There's no option to save as an AAF file.
I did. There's no option to save as an AAF file for me.Watch the video
I believe I have v3.Which version of Studio One / Studio Pro are you using? AAF export is possible since v4.0
We use essential cookies to make this site work, and optional cookies to enhance your experience.