[quote=Platonius post_id=486018 time=1629878174 user_id=108036]
I already started checking add-on code yesterday, but it's difficult to get my head around the way it's set-up. Also because I can't find a good starting point as far as existing add-ons. And JS isn't my primary language (but I know my way around C/C++/C#/Ada/Powershell/Python, so it should come... sometime...).

But at least the "Hello World" sample script works :wink:
[/quote]Only thing I can tell is welcome and see you in dev part of forum where you can threw more questions to us.
Feel free to ask anything there, we can figure out space where you swim the best at.

I already started checking add-on code yesterday, but it's difficult to get my head around the way it's set-up. Also because I can't find a good starting point as far as existing add-ons. And JS isn't my primary language (but I know my way around C/C++/C#/Ada/Powershell/Python, so it should come... sometime...).

But at least the "Hello World" sample script works :wink:

Hi,
[quote=Platonius post_id=486002 time=1629818378 user_id=108036]
You're the only ones constantly talking about supporting every tag. None of the 3 people requesting this have ever asked for ALL possible tags to be supported and properly parsed into the corresponding data! We just want the custom tag(s) we use to be visible in the views.[/quote]It is not a problem with you 3, but with whole concept of adding something Natively. Even single field need case checker, format case, UI, Translation, skins update, Check for supporting in other file types, ... and what if there is another 3 users want other tags, they would say if you made one support you can make few more. There is no end to that. NOTE that these fields are EXTENDED non-Standard fields.[quote=Platonius post_id=486002 time=1629818378 user_id=108036]
I don't know how extended tags are implemented in MM5. I don't know at what point they are read from the file.
[/quote]They are read on import in a way: Read file tags -> Extended tag found -> Read all as single special tag and write down.
[quote=Platonius post_id=486002 time=1629818378 user_id=108036]
But I know they are read (hence the "extended tags" column) and there's code to split them (for the properties page, but even the "Extended Tags" column is already parsed). So the tags should already be available.
[/quote]They are read exactly as you pointed during rendering of properties dialog or by call from API on specific tag requested.[quote=Platonius post_id=486002 time=1629818378 user_id=108036]
Say that I want the "RemixedBy" tag, or my own tag "VERIFY_RESULT" to be visible. All that's needed is to create a link between a column that can be used in the view and a single extended tag.
[/quote]That is not true, you need to create script that will call MM API to fetch/read Your Specific Tag from all extended tags, Ask MM UI API to Create UI element in MM main scree, call registry to read positions, format, color, translation, then after you have all the info tell MM API to Render the UI (Which will call Chromium), format Information in UI usable info, tell Chromium to show it, Assign Mouse gestures, Keyboard shortcut, assign index for search engine, Sort the format in UI, .... and that is all is needed in order to show 5 letter text at right place in MM UI. Not talking about debugging wrong cases, corrupted data, invalid data, .... or even what is also needed to make writing support for same tag you only made for yourself and you can change/decide you do not like it anymore because you have found that other one would be better, which means all work invested is wasted. Now instead of all that you have column and once you open properties for track you can edit/change your own extended tag or decide that for yourself create plugin/addon which will format and do that for you when you select track.
[quote=Platonius post_id=486002 time=1629818378 user_id=108036]
Doesn't even cost additional processing time or memory when it's not used if that's a concern.
[/quote]As I previously pointed you only count one track not bunch of tracks, which really takes literally <500ms to do that and you see the properties of track and can edit the tag (try to notice how long it takes to get into edit mode). All takes resources and takes time.

Have you tried to load 10k-15k of tracks in Tagscanner and see how long it takes to read all the custom tags, sort them and show them (Scan the physical files not query internal DB for the tags after they are already scanned). Even try to Drag and drop 1000 tracks to Tagscanner and see. No matter how MM is close to be perfect it will never be perfect for all users. Extended tags implementation was very requested feature in previous versions where MM simply skipped the tags. MM5 added reading of such tags, created tools and API calls so that anyone that really have need for them can easily make support for them self with as little fuzz as possible. We are always willing to help in terms of debugging, suggestions and improving API/Tools that are supplied in order to make that user make himself more perfect enviroment for its needs.

For example see MonkeyRok, LyricsViewer, Song Information Panel Plugins that do similar thing in MM4 and none of main MM devs were made it. MM5 opens things further, especially as it uses more common tools to create that can be also used not just in MM, but on whole WEB, or to expand Browsers like EGDE, Chrome, Firefox, .... or apps in MACOS, Linux, Android, iOS.
[img]https://www.happymonkeying.com/plgimages/300022_resized.png[/img][img]https://www.happymonkeying.com/plgimages/300028_resized.png[/img][img]https://www.happymonkeying.com/plgimages/300029_resized.png[/img]

Why not trying by yourself, we and our community are more than willing to help you archive your goal, but majority of work and invested time is yours for your own needs and will stay yours for life. Seeing not 3 but several thousand of user use your plugin/script for 15+ years means something and accomplished. MM is a swiss knife, but like swiss knife it can't weld steel or laser cut.

We really care, but we unfortunately we can't make all. At least we try to supply means and tools in order that someone can make his/hers life better (if in time make some other user life better I think it is Win Win).

[quote]There is no way that MM easily support all of them especially as they are some app specific tags like Serato. [/quote]
You're the only ones constantly talking about supporting every tag. None of the 3 people requesting this have ever asked for ALL possible tags to be supported and properly parsed into the corresponding data! We just want the custom tag(s) we use to be visible in the views.

I don't know how extended tags are implemented in MM5. I don't know at what point they are read from the file.
But I know they are read (hence the "extended tags" column) and there's code to split them (for the properties page, but even the "Extended Tags" column is already parsed). So the tags should already be available.

Say that I want the "RemixedBy" tag, or my own tag "VERIFY_RESULT" to be visible. All that's needed is to create a link between a column that can be used in the view and a single extended tag. Easiest by manually typing the tag. If it's not present - do nothing, otherwise print the contents. Doesn't even cost additional processing time or memory when it's not used if that's a concern.

I'm not asking for reverse-engineering Serato tags or whatever, and if somebody wants to print the Serato Base64 encoded strings - let them... I don't care.

Hi,
Additionally as it is not all that black for good example as you have DISCOGS extended tags available, so if Discogs plugin gets ported to MM5 it can easily take advantage of Discogs extended tags and improve Auto Tag.

Hi,
Your example is clear thing what I am explaining here. There is no way that MM easily support all of them especially as they are some app specific tags like Serato. Which means that we need to do reverse engineering of Serato propritery format and make it available in MM. Which after months of development can even result in DMCA request from Serato that we use their custom tags and we would need to remove it. Also checking reading and decoding such extended tags would slow MM considerably. even it is 10ms on 200k of tracks it is hours eg. 10x200000=33.5Min per single extended tag and from what I see you have 10+ different one which represent 5h+ of not being able to use MM.

I would be more than glad if you can prove me wrong, but making single addon that would extract desired info from Extended tags is way faster than native support that will bloat MM will suffice your needs.

NOTE: MM5 already read many more tags than MM4 and many users complain it is slower, not counting additional bandwidth/CPU/RAM needed to make that happen.

As far as I could see, there's an "Extended Tag" field that just shows ALL extended tags in one field. I couldn't find a way to show just a single extended tag.

I mean, I'm not sure how useable this is for sorting on a specific tag
[img]https://i.imgur.com/P0DcM66.png[/img]

Hi,
Not sure where is exactly the problem, I just checked and if you in Music -> All tacks right on column header under Custom submenu you have all MM custom Tags and even Extended Tag that is then added as column in List view.
[url=https://ibb.co/yns9b1m][img]https://i.ibb.co/gMg2Bpb/image.png[/img][/url]

I must admit I'm in favour of this as well.

Currently going through all FLAC files using the FLAC encoder's verify option and using a custom tag to note if something's wrong. It would be nice if you could add colums in view with your own %CUSTOM_TAG%. MM would know to look for it in the extended tags field.

At the moment, it's easier for me to just start Tagscanner and drag the file from MM to there to check the tag, than checking the properties in MM5.

I must say that it's handled pretty nicely in Tagscanner. I can just create a column with a custom thing, a single tag or a combination of tags. "Verify" in this case being my own tag and "Bitrate" being a combination of bitrate, sample rate and bit depth (saving space and make it easier to spot 16 bit 44/48 khz files with way too high bitrates).
[img]https://i.imgur.com/hoo59S1.png[/img]

If there were custom display fields that could just be set to %CUSTOM_TAG% or something, that would make a lot of us happy...
Or at least the 3 of us :wink:

[quote=Barry4679 post_id=484453 time=1626575604 user_id=28275]
I will leave the OP to push his own barrow ... I think that the idea has merit and that something is needed to rescue the implementation of Extended Tags in MM5.
[/quote]

Thanks for the additional input. You can see I joined here 5 years ago when I purchased a Lifetime Gold key, and this is my first post. I've been in IT nearly 40 years, I can make my way 'round many things, but this one had me stumped. Dismayed to learn the answer is "nope".

That said, the primary reason for my absence, is that I'd left lossy music in the rear view many years ago, and for the last few years, I've been plodding through nearly 11,000 live lossless concerts, with almost a quarter million tracks, spending 12+ hours daily in Xyplorer (not to shill for that program, rather as illustration). With a zillion features including "branch view", which effectively flattens the presentation of a folder, I'm able to list a couple hundred thousand records with custom columns, including extended tags, and that file browser happens to also have in-built support for media playback/preview, so, based on the issue at hand here, I returned to look at using that tool as my MM alternative. Turns out, it works quite well, includes a powerful native scripting language which seems endless in what it can accomplish, and, bonus, it's loads faster than the scan MM took of these quarter million records. No bashing here, I love MM, but, it's just not up to my particular needs.

Thanks again for the input, I'll continue to check back from time to time to see if either natively or with someone's addon, I can sort the listview by any extended tags.

[quote=Lowlander post_id=484442 time=1626553474 user_id=262]
You can use Custom tags if you wish, but Custom tags are independent tags from Extended Tags (stored differently within the file). If you map, you start doubling data as now you have two tags managing the same data.
[/quote]

I didn't know that the Custom tags were persisted to the Tracks. I thought that they were db-only tags.
Mine are, because I push them there from another app, but that is a different story.

A couple of extra redundant bytes stored, to some tracks, is not a problem. There is lots of redundant (to MM) data stored there already, like album art, and Catlogue number, and ACCURATERIP IDs and results. Another couple of bytes is no issue, especially since it would be MM5 that manages sync, and not rely on manual actions by the User.

The thing is that Custom Tags in MM5 is a half arsed implementation atm. Much like MM4's Album Comment tag was. ie. inconveniently and obscurely hidden in he MM4 UI. Some people used it, thinking that it was going to become a 1st class feature of MM ... and then it was dropped in MM5 due to "lack of use" .. quelle surprise



[quote=Lowlander post_id=484442 time=1626553474 user_id=262]
As you could have any number of Extended Tags it makes it really hard to manage this elsewhere in the interface.
[/quote]

Not so. It Custom Tags were able to be linked to the Customx database fields in some manner, as expected by the OP, he would be able to establish linkages to just the few tags that were significant to him.

I will leave the OP to push his own barrow ... I think that the idea has merit and that something is needed to rescue the implementation of Extended Tags in MM5.

You can use Custom tags if you wish, but Custom tags are independent tags from Extended Tags (stored differently within the file). If you map, you start doubling data as now you have two tags managing the same data.
As you could have any number of Extended Tags it makes it really hard to manage this elsewhere in the interface.

If you wanted to copy data from 1 tag to another, this could be done through an Addon (doesn't exist yet).

Now if there are additional tags in the tagging standards that MediaMonkey should natively support that could be a request.

[quote=Lowlander post_id=484424 time=1626500673 user_id=262]
Custom fields are their own fields, which is different from Extended Tags. Extended Tags can be anything, so in a Library you could've tens of different tags being used.
[/quote]

Yes, but I don't see how that affects the suggestion.
[list]eg. I use the Extended Tag facility to create one of the "missing" MM tags
[list]eg. COMPOSERSORT[/list]
[list]or MOVEMENT[/list]
[list]or MIXARTIST[/list]
[/list]
[list]it's good as far as it goes, I can see|use the tag outside of MediaMonkey[/list]
[list]but it very limiting that I can't use it inside MediaMonkey; it's not in the MM database
[list]can't sort nor filter by it, in neither displays, playlists nor collections[/list]
[list]can't see or easily audit, or find it so I can make editing corrections[/list]
[list]===> hence the OPs disappointment [/list]
[/list]

Currently it is like Extended Tags is only partially implemented.

Workaround:
[list]an optional naming syntax for the Custom columns
[list]eg. I rename Custom1 column to "<MIXARTIST> Mixer [/list]
[list]==-> MM5 populates, and syncs, the Custom1 tag, in the MM database, with whatever it finds or stores into tracks' MIXARTIST tag, and labels the cell or column as "Mixer" [/list]
[list]=====> happiness all round[/list][/list]

Custom fields are their own fields, which is different from Extended Tags. Extended Tags can be anything, so in a Library you could've tens of different tags being used.

[quote=JoppyFopFop post_id=484372 time=1626450228 user_id=86674]
I can see an extended tag field when viewing the properties of a track, but I cannot seem to get this field to display in the list.
I tried renaming a custom field to match the name of the extended tag, but after restart the column is still empty. Something I'm missing?
[/quote]

Some name syntax that you could use when renaming Custom columns, which would cause them to act as you expected, would be excellent. .. Or something less of a kludge which achieved the same result,
ATM the extended tag facility is a bit useless in a MM context.