Thanks for the explanation.
I will weight the pros and cons of both methods.
Making unique filenames is my concern (as long as the filename parsing feature - which I'm really hoping for - is not available).
E.g. I was lately transcribing the Jeremy Steig's version of Hop Scotch which differs from the original one from Charlie Rouse.
One my OneDrive these are just stored in 2 folders:
Jeremy Steig/Transcription/Hop Scotch.pdf
Charlie Rouse/Transcription/Hop Scotch.pdf
The batch import deduce the composer ("Jeremy Steig", "Charlie Rouse"), the tile ("Hop Scotch") and Source type ("Transposition"). And this is what I want.
I could easily make unique filenames, but that means that the song titles won't be correct/nice any more ("Jeremy Steig--Hop Scotch", "Charlie Rouse--Hop Scotch").
And this would require a manual intervention for each imported song :-(
While 90% of my songs don't require (in today's approach) to be manually edited. A bunch of extra workload.
I will weight the pros and cons of both methods.
Making unique filenames is my concern (as long as the filename parsing feature - which I'm really hoping for - is not available).
E.g. I was lately transcribing the Jeremy Steig's version of Hop Scotch which differs from the original one from Charlie Rouse.
One my OneDrive these are just stored in 2 folders:
Jeremy Steig/Transcription/Hop Scotch.pdf
Charlie Rouse/Transcription/Hop Scotch.pdf
The batch import deduce the composer ("Jeremy Steig", "Charlie Rouse"), the tile ("Hop Scotch") and Source type ("Transposition"). And this is what I want.
I could easily make unique filenames, but that means that the song titles won't be correct/nice any more ("Jeremy Steig--Hop Scotch", "Charlie Rouse--Hop Scotch").
And this would require a manual intervention for each imported song :-(
While 90% of my songs don't require (in today's approach) to be manually edited. A bunch of extra workload.