The Portable Freeware Collection Forums

I am Baas wrote:Cheers for that.

Agreed. Hopefully that "accepted" status means we'll see it soon.

I am glad to announce the first portable version of Qmmp- 0.10.1, changes:

- added ffmpeg 3.1 support;
- added portable mode for Windows;
- fixed GNOME3/MATE/Cinnamon support (0.10.1 only);
- fixed qt5.7 support (1.1.1 only)
- fixed Russian translation;
- updated Ukrainian translation;
- updated Portuguese translation.

How to make Qmmp portable:
-1. Download the latest installer- qmmp-0.10.1-win32.exe.
-2. Run the installer.
-3. During installation choose "Portable configuration" (screen-shot below).



-4. Choose the installation folder and install the program.
-5. Open the installation folder and run qmmp.exe.
-6. All data and settings are saved in .qmmp sub-folder inside program folder.

I uninstalled the Qmmp and successfully imported my configuration to the portable version copying .qmmp folder.

I have already thanked the developer but I want to do it once again here:
trialuser02- thank you very much for the portable installation mode!

@moderators
Please move this thread to Portable Freeware Submission sub-forum.

smaragdus wrote: @moderators
Please move this thread to Portable Freeware Submission sub-forum.

@mod a gentle reminder

I am Baas wrote:a gentle reminder

Thanks, missed that one.

Tested out today again. It's really, really nice.

* Super similar to the old Winamp - window snapping, animation, even uses the same hotkeys
* Support for 29 world languages

Wishlist
* Ability to drag and drop files onto the main window
* Scale size - on high detail monitors, it the buttons are very small

Qmmp has been added to the database.

@I am Baas
If you have time please check whether Qmmp for is stealth or not- there might be remnants in the tegistry from my previous installations when it was not portable.

@webfork
Qmmp offers support for drag&drop for both files and folders. Feature requests and bug reports can be submitted here.

smaragdus wrote:Qmmp has been added to the database.

Thanks for doing that.

I saw in the description that it works with old Winamp skins so I tested out an old one and was very pleased to see it worked perfectly:



The author is listed as Robert Eldredge and, as I can't find a copy of it, I've posted the contents: Vector Red.

While taking another look at Qmmp, I found this notice at the bottom of the homepage about the "future of Qt4 branch" (which the Windows build is based on), dated 2019-02-29:

Qmmp 0.12.0 is the last major release of the Qt4-based version. But I have no plans to abandon Qt4 support suddenly. 0.12.x will receive bug fixes and small improvements as long as it makes sense.

I also found a site with plenty of Winamp format skins with nice and easy previews:



BTW, the Qmmp skins repo is at http://qmmp.ylsoftware.com/files/skins/.

Midas wrote: ↑Wed Aug 21, 2019 5:35 am While taking another look at Qmmp, I found this notice at the bottom of the homepage about the "future of Qt4 branch" (which the Windows build is based on), dated 2019-02-29:

Qmmp 0.12.0 is the last major release of the Qt4-based version. But I have no plans to abandon Qt4 support suddenly. 0.12.x will receive bug fixes and small improvements as long as it makes sense.

Dang.

Midas wrote: ↑Wed Aug 21, 2019 5:35 am

http://waskins.rubyx.eu/

Very nice. I miss winamp skins.

A 1.3.5 stable release is available and based on qt5 and the "portable configuration" option is available in the installer.

thepiney wrote: ↑Sun Dec 22, 2019 1:28 am A 1.3.5 stable release is available and based on qt5 and the "portable configuration" option is available in the installer.

Thanks for that -- looks like a mostly bugfix update:

http://qmmp.ylsoftware.com/

thepiney wrote: ↑A 1.3.5 stable release is available and based on qt5 and the "portable configuration" option is available in the installer.

Thanks for checking, thepiney. It had never ocurred to me to try the newer version in Windows...

Portability confirmed -- apparently all it takes to achieve native portability with QMMP is an empty file named 'portable.txt' in the program's folder that causes Qmmp to store settings in a '.qmmp' sub-folder.

So here's QMMP v1.3.5 sporting the Nucleo_NLog_v102 skin.



Note: If using the installer to get the portable, people should be warned never to go with the default location offered.

And why you updated the entry for less-compatible Qt5 branch!?
wtf

I would recommend bumping the entry to 1.3.6. It's listed as stable for Qt5 branch:
https://sourceforge.net/projects/qmmp-d ... s/windows/

The developer does update the Qt4 branch as well.

It has been brought to my attention the disagreement over how this entry should be updated.

Both me and webfork did some research, and we were unsure what to make of the differences over the qt4 and qt5 versions. The general gist (correct me if I am wrong) is that qt4 has better compatibility with legacy systems but will no longer be developed (other than patching security issues), while qt5 is the current mainline but does not support older systems.

Given that the developers are making both product lines available, I think there are 2 ways we can move forward.

1) Create a new database entries for qt5 (so Qmmp/qt4 and Qmmp/qt5), crosslink them, and explain their differences. A precedent comes to mind: KeePass Classic (V1) and KeePass V2. Some people still prefer using KeePass V1, though V2 has been the mainline for a long time now.

2) Update current entry to qt5, but provide a link to qt4 with explanations.

I myself am more inclined to solution 1). If there are no objections, I will create a new entry for qt5 on Monday, and you guys can edit to your heart's content.

- - - - -

I would also like to address the unhappiness that arose out of how the update and reversion was done.

Looking through the series of events that led up to this, I can understand how the unhappiness could have arisen. On the Internet where we are using solely text as our medium of communication, there are a lot of other communications cues that are missing, which can very easily lead to misunderstanding on each other's emotional states when we are typing certain replies.

I think the only way to combat this is more communication. For example, in this case if I strongly believe that qt4 should remain an entry, maybe I would lay out my arguments and suggest various options for dealing with the dichotomy. With more discussion, I think we will come to a better understanding of each other's positions.

- - - - -

Lemme know what you think. Cheers!