MediaMonkey on ubuntu (or linux)

[bougie]

I'm still a beginner. how to use MM in linux. using wine, I'm still worried about using the database (install database).

[ttdijkstra]

Please make a native MediaMonkey application for Linux.

[Dancer]

Recently I installed the program Musescore as AppImage in Linux Mint. Could it be that it is also easier for you MediaMonkey developers to offer MM as AppImage? I imagine that it needs less code adjustments than a standard installation.

[Timo_Beil]

I imagine that it needs less code adjustments than a standard installation.

I'm afraid your imagination is deceiving you.
AppImages are pure Linux programs designed to make things easier for the USER. All dependencies are packaged there, so that the programs (should) run on any distribution without installation from a dedicated package source.
That would be a second step, after compiling the highly anticipated linux build.

[CosmicKnowledge]

Please make a native MediaMonkey application for Linux.

I second this (and have been doing so for years). MM is the best music manager but Windows is spyware for big-tech, AI, and the government. No version of Windows is safe. I've gone 100% linux now but I'm screwed with respect to MM. I found a guide here: https://www.mediamonkey.com/wiki/index. ... y_.2B_Wine
It's ridiculously complex and probably horribly outdated.

Surely the MM developers can create a profile for Bottles where all the settings are defined for the customer and the user just needs to run the installer? FYI, Bottles is a user friendlier GUI for Wine. This is a great time to get away from the Windows sinking ship. With Co-Pilot, Windows has turned into the enemy of privacy because it allows absolute government/corporate surveillance. Now they're regressing their words saying that co-pilot will be local to the machine but remember that Windows already has deep Telemetry hooks everywhere and Micro$oft *will* lie, they will use technicalities to effect their surveillance objectives. So, there's no better time to switch to Linux and to get MM running in Linux. Linux Mint is the easiest distro for most people .

[Intraspectre]

I am also eagerly awaiting a Linux release. I have not been able to get MediaMonkey working properly with Wine, or by using Lutris/Wine with various versions of Proton. It throws an extremely unhelpful error at launch ("Not implemented". That's literally the entire error.) which does not prevent the application from running, but if you try to actually do anything most of the GUI elements will go black and it becomes unusable within a few seconds. I've tried messing with every setting to do with the GUI and hardware acceleration both within MediaMonkey (which I can manage in the few seconds of functionality I get) and Wine but nothing changes.

I have MediaMonkey running in a Windows VM of course, but all the extra setup required to share my music files with the VM and then have the server actually work for syncing to my phone means it's quite a bit easier for me to just boot into my Windows installation instead. It's maddening that I can play just about every video game I want on Linux with zero extra steps or hassle but MediaMonkey is so broken even with cutting edge compatibility tools, wasn't the whole idea of MM5 that it was cross platform?

[PoooMukkel]

Yesterday I installed MediaMonkey v5 in Bottles. I created an application bottle, installed all Microsoft fonts and MediaMonkey works. It opens and after adding my DB the collection is visible. But when trying to play a song, nothing happens. I don't know why. Maybe a codec is missing? Have to investigate further ...

[Peke]

In MM options Output plugins use WAVEOUT and it should work.

[PoooMukkel]

it should work.

I already tried that, but sound is still not playing. The issue seems to be, that playing doesn't start. Time isn't running. But the songs are there. They exist.

[Peke]

Hi,
Have you tried to use other input plugins (Extract MMIPs from my happymonkeying site?)

Also a full debug log as described at https://www.mediamonkey.com/forum/viewtopic.php?t=86643 should show us what is going on.

[PoooMukkel]

Have you tried to use other input plugins (Extract MMIPs from my happymonkeying site?)

Just installed the OPUS Plugin from your HappyMonkying-Site. Seems to be the only plugin working on v5. No changes.

Also a full debug log as described at https://www.mediamonkey.com/forum/viewtopic.php?t=86643 should show us what is going on.

Just wanted to download the latest debug version of MM2024. Is my lifetime license working with this version? It seems that there will be special MM2024 license keys?

[Lowlander]

Lifetime Licenses work on MediaMonkey 2024.

[Peke]

Just installed the OPUS Plugin from your HappyMonkying-Site. Seems to be the only plugin working on v5. No changes.

Rename downloaded MAD input plugin (for example) -> Rename MMIP to ZIP -> Extract DLL to MM plugins folder and restart MM it should be there.

[PoooMukkel]

Lifetime Licenses work on MediaMonkey 2024.

Good to know.

Rename downloaded MAD input plugin (for example) -> Rename MMIP to ZIP -> Extract DLL to MM plugins folder and restart MM it should be there.

I'll try it ...

[TIV73]

I've had little to no success getting mediamonkey in a usable state with wine or bottles. Crossover fared way better right off the bat, and I got the application in a semi-stable state with close to no effort. The biggest issue that persists for me is are occasional, and seemingly random, hard crashes with the `not implemented` error that were mentioned before. When doing a quick trace in wine it looked like these errors come mostly from two different sources.

The first one is networking. I noticed that whenever mediamonkey wants to do a network call and it doesn't work for whatever reason, the error occurs. I guess it's some outgoing calls where mediamonkey tries to check for updates, query local upnp devices, or something along those lines. Turning off the local firewall to open all ports before starting mediamonkey greatly reduced these errors. It's not ideal, but at least a starting point.

The second one seems to be, and I could be totally wrong about this, related to oledb calls. I have no idea if that's correct or not, and if mediamonkey even uses oledb to talk to its database or not, but judging from the logs wine seems to think so.

If we just need to find the right dependencies to make everything work, or if some calls are just not yet implemented by wine is anybodies guess, though.

Another thing that makes matters more complicated is the frontend mediamonkey uses. From what I can tell chromium (and by extension cef) has traditionally been a little rocky to get working on wine, for various reasons. It doesn't help that chromium already runs natively on linux, as do most framework that depend on the engine, like electron. Applications like mediamonkey that rely on the chromium engine but are strictly windows-only are, in the grand scheme of things, outliers, so there is also not much incentive or huge push from wine to get chromium to run better.

There are various proposed workarounds related to hardware acceleration, passing startup parameters to chrome (which is not applicable in our case), setting different desktop modes, switching between xorg and wayland, or getting different hardware. It's all very trial-and-error.