peter hi Peter, I totally understand how ST3 treats the files and the naming process, but can you explain to why I would want to create multiple song files with an exactly same song name and artist name pointing to one file or perhaps different files.
I don’t see a usefulness in that, can you give me some examples of using this to an advantage, the way I see it, it just creates a messy database and operator confusion as others are obviously experiencing to understand.
I might be missing something, perhaps I am looking at it from one perspective and can’t shift my perspective to understand.
My simple way of seeing things would be, I expect the file in ST3 folder to exactly represent one song in SONG mode, any song name change in SONG also updates the File in ST3 folder, there is no way to have two identical files in either and updating one changes the other, this way no confusion and time wasting when dealing with songs.You should not be able to have multiple identical song names in SONG even if artist naming is different, this saves time and keeps things simple, if you want the same song with different settings or lyrics you duplicate it and rename it this creates another complete version in both file systems, so if you decide to delete one it leaves the other one alone. As you load a song in to SONG you don’t need to go to ST3 folder to change its name you actually do that in SONG and vice versa if you rename your ST3 folder song file name it updates in the SONG list, the two should appear as one, this creates simplicity and speed of operation.
This is simple and consistent with all operating systems I know.
If there is an advantage of the existing system the way it is I would like to know about it as I can’t think of one, unfortunately all I see is disadvantages.
I know you must have a good reason, can you simply explain to what that is, I think we spoke about this way back but my memory cells must be fading ?
Thanks Damir