Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - slonopot

Pages: 12 3
1
Plugins / Re: Beenius - Genius for MusicBee
« on: January 24, 2024, 02:40:53 PM »
Is there a reason the plugin omits certain portions of lyrics?

For instance

https://genius.com/Blink-182-rich-lips-live-lyrics

The retrieved lyrics in musicbee will omit the stage banter at the end

Well, it will not match with default settings. You need to adjust allowedDistance to at least 7 to get a match from Beenius. The reason to this is that MusicBee feels like it knows better and removes all content in round parentheses and that's what gets into lyrics plugins. For example, if you have "blink-182 -- Rich Lips (Live)", Beenius will only receive "blink-182 -- Rich Lips". This will indeed get a match with the link you provided, but this result will be ignored since " (Live)" is a 7 character difference with the original.

With adjusted settings I can see the banter. My guess is that the result you get is from some other plugin, not mine.

2
Plugins / Re: Museexmatch - Musixmatch for MusicBee
« on: November 17, 2023, 08:00:59 PM »
Tested and confirmed. It's behaving exactly as described.

Thanks for testing, the update is now live, anyone interested can grab it here.
I've added two option, one will enable synced lyrics and another will only use synced lyrics from Musixmatch and pass to the next plugin otherwise.

3
Plugins / Re: Museexmatch - Musixmatch for MusicBee
« on: November 13, 2023, 01:25:59 AM »
Having said that, the actual lyrics page at https://www.musixmatch.com/lyrics/Coldplay/Princess-of-China shows the artist as "Coldplay, Rihanna" - with a comma - which should mean that the delimiters config setting should separate the two artists, right?

Any idea why I don't get the lyrics for a situation like this?

That's the main issue with lyrics, I've explained it in detail back in Beenius thread somewhere. In a nutshell, the plugin trims present data as much as possible and compares it against server data with allowed distance which is tolerance to mistakes/inconsistencies measured in characters. In current conditions there's no option to get 100% precision since everything's messed up on "their" side. You may fill as much as possible with default allowedDistance and then increase it to 10-15 and make one more run on your tracks. This will inevitably lead to false positives but you'll be able to clear these out or reload them with another plugin later on when you encounter the error.

In case with Genius there are aliases for each artist and I use them for more precision, but for your particular track it's still a different page for "Coldplay & Rihanna" and there's nothing you can do about it other than editing your data or fixing theirs.

So now I'm wondering, which lyric source was used to grab these (wrong) lyrics, when I don't have any other lyric source enabled? And why didn't it simply return "No changes" like other songs do when they don't get a hit?

It feels like MusicBee is falling back to some other, default lyric source here, and getting the wrong lyrics as a consequence, but I don't know why or how to prevent this. I only want to use Musixmatch via the Museexmatch plugin, and if it gets no result, then I don't want it defaulting to any other source.

Any ideas?

No ideas, lyrics plugins were messed up until recent updates and fixes, try to update your MusicBee to the latest version and see what's happening. Maybe the settings were not saved before you did your check, MusicBee queries all plugins simultaneously and later makes a decision based on priority, something like this. I have Beenius first and Museexmatch second, zero issues since day one.

Last thing is that this is not perfect and never will be, even if the track is matched against Shazam for correct tags and those are used to query lyrics there will be issues. Both my plugins are made for a sole purpose to figure out the lyrics issue as much as possible with minimal effort. I bet on precise hits and leave vague options out of scope, you also have LyricsReloaded that will probably have you covered for almost any bassboosted remix there is, just balance those options as you prefer and you'll be good.

4
Plugins / Re: Museexmatch - Musixmatch for MusicBee
« on: November 12, 2023, 06:31:19 PM »
A while ago, I had directed a user towards you who'd wanted Musixmatch's synced lyrics in MusicBee - not sure if he ever contacted you.
Could you look into it if you ever get the time? I think it'd be a great benefit to MusicBee if you could crack that.

Nope, it's the first time I hear about this.

I guess it's now a matter of MusicBee survival as a product to rearrange efforts from fixing LyricsReloaded to writing useful docs and hints. I've already spent my time writing how it won't work and that we need to create a custom component for synced lyrics to work and then it turned out that lyrics could be LRC and it will just work. Maybe there's also an undocumented way of running MusicBee in the cloud or on a Mac, let me know if it's common knowledge that I'm unaware of.

Advanced LRC (word by word) is not supported but it's available in Musixmatch. I'm not really interested in synced lyrics myself and won't trash my entire library for testing, but you can. This build is configured to prefer synced lyrics if available. Let me know if it works and if it's any good and I'll push it once I have any good feedback.

