Hi Craig,
thanks a lot for driving this plugin and your work on Material and
everything else in the Squeezebox area.
I used an earlier version of you music-similarity plugin, before you
made it public (via Github - I was interested in this "mysterious new
project...". So far that version worked
Awesome reply. When I get a chance I will give it another shot. Thanks
shinedou's Profile: http://forums.slimdevices.com/member.php?userid=72027
View this thread: http://forums.slimdevices.com/showthread.php?t=112713
shinedou wrote:
> Anyone got some pointers on getting this up and running? I have a Fedora
> 34 VM with cmake and ffmpeg-devel installed. This VM is not on my LMS
> server which I'm not clear is required. I am trying to get the musly.git
> compiled and I believe I got it. I was able to run the t
Anyone got some pointers on getting this up and running? I have a Fedora
34 VM with cmake and ffmpeg-devel installed. This VM is not on my LMS
server which I'm not clear is required. I am trying to get the musly.git
compiled and I believe I got it. I was able to run the test mentioned in
the musl
afriend wrote:
> What's the difference between '-Create Similarity Mix-' and '-Similar
> tracks-' if I call them on the same track (other than the number of
> added tracks)?
'Similar tracks' has no filtering on artist, genre, etc, and allows
repeated artist, album, etc. - whereas a mix has filt
cpd73 wrote:
> Added 'Similar tracks' and 'Similar tracks by artist' to 'More' menu.
Thanks.
What's the difference between '-Create Similarity Mix-' and '-Similar
tracks-' if I call them on the same track (other than the number of
added tracks)?
Are the results of '-Similar tracks-' or '-Simil
afriend wrote:
> Therefore I thought maybe you could just register 2 similarity DSTM
> mixers: 1 without and 1 with enabled genre filtering.
Done.
afriend wrote:
>
> I'm really using Musly/Similarity a lot right now and sometimes I wish
> there were other ways to use the similarity score/mus
cpd73 wrote:
> [Edit] Changed default to 30 seconds.
I did actually change exactly that value in your code for testing. You
probably won't believe this (I wouldn't) but even though logic dictates
otherwise in the end I wasn't able to get rid of this timeout problem
until I set timeout: 30 in the
afriend wrote:
> Good news is that I may have 'fixed' my song mix/timeout problem for
> now. Your Similarity code suggests that you'd planned to make the
> '*getjsondata timeout value*'
> (https://github.com/CDrummond/lms-musicsimilarity/blob/master/MusicSimilarity/Plugin.pm#L271)
> a configurabl
Thank you for adding that option. I'm a bit of a serialskipper
sometimes. This setting will also help prevent me looping back to the
beginning of the playlist when I skip too many tracks before enough new
tracks have been added. Even if it wasn't intended to do that :-)
And you're right, my hard
afriend wrote:
> I've been using Similarity a bit more. I like it. Far better than random
> mixes.
Glad you like it :)
afriend wrote:
> Can I just ask about genre filtering: if I create only *one* genre
> filter group for Classical music genres does this mean that if I start a
> mix with *no*
I've been using Similarity a bit more. I like it. Far better than random
mixes.
Can I just ask about genre filtering: if I create only *one* genre
filter group for Classical music genres does this mean that if I start a
mix with *no* classical music seed tracks does it mean that this mix
will co
cpd73 wrote:
> Changing 'styletracks' requires the jukebox file to be *removed*, but
> this only takes a minute or so to be recreated.
Sorry, misread that one. Wasn't necessary. And I did it anyway. :-)
If I could ask one thing in some future update it would be -debug log
markers- that tell me
afriend wrote:
> Thank you for letting me know (was using the default 1000). Do you know
> how many tracks that bug affects?
It only affects the similarity function, not the analysis. When broken
all similarity checks return the same value. To fix you delete the
jukbox and recreate with a diff
cpd73 wrote:
> Just to let you know, Musly has a 'bug'
> (https://github.com/dominikschnitzer/musly/issues/43) where sometimes
> all songs get the same similarity score. I noticed this last night after
> I did a complete rescan. My mixer produced odd results, and they were
> all from the first a
afriend wrote:
> Anyway, I'll probably need a couple of months before I can say anything
> on how much I like the results musly provides. Thank you for your help
> and scripts/plugins.
Just to let you know, Musly has a 'bug'
(https://github.com/dominikschnitzer/musly/issues/43) where sometimes
afriend wrote:
> Are album style tracks kept in the musly.db or in musly.jukebox?
> I know the jukebox is supposed to make the start of musly faster but on
> the other hand it seems that the whole musly.db is kept in RAM. So once
> the db is in RAM is the jukebox still in play? Maybe I have the
afriend wrote:
> BTW if I import new music into LMS will musly-server recreate all album
> style tracks from zero? Or just for new tracks (cleaning up possible
> dead tracks in the process)? Are album style tracks kept in the musly.db
> or in musly.jukebox?
On subsequent analysis runs, new trac
Ok, so now the musly-server is up and running on macOS. The guide and
binaries are 'here' (https://github.com/AF-1/sobras).
BTW if I import new music into LMS will musly-server recreate all album
style tracks from zero? Or just for new tracks (cleaning up possible
dead tracks in the process)? Ar
afriend wrote:
> Ok, done. I'll put this on hold until you've found the time to do your
> tests.
Updated code seems to work.
*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 qu
afriend wrote:
> Ok, done. I'll put this on hold until you've found the time to do your
> tests.
Musly needs to be initliased with a random selection of about 1000
'style' tracks - which, I think, lets it know the style of music you
have. I thought rather then just random, I'd pick 1 random tra
Ok, done. I'll put this on hold until you've found the time to do your
tests.
Would be nice if the database file I have so far (almost all tracks =
analyzed) could be reused with the new/revised code.
Thanks for looking into this.
---
I've just made some quick, and untested, changes that should resolve
these issues. I need to re-run an analysis from scratch to be sure but
can't do this at the mo.
*Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json
(Use http: //SERVER:9000/material/?debug=json,cometd to
afriend wrote:
> Just a quick question:
> I'm now at a stage in the analysis process where there's no more HDD
> read access but the python process is still doing something (100% on one
> core) (no freeze).
> The debug log hasn't moved past these message for quite a few hours:
Hours??? I'd canc
afriend wrote:
> Just a quick question:
> I'm now at a stage in the analysis process where there's no more HDD
> read access but the python process is still doing something (100% on one
> core) (no freeze).
> The debug log hasn't moved past these message for quite a few hours:
> >
Code:
---
Just a quick question:
I'm now at a stage in the analysis process where there's no more HDD
read access but the python process is still doing something (100% on one
core) (no freeze).
The debug log hasn't moved past these message for quite a few hours:
Code:
DEBUGSel
afriend wrote:
> Created the OS PR.
Thanks, merged.
afriend wrote:
> I see you've changed to extraction length to 30s. Will it distort the
> result of my ongoing analysis by much or at all if I stop the process
> now, change the value from 60s to 30s and then continue? Would love to
> save so
Created the OS PR.
I see you've changed to extraction length to 30s. Will it distort the
result of my ongoing analysis by much or at all if I stop the process
now, change the value from 60s to 30s and then continue? Would love to
save some time.
And I was actually thinking mostly of NUM_PREV_TR
afriend wrote:
> BTW does it fill the metadata at the end because a first look at the
> musly.db (in progress) shows the relative path (files) and the values
> (vals) but the other metadata columns are still empty.
Yeah, meta-data is saved at the end.
afriend wrote:
> Good to know. So if I do
cpd73 wrote:
> My code does not touch the LMS db, it creates its own SQLite database.
> Therefore, I wanted a quick way to update this database to reflect and
> metadata changes in my files. When doing this the script just reads the
> tags and updates the DB for any changes.
I keep my music file
cpd73 wrote:
> Not sure, never used Roland0's script. I used (well copied and modified)
> Roland0's musly.py which interfaces Python->libmusy.so Musly does not
> process the whole track, but only a portion. One of the changes I made
> was how much to analyse - Roland0's is 30seconds, mine 2 minu
afriend wrote:
> 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'
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
afriend wrote:
> >
Code:
> >
> File "/Users/defuser/Documents/musly-server-master/lib/musly.py", line 31,
in __init__
> ctypes.CDLL(libmusly.replace('libmusly.so', 'libmusly_resample.so'))
> >
Perhaps "libmusly.replace('libmusly.so', 'libmus
afriend wrote:
> So I've compiled musly on macOS 10.15. No errors, some deprecation
> warnings (libavformat and such...).
Sorry, I don't use macOS - so really can't help much. If/when you get
this working, I have moved the LMS side from 'lms-muslymixer'
(https://github.com/CDrummond/lms-muslymi
So I've compiled musly on macOS 10.15. No errors, some deprecation
warnings (libavformat and such...).
But when I try to run anything Python3 I get
> ./musly-server.py --analyse /Users/defuser/Music/MEDIA/
> Traceback (most recent call last):
> File "./musly-server.py", line 33, in
> mus = musl
cpd73 wrote:
> There's no rush - I'm not actively working on this. Still, it'd be nice
> to know how it works for others. I still prefer MusicIP, but the Musly
> analysis is so much faster!
The speed is indeed the main attraction point here. MusicIP is a rather
heavy workflow for adding new musi
bakker_be wrote:
> I think the issues I'm having are related to my Ubuntu install dating
> back all the way to 14.04 and having been upgraded each time to the
> newer version when it came out. I've been having some other issues,
> unrelated to the LMS ecosystem, so I think the time for a clean i
I think the issues I'm having are related to my Ubuntu install dating
back all the way to 14.04 and having been upgraded each time to the
newer version when it came out. I've been having some other issues,
unrelated to the LMS ecosystem, so I think the time for a clean install
has finally come ;)
gorman wrote:
> Question: where is the "similarities info" saved? Into a single file
> library? Separate file for each music file? Tags?
> I don't want to mess with tags in my music.
Two files are created; an SQLite db that stores some meta-data and a
binary blob containing the musly data for e
Question: where is the "similarities info" saved? Into a single file
library? Separate file for each music file? Tags?
I don't want to mess with tags in my music.
gorman's Profile: http://forums.slimdevices.com/member.php?
cpd73 wrote:
> Something is broken on your 18.04 install. I've just created an 18.04VM,
> and unzipped the 0.0.1 release - this works. I hacked the musly.py file
> as I have not built musly, so removed all the main functionality. Still,
> musly-server.py starts just fine. Very odd.
OK, I'll try
cpd73 wrote:
> OK. I'm creating an Ubuntu 18.04 VM so will check with that.
Something is broken on your 18.04 install. I've just created an 18.04VM,
and unzipped the 0.0.1 release - this works. I hacked the musly.py file
as I have not built musly, so removed all the main functionality. Still,
m
bakker_be wrote:
> Oh damn, no ... Stupid typo, should've been this DIDN'T resolve the
> issue!!!
OK. I'm creating an Ubuntu 18.04 VM so will check with that.
*Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json
2. Open browser's developer tools 3. Open console tab in dev
cpd73 wrote:
> So, the first (path) mod works? If so I'll update the code.
Oh damn, no ... Stupid typo, should've been this DIDN'T resolve the
issue!!!
Main System: Touch; Marantz SR-5004 + TMA Premium 905 + TMA Premium 901
+ Teufel Ultima 20 Mk 2 + BK Monolith+ FF + Lenovo T460 + Kodi + Pio
bakker_be wrote:
> EDIT: I first modified the code as you suggested. This resolve the
> issue. I've then changed the names of the files (and modified the
> musly-server.py accordingly of course), still no luck :(
So, the first (path) mod works? If so I'll update the code.
*Material debug:* 1
cpd73 wrote:
> Ah, is it just 'app' that has the error? If so what if you rename app.py
> to (e.g.) muslyapp.py and use "from lib import muslyapp, config,
> metadata_db, musly, analysis" ???
It's not only app. Initially analysis was first in the line of imports
(you had it alphabetically, struc
bakker_be wrote:
> Hmmm, running into a bit of bother with the musly server ...
> >
Code:
> > bart@ubuntu_t540:~/musly-server$ ./musly-server.py -l DEBUG --analyse
/mnt/music
> Traceback (most recent call last):
> File "./musly-server.py", line 13, in
> from lib
bakker_be wrote:
> Hmmm, running into a bit of bother with the musly server ...
> >
Code:
> > bart@ubuntu_t540:~/musly-server$ ./musly-server.py -l DEBUG --analyse
/mnt/music
> Traceback (most recent call last):
> File "./musly-server.py", line 13, in
> from lib
bakker_be wrote:
> EDIT: I'm now on 3.8.5, thanks to a PPA, it's not present in the default
> repositories, and I still have the same error ...
Hmm, OK I'll see what I can do - but I'm not really a python coder.
*Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json
2. Open
cpd73 wrote:
> Odd. I don't use Ubuntu, but Fedora32 (I used Ubuntu for years, but
> switched due to 'snap' apps). Which version of python3? Fedora32 has
> 3.8.5, and Raspbian (which also works for me) has 3.7.3
>
> Does "python3 ./musly-server.py -l DEBUG --analyse /mnt/music/" Work???
This is
bakker_be wrote:
> Hmmm, running into a bit of bother with the musly server ...
> >
Code:
> > bart@ubuntu_t540:~/musly-server$ ./musly-server.py -l DEBUG --analyse
/mnt/music
> Traceback (most recent call last):
> File "./musly-server.py", line 13, in
> from lib
Hmmm, running into a bit of bother with the musly server ...
Code:
bart@ubuntu_t540:~/musly-server$ ./musly-server.py -l DEBUG --analyse
/mnt/music
Traceback (most recent call last):
File "./musly-server.py", line 13, in
from lib import app, config, metadata_db,
Will test this one as well :)
Main System: Touch; Marantz SR-5004 + TMA Premium 905 + TMA Premium 901
+ Teufel Ultima 20 Mk 2 + BK Monolith+ FF + Lenovo T460 + Kodi + Pioneer
PDP-LX5090H
Workshop: iPad 32GB Wifi + Squeezepad (local playback activated)
Wherever needed: Acer Iconia Tab A700 + Sq
cpd73 wrote:
> This is a DSTM mixer that uses 'Musly' (https://www.musly.org) to obtain
> 'similar' tracks to 5 seed tracks. I started this plugin as MusicIP
> takes a *long* time to analyse files (and is closed source), whereas
> Musly is *much* faster (and open source) - ~20k tracks took about
55 matches
Mail list logo
