R/E/P Community

Please login or register.

Login with username, password and session length
Advanced search  

Pages: 1 2 [3]  All   Go Down

Author Topic: file naming conventions  (Read 10725 times)

jdg

  • Full Member
  • ***
  • Offline Offline
  • Posts: 119
Re: file naming conventions
« Reply #30 on: April 20, 2011, 09:32:33 pm »

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
Logged
John McCaig
-the caption captain

jdg

  • Full Member
  • ***
  • Offline Offline
  • Posts: 119
Re: file naming conventions
« Reply #31 on: April 20, 2011, 09:33:22 pm »

rock_song_McCaigs_best_possible_work_really.wav

i really lol'd
Logged
John McCaig
-the caption captain

Treelady

  • Newbie
  • *
  • Offline Offline
  • Posts: 48
Re: file naming conventions
« Reply #32 on: April 20, 2011, 10:09:29 pm »

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.
Logged
______________________________________________
Garrett Haines
Chief Mastering Engineer, Treelady Studios, Pittsburgh, PA
Senior Contributor, Tape Op Magazine

adamgonsa

  • Newbie
  • *
  • Offline Offline
  • Posts: 36
Re: file naming conventions
« Reply #33 on: April 21, 2011, 02:30:17 pm »

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
Logged
Adam Gonsalves
Telegraph Mastering

SafeandSoundMastering

  • Full Member
  • ***
  • Offline Offline
  • Posts: 222
  • Real Full Name: Barry Gardner
  • My analogue rack
Re: file naming conventions
« Reply #34 on: April 21, 2011, 03:19:41 pm »

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.



Logged
Barry Gardner
SafeandSound Mastering UK based online mastering studio.

bblackwood

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 254
Re: file naming conventions
« Reply #35 on: April 21, 2011, 03:55:59 pm »

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.
Logged
Brad Blackwood
euphonic masters

Mastertone

  • Newbie
  • *
  • Offline Offline
  • Posts: 38
Re: file naming conventions
« Reply #36 on: April 21, 2011, 03:57:35 pm »

01_RevRun-RevTheEngineForRevolution_1644_r1

*spinning*  :)
Logged
Jonas Ekstrom
Mastertone Mastering
www.mastertone.se

Tim Boyce

  • Newbie
  • *
  • Offline Offline
  • Posts: 38
Re: file naming conventions
« Reply #37 on: April 21, 2011, 05:40:33 pm »

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.

Gold

  • Jr. Member
  • **
  • Offline Offline
  • Posts: 85
Re: file naming conventions
« Reply #38 on: April 21, 2011, 05:50:42 pm »

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.
Logged
Paul Gold
Salt Mastering

Ed Littman

  • Jr. Member
  • **
  • Offline Offline
  • Posts: 50
  • Real Full Name: Ed Littman
Re: file naming conventions
« Reply #39 on: April 22, 2011, 09:11:40 am »

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

Viitalahde

  • Jr. Member
  • **
  • Offline Offline
  • Posts: 99
  • Real Full Name: Jaakko Viitalähde
Re: file naming conventions
« Reply #40 on: April 22, 2011, 03:25:19 pm »

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.
Logged
Jaakko Viitalähde
Virtalähde Mastering, Kuhmoinen/Finland
http://www.virtalahde.com
http://www.facebook.com/VirtalahdeMastering

Ben F

  • Newbie
  • *
  • Offline Offline
  • Posts: 18
  • Real Full Name: Ben Feggans
Re: file naming conventions
« Reply #41 on: April 24, 2011, 06:36:36 pm »

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.
Logged

Twerk

  • Full Member
  • ***
  • Offline Offline
  • Posts: 143
  • Real Full Name: Shawn Hatfield
Re: file naming conventions
« Reply #42 on: May 20, 2011, 03:30:42 am »

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.)
Logged
Pages: 1 2 [3]  All   Go Up