Again, I just happy to know that you wonderful people are working on a Mac version!

[quote=Bakoes post_id=532693 time=1776843459 user_id=126485]
Doesn't this mean that MM 2027 for MAC,
will also be functional on Windows ánd Linux ???
[/quote]I must say that ChatGPT got most things correct, bit simplified, but core meaning is correct. Let me clarify few points.

re 1) This is true. MM4 and Earlier were dependent on Windows Frameworks and libraries like UI even MM3/4 used Early versions of Delphi FireMonkey® framework (eg. Eugene Kryukov KSDEV Theme Engine) and as of MM5 MM UI is rewritten to use Chromium (HTML5+CSS+JS)and we switched from VBS (Visual basic Script) Windows exclusive to JScript (JavaScript)

re 2) Totally true MM5/2024 is transition to fill the gaps and polish 20 Years of developing before real Cross platform releases gets started.

re 3) True, good assumption but except I would instead "If a Mac version is released" I would say "When Mac version gets released" and leave rest as as is.

re 4) Mostly true except that Mac also supports X11

re 5) Mostly true but I would say things bit different eg. “... First time the same core application exists ... ” ->
"... First time the some core application features uses most of source code in order to work and behave same ..."

I also agree with rest but would state like this:
"Cross-platform rewrite = technical capability where many core functionality source code can be re used on multiple platforms and fixes on one in most cases also fix same thing on other platforms
Windows support = exists and now uses non platform dependent libraries
Mac release = another realized platform were core functionality shares same behavior, features and many source code from originally developed platform
Linux support = still considering, not guaranteed and many Linux development stalled across all Delphi developed applications not just MM as Delphi lost one of fathers of Cross-Platform UI developers https://blogs.embarcadero.com/eugene-kryukov-father-of-firemonkey-and-incredibly-talented-developer/ and till recently many of his contributions could not be downloaded till legal things are not settled.

Personally I would really like to see how much of MM source code can be compiled on Linux, but not ATM as there is so much work on MM for MAC (MMM)

[quote=Lowlander post_id=532664 time=1776532713 user_id=262]
MediaMonkey 5 was the complete rewrite for cross-platform compatibility. MediaMonkey 2027 for MAC will be the first cross-platform release.
[/quote]

Doesn't this mean that MM 2027 for MAC,
will also be functional on Windows ánd [b][u][i]Linux [/i][/u][/b]???

[b][u]EDIT: I asked ChatGPT[/u][/b]
Your reasoning is understandable, but there’s a subtle distinction between “cross-platform architecture” and “actually shipping on all platforms.”

1) What “cross-platform rewrite” really means
When the developers of MediaMonkey say version 5 was rewritten for cross-platform compatibility, they mean:
The internal codebase is designed so it can be adapted to multiple operating systems
It reduces Windows-specific dependencies (e.g., UI frameworks, APIs)
It makes future ports (Mac, Linux) feasible, not automatic
This is a software engineering decision, not a release guarantee.

2) Current reality (important context)
As of now:
MediaMonkey 5 / 2024 is Windows-only
There is no native Mac or Linux version yet
Cross-platform support is still described as “preparation” rather than delivery

3) What “MediaMonkey 2027 for Mac” implies
If a Mac version is released, it means:
They successfully ported the app to macOS
The cross-platform groundwork paid off
But it does NOT automatically imply:
A Linux version exists
A unified binary runs everywhere
Or that all platforms are released simultaneously

Each platform still requires:
Testing
UI adjustments
Packaging and distribution
Ongoing maintenance

4) Why Mac ≠ Linux (even in “cross-platform” apps)
Even with a shared core:
macOS uses Cocoa / Swift / Metal APIs
Linux uses GTK / Qt / Wayland/X11
Hardware access, drivers, and packaging differ significantly
So supporting Mac does not automatically translate to Linux support.

5) Practical interpretation
Your statement: “First cross-platform release”
Most likely means: First time the same core application exists on multiple OSes (e.g., Windows + Mac)

It does not mean:
“Write once, runs everywhere instantly”
Bottom line
Cross-platform rewrite = technical capability
Mac release = one realized platform
Windows support = already exists
Linux support = still optional, not guaranteed

