![]() Now, the same data, with the last key (track 7 in this example) missing the desired key/value: > This is correct, desired, and interpreted properly in the 'Tag information' dialogue. ![]() Outputting either json_select_many "array" "key" "|" "|" 1000 1 or json_select_many "array" "key" "|" "" 1000 1 to variable "Output1" produces the following debug line: Tracks 2, 4 and 5 have some keys/values absent (this is verified to happen in iTunes API data I'm unsure about others). Let's say an album with 7 tracks has data with keys and values (album title IS "X", track title IS "Y", track number IS "N", etc.) for tracks 1,3,6 and 7. Json_select_many "array" "key" "|" "" 1000 1īoth fail when the data has or includes the last key in the array with a missing value. This is useful for json-formatted data with omitted array values (read previous bug report -above- for details and examples). And here's what I found:īug ticket #62095 was fixed with the addition of and extra parameter to the json_select_many and json_select_many_count commands which now (can) include result entries for non-existent items. So I'm opening a new one regarding the same topic. In a simple example, the ra…īut, between work + personal commitments + fighting a cold I couldn't devote the proper time to test run my script against the new release until today, which was 2 days after the original thread expired and was closed. ![]() It's important to note that the "contentAdvisoryRating" key is only present if that track is considered explicit and absent if it is not. Using my own script to parse json formatted data from iTunes API, on I use json_select_many to get the "contentAdvisoryRating" value for each track, which classifies it as explicit or not. ![]() I think there is a bug with version 3.22, on the json_select_many function. Mp3tag version 3.22 - json_select_many function Fixed Bugs ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |