I had already replaced that part. In the end I had to "bake" the -absolute- path of -libmusly*_resample*.dylib- into libmusly.dylib.
Before I start more tests on my main library may I just ask some questions because I'm really new to this. The value (analysis result) for a track in the musly.db is different from the one Roland0's script (LMSmusly-0.1.1) generates. I don't know much about the underlying models used to compute the similarity score. Do you use different settings? Also, could it be that Roland0's script is a bit faster or is yours just more thorough? If I put all the paths into the configure.json I just need "-a m" to analyze the music files, right? And what does "*only* updating the *metadata* database" do as opposed to "-a m"? Just remove dead tracks musly couldn't find in the LMS database? About jukebox and LMS/musly startup time: your script seems to (auto-)create a jukebox. Does it use the jukebox automatically? In general, how long does the start of (lms)musly take? I'm only asking because Roland0 said that with a large number of tracks in the database the startup time of lmsmusly would increase significantly. And finally, I've notice that "create similarity mix" doesn't show up in the LMS default web UI. Is this by design? Thank you. P.S. If it all works out I'll leave the macOS binaries and some instructions 'here' (https://github.com/AF-1/sobras). ------------------------------------------------------------------------ afriend's Profile: http://forums.slimdevices.com/member.php?userid=39306 View this thread: http://forums.slimdevices.com/showthread.php?t=112713 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
