R/E/P Community
R/E/P => Mastering Dynamics => Topic started by: jdg on April 18, 2011, 05:07:06 PM
-
how are you guys naming your "master" files.
esp those doing alot of digital delivery.
i used to go: track_number-song_name-version
these days im more inclined to use the file name as i got it from the client with a -version after it.
-
For listening copy's / approvals i usually go tracknumber_clientsfilename_mystudioname, any revisions gets the date added to that.
-
filename_studioname for me
-
how are you guys naming your "master" files.
esp those doing alot of digital delivery.
i used to go: track_number-song_name-version
these days im more inclined to use the file name as i got it from the client with a -version after it.
I use the file name as given by the client (or a shortened version) with _PBM to mean the mastered version. As I sometimes (actually, often) limit again after the first pass I'll put the gain added as a further element e.g. Bethel Blues PBM+1
Everything else is in my notes.
Cheers,
Eric
-
im thinking if i was the client, i would like to line everything back up like i had, and having the same file name could make that easier... but i may be vitamin D deficient at this point, and not thinking straight....
-
project name_file type_date_track number
i.e.
booty_fresh_revised_master_041811_01
or sometimes I include the resolution or side info as well when multiple formats or vinyl pre-masters have been requested:
i.e.
booty_fresh_lp_master_24-96_041811_A
When bouncing a cue sheet layout to disc SAWStudio just appends the track number to the end of the name for each of the wav files it renders out, so for the most part I don't have to think about the track numbering.
Best regards,
Steve Berson
-
Interesting seeing all the ways guys address this...
I create reference files in sequence, using initials for tracks titles, followed by format, so for a standard 16/44.1 reference of a track called 'Rock Song', I'd create:
01_RS_16441
Revisions get a v2, v3, etc added to look like:
01_RS_v2_16441
-
these days im more inclined to use the file name as i got it from the client with a -version after it.
That's what I do. Song name as provided by the client.
I'll include the song number if the client has it in the name originally.
If there is a revision, I'll put the revision number after the name.
If I do a couple versions of the same song,
I'll put a general code like Bv, H^, Mv, or L^
Where B is bass H is highs M is Mids and L is Level..and I'll add 24 if it's 24 bit
-
That's what I'll do. Song name as provided by the client.
I'll include the song number if the client has it in the name originally.
If there is a revision, I'll put the revision number after the name.
If I do a couple versions of the same song,
I'll put a general code like Bv, H^, Mv, or L^
Where B is bass H is highs M is Mids and L is Level..and I'll add 24 if it's 24 bit
What happens when you get Sibilant Highs with Impacting Transients?
-
What happens when you get Sibilant Highs with Impacting Transients?
Time to see the dentist. Ouch.
-
What happens when you get Sibilant Highs with Impacting Transients?
There's nothing worse than when it's
Flat & Ultra Conservative @15 Khz...ed
-
awesome
Boosted Obvious Outake Bass is sometimes an issue as well
-
Brighter Added Lows Limited Significantly.
Seriously though, I've also done song title followed by version (vX).
-
Original Song Title: "Bob's Song"
Processed and Captured File: "Bob's Song v1" (processed 24 bit file at native rate, not limited)
Delivered File: "Bob's Song v1 44k16L" (final mastered track, typically 44k1/16 limited)
GR
-
Similar here:
01_Django's Moustache_EQ2_Vinyl
I don't mess with the date or the sampling rate in the title unless needed.
If required I'll abbreviate the title to:
01_Django's_EQ2_V
Especially to fit soundBlade's character limit ;-)
I found using song title initials was too vague, for me.
JT
-
recorded premasters get named rec_01_title, revisions become 01a etc. if all is approved the master files get the prefix mst_01_client_title. maybe not the most readable system, but there's no room for mistakes which is more important imho, especially when doing post/sd/rerecording jobs.
-
what interesting responses :D
my naming convention is to start with a sequential number, then a space, then the official name of the track as it should appear in the CD-Text. when new versions are generated the old file is renamed to V1 (or V2, etc. . .) and the newest file has no postfix.
-
I just do "song name_mv1". The mv1 stands for "mastered version 1". If I get a revision the next version will be "mv2". Simple and it works for me.
-
Project files I tend to name:
Client Name - Artist Name - [Track Number] - Track/Album Name
and
Client Name - Artist Name - [Track Number] - Track/Album Name - Limiting
Digital Delivery Files I name:
Artist Name - [Track Number only if known] - Track Name - Subsy Master [revision version if not the first]
[info in square brackets optional and only used when known]
-
01.SongTitle.MV#.110419
(Track #.SongTitle.MasteredVersion#.YearMonthDay)
-
Mine go:
TrackNumber_RevNumberIfNeeded_SongTitle_Format
ie: 01_RockSong_16441.wav
I like adding the format-suffix in case there's a higher rate/wordlength version saved for any reason, or to distinguish between multiple MP3 bitrate versions at a glance, (if they're in the parts order/file-pile) ... and I avoid spaces and punctuation in the title to make them more URL friendly.
Also, if there's any kind of comparison/shootout going on, I'll add my name or studio name and of course, zip the file along with 2 other, brutal/horrible-sounding versions of the song, each with one of you-guys' names subtly added to the filename.
ie: unzips to deposit the following in the client's comparison pile:
RockSong_Sonopod_16441.wav
Docksong_Blackwood_really_did_this.wav
rock_song_McCaigs_best_possible_work_really.wav
If the client seems exceptionally difficult I put Tom Bethel's name on 3 copies of the 'good' one.
good times, good times.
-DG
-
you are on fire in this thread.
i'm a simpleton, long file names and underscores make my eyes cross, so it's just "Rocksong Master" here. if a revision is needed i creatively add "v2".
-
I usually record from the outboard at 32 float, so I label those captures with the full track title, followed by 32.
I'll keep em that way for assembly, fades, PQ, etc.
Any separate files that I dither to 16, I'll just label with just the track title.
Any revisions, I'll just put V2 afterwards
-
Depends, if it's a few tracks so long as the track has a name I just add the word "master" and the SR. If it's a compilation it gets T1,T2,T3 this stuff should not really need to be asked about. It's pretty embarrassing to even see a post about it. Nothing gets easier. :-\
-
Song Number (if given) and Song Title
Then:
HM (Hermetech Master - means it has passed through the DAC-outboard-ADC loop)
E (means it has been limited with Elephant)
And then either:
CD (has been dithered down to 16 bit)
or
24 (24 bit)
So when a project is finished the file name ends up something like:
01TheTroubleWithTribblesHMECD.wav
I don't like underscores, so never use them. If the project is not at 44.1kHz, I'll sometimes add that to the file name too.
-
It's pretty embarrassing to even see a post about it. Nothing gets easier. :-\
http://www.gearslutz.com/board/mastering-forum/ (http://www.gearslutz.com/board/mastering-forum/)
-
Barry, you find people's curiosity over how others do thing embarrassing?
If so, maybe internet forums aren't 'your thing'...
-
I have to admit I find it interesting seeing how other ME's label their audio.
-
I have to admit I find it interesting seeing how other ME's label their audio.
Same here. This information is certainly more useful for me than "are EQ's made of Play-Doh better than EQ's made of space age wonder material". I may even incorporate some of these ideas into my less than stellar file naming conventions.
-
I may have the most boring system of all... I just let the Sadie's auto-take do it's thing.
So "Song One" original file becomes "Song One [01]" once mastered. A second revision or remix is "Song One [02]".
Seems to work for me. If I really get stuck on what version is what I can check the folder from Windoze to check the file date and/or edit time.
-
Depends, if it's a few tracks so long as the track has a name I just add the word "master" and the SR. If it's a compilation it gets T1,T2,T3 this stuff should not really need to be asked about. It's pretty embarrassing to even see a post about it. Nothing gets easier. :-\
i need help in the bathroom, whats your number
-
rock_song_McCaigs_best_possible_work_really.wav
i really lol'd
-
Almost exactly like JT
01_MotherInLaw_v3.wav
The _ are from old coding days.
The single . in the name is because there are people who use PCs and more than one dot can cause sadness.
-
Mine go:
TrackNumber_RevNumberIfNeeded_SongTitle_Format
ie: 01_RockSong_16441.wav
Similar to Dave. I leave the "1" off 441, join the artist name and song title with a "-" for compilations, and if there's a revision I throw an additional underscore and "rev1" at the end.
I guess if there were lots of "revs" in the song title I might change the revision model.
ie: 01_RevRun-RevTheEngineForRevolution_1644_r1
-
Seriously if labelling files has become of great interest I will focus on audio quality while you focus on file names, lol.
I have to be honest I could not think of anything I would want to know less about.
I love audio forums, but I do apologize if not getting off on other engineers file naming protocol is the exception round here.
The mind literally boggles.
-
And yet you continue to post about it...
If your only purpose for posting is to be critical of what other people wish to discuss, take your thoughts elsewhere.
-
01_RevRun-RevTheEngineForRevolution_1644_r1
*spinning* :)
-
I like seeing how all the oldschool kids use the underscore. (or at least heavy FTP users).
Ditto here :: makes a big difference when encoding the file name into a URL. (%20)
SongTitle_TCB_Master_YearMonthDay
unless I'm exporting out a whole album, then track numbers 01_... go first. (I also include gaps in the exports) so file-start is from track ID start -> start of next ID.
edits, changes, and version get's added if needed before date.
-
Seriously if labelling files has become of great interest I will focus on audio quality while you focus on file names, lol.
I can do both at once! The mind boggles at the complexity of this task. Only a select few could manage to both master a record and keep the files organized. I am happy to pronounce that I am one of the select few who can do this.
-
I apparently do things a bit differently....
Mastered songs will have the full name with (24mastered) added as I always capture at 24 bit.
"Bad Ass Song(24mastered)". I keep seperate folders for original mixes & mastered files within the project folder. When I need to send a ref I'll dither/limit to16 bit & rename "Bad Ass Song(16mastered)"
If their are revisions I'll re name "Bad Ass Song-REV(24mastered)" Final digital delivery are WAV & MP3's in seperate folders with full name only.
Ed
-
I've become a little lazy. I used to separate_everything_with_these_thingys, but these days, I usually type the CD text ready for the first time and let Samplitude to the prefix number automatically when exporting separate WAV's. If it's a revision, I add a "_v2" at the end, if it's a new mix it's "_newmix_v2".
Come to think of it, if I type the direct file names myself, I still use_these.
What I shouldn't do is to use ä's ad ö's in the file names. Sometimes I've received AIFF's that display ä's and ö's normally in Windows, but Samplitude craps out. Renaming the files works.
So it's all "01 Jätkän humppa_newmix_ lessvuvuzela_v2" for me.
-
I've become a little lazy. I used to separate_everything_with_these_thingys, but these days, I usually type the CD text ready for the first time and let Samplitude to the prefix number automatically when exporting separate WAV's. If it's a revision, I add a "_v2" at the end, if it's a new mix it's "_newmix_v2".
I do the same- name the tracks before they are recorded into Sequoia (or use CD-text), and then let Sequoia do the labelling on the exported files.
-
Over the years I've changed it up but currently, and because of a few mishaps with clients confusing files, I now rely on;
Tests:
01. Song Name - Test.wav
01. Song Name - Test B.wav
Masters:
01. Song Name - Master.wav
01. Song Name - Master B.wav
As for the various bit/sample rates of these files, I keep sub-folders within the "Masters" folder of that project such as:
4824
4416
I'm not sure why having Master in the file name makes me feel better. Maybe it's from back when I used to buy DAT's and put the "master" sticker on it to be sure it was the final version.
(p.s. sorry for digging up an old thread. I was out of town for a bit and just discovered this wonderful forum on my return.)