10-16-2013, 05:29 PM
Here's the workflow at our (non-profit) venue:
o 24 tracks (or sometimes 26 or 28 with kluges) are recorded as .wav 48k 24bits
(these are raw files, no song markers, etc. and may be recorded using one or more of several different applications, OS's and the like)
o Talent is eager (or at least willing) to buy multitrack at nominal cost
o Talent doesn't bring a USB thumbdrive that's big enough (or that uses a compatible file system)
o Me: "No problem, I'll trim the heads and tails then convert the files to flac"
o Talent: "How long will that take? The bus leaves in 30 minutes"
o Me: "Longer than that, but I can send you the files"
o Talent: "Let me think about it, I'll get back to you"
You can probably guess how that works out. Long delays may have a place in music, but not that long. And not that kind of delay.
So what I would like is a DAW that works much faster for a limited set of tasks.
First, my dream app would sample each original track at .5 to 5 second intervals (user choice) and show what is happening in the waveform display. This behavior would continue until I tell it to stop displaying or until it reaches the end. If it reaches the end without being stopped, then it would begin again with finer grained behavior, etc.
Second, my dream app would let me simply set two edit points without moving any of the tracks. One to (roughly) define the beginning, and one to (roughly) define the end. These would be labelled: Start and End. The screen real-estate between Start and End would be selected. (The youtube tutorials for doing this would not include any other task. No comping. No effects. No nothin' except how to trim heads and tails. Nada. Zip.) Empty tracks could be designated with the Mute button.
Third, my dream app would let me export selected, non-muted tracks to one or more locations as FLAC files using the default criteria of my choice.
Naming conventions would be handled by one question (at most) and dire warnings of data loss would be avoided because the original tracks are only being read, not written to. And no music would need to be heard. I'm just trying to get rid of large white spaces.
How close is Mixbus to being able to emulate that kind of behavior? And if not Mixbus, then what else?
best,
john
o 24 tracks (or sometimes 26 or 28 with kluges) are recorded as .wav 48k 24bits
(these are raw files, no song markers, etc. and may be recorded using one or more of several different applications, OS's and the like)
o Talent is eager (or at least willing) to buy multitrack at nominal cost
o Talent doesn't bring a USB thumbdrive that's big enough (or that uses a compatible file system)
o Me: "No problem, I'll trim the heads and tails then convert the files to flac"
o Talent: "How long will that take? The bus leaves in 30 minutes"
o Me: "Longer than that, but I can send you the files"
o Talent: "Let me think about it, I'll get back to you"
You can probably guess how that works out. Long delays may have a place in music, but not that long. And not that kind of delay.
So what I would like is a DAW that works much faster for a limited set of tasks.
First, my dream app would sample each original track at .5 to 5 second intervals (user choice) and show what is happening in the waveform display. This behavior would continue until I tell it to stop displaying or until it reaches the end. If it reaches the end without being stopped, then it would begin again with finer grained behavior, etc.
Second, my dream app would let me simply set two edit points without moving any of the tracks. One to (roughly) define the beginning, and one to (roughly) define the end. These would be labelled: Start and End. The screen real-estate between Start and End would be selected. (The youtube tutorials for doing this would not include any other task. No comping. No effects. No nothin' except how to trim heads and tails. Nada. Zip.) Empty tracks could be designated with the Mute button.
Third, my dream app would let me export selected, non-muted tracks to one or more locations as FLAC files using the default criteria of my choice.
Naming conventions would be handled by one question (at most) and dire warnings of data loss would be avoided because the original tracks are only being read, not written to. And no music would need to be heard. I'm just trying to get rid of large white spaces.
How close is Mixbus to being able to emulate that kind of behavior? And if not Mixbus, then what else?
best,
john