My OperaSpaces in your music file names: don't do it!
Friday, March 2, 2012 4:40:36 PM
When you are organizing your music files, it is important to keep both the file paths and the tags accurate. Tags within the music file denote the metadata for this music, such as the track name, the artist name and so on, and the file paths can also name the same meta data by using the names for folder and file names.
Many music listeners can store their files in locations that will synchronize their location of tags. However, if you have a space in the filename, then it will also come up when you search for it, such as;
As you can see, the first example looks alright, but if you were to use different software from the original one, it might not be able to be recognized.
For example, this happens to be a problem for *nix operating systems like MacOS or Linux. Those operating systems have a lot of power, and are naturally more generic with flexible command line software that works with your music library. However, as you can see in the example, the operating system already has a space to begin with, causing confusion.
In operating systems like *nix, that lists the files within an Oasis directory.
This command lists all of the files in both the Oasis and the Blur directory. Because there's a space between the two paths, the operating system knows this is two separate requests for file listings.
Now, as the spaces get more elaborate things fall apart. There is a space between 'Definitely' and 'Maybe'. This means the Operating system will try to list the contents of three directories: Music/Oasis/Definitely, Maybe and Music/Blur/Parklife. This is not what we wanted!
In essence, when you were trying to enact the command, the command fails with these operating systems because it tries to enact commands that are not meant to be run. This can be fixed by putting a backward slash, or putting quotes. This is called 'escaping' or quoting the string.
OR:
For the longer term, it is much easier to just covert the characters into something else that you are more familiar with and can be consistent. It'd be better off to use underscores, as they are the most recognized in the music genre. However, if you have a huge music library and want to make these changes, that is a lot of renaming. If you have a rule based music library organizer, it'd be much easier then having to worry about your renaming process.
Many music listeners can store their files in locations that will synchronize their location of tags. However, if you have a space in the filename, then it will also come up when you search for it, such as;
C:/music/Oasis/Definitely Maybe/
As you can see, the first example looks alright, but if you were to use different software from the original one, it might not be able to be recognized.
For example, this happens to be a problem for *nix operating systems like MacOS or Linux. Those operating systems have a lot of power, and are naturally more generic with flexible command line software that works with your music library. However, as you can see in the example, the operating system already has a space to begin with, causing confusion.
ls Music/Oasis/
In operating systems like *nix, that lists the files within an Oasis directory.
ls Music/Oasis/ Music/Blur
This command lists all of the files in both the Oasis and the Blur directory. Because there's a space between the two paths, the operating system knows this is two separate requests for file listings.
ls Music/Oasis/Definitely Maybe/ Music/Blur/Parklife
Now, as the spaces get more elaborate things fall apart. There is a space between 'Definitely' and 'Maybe'. This means the Operating system will try to list the contents of three directories: Music/Oasis/Definitely, Maybe and Music/Blur/Parklife. This is not what we wanted!
In essence, when you were trying to enact the command, the command fails with these operating systems because it tries to enact commands that are not meant to be run. This can be fixed by putting a backward slash, or putting quotes. This is called 'escaping' or quoting the string.
ls Music/Oasis/Definitely\ Maybe Music/Blur/Parklife
OR:
ls “Music/Oasis/Definitely Maybe” Music/Blur/Parklife
For the longer term, it is much easier to just covert the characters into something else that you are more familiar with and can be consistent. It'd be better off to use underscores, as they are the most recognized in the music genre. However, if you have a huge music library and want to make these changes, that is a lot of renaming. If you have a rule based music library organizer, it'd be much easier then having to worry about your renaming process.
