Split Stereo Files
-
Whilst trying out the reported bug from this post I realised that the way AF splits stereo files is quite counter intuitive:
AF splits interleaved files from "filename.wav" into "filename 00001.wav" and "filename00002.wav". These files are not generally recognised as split stereo files (by anything other than maybe AF itself).
Snapper on the other hand just splits the files from "filename.wav" into "filename.L" and "filename.R" - the same way Pro Tools does. I would prefer if AF did it the same way.
The same is true for combining split stereo files to interleaved files - the combined file created from "FILENAME.L.wav" & "FILENAME.R.wav" is "FILENAME.L 0001.wav"
It would be a lot easier to just call it "FILENAME.wav" Again, this is the way Pro Tools works (and Snapper follows).
I agree with the poster in the the thread above that it would be beneficial if AF recognised split stereo files from the fact that they are called the same with a .L and .R respectively. -
"funkymothers" said:Whilst trying out the reported bug from this post I realised that the way AF splits stereo files is quite counter intuitive:
AF splits interleaved files from "filename.wav" into "filename 00001.wav" and "filename00002.wav". These files are not generally recognised as split stereo files (by anything other than maybe AF itself).
The same is true for combining split stereo files to interleaved files - the combined file created from "FILENAME.L.wav" & "FILENAME.R.wav" is "FILENAME.L 0001.wav"
It would be a lot easier to just call it "FILENAME.wav" Again, this is the way Pro Tools works (and Snapper follows).
I agree with the poster in the the thread above that it would be beneficial if AF recognised split stereo files from the fact that they are called the same with a .L and .R respectively. -
Here is the naming convention AudioFinder use ONLY when using "Stereo Split to Dual Mono" (using the Spot feature produces ProTools friendly file names)
If there are no other files with the same name in the directory already exists it looks like this:
myFile.AIFF = myFile-L.AIFF and myFile-R.AIFF
if there's already something with the same name in the destination folder, it will create a unique name as to not overwrite the file that is already there.
myFile.AIFF = myFile-L 0001.AIFF and myFile-R 0002.AIFF
AudioFinder always makes sure to never destroy existing files.
For example it is possible to have a scenario like this in the folder.
snare.AIFF
snare-L.AIFF
snare-R.AIFF
AudioFinder doesn't assume the -L and -R are the same as snare.AIFF. There's actually no way to programmatically know so it does the safest thing possible and create a new file.
Why not just follow ProTools and always use .L and .R. Because ProTools is wrong. Users let Avid get a way with a lot of non-standard behaviors. On OS 9, files had a thing called type/creator codes that were part of the file system, this means you alway new what format a file was without needing to know in the filename. That was lost in the year 2000 when Unix became the base of the OS. ProTools thinks this is 1999.
Why is ProTools not keeping pace with the times bad? For example imagine Filename.R. what file format is that? WAV, Aiff, sd2, or perhaps not even an audio file, could be a word processing file? You cannot know what it is without using deeper inspecting tools. -
"icedaudio" said:
myFile.AIFF = myFile-L 0001.AIFF and myFile-R 0002.AIFF
In my limited tests, it seems that ProTools will recognize the -L and -R extensions in addition to the .L and .R extensions. Why not append that extension at the end of the file name so pro tools can recognize it rather than before the unique identifier?
Also why name the -L and -R file numbers differently? If you are splitting one stereo file, wouldn't it make sense to have the unique id number be the same for both sides of the file, and the only difference in the file name be the -L/-R ? I.E.:
myFile.AIFF = myFile_0001-L.AIFF and myFile_0001-R.AIFF
This way I know that the -L and -R both came from the same file, but still have unique file names."icedaudio" said:
Why not just follow ProTools and always use .L and .R. Because ProTools is wrong. Users let Avid get a way with a lot of non-standard behaviors. On OS 9, files had a thing called type/creator codes that were part of the file system, this means you alway new what format a file was without needing to know in the filename. That was lost in the year 2000 when Unix became the base of the OS. ProTools thinks this is 1999.
Why is ProTools not keeping pace with the times bad? For example imagine Filename.R. what file format is that? WAV, Aiff, sd2, or perhaps not even an audio file, could be a word processing file? You cannot know what it is without using deeper inspecting tools.
I don't know about the type/creator codes you mention, but when PT splits a file into a dual mono, it doesn't remove the extension as you are suggesting. I.E.
Filename.wav will become Filename.L.wav and Filename.R.wav
The .L and .R are appended onto the end of the file name before the file extension, but do not replace or remove the file extension.
Are you talking about having a different way of knowing what type of file it is beside using the file extension (.wav .aiff etc...) ?
I think I don't understand what Pro Tools is doing that is wrong, could you please elaborate on that?
Thanks
K -
Thank you so much!
I can't believe how quick you are with user requests!
Incredible!
-
This is incredibly quick, and you guys are extremely responsive to user feedback!
That equates to phenomenal customer service in the software realm.
Thank You!
K -
Hello Icedaudio, I am trying to batch convert multiple split stereo files to interleaved stereo. They all have the naming convention discussed above - i.e. "filename.L.wav, filename.R.wav" etc.
Joining the files works as long as I select two files to be joined. Would it be possible to add batch-type functionality where you can select all files and AF will join those files that have identical filenames and types but have a .L and .R in their filename respectively?
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!