Home of the Squeezebox™ & Transporter® network music players.
Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13
  1. #11
    Senior Member
    Join Date
    Mar 2017
    Posts
    3,225
    Quote Originally Posted by mruddo View Post
    Looks like I need to see if I can find some time to enable the Musly analysis on a PC.
    If you do checkout the code, use the 'lowlevel' branch for music-similarity and lms-musicsimilarity. This will only use Essentia for BPM, Key, and 'danceability' - and you should be able to use the pre-compiled binaries from https://similarity.acousticbrainz.org/download. Then you should only need to compile the Musly library.
    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.

  2. #12
    Thanks for the information... much appreciated. I'd love to have a go at something in this space - just can't commit to any timescales as free time is short at the moment.

  3. #13
    Senior Member
    Join Date
    Mar 2017
    Posts
    3,225
    Quote Originally Posted by cpd73 View Post
    Then you should only need to compile the Musly library.
    I've added a pre-built windows DLL for Musly. This is a bit hacky as compiling the ffmpeg libraries (required to decode audio files) was too much hassle. So, this windows version of Musly does not link to the ffmpeg libraries but instead calls out to the ffprope and ffmpeg executables to do the audio decoding, etc. I used MinGW32 to compile Musly - and this produces a 32-bit DLL, therefore a 32-bit version of Python3 will be required. You also need to download the windows ffmpeg/ffprobe executables - but you can get these from https://github.com/BtbN/FFmpeg-Builds/releases

    Note, I only tested my windows DLL on one MP3 file but it should be fine.

    [Edit] 64-bit DLLs also added.
    Last edited by cpd73; 2021-12-06 at 10:16.
    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.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •