Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: custom field names starting with an underscore suddenly don't work. (Read 702 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

custom field names starting with an underscore suddenly don't work.

Sometimes I need to save alternative versions of some tags, for diverse reasons, and to facilitate differentiate them from other fields that are also displayed with RAW fieldnames (such as those from musicbrainz), I started adding leading underscores to my special fields:

_ALBUM_ALT0
_ALBUM_ALT1
_TITLE_ALT0
etc...

This seemed to work when I started doing it and for a long time, but something must have changed in recent versions, because now, whenever I try to use these tags for display or in the "Automatically fill values" menu, I just get an "?"

Re: custom field names starting with an underscore suddenly don't work.

Reply #1 –
I suspect the underscore issue is a side effect from tech info handling. Accessing those used to require using underscore prefixes.

You can display your fields using $meta function, for example $meta(_ALBUM_ALT0). I see no problem using a starting underscore with the "Automatically fill values" tool.

PS: I tested foobar2000 v1.0 and it behaved the same as 1.3.17. Doesn't look like a recent change.

Re: custom field names starting with an underscore suddenly don't work.

Reply #2 –
Thanks for the heads up on $meta()
It's not as convenient, but, if that's how it has to be...

As for this working or not before... well, lately my memory has been really bad, but I'd swear I did use these custom tags before not too long ago and they did resolve...
Could a component interfere with this?
 

Re: custom field names starting with an underscore suddenly don't work.

Reply #3 –
Quote from: radorn on
As for this working or not before... well, lately my memory has been really bad, but I'd swear I did use these custom tags before not too long ago and they did resolve...
Could a component interfere with this?

I have no idea whether it can interfere, but foo_dynfil custom tags have to be prefixed with an underscore.
I'm late