It's a small team working on this, so it does take time unfortunately

[quote=Lowlander post_id=532664 time=1776532713 user_id=262]
MediaMonkey 5 was the complete rewrite for cross-platform compatibility. MediaMonkey 2027 for MAC will be the first cross-platform release.
[/quote]
someone have to
I guess I misunderstood when I heard it didn't compile on Linux properly.
My earnest apologies for misstating.

[quote]Delphi Linux compiler is not yet producing current MM grade of quality we all used to.[/quote]
Are the issues something low priority for the Delphi maintainers, or would your programmers have to submit patches to get the results needed?

[quote=Lowlander post_id=532664 time=1776532713 user_id=262]
MediaMonkey 5 was the complete rewrite for cross-platform compatibility. MediaMonkey 2027 for MAC will be the first cross-platform release.
[/quote]

Oh it already was...great. But that mac-one probably still takes a lot of time before even pondering to hop to linux?

MediaMonkey 5 was the complete rewrite for cross-platform compatibility. MediaMonkey 2027 for MAC will be the first cross-platform release.

Complete rewrite would be optimal, but probably unlikely. That is a tremendous effort.
And "lesser tools" are sadly so inferior that there is, to my current knowledge, no alternative that even comes close halfway.
Still, today, the next best thing would be my own Musicplayer I wrote BEFORE i discovered MM, which was superior to mine.

Sad to see they focus on Mac currently. Apple-users are usually not the kind of "nerds" or "power-users" that MediaMonkey attracts.

So far, I can live with my remoteapp-solution. Wouldn't do this for any other app though :)

These stories are the reason I just gave up on MM and use lesser tools to get the job done. Even with all the workarounds and hacks, you still don't get the full native experience. I tried earlier on to get things to work, but it was just too fragile and caused more frustration than joy.

The real answer for the long term health of MM would be to a complete rewrite in an OS agnostic language. Windows is not going away tomorrow, but the tea leaves are already indicating where it's headed. Governments around the world are now considering Windows a national security risk, and how long will users put up with advertisements and invasive data collection from their OSes?

If a Linux version is ever released I'd be first in line, but I stopped holding my breath a long time ago. 😩

While I agree with the notion of that, not upgrading graphics drivers is not something I consider realistic on linux, especially with nvidia. This is not the same situation as in windows where the drivers are stable and mostly just bring new game enhancements. In linux these drivers are still under active development and are adding fundamental features with each release, both for gaming and regular desktop use.

[quote=TIV73 post_id=532655 time=1776456903 user_id=49509]
I've been running mediamonkey in wine (via bottles) for a couple of months without major issues, and upgrading the nvidia driver from 590.44.01 to 595.58.03 completely broke mediamonkey...
[/quote]

If it works...
don't fix it. :cry:

Heads-up to nvidia users - I've been running mediamonkey in wine (via bottles) for a couple of months without major issues, and upgrading the nvidia driver from 590.44.01 to 595.58.03 completely broke mediamonkey. The application itself starts fine, but no UI is being rendered. As far as I can tell the chromium frontend hits some kind of vulkan/dxvk issue, causing a crash on the Chrome_InProcGpuThread when DXVK is enabled. Without DXVK, it fails earlier due to missing d3d9.

No amount of tinkering, other than downgrading to the older driver version, did anything to help, and since I know fuck all about about wine debugging or rendering APIs that's also the point where completely out of my depth in terms of how to debug this further.

Maybe it would be fairly easy for the development team,
to tweak the integration with Wine / Bottles? ♥

I totally gave up on MM-integration via Wine. It's just a mess.

My solution now, which is a horrible overkill but works:

I did set up a win10 iot enterprise ltsc with absolute bare minimum for just MM. then use xrdp and some tweaks to run it
as a shell-replacement. So it kinda looks like a native app with another icon. Works great, except mini-player, obviously.
My before mentioned remote-control-script also works this way.

Guess I can forget about the highdef audio as rdp probably caps at 44.1/16bit, but it's a start.

Please do the linux version, we're in the 5% range of OS nowadays :-)

"Do it !"
-Palpatine