5
Plugins / Re: Museexmatch - Musixmatch for MusicBee
« on: November 12, 2023, 02:50:35 PM »
My understanding is that trimTitle=true should remove whatever is inside square brackets in the song title, and only search Musixmatch using the remaining text. Therefore it should search for "Princess of China", for example, without including [feat. Rihanna] - is that not correct?

It should indeed and for an unknown reason it doesn't. Make sure to download the latest version again and replace mb_Musixmatch.dll, I've been moving stuff for both Beenius and Museexmatch back in the day and they should now be stored at %APPDATA%/MusicBee/Plugins/ (paste this into your path bar in explorer, by default it's Users/xyz/AppData/Roaming/MusicBee/Plugins/). trim_title is not a default option, maybe your configuration file was not loaded for some reason. Take a look at the first line of the log file, it will say if the configuration file was loaded and which options were applied. If the log states that the defaults were loaded, make sure your configuration file is in %APPDATA%/MusicBee/Plugins/ and that it's museexmatch.conf and not museexmatch.conf.txt or whatever. Ping me if the issue persists.

6
MusicBee Wishlist / Re: MARKDOWN support for lyrics
« on: August 05, 2023, 03:08:23 AM »
Remembering that the decription/markdown must actually appear in what was submitted to Genius, using the Beenius plugin will show it, but be sure that the setting "removeTags": in beenius.conf is set to "false."

In Beenius tags are lines with square brackets that distinguish paragraphs and act like headers, not the markdown. Genius can return lyrics in different formats: dom tree (default), HTML or plain text. Since reading docs first is not an option, I've been parsing just dom and ignoring formatting tags.

Regarding the OP's request, there's no point to make it a built-in feature since MusicBee will be the only software capable of rendering markdown lyrics. It won't cause visual issues unless you export the tracks to any other software, hifi players included. Once these lyrics are open there, you'll see a beautiful unreadable mixture of text, asterisks, underscores and other markdown elements.

Since the request is Genius-related and Steven is not really interested in extending the lyrics API (and it's obvious, it just works), my proposition is that we need Beenius Ultimate that will not be just a lyrics provider but will substitute/extend the lyrics lookup subsystem completely: the plugin will have a distinct lyrics panel with a custom renderer capable of handling markdown, a lyrics lookup core that will get invoked on track changes and lookup lyrics to later convert dom to markdown and save these to a custom tag in a markdown format and in plain format to the default lyrics tag. The lyrics panel should be able to load the formatted lyrics from the markdown tag and use the default one as a fallback.

Complications are:
1. API is not documented, someone will have to take time and thoroughly test this stuff until (and if) it works. We also expect users with custom themes and the panel should look accordingly.
2. Lyrics should be editable, this will need to be cleared of markdown before syncing back to plain lyrics.
3. Some tracks already have lyrics, including already manually edited. This will either remain a fallback and only markdown lyrics will need to be synced or these will have to be cleared.
4. No other providers except Genius care about formatting. I don't expect Genius to limit their API, but there were complaints from dudes who don't understand that Genius was called Rap Genius back in the day and try to query my dude Giuseppe Verdi expecting a ghetto wiki to be conversant in 19th century.

The project looks interesting in terms of deep MusicBee tweaking and might work as a customization example, but the expected user count is minimal. I mean, I have around 3.1k Beenius "downloads" from getmusicbee.com plugin catalogue and it's a main source of traffic according to Github stats. Beenius doesn't have any UI at all since it's all about the main function to configure once and forget about it forever. This thing will need to do more than that and I have zero idea about the number of user interfaces required to make a proper lyrics engine replacement/extension.

As for me, it's an overkill feature and I have no immediate interest in making this a reality. We can run a poll on Github or in the Beenius thread to see the possible userbase and maybe one day someone will have nothing to do and consider making a banger.

7
Plugins / Re: Beenius - Genius for MusicBee
« on: August 01, 2023, 08:34:37 AM »
MusicBee Portable 3.5.8606 P, installed to C:\MusicBee.

As a workaround for your portable setup you can try and create a bat launcher that will override %APPDATA% environment variable with a local folder:

Code
set BAT_DIR=%~dp0
set APPDATA=%BAT_DIR%\PortableData
start /d %BAT_DIR% MusicBee.exe

I haven't tested this, but the approach should be functional. You are expected to manually create a folder tree for PortableData\MusicBee[\Plugins] (which is an alternative to AppData\Roaming\MusicBee[\Plugins]). I guess AppData should be the only place for plugins and user files to prevent further confusion, but it's not up for me to decide so we'll just somehow hack around this and it'll just work for the rest of the days. No more feasible fixes and updates for both plugins in my forecast anyways.

8
Plugins / Re: Museexmatch - Musixmatch for MusicBee
« on: July 31, 2023, 08:56:23 PM »
You should update the start-post to indicate a new version is available. Users may come across this thread, read the first post and download the former version.

If you check the first post of this thread, there is a link to Github releases page which shows the latest release first. The post is made as a notification to those who are subscribed to the thread.

9
Plugins / Re: Beenius - Genius for MusicBee
« on: July 31, 2023, 08:03:53 PM »
My Beenius stopped creating a separate log file since version 1.3.4.  I use MusicBee 3.5.8606 Portable and Beenius 1.3.6.

The log was broken indeed if the plugin is used with Museexmatch or another one that is using NLog. Since all the plugins are running in the same scope, NLog is global as well and is expected to distinguish log targets between different classes. I've attempted to fix this multiple times, this one is final (I hope).

Have you confirmed that any changes you made to the defaults inside the beenius.conf file are still present?  Please post a shot of its contents--it's possible that you may have accidently damaged the syntax in a way that makes it not visible to the dll.

The plugin .dll was working from any Plugins folder, but .conf file was hardcoded to "./Plugins/beenius.conf" since day one. This is expected to be in Program Files and it's not writable. Now it's moved to %APPDATA% and will remain there.

As for the portable version, I guess we've discussed this a certain time ago and by then I've suggested to ask Steven to remap %APPDATA% to something in the portable folder. Don't know how did it end up being, but you always can just manually create MusicBee/Plugins in AppData/Roaming and it should work.

10
Plugins / Re: Museexmatch - Musixmatch for MusicBee
« on: July 31, 2023, 07:54:42 PM »
Fixed the logging issue, moved the plugin to %APPDATA%.
Grab the update here and move the plugin from Program Files/MusicBee/Plugins to %APPDATA%/MusicBee/Plugins.

11
Plugins / Re: Beenius - Genius for MusicBee
« on: July 31, 2023, 07:53:04 PM »
Is there any way I can make Beenius find the configuration file? I don't know what I''m doing wrong, but it never sees the configuration file, and uses the defaults

There is a certain confusion about Plugins folder that I got trapped in since the initial release. MusicBee expects both Program Files and %APPDATA% Plugins folders to function, but by default the Program Files one is not user-writable.

Now the plugin is expected to be working only from %APPDATA%. I also fixed the logger if this plugin is used alongside Museexmatch.
Grab the update here and move the plugin from Program Files/MusicBee/Plugins to %APPDATA%/MusicBee/Plugins.

(%APPDATA% is Users/<>/AppData/Roaming by default)

12
Plugins / Re: Beenius - Genius for MusicBee
« on: July 11, 2023, 01:51:37 PM »
Nevermind, found a computer with Visual Studio. Grab the update here.

13
Plugins / Re: Beenius - Genius for MusicBee
« on: July 11, 2023, 01:30:45 PM »
Can you add some code to remove [Intro], [Verse], and stuff like that

GeniusClient.cs, line 199
Code
result = Regex.Replace(result, @"\[.*\]\r?\n", string.Empty);

or use Museexmatch, it doesn't have these.

14
Plugins / Re: Museexmatch - Musixmatch for MusicBee
« on: January 21, 2023, 09:31:21 PM »
Hello,

I am trying to install this plugin but when I create the configuration file and start up MusicBee I get the following error.

Quote
An error occurred during Museexmatch startup: Access to the path 'C:\Program Files (x86)\MusicBee\Plugins\museexmatch.conf' is denied.

The plugin can't write to the config file, this issue is exclusive to this plugin. The plugin gets a user token from Musixmatch and saves it into the config file.

You can install the plugin into %AppData%\MusicBee\Plugins as @boroda have already suggested, this folder is writable. You can simply unpack the zip there and restart MusicBee (but you can't have dlls in both places so remove them from Program Files first).

As an alternative workaround you can either start MusicBee as admin or change permissions for the Plugins folder (RMB on the folder, Properties tab, Edit..., Users group, Allow full access with the checkboxes). You can do the same for the config itself.

I think I've changed permissions on my side before even thinking of developing this plugin and that's why I had not encountered the issue myself.

15
Plugins / Re: Museexmatch - Musixmatch for MusicBee
« on: January 08, 2023, 11:27:17 PM »
I'm currently experiencing an error when trying to install this and Beenius. Not sure if I'm doing anything wrong. Both plugins are added to C:\Program Files (x86)\MusicBee\Plugins. Not sure if I'm doing something wrong or if the plugins are not working anymore?

They show up in MusicBee. When trying to enable them I get the same error:

Code
"Unable to initialise plugin: *plugin_name*
"Exception has been thrown by the target of an invocation."

Make sure to drop all included dlls straight into the Plugins folder and not into a subfolder. You may keep/replace the external dlls with no issues.

Pages: 12 3