▲

[saga]

Maybe what you are looking for is the ReadAhead hidden setting? See here: http://support.xmplay.com/article.php?id=82
Note that this might not be a good idea in combination with gapless playback though, if the HDD takes a long time to spin up.

[FrankyMcBobson]

Maybe what you are looking for is the ReadAhead hidden setting? See here: http://support.xmplay.com/article.php?id=82
Note that this might not be a good idea in combination with gapless playback though, if the HDD takes a long time to spin up.

Didn't know about that setting, thanks! Wish it would work for all filetypes, though.

[Ian @ un4seen]

The "ReadAhead" setting applies to all file formats except MP3, which are already pre-read/scanned (for accurate length and seek points).

[Od1n22]

I would love for XMplay to be able to write modules containing subtunes into a single file using the WAV Writer or encoders.

For years it's been driving me up the walls when I want to export S3M, IT or other formats containing subtunes into .WAV or MP3, that XMplay insists on writing every subtune as an individual file even though many of these modules are supposed to play as a single song. It means I have to do a ton of work afterwards by merging files together in a sound editor.
It would be such a treat with a checkbox under the "Output" or "Encoders" section that says: "Merge subtunes".

Except for this burning wish, I'm happy as a clam with XMplay. Thanks for providing me with years of joy.

[saga]

Here's another suggestion for the list of dead files that would greatly speed up my workflow... I'm currently replacing a lot of albums with FLAC versions. In general the filenames will stay the same, but the file extension changes. Right now I have to manually edit each library entry to change the file extension. Would it be possible to have an "ignore extension" option for the "scan for new locations" action so that this workflow can be automated?

[Ian @ un4seen]

I started to look into that, but then it occurred to me that it may not be the quickest way to do what you want. If you enable monitoring of the folder(s) in XMPlay then it should automatically add the new FLAC files and remove the missing old ones. Even without monitoring, it may be quicker/simpler to manually remove the dead old entries and add the new FLAC files (eg. drag'n'drop the containing folder), rather than using a looser dead track recovery option. Such a new option would probably require some checking of the search results before applying them to make sure it didn't find something unexpected with the looser matching.

[saga]

Even without monitoring, it may be quicker/simpler to manually remove the dead old entries and add the new FLAC files (eg. drag'n'drop the containing folder), rather than using a looser dead track recovery option.

I try to avoid that as it will lose play counts and custom tags.

[Marto]

Linux Version would be GREAT!!!
Nowdays, almost all you want to do, can be achieved within a linux distribution.
With AppImage implementation, most of the software out there could be used in any Linux distro, without package requirements.
Since almost two years ago, I switched to Linux totally. but I dont have XMPlay!!!! Most light, fast, adn configurable software out there.

Maybe I'm just dreamer, but a Linux version (AppImage, snap,, flatpak... you choose) would be awsome

[Ian @ un4seen]

Even without monitoring, it may be quicker/simpler to manually remove the dead old entries and add the new FLAC files (eg. drag'n'drop the containing folder), rather than using a looser dead track recovery option.

I try to avoid that as it will lose play counts and custom tags.

Are you doing the FLAC conversion with XMPlay? If not, you could try that, as it will use the source's overridden tags when writing the FLAC file, so you won't need to be concerned about losing those tags when replacing the old track

Linux Version would be GREAT!!!
Nowdays, almost all you want to do, can be achieved within a linux distribution.
With AppImage implementation, most of the software out there could be used in any Linux distro, without package requirements.
Since almost two years ago, I switched to Linux totally. but I dont have XMPlay!!!! Most light, fast, adn configurable software out there.

Maybe I'm just dreamer, but a Linux version (AppImage, snap,, flatpak... you choose) would be awsome

While not as nice as having a native Linux version, XMPlay does work on Linux with Wine. When I last tried it there were some visual glitches with the z-order of the panels but that was many years ago, so things may have improved since then, or perhaps you could use a skin that doesn't have sliding/overlapping panels.

[saga]

Are you doing the FLAC conversion with XMPlay? If not, you could try that, as it will use the source's overridden tags when writing the FLAC file, so you won't need to be concerned about losing those tags when replacing the old track

To be clear, I'm replacing some OGG and MP3 files with FLAC replacements; so converting them with XMPlay wouldn't make much sense.

While not as nice as having a native Linux version, XMPlay does work on Linux with Wine. When I last tried it there were some visual glitches with the z-order of the panels but that was many years ago, so things may have improved since then, or perhaps you could use a skin that doesn't have sliding/overlapping panels.

Unfortunately I can confirm that those issues still exist. In particular some invisible panels (e.g. the EQ panel) become visible just by clicking on the main window, which makes some skins difficult to use.

[Ian @ un4seen]

Are you doing the FLAC conversion with XMPlay? If not, you could try that, as it will use the source's overridden tags when writing the FLAC file, so you won't need to be concerned about losing those tags when replacing the old track

To be clear, I'm replacing some OGG and MP3 files with FLAC replacements; so converting them with XMPlay wouldn't make much sense.

Oh, were the OGG/MP3 files generated from MOD files and you now want FLAC versions, but the custom/overridden tags are set on the OGG/MP3 files rather than the original MOD files?

[saga]

No, MOD files aren't involved this time... They are downloads from Bandcamp. Sometimes I use custom tags for them to not edit the original files.

[saga]

Would it be possible to set the BIF_EDITBOX style on the BROWSEINFO struct passed to SHBrowseForFolder? This would allow the user to manually enter (or copy&paste) a path in the folder browser dialogs, making them a lot more useful.

[Ian @ un4seen]

Yep, here's an update with that flag set:

   www.un4seen.com/stuff/xmplay.exe

It seems to behave a bit strangely, in that only the final subdirectory is initially shown in the box but you need to enter a full path for it to work. I don't know if that's normal?

[saga]

Thanks for the quick update! Indeed it behaves as intended - the dialog itself will not put a full absolute path there but it is still possible by the user to supply one. So for example if you are browsing your music library with Explorer, you can quickly copy the current path and paste it in the dialog to add that folder.

[piovrauz]

Would it be possible to have single line track copy/paste from info windows?
When playing a stream I often need to copy all the text to a text editor (usually closed) and then copy and paste again the single track I want info on.
This because even if the recent \tracks are properly separated, but they "only" are in a single big block text when copied.

[Ian @ un4seen]

Do you mean adding something like a "Copy line to clipboard" option to the info window's right-click menu? XMPlay doesn't currently check where exactly the mouse is when clicked in there but it may be possible to add that.

[404notfound]

Does plugin API have way for a plugin to be notified that it's gonna play next, before end of current tune?
This would be handy for plugins that have to do things which take time(say, send network requests and read response), before they can start playing.

I've been pondering a Youtube plugin for some time.

[Ian @ un4seen]

If the next track has the same output format as the current track (so gapless playback is possible) then a general/DSP plugin's NewTrack function will be called before the next track is actually heard. How early will depend on how big the output buffer is.

[404notfound]

> How early will depend on how big the output buffer is.
You mean to say it's tied to the player's output latency?