mruddo wrote:
> I've updated my config.json file to add the the exclusions, as below:
>
> >
Code:
--------------------
> >
> {
> ...
> "excludegenres":[
> "Audiobook","Children's","Language
Course","Meditative","Opera","Pronunciation Guide","Vocal","Other"
> ]
> }
>
--------------------
> >
>
> However, when I re-run the analysis, I can't see any difference - i.e.
> no logging of Excluded Genres or anything like that.
>
I've just tried with:
Code:
--------------------
"excludegenres":["Pop", "Rock"]
--------------------
And I see the following during analysis:
Code:
--------------------
2022-01-09 21:28:12 E Failed to analyze ABBA - Gold - Greatest Hits/01
Dancing Queen.mp3 (Excluding genre (Pop))
--------------------
Checked the DB, and no "Pop" tracks. (I tried with a subset of just 2
albums). So, for me, it's working.
mruddo wrote:
>
> If it's a simple question, I was just wondering what the following
> logging is about:
>
> >
Code:
--------------------
> >
> 2022-01-09 17:54:11 D Numtracks = 30962
> 2022-01-09 17:54:14 D Choosing 6 Indie track(s)
> 2022-01-09 17:54:14 D Choosing 5 Rock track(s)
> ...
> 2022-01-09 17:54:18 D Choosing another 968 tracks from DB
> 2022-01-09 17:54:18 D Using subset (1000 of 30962) for setmusicstyle
(chosen from meta db)
> 2022-01-09 17:56:37 I Added 30962 tracks
>
--------------------
> >
>
>
Musly has a setjukeboxstyle function that is given a few (e.g. 1000)
random tracks. It uses this to help with the similarity score - how
exactly I'm not 100% sure, you would need to read the musly docs more,
But, I thought (perhaps incorrectly) that rather than just random tracks
I should have random tracks from each genre - with the number for a
genre dependent upon which percentage of your library it is. You can,
however, configure music-similarity to jsut choose random tracks - see
docs/OtherConfig.md
As stated before, this is not an ready I know much about - so I really
am just throwing things together to see what works.
*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=115609
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
