Author Topic: Museexmatch - Musixmatch for MusicBee [+ synced]  (Read 29816 times)

sveakul

  • Hero Member
  • *****
  • Posts: 3268
AH HAH!!!
Looking at the log I see that it says "No configuration file was provided, defaults were used." Okay, that explains the behavior I'm seeing even though I've edited the .conf file. I first placed it in G:\MusicBee\Plugins and when that didn't work I placed it in G:\MusicBee\AppData. Since the .conf file isn't recognized in either of those locations, I have to ask, where should it be? If it needs to be somewhere in C:\Users\phred\.... that's not what the readme says. It says all four files go in the Plugins directory.

So now that we know what the problems is, how do I fix it?
phred you shouldn't be having all these problems;  follow this step-by-step please:

1.  First, exit MB, and delete all the existing museexmatch 1.06 files so we're all on the same sheet of music;  also flush the MB lyrics cache with that script I posted a while ago that you did use.

2.  Download a fresh copy of Museexmatch 1.06 (https://github.com/slonopot/Museexmatch/releases/download/v1.0.6/Museexmatch_v1.0.6.7z).

3.  Extract the 3 DLL files Nlog.dll, ToptenJsonKit.dll, and mb_Museematch.dll into your MB Portable's "Plugins" directory, G:\MusicBee\Plugins.  Note:  if you are using the LRCLIBee plugin it has newer versions of the first 2 DLLs so it's best to decline an overwrite offer of those.

4.  The 4th file in the zip, "museexmatch.conf.template" needs to be extracted to this location OUTSIDE of your MB Portable directory: (your OS drive):\Users\(username)\AppData\Roaming\MusicBee\Plugins.  Create the last two folders if necessary.  This procedure is needed because you (like me) have a non-Installer version of MB--the Readme was only referring to Installer versions.

5.  Drop the "*.template" off of museexmatch.conf, open in Notepad and instead of deleting anything just change the values to read:
Code
{
  "allowedDistance": 5,
  "delimiters": [ "&", ";", "," ],
  "verifyAlbum": false,
  "addLyricsSource": true,
  "trimTitle": true,
  "preferSyncedLyrics": false,
  "onlySyncedLyrics": false
}
As I mentioned before a "userToken" line will be automatically added after first use, just leave that line as-is.

6.  Select Museexmatch as a source in Prefs/Tags(2), open MusicBee, and let 'er rip!  I promise, you WON'T get synced lyrics!  Thanks to slonopot for this great API plugin.

Last Edit: July 08, 2024, 09:18:35 AM by sveakul

slonopot

  • Jr. Member
  • **
  • Posts: 95
It's possible to have DLLs in Plugins folder for the portable setup, but the configuration should now be placed in appdata on C: drive.

This plugin will support portable setups at fullest with the next update, coming soon™

phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 10269
phred you shouldn't be having all these problems;  follow this step-by-step please:
I agree 100%. And I thank you for providing a step-by-step. But it shouldn't be this difficult. Yet sadly, it is. I have followed your instructions exactly with the same results as yesterday.
Among the continued issues...

1- no source listed at top of retrieved lyrics


2- time stamped (synced) lyrics retrieved and no non-time-stamped lyrics retrieved



3- only this plugin enabled in Tags (2)


4- users\phred\appdata\roaming\musicbee contains the conf and log files


5- copied your quoted conf text over the default


6- log shows no config file found


7- confirmed that three DLLs are in G:\MusicBee\Plugins

8- confirmed that .conf is in users\phred\appdata\roaming\musicbee

Where do I go from here?
Download the latest MusicBee v3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Custom Forum Search
Posting screenshots is here

slonopot

  • Jr. Member
  • **
  • Posts: 95
We as a society should start charging average portable version enjoyers per thousand characters at this point.

I've bumped Museexmatch with new stuff from lrclibee, portable support and metadata extraction included. Use this version, put your conf into AppData for portable and we should be good for next year or so.

phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 10269
We as a society should start charging average portable version enjoyers per thousand characters at this point.
Funny. I feel the same way about people who use the Store or Installer versions. :-)
Forcing users of Portable versions to place files in directories other than the one where the app is installed, defeats the purpose of it being portable.

Quote
I've bumped Museexmatch with new stuff from lrclibee, portable support and metadata extraction included. Use this version, put your conf into AppData for portable and we should be good for next year or so.
Sounds good. I will remove all traces of the previous non-working version and try again. If it works as it's supposed to, great. Otherwise I'll just wait for Mayibongwe to correct the Musixmatch issue in his Lyrics Reloaded plugin.

Thanks for the time you've put into this. Here's hoping this version is a keeper.
Last Edit: July 08, 2024, 05:57:26 PM by phred
Download the latest MusicBee v3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Custom Forum Search
Posting screenshots is here

