I came across a discussion about sound effects distribution on Game Audio Forum (from last year) and Gearslutz (recent). The question is… which way you like to get your sound effects: multiple takes in one file or each take separate into individual files?
The only goal with this is to help sound effects makers to know which way his customers like the most, so they can improve their formats and releases with options that can fit all kind of tastes. If you want to collaborate, feel free to visit the mentioned discussions or just pick your option here.
In my opinion, I’d say that multiple takes in one single file is faster and much better for finding sounds that were recorded with the same perspective, performance, tools, etc. Also, I’m a big fan of Soundminer’s VSTrack, so having the file with multiple takes makes easier the process of making variations of a sound. But well, each person has a different workflow, and that’s why is so important to hear what do you think about this.
Multiple takes in one file works for me as a user and a provider of sound effects.
Multiple takes per file works fine if it is the same performance, using the same prop in the same mic configuration. As soon as any of those parameters change I would prefer it in a seperate file.
Exactly the same as above. Whichever way the files are distributed, they have to be coherent to be easy to use.
I prefer my FX with multiple takes IF i’m using workspace to find sound files, which is annoying because most of my files are labeled ’SD-1332’ or something of that nature, but in Sound Miner I prefer takes to be separated into their own files just because I like to edit the meta data on certain files to my liking, but its just easier for my work flow.
Same thing, multiple takes (recorded at the same Gain) per files with a short silence between each take makes my job way easier later on, either in film or game sound.
Multiple takes with brief silence between. Makes it simpler for me to see what I’ve got instead of 30 files named the same with Take 1, 2, 3 etc. Less files = better organization.
Multiple takes on one file with proper ringout between (!!). Same room, mic, mic placement, etc. Less files = less digging around for alts, and less time consuming when using plugins. Thx
Thanks for the comments, guys! I’ll make another post in a few days, grouping some of the comments and also showing the results ;-)
It seems I’m in the minority. I can certainly see the benefits for having all takes in a single file, but for my workflow, I like having every sound effect as a separate file, with all of the silence removed. In my workflow, I like to park my cursor in Pro Tools at the exact frame I want the hit/event to happen, and spot it from Soundminer Pro, without having to do any additional editing/ trimming. If I need to process a series of sounds through the VST rack, I can select multiple files and have them all processed and laid out on a track in a couple of clicks/key strokes.
It depends the issues of the sound content, I think. For the same type of sound, multi-traks in 1 track is good. But sometime it’s not so ideal. The takes in 1 track might be very different type or purpose. In this case, some good tools like Soundminer shall be very necessary. Any way, the naming of file shall be very clear on naming format and description. For sound recordist, daily records must be clean up before sleeping and vocal makers in each track must be clear.
i prefer multiple sounds in one file, like most of the others said.
less files = more easy to navigate.
interesting question though.
maybe you should do a series of questions, so that library makers can improve there way of doing a library. and people get more what they want..
everybody will win with that. me as a library maker, and me as a library buyer:-) i will contact you via mail..
As an editor and sound effects provider as well I prefer separate takes. They’re just easier to source, listen to and drop into a session.
I see the reasoning for having one long file with multiple takes but it makes it a pain to audition all of them. And however slight the effort, I don’t like trimming the file down.
If the sound is named well, you can tell from the name that it is the same mic placement and is from the same sound effect ‘family’.
Almost all of the sounds on my website http://www.airbornesound.com are this way… my customers seem to like it this way.
Again, I’m going against the majority here by saying I believe I prefer multiple files. The main reason is my specific workflow at this point… I actually have all of my sound effects loaded up in iTunes, and can easily click and drag a track from there into my DAW, be it Sonar, Logic, ProTools, or even a video editor like Vegas. I audition them quickly in iTunes, and then take the one (or ones) I want in. With multiple takes per file, when I find just one sound out of the 4 or 5 (or more) in a file, that’s just more editing for me to do later, albeit not much.
Both versions have their positives and negatives. Rather then preferring one over the other I would love to cast a vote for uniformity. I buy just about everyone of the indie libraries (Recordist, Rabbit Ears, Hiss and Roar, Boom, Tonsturm, Russom, Hart, ect) as well as products from the majors (Sound Ideas, Blastwav ect) and what I most want is everyone doing the same thing so I can set a workflow and stick with it. I hope through these great threads everyone can come up with a consistent way to move forward. I love all the innovation happening right now with SFX, keep up the great work everyone!
As a content provider, I’m currently using a file per sound effect as my deliverable. But, if the general consensus is to have similar files grouped together, then that should change.
As a sound designer, my workflow suits working with individual files per sound effect. Just scanning through short, transient sounds is easier with them in individual files.
Cheers
Nice discussion, perhaps we can find some general language in providing sound effects. Doing sfx especially for games its common to provide multiple variations of one specific action which will be randomised through the code. I.e. medium_sword_hit_1-4.
Those should slightly differ in performance but not in character, material, perspective or intensitivty. So I like to have at least 6 variations, well named in one file which only differ in their performance. For all other deviations should be another file. Thats how we serve our meals. For me it makes no difference either to preview through the SM datatabase or skip its waveform player. (if the description is precisely)
The main issue I think with this topic is: does it scale? How you deal with a library that has 20,000 sounds in it, is quite different to that of eg 500,000… If every file in my library was split into seperate files for individual takes then the 450,000 sounds would end up being approx 10 million, which would be very difficult to manage & inefficient to use.
Libraries are a long term, constantly growing asset – they must be scaleable, because you do not want to get five or ten years down the track and realise your workflow is flawed/inefficient and must be changed….