Thanks Hard
File naming Protocols
Thanks Hard
I agree a little wiTh
I agree a little wiTh ♫Mikedred♫ but,
impose an uniform protocol will be
problematic in the future.
And yes I see the bad/disaster that
my files done in the list box :(
So for instance,
SOUND_-_SOUNDSNAP_-_HardPCM_-_Beep_-_001.wav
can be renamed to:
beep_001_snd_snap_hardpcm.wav
So I will delete my file and
re-upload them with an better naming :)
I 'll have a thought about
I 'll have a thought about it again, sorry about the delay.
Keep in mind that we have to make it easy for anyone to implement this naming protocol. We don't want to scare contributors away..
I 'm putting this on my 'to think about' list, cause I 'm mad busy today!
Thnx Mike
On the MAC I can't live
On the MAC I can't live without Renamer4Mac. It's free with the option to donate (I donated). It's one of the most pleasent interfaces for renaming huge numbers of files according to a preferred criteria. e.g inserting designer initials, leading numbering systems and character insert / overwrite / removal.
Great points Mike. I agree-
Great points Mike. I agree- and have tried to be sensible in my own naming schemes, as I am in the painful process of having to reorganize my hard drive full of samples with meaningless/irrelevant names and know how important it is.
While my naming schemes make sense, they don't quite fit to your specs. However, once a standardized naming convention is decided upon, I am happy to rename all of my contributions to follow [Tasos- you said you can't edit the names, is that just admins or even the authors themselves?], even re-uploading if necessary.
.Matt
Sure not everyone will
Sure not everyone will follow.
But unless a meaningful (guideline) standard is implemented, browsing multiple files on multiple pages within a tagged category could get well out of hand. It's inevitable that this site will become a valued resource for commercial users in film and tv advertising. It's how we operate when supplying libraries, music beds and spot fx in the commercial world. It makes it easier in terms of ***at a glance***:
1) what generation a particular file is,
2) who authored the file and
3) gives a pretty good visual clue as to what the file is.
4) Saves valuable time with inevitable deadlines and helps clarify communication when a client is making a choice between 2 or more generations (variations).
5) Spaces in file naming should always be considered bad practice and replaced with underscores.
I also want to add another point:
6) Repetition in a file is unnecessary:
uses up valuable storage space both remotely and locally;
increases up / down time.
unless it is a component of a multi-component loop i.e. A hi-hat pattern that is uploaded with the intention of fitting with separately available kick, snare and percussion sections originally intended as a group but offering users flexibility to restructure new loops.
These standards will be particularly useful for users who are browsing files from here but on their local hard drives.
Cheers,
Mike.
Hi Mike,
I 'm into your
Hi Mike,
I 'm into your idea, but I 'm not sure if it would work. What happens when someone doe NOT follow this? We can't edit it, and deleting the sound seems too harsh... I suppose we can recommend a way of naming anyway.
Especially for BPM, its nice to have that info on the filename.
I 'm keeping track of all this and we could implement them when there's a bit more time in our hands.
T
Why not advocate a meaningful file naming protocol.
a 4 digit number followed by designer initials followed by a meaningful sound name and bpm or note if applicable all seperated by underscores no spaces.
i.e.
0001_md_1940s_telephone
0002_abc_stags_rutting
0250_hpcm_hardcore_bassline_170 (still within the long file name 32 character limit)
This is good practice both for personal and online database sorting and cross-refrencing.
HardPCM (I'm not picking on you!) should consider this as all his sounds are the same and therefore meaningless on initial inspection when in the latest audio list.
mike.