it would be nice if I could save multiple “File and Folder Correct” settings, so under each tab I can create a format and then save it, and switch between saved formats or create a new one without worrying about losing my current format.
it would also be nice if I could set a folder and filename all in one option so I don’t have to go through the long process of changing a base folder, then setting the folder name, and then setting the file name. Just one click and all of that gets done.
[quote=TinCanFury]it would be nice if I could save multiple “File and Folder Correct” settings, so under each tab I can create a format and then save it, and switch between saved formats or create a new one without worrying about losing my current format.
[/quote]
Yes, I think this is already on the Enhancement list somewhere.
[quote=TinCanFury]
it would also be nice if I could set a folder and filename all in one option so I don’t have to go through the long process of changing a base folder, then setting the folder name, and then setting the file name. Just one click and all of that gets done.[/quote]
You mean when actually using the tasks under Action/File and Folder Correct ?
Yes, would be a good idea to change both subfolder and filename in one go, base folder slightly harder as we don’t really have a default although I am adding a default Save and Move folder in this release.
[quote=paultaylor][quote=TinCanFury]it would be nice if I could save multiple “File and Folder Correct” settings, so under each tab I can create a format and then save it, and switch between saved formats or create a new one without worrying about losing my current format.
[/quote]
Yes, I think this is already on the Enhancement list somewhere.
[/quote]
Cool, this would help immensely since I have a few “different” collections that I like to tag in different manners.
[quote=paultaylor][quote=TinCanFury]
it would also be nice if I could set a folder and filename all in one option so I don’t have to go through the long process of changing a base folder, then setting the folder name, and then setting the file name. Just one click and all of that gets done.[/quote]
You mean when actually using the tasks under Action/File and Folder Correct ?
Yes, would be a good idea to change both subfolder and filename in one go, base folder slightly harder as we don’t really have a default although I am adding a default Save and Move folder in this release.
[/quote]
Well, I was thinking in this method the “base folder” is antiquated and unnecessary, the user would just place the whole, entire directory structure in the tag list. Or, keep the “base folder” idea and have it as a variable the user could include in the list if they so desired (would probably be useful in OSX because of its /Volume… structure)
Maybe it is antiguated - I dont know.
But the reason I split the base folder from the subfolder is so users could modify the part of the foldername that related to the songs themselves without modifying the part which doesn’t, i.e c:\Music.
I don’t fully understand your solution.
[quote=paultaylor]Maybe it is antiguated - I dont know.
But the reason I split the base folder from the subfolder is so users could modify the part of the foldername that related to the songs themselves without modifying the part which doesn’t, i.e c:\Music.
I don’t fully understand your solution.[/quote]
well, if the user can save multiple rename schemes, then all you really need is one field for renaming that would include the “base folder” the “sub folder” and the filename.
so for instance I could have
/Users//Downloads/SXSW Tagged/%artist%/%album%/%trackno% - %title%
and
/Users//Music/My CDs/%artist%/%album%/%artist - %album% - %trackno% - %title%
and
/Volumes/media2-1/Music/Music/KEXP Song of the Day/%album% - %trackno% - %artist% - %track%
etc. since the base and subfolders are part of the scheme I don’t have to keep changing the base depending on where I’m putting the music I’m tagging, I just select which scheme I want and it’s all there.
the base folder idea is great if all your music goes in one place, but when it doesn’t the user has to change things up. now, as a side option, to keep the base folder field, you could have a variable called
%basefolder%
that would allow for the user to keep the base folder as is now, and place it in their rename field, but also have the option of not using it if they don’t want to.
oh, ps, if you do implement the ability to save renaming formats, it would be nice if they had “titles” so you could say, implement a drop down box in the toolbar with a list of the rename formats without it showing the actual string but just the name, ie
SXSW
My Music
KEXP Podcasts
time to start playing with the latest beta…
Actually the base folder work well if everything is in different places because it means you can rename your songs to a consistent folder structure but have them rooted at different places, all with just one mask . Unless you want to move the base which is what you want to do, which is unusual because most users who move their songs just move them all to the same new place.
But I like your idea of having a %basefolder% field which you can use or hardcode a specify rooted path, I guess that could work.
[quote=paultaylor][quote=TinCanFury]
the base folder idea is great if all your music goes in one place, but when it doesn’t the user has to change things up. now, as a side option, to keep the base folder field, you could have a variable called
%basefolder%
that would allow for the user to keep the base folder as is now, and place it in their rename field, but also have the option of not using it if they don’t want to.
[/quote]
Actually the base folder work well if everything is in different places because it means you can rename your songs to a consistent folder structure but have them rooted at different places, all with just one mask . Unless you want to move the base which is what you want to do, which is unusual because most users who move their songs just move them all to the same new place.
But I like your idea of having a %basefolder% field which you can use or hardcode a specify rooted path, I guess that could work.[/quote]
yea, I can see that most people won’t use it, but I definitely would because of how I have my music saved on network storage with only my new downloads/rips to my laptop, plus other oddities of my setup. I know other apps don’t do the basefolder thing but usually have the ability to save full formatting strings so it didn’t matter.
i know the base folder thing can confuse some people, but it seems necessary for the way I work.
When I choose “Fix Subfolders from Metadata” it puts in in a very traditional “/Artist/Album/” folder structure.
Then I select all the subfolders that begin with letter A,B, or C and change their base folder to Volumes/Jukebox/Music/[Sorted]/[A-C]/
and so on for each group of three letters (roughly).
It’s just too unwieldy to dump all artists into one huge folder.
[quote=wynlyndd]i know the base folder thing can confuse some people, but it seems necessary for the way I work.
When I choose “Fix Subfolders from Metadata” it puts in in a very traditional “/Artist/Album/” folder structure.
Then I select all the subfolders that begin with letter A,B, or C and change their base folder to Volumes/Jukebox/Music/[Sorted]/[A-C]/
and so on for each group of three letters (roughly).
It’s just too unwieldy to dump all artists into one huge folder.
[/quote]
wynlyndd, my arguement is that whole workflow is flawed to begin with.
there should be no Base Folder, or “Correct Subfolders”, or “Correct Filenames”.
There should just be “Correct” which encompasses the entire directory tree and file name, all in one formatted line, which can be saved, so that if you have more than one collection in more than one location you save the format you want for that location.
Then when your tags are set and your ready to save, you can just choose to apply the format you wish to use for those files and click Save.
right now, if you have multiple collections in their own locations with their own folder and filename structure, you have to manually change all those separate fields in the options, then select three different “Correct” functions to correct the base, then the sub, then the filename. if you then later work on files in another “collection” you have to go through the entire cycle. You have to save all those options in a separate text file, etc.
I guess in your mind, each main branch of my main folder structure, the folders labeled [A-C], [D-G], etc would be a “collection” and the files I am working on would just go there automatically.
But when using jaikoz, I typically work on a large folder of varied artists and album combinations in a location other than where I ultimately want them to reside and so in a typical session I would be saving to multiple “collections”. Direct control over where the files get saved to is critical.
Maybe I am confused over your meaning but here is a typical scenario for me.
I have a folder named “To Be Jaikoz’ed” on my main drive. The path to this folder is “The Vault/Downloads/To Be Jaikoz’ed”. Inside, there may be folders of files all in one album/artist combination or some loose files.
Let’s say in that path I have a folder of the band Infected Mushroom’s Converting Vegetarians double CD release and a folder with Laura Marling’s latest album, both of which that need tagged, artwork, and lyrics.
Ultimately, the paths I want the Jaikoz’ed files to be are:
/Volumes/Jukebox/Music/[Sorted]/[G-I]/Infected Mushroom/Converting Vegetarians/.mp3
and
/Volumes/Jukebox/Music/[Sorted]/[J-L]/Laura Marling/I Speak Because I Can/.mp3
If the current way is flawed, how does this work in what you are proposing?
[quote=wynlyndd]I guess in your mind, each main branch of my main folder structure, the folders labeled [A-C], [D-G], etc would be a “collection” and the files I am working on would just go there automatically.
But when using jaikoz, I typically work on a large folder of varied artists and album combinations in a location other than where I ultimately want them to reside and so in a typical session I would be saving to multiple “collections”. Direct control over where the files get saved to is critical.
Maybe I am confused over your meaning but here is a typical scenario for me.
I have a folder named “To Be Jaikoz’ed” on my main drive. The path to this folder is “The Vault/Downloads/To Be Jaikoz’ed”. Inside, there may be folders of files all in one album/artist combination or some loose files.
Let’s say in that path I have a folder of the band Infected Mushroom’s Converting Vegetarians double CD release and a folder with Laura Marling’s latest album, both of which that need tagged, artwork, and lyrics.
Ultimately, the paths I want the Jaikoz’ed files to be are:
/Volumes/Jukebox/Music/[Sorted]/[G-I]/Infected Mushroom/Converting Vegetarians/.mp3
and
/Volumes/Jukebox/Music/[Sorted]/[J-L]/Laura Marling/I Speak Because I Can/.mp3
If the current way is flawed, how does this work in what you are proposing?
[/quote]
I’m not saying the files would go there automatically, you would still have to tell Jaikoz which output format you want to use for those files.
(I’m ignoring the how variable artist albums would work, as they can either be their own saved strings, or a second string under the same saved format case)
For your case above , you would have two saved format strings,
Sorted G-I=/Volumes/Jukebox/Music/[Sorted]/[G-I]/%bestartist%/%album%/%wynlyndd’s track format%
and
Sorted J-L=/Volumes/Jukebox/Music/[Sorted]/[J-L]/%bestartist%/%album%/%wynlyndd’s track format%
(and then obviously any others you would want to use)
So, for you, in the end, you wouldn’t necessarily gain anything from the change, other than instead of having to do the:
Choose Base Folder
Apply Sub-folder format
Apply Filename format
Save
you would just:
Choose Output Format (Sorted J-L, or sorted G-I)
Save
which, is still a saved few steps.
Now, for people like me, I have a few different actually separate collections, much like yours, on a networked drive.
-My CDs
-Free Music (freely released sample tracks downloaded from labels, band websites, and the such)
-my girlfriends music
each go in their own directory, (…/ is what is now considered the “base” directory)
…/Music/My CDs
…/Music/Free Music
…/Music/GF’s Name
and each with their own folder/filename structure
/%bestartist%/%year% - %album%/%bestartist% - %album% - %track% - %title%
/%artist$/%album%/%track% - %title%
/%bestartist% - %album%/%track% - %title%
but now, sometimes I’m not at home, so I like to tag my rips and downloaded tracks to the local drive, or one of my housemates gives me a bunch of their music to tag for them, each with their own desired output format…
So what I’m suggesting is a method that enhances Jaikoz with a feature for people that use multiple layouts to save them within the program, while shortening the entire tagging process for others, without removing any of the current abilities.
Yes, the work flow will change, but I feel would do so for the better of everyone.