Sounds like a script or plug-in to me. Which ones do you have enabled/setup?
Check the source data… some database entries have some funky apostrophe’s in error. Nothing should be using a backtick
In the database it should either be a typographical apostrophe or the keyboard (ASCII) apostrophe.
I’m using this one.
It makes the format similar to how it would be if I had ripped from a cd.
Where would I find this please?
In Picard, click on “lookup in Browser” on the toolbar. Then let us know the URL and we can help check.
This forum does not let us easily type the various variations of apostrophes.
Are you sure it is a backtick? Is “rekordbox” just after plain keyboard style ASCII?
In Picard, Check OPTIONS \ Metadata
Look for “Convert Unicode punctuation characters to ASCII” to keep it all clean and simple.
Hope this is what you meant.
The album name uses back tick (`) and the track I’ll be there also uses it.
This has worked!!!
I’ve had to use powershell to find all the back ticks and convert them then re-analyse etc, been pretty painful.
That is a standard apostrophe. Or “Typographical Apostrophe” as they get called. It’s a Unicode thing.
So change it all to old fashioned ASCII which matches your keyboard.
There are dozens of variations of this stuff.
(None of these things are on your standard keyboard…)
The perfectionists love it and have to put them into place “because the keyboard is limited”.
Personally I am like you and wipe them out of my filenames and tags and wrote my own plugin to go further.
It is especially confusing if you have folders with three different types of dashes\hyphens side by side… it also confuses searches on a computer…
It makes the file name look like this and it’s horrible as you think there’s some kind of spacing error but it’s not.
This looks much better.
Once again thanks for you help.
It is the font being chosen on your device that make it look funky like that. The device is expecting plain ASCII I expect.
Use a more common font and you will not get the problem. Like in this forum, you don’t see them change. But it is not “as you type”. (Compare the right window to the left window and you’ll see it)
Speechmarks, Apostrophe’s and hypens all get “the treatment”.
Yeah - you may want to get that powershell script out on your hyphens too… otherwise any sub-folder with a dash in it will now be different to sub-folders you tag in future… first time that happened to me it confused me as to what was happen-ing!
Maybe I’m missing something, but why PowerShell and then re-analyse?
Wouldn’t you let the Picard plugin do it for you?
Picard couldn’t go back and fix the already tagged files. Much quicker to write an OS repair script.
Especially as they had not spotted the “Convert Unicode punctuation characters to ASCII” option. All Picard would do it keep the Unicode stuff from the database.
(Yes, I know, pedant hat on… now they have ticked the option Picard can correct everything… but powershell is quicker)
I’m not sure I follow - If the files are already tagged (including MBID tags) it’s just as matter of dragging into Picard and hitting ‘save’.
Yes, that would have been easier but I didn’t have the reason why it was putting in that particular symbol, the 2nd headache I had was that the metatag had them too but I was able to use another problem to eliminate them manually/painfully till again I found that there was a quicker way, all a learning curve for me, these programs are very powerful when you know how.
Thanks to @IvanDobsky the remaining ones I did drop back into Pickard and it sorted them.
And Picard would have just put all the Unicode punctuation back. @winston79 had not spotted the option to turn that off so had to resort to external means.
When you are an old hand with Picard, you know of “Convert Unicode punctuation characters to ASCII”. But when just trying to quickly tag some files the whole thing is a huge complex mystery of options.
I must be missing something… change the setting (obviously), drag all the files in, and hit save again, done. Unicode gone.
If the files have been previously tagged there are no other steps?
Yes. You are missing something. You keep assuming @winston79 had hit the switch to disable Unicode. Even to the extent of saying “obviously”.
This is not an obvious option to new users of Picard.
When the script was written @winston79 had not found the switch. So Picard just kept putting in Unicode.
AFTER asking in this thread I taught them about the switch. Only then did Picard get the ability to use ASCII and the script became obsolete.
You are seeing the world through your eyes. You are someone who is skilled in the use of Picard. You are forgetting the confusion the first time you picked the app up. There are solutions outside of the MB world that work well - Powershell\MP3TAG\etc.
To repeat my above comment from earlier - I am not saying Picard can’t fix the problem. But it can only fix it when you find (and understand) “Convert Unicode punctuation characters to ASCII”. Most people in The RealWorld™ will not realise it is Unicode that is messing with their text.