slonopot

  • Jr. Member
  • **
  • Posts: 95
Forcing users of Portable versions to place files in directories other than the one where the app is installed, defeats the purpose of it being portable.

There are two ways to make stuff portable: a proper one and the wrong one. I mention %APPDATA% every time and don't mention C:/users/<you>/appdata/roaming for a reason. %APPDATA% is a variable and it can be changed by the program. What a developer expects from the program is consistency and general compatibility: there's always some %appdata% that could be used for storage. Since there's very little documentation to the API and it's more like trial and error, first and subsequent plugin versions were %appdata%-aware, but the portable version does not rewrite %appdata% to the one in the directory, there's actually a separate API function that I initially overlooked that will give us, well, appdata for storage. Why can't we have nice things and just use %appdata%? I dunno, not my design choice. That's not expected, poorly documented, but now it's used and you should be just fine, I tested it with a portable setup before publishing.


phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 10269
Not being a programmer, but always reading this forum and others, I do indeed know that MB's API has little documentation. Docs and the API in general could be improved. I give Steven credit for adding to the API when someone is trying to create a plugin for which an additional element is needed. So my thanks go to you, Steven, and all the others here who have created plugins.

And now for the big reveal: EUREKA!!! The new version works as expected. And all files are now in MB's AppData directory including the log file.

Thank you!
Download the latest MusicBee v3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Custom Forum Search
Posting screenshots is here

sveakul

  • Hero Member
  • *****
  • Posts: 3268
8- confirmed that .conf is in users\phred\appdata\roaming\musicbee
Where do I go from here?
So much for the step-by-step method;  at the risk of sounding blunt, the problem is you weren't following instructions.
As I explained a couple of times and in Bold, the .conf goes into users\phred\appdata\roaming\musicbee\plugins, not users\phred\appdata\roaming\musicbee.

Well I guess the "new version" is more friendly about all this and I'm glad you finally have Museexmatch working.

phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 10269
at the risk of sounding blunt, the problem is you weren't following instructions.
As I explained a couple of times and in Bold, the .conf goes into users\phred\appdata\roaming\musicbee\plugins, not users\phred\appdata\roaming\musicbee.
When I'm running into a wall with an issue, I don't might someone being blunt when they're attempting to get me to see the light of day.

But in my defense (and there's no way you could've known this) I -was- putting the .conf file in the proper directory. What I didn't do was type the path correctly into my post. I typed the full path with the exception of the last directory: plugins. <sigh>
Last Edit: July 15, 2024, 02:58:26 AM by phred
Download the latest MusicBee v3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Custom Forum Search
Posting screenshots is here

bkev

  • Jr. Member
  • **
  • Posts: 70
I really like this but I've noticed there is a tendency for the non explicit lyrics to be chosen.

Is there any way to prefer the "Non Clean" or "Explicit" version of lyrics?

slonopot

  • Jr. Member
  • **
  • Posts: 95
I really like this but I've noticed there is a tendency for the non explicit lyrics to be chosen.

Is there any way to prefer the "Non Clean" or "Explicit" version of lyrics?

Examples?

bkev

  • Jr. Member
  • **
  • Posts: 70
Tend to see it if there are 2 versions of an album, a clean and explicit.

Sometimes the lyrics is like this

f---

Or sometimes it's the clean lyrics, like

And the skeletons in both our closets.
Plotted hard to mess this up

Instead of the explicit version of the lyrics.

slonopot

  • Jr. Member
  • **
  • Posts: 95
Tend to see it if there are 2 versions of an album, a clean and explicit.

I meant to ask for track examples that have two versions on musixmatch, but I managed to google your lyrics to get Taylor Swift -- cowboy like me.

Yes, there are two versions, and when I search this exact track I get an explicit version first and that should get you a correct result. I can filter the results to be explicit, it will be better.

I'd like to see more examples to make sure that there are occasions when the "polite" version is returned first. If they exist, I'll make an update.

bkev

  • Jr. Member
  • **
  • Posts: 70
Ok thanks for replying and testing.

It seemed to get the polite version quite a bit more for me but I don't have any example at the moment.

I'll keep testing and if I come across any I will let you know.

Moshi_

  • Full Member
  • ***
  • Posts: 135
  • http://www.last.fm/user/Moshi_
I am pretty sure I have files in right places. But log says no config file provided and when defaults are used the log says preferSynced=true and even then I get non-synced lyrics in MusicBee even though they are synced on MM website.



Edit:
log file now shows that config file was found and used. But I put the museexmatch.conf file in the C:\Users\ - \AppData\Roaming\MusicBee not C:\Users\ - \AppData\Roaming\MusicBee\Plugins!
Last Edit: October 12, 2024, 05:54:53 PM by Moshi_