gorman wrote: 
> Sure, I wasn't complaining. Just providing some info. Now it's
> progressing in its analysis. Once it finishes I will run a new analyse
> with debug logs active, maybe those could give a clearer idea?

Well, the tag reading is handled by a library - so unless I'm using it
wrong (which is not unlikely) there is not much I can do. The library is
fairly young, about a year old, so will hopefully get better. When a new
release of it is made I'll update bliss-analysers dependency. I found an
issue with its M4A tag reading, reported it on github, and the dev fixed
within a day - they are very responsive.

gorman wrote: 
> I mentioned this especially because the error message is wrong in this
> case. There are tags and they are of the type the library should be
> capable of interpreting. I'll try and provide more info later.

Well, that bit of code as taking from the library's 'tag reader
example.'
(https://github.com/Serial-ATA/lofty-rs/blob/main/examples/tag_reader.rs)



*Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json
(Use http: //SERVER:9000/material/?debug=json,cometd to also see update
messages, e.g. play queue) 2. Open browser's developer tools 3. Open
console tab in developer tools 4. REQ/RESP messages sent to/from LMS
will be logged here.
------------------------------------------------------------------------
cpd73's Profile: http://forums.slimdevices.com/member.php?userid=66686
View this thread: http://forums.slimdevices.com/showthread.php?t=116068

_______________________________________________
plugins mailing list
plugins@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/plugins

Reply via email to