Which dotnet requires the latest version of AIMP for Windows?

[rado84]

I have an idea how I can make AIMP run like a native program in Linux (if it works, I'll share it with everyone on this forum) but before that happens, I need to know which dotnet framework the latest AIMP requires. And I'm hoping it requires dotnet 6 or newer, because these versions will make things immensely easier.

[CkopoxoD]

AIMP is written in Delphi.
Just wait for AIMP 6: https://www.aimp.ru/blogs/?p=1498&language=en

[rado84]

Nice! Cuz the current build "for Linux" isn't exactly that and I had to fix some parts of the script in order to make it work properly. There are still some edges to smooth out, though. But for the most part it works a lot better than what came from the link "AIMP for Linux".

I'd love to test the native version whenever it comes out.

[Artem]

current build "for Linux" isn't exactly that and I had to fix some parts of the script in order to make it work properly.

What exactly you've patched?

[Artem]

I'd love to test the native version whenever it comes out.

AIMP6 will be released in 3 editions: native for Windows / Linux and WINE for Linux. So, I mean wine-based build will be supported too, because it provides windows-relates features for Linux users such as VST/DSP support and others

[rado84]

What exactly you've patched?

"Patched" is a strong word but:
1. The start script was named wrong. You had named it .bash which makes it useable only for bash shells. Other shells like zsh or fish might ignore it because they'll be looking for .sh extension, altough linux doesn't really care about extensions, some shells might still look at the extension. Linux is looking for what's inside the file to determine what it is. The extension is just conveniency for humans. So I made it universal by renaming its extension to .sh.
2. The start script again: the first line of it was all wrong and redundand. This line is to convert linux paths to Windows, when what a Linux user needs is the other way around - convert Windows paths to Linux paths, so that you can run any playlist that contains /B/MUSIC path directly into AIMP and AIMP would recognize it thanks to Wine.
3. Changed the config path of AIMP in order to make it portable and so that the user wouldn't lose their settings, if they (accidentally or not) delete wine.

This is what the edited script looks like now:

Code: [Select]

#!/usr/bin/sh

CONFIG="$HOME/AIMP_LINUX/AIMP/config"
TARGET="$HOME/.wine/drive_c/users/rado/Application Data/AIMP"

[ -L "$TARGET" ] || ln -s "$CONFIG" "$TARGET"

wine start /unix '/home/rado/AIMP_LINUX/AIMP/AIMP.exe' ${_paths}
Plus a few other changes but they're only for my computer, so not worth mentioning.

Btw, if AIMP were made to require a dotnet 6 or newer, it would be a child's play to nativefy it and neither you or the user would be the wiser. I already nativefied another program for Windows and you can't even tell the difference.

I did what I could with 5.40, but I'd still prefer to test the native linux version bc when such a version is present, no normal linux user would wanna use the wine version. 

[Artem]

You had named it .bash which makes it useable only for bash shells

Its not true in most cases. Linux choose shell by file's content sample. In this case, shell will be selected according first line of the file - "#!/usr/bin/sh".

Of course, you can setup free desktop to ignore file content and make decision only by file extension, but this is not common scenario in Linux.

This line is to convert linux paths to Windows, when what a Linux user needs is the other way around - convert Windows paths to Linux paths

This command get used to translate file paths that send by Linux via command line to AIMP app.

so that you can run any playlist that contains /B/MUSIC path directly into AIMP
and AIMP would recognize it thanks to Wine.

This is different case.

Btw, if AIMP were made to require a dotnet 6 or newer, it would be a child's play to nativefy it and neither you or the user would be the wiser. I already nativefied another program for Windows and you can't even tell the difference.

I am not sure that windows-specific things may be converted so easy.

no normal linux user would wanna use the wine version.

Only if it requires windows-specific things like VST/DSP or other plugins

[rado84]

This command get used to translate file paths that send by Linux via command line to AIMP app.

It IS a fact that after removing the command in question, AIMP started recognizing paths like /B/MUSIC and I was able to run one of my playlists without drag-and-drop of files.
The only problem is to figure it out why no version of AIMP will take my settings. On Spyware 10 & 11 these settings work just fine but not when AIMP's run through wine.

[Artem]

AIMP started recognizing paths like /B/MUSIC

Most likely this feature depends from wine version.