If we’re going to make a new ID3 TXXX frame, can’t we please call it “Recording Id” as that’s what it is? The reason it’s called “track id” in some contexts is for legacy purposes. “Recording ID” is the proper term for it.
Well anything is possible because we’re not really dealing with frames at a lower level within foobar. Everything is plain text strings so musicbrainz_trackid will remain an option because it’s used by flac, vorbis, opus, wavpack, musepack etc and musicbrainz track id is used in m4a files. I thought it would be good for id3v2 because it matches the existing naming convention.
I guess I could provide a dialog of some sort for people to use whatever they like.
Well I’m pretty much done with my next update…
it has support for caching listens when LB is down or you are offline (no doubt real world usage will break it in ways I haven’t imagined yet!!)
bulk submission of cached listens (50 at a time if needed)
client side validation of MBIDs
other sanity checks/adherence to API guidelines
Are you guys going to agree amongst yourselves on a new recording ID tag name or do you want the option to use anything you like?
For what it’s worth, I’d vote for consistency, but am perfectly happy either way.
New version uploaded, details in first post. No changes to supported tag names have been added for now.
Looking at the docs, “TXXX:MusicBrainz Track Id” would be most consistent with other, similar tags. I don’t really understand why it isn’t simply called recording id in all those tags by the way. Is that for historical reasons?
History of Tracks and Recordings
I just tried the “
$copy(_id3:TXXX:MusicBrainz Track Id,musicbrainz_recordingid)” tagger script and it seems to work with the current version of the ListenBrainz script. Jay!
Now I just need to re-tag my entire music collection.
I had a bit of a temper tantrum over on the foobar forums and removed that github account!! I have a new one with an updated component but it’s not really ready for all users just yet due to a lack of documentation. I’ll post back in a few days when it’s done
My updated component even supports Windows XP which it never did before but unfortunately this is not good news for anyone here because it simply doesn’t support the security protocols necessary to communicate with listenbrainz over https.
Well anyway thanks for still being a part of the MusicBrainz community. I thought you had left. I’m glad you are still here and working on things
…and I do appreciate your previous efforts to add https://wayback.archive.org/web/20171130190044/https://github.com/19379/foo-jscript-panel/wiki/WINE instructions. I hope that your tool becomes good for Windows users. I suppose we other *nix users can use stuff I’ve already posted in my list here:
Ah, I didn’t realise I could retrieve the old wiki from archive.org. That will help, thanks.
I can’t edit the first post any more but the new link for the project is what @jesus2099 posted above.
If anyone is using v2.0.0, they should upgrade to v2.0.1 because I introduced a silly bug that broke the caching feature. Anyone still using component version v1.x.x is unaffected. Also, there is no compelling reason for v1 users to upgrade at this point. I’ll update the thread if any worthwhile changes are made.