|
Post by GoneMAD on Sept 15, 2020 8:16:22 GMT -5
i updated the original post to include which view a variable is available in. I did it from memory so i'll go through and verify it all when i have access to the code. If you import something with an unsupported variable, the error pop up will tell you which ones you tried to import are unsupported
Composer might be added to more views in the future.. as of right now it was messing up the queries since not every track has an associated composer
|
|
|
Post by MotleyGord on Sept 16, 2020 19:49:39 GMT -5
I've updated to the latest beta and was happy to see the nested functions working. Except in one specific case. I was expecting to see only the %al% album title in this case. But for any where the tag contains a comma, any text including and after the comma gets dropped. This only happens within the nested function. Line 5 is the trouble, line 6 isolates the nested function to a new line and displays correctly. Still a bug? Attachments:
meta tester.json (965 B)
|
|
|
Post by GoneMAD on Sept 16, 2020 20:41:08 GMT -5
slightly separate bug but still related to the nested functions. The parser use commas as the delimiter so most likely one of the variables is being resolved (parameters in functions have to get resolved ahead of time in order to handle nested functions) and then those commas are interpreted as part of its parent function.
Thats gonna be a hard one to fix, i'll add it to trello but it may not be resolved til the 2nd/3rd phase of the beta
|
|
|
Post by MotleyGord on Sept 17, 2020 6:33:19 GMT -5
slightly separate bug but still related to the nested functions. The parser use commas as the delimiter so most likely one of the variables is being resolved (parameters in functions have to get resolved ahead of time in order to handle nested functions) and then those commas are interpreted as part of its parent function. Thats gonna be a hard one to fix, i'll add it to trello but it may not be resolved til the 2nd/3rd phase of the beta Got it. Not sure if you applied the file to see the layout live on your end. Intention is for the Album line to also show the Album Artist unless it is already in the album name (self-titled, best of's, etc) or if it is "Various Artists." Below the track name, the track Artist is displayed, but again only if it doesn't match the Album Artist. Other than the few albums that have a comma, it is now working perfectly as expected. Thanks for the update.
|
|
|
Post by GoneMAD on Sept 17, 2020 9:05:52 GMT -5
slightly separate bug but still related to the nested functions. The parser use commas as the delimiter so most likely one of the variables is being resolved (parameters in functions have to get resolved ahead of time in order to handle nested functions) and then those commas are interpreted as part of its parent function. Thats gonna be a hard one to fix, i'll add it to trello but it may not be resolved til the 2nd/3rd phase of the beta Got it. Not sure if you applied the file to see the layout live on your end. Intention is for the Album line to also show the Album Artist unless it is already in the album name (self-titled, best of's, etc) or if it is "Various Artists." Below the track name, the track Artist is displayed, but again only if it doesn't match the Album Artist. Other than the few albums that have a comma, it is now working perfectly as expected. Thanks for the update. I havent yet but i linked your post to the card on trello so i can take a look at it when i investigate the bug more. Thanks!
|
|
|
Post by MotleyGord on Sept 17, 2020 13:14:59 GMT -5
Hi all. I'm sharing an update to the custom metadata I am using for the main UI. Feel free to download and use if you find it useful. This is what is displayed by line; 1) If the track contains a Composer tag, it is shown first. Otherwise this line is left blank and adds a buffer space between the artwork and the rest of the metadata. It pulls the current primary colour, great if you are using the dynamic functions. 2) The Album Artist and Album are shown next, with a couple of conditions. If the Album Artist name is found within the Album title, it isn't shown as a duplicate. It is also not shown if it is Various Artists. Both of these conditions save space as they are not necessary. It pulls the current accent colour, also great if you are using the dynamic functions. 3) The Title of the current track in bold white. The center piece of the metadata. 4) The Artist is shown next, in smaller white. Again to save space and avoid duplication, this line is omitted if it is already contained from the Album or Album Artist tags. 5) a small blank line to separate the technical details. 6) The current queue position and total queue tracks. 7) Technical track details including the format, sample rate,bit rate, channels, and year. Enjoy! Attachments:meta MotleyG.json (854 B)
|
|
|
Post by MotleyGord on Sept 17, 2020 13:57:57 GMT -5
This is what is displayed by line; 7) Technical track details including the format, sample rate,bit rate, channels, and year. Enjoy! BTW - ALAC and AAC types are assumed at this point, as the %codec% tag is not scanned currently by GMMP. The setting was based off of the m4a extension, and a bit rate of 365k or higher being ALAC and below being AAC. You can edit the line if you prefer to change this threshold higher or lower for your library preferences.
|
|
|
Post by GoneMAD on Sept 17, 2020 17:41:02 GMT -5
thanks for sharing! at some point i'll make another thread or something to curate the good custom metadata setups (assuming enough are posted).
|
|
|
Post by MotleyGord on Sept 17, 2020 17:51:29 GMT -5
thanks for sharing! at some point i'll make another thread or something to curate the good custom metadata setups (assuming enough are posted). This would be handy for all I'm sure. The first few posts will probably have some very different ways of looking at things. From there, users will be able to start taking the code and modifying it to tweak to their own preferences. Especially with the custom metadata options you have just opened up for some of the lists now and more on the way. Is there a way to also share settings for the UI as well? Background style and settings, theme colour choices, etc? Or can this all be done using the backup files?
|
|
|
Post by GoneMAD on Sept 17, 2020 17:57:19 GMT -5
thanks for sharing! at some point i'll make another thread or something to curate the good custom metadata setups (assuming enough are posted). This would be handy for all I'm sure. The first few posts will probably have some very different ways of looking at things. From there, users will be able to start taking the code and modifying it to tweak to their own preferences. Especially with the custom metadata options you have just opened up for some of the lists now and more on the way. Is there a way to also share settings for the UI as well? Background style and settings, theme colour choices, etc? Or can this all be done using the backup files? technically its all saved in the settings that can be exported, but i'd like to eventually add a UI export type thing which does what you said (was actually thinking about this on the drive to work today).. exports all the UI related settings so they can conveniently be loaded from a single file. I think once all the UI settings are finalized i'd be able to add it in. Would basically be the closest thing to loading a "custom skin" gmmp could support
|
|
|
Post by MotleyGord on Sept 18, 2020 19:09:40 GMT -5
Is there any tag available to get the bit depth (9/16/24/32)of the file? The tag is %_bitspersample%.
|
|
|
Post by GoneMAD on Sept 18, 2020 19:27:31 GMT -5
no. there is no standard bit depth tag. %_bitspersample% is not a valid tag for any format ( i mean i guess ones that allow any text to be the tag ). GMMP's tagging library does not read bit depth regardless
|
|
|
Post by MotleyGord on Sept 19, 2020 18:25:09 GMT -5
In the song list, the field for %aa% album artist is returning the value from %ar%. See the third line from this file. The preview on the selection list looks correct, just not in the actual song list.
|
|
|
Post by GoneMAD on Sept 19, 2020 20:41:13 GMT -5
fyi using artist and album artist in the same custom metadata will most likely not work as u've seen. They conflict (same database table). Pick one or the other and it should populate correctly
|
|
|
Post by GoneMAD on Sept 19, 2020 22:17:06 GMT -5
wow completely missed documenting a big part. my bad guys. Added to the main post:
Splits can be assigned weights so they only take up a percentage of the width (default is 50/50 for 2 splits and 33/33/33 for 3 splits). The following example will use 75% of the width for the left split and 25% for the right split
["<weight=0.75><align=left><typeface=sans-serif><size=30>%ps%) %tr%", "<weight=0.25><align=right><typeface=sans-serif><size=30>%du%"]
|
|