If not totally clear, just save duplicates so you're not writing over anything. So, if you are confident that the content of your stereo files is identical in each channel then you could just save them back through Edison, switching them to mono files there. Unfortunately (and bizarrely) FL Studio doesn't give any option to export mono audio files. If you are exporting single channels as stereo files then you are also wasting hard drive space. For a stereo effect such as reverb the same treatment would be required where you would need to export as two separate audio files for working with in a hardware mixer. So, for example, if you have stereo overheads on drums, these will take up two separate mixer channels and would be represented by separate audio files to feed those channels. If your engineer is mixing using a hardware console then the inputs will indeed be mono. Equally, if you process in stereo and then sum both channels as one, then you might encounter phase issues. drop the second channel and keep the first) then you will lose vital data. If you are processing in stereo and you force to mono (i.e. If I have a mono file and send it to two channels then I can send more to one than the other if I wish to create the illusion of sound being positioned between two speakers. To be clear when we talk about stereo panning we are really talking about routing between two channels. Which one of us is right? Is there something I am not understanding when a mono file is split into stereo? as long as there is no resulting loss of audio quality from 'bouncing back' to mono (I can't make 'export song, make separate file for each stem' work, it crashes and locks up)

So I'd much rather he spend 5 minutes bouncing the tracks back to mono if he insists they need to be in that form for mixing, rather than ME spend an hour or so re-exporting the files one at a time, haha. So when a mono wav file is portrayed as a stereo file, isn't it just a L & R of two identical files? (Of course I am exporting w/ 'pan' set dead middle) And doesn't any stereo mixer 'think' of a mono file in this manner anyway? S1 guy seems to think there is possible audio loss and potential phase issues at risk from 'bouncing' stereo track to mono (a simple mouse-click in S1), whereas I'm thinking that the end result of exporting as mono, or 'bouncing' the 'mono-as-stereo' L&R FL export back to mono should be identical, there is no possibility of audio loss or phase cancellation issues in re-combining a split mono file.Īnd, if he has a stereo track that's default-middle, no panning, as exported - if he pans L or R isn't it only making one side or the other louder, the same as if it were appearing on his screen as a mono file? What is the difference? Why is it necessary, isn't any stereo mixer doing the same thing to a mono file as the one he's looking at and saying he can't use? I found that the 'Stereo Separation Control', when turned all the way right, makes the track 'mono', but it STILL exports/renders it in stereo form.

wav file, dry signal, no processing, just cutting, clipping, moving pieces around, etc., for composite mix of best takes, pieces in the right place, skeleton correct form), taking them back to Studio One guy for mixing - when FL exports a stem as stereo, my S1 guy says 'I can't use a stereo file for mixing, it has to be mono'.

I'm doing some editing of takes in FL- ( mono single.

Mixbus export with clicktrack