4.0 reports, queries and bugs

[yoba]

Merry Christmas! 


So it begins 

Where is the balance? Is it completely gone from the new interface and now only in the bottom of "Options > DSP"?

Bug. "Internet streaming" is messed up - in Options, set, for example, "Timeout: 5" "Buffer: 10" but in xmplay.ini it become completely opposite - NetBuffer=5 NetTimeout=10

Bug? After manually  adding in xmplay.ini some "Secret settings", on next start player completely ignores xmplay.ini and starts like first time and strangely append fresh new settings to the end of the already existing xmplay.ini. Are there now some strict order in which values appears in xmplay.ini? Some settings are incompatible with the new version?
Generally, how many "Secret settings" are not "secret" anymore? Which one invalid? Too bad Jimmy Neutron stopped updating this list back in the 2016 and few secret settings and their descriptions now lost somewhere in the depth of the forum.

How critical were API changes? All new plugins will now be incompatible with the last 3.8.5.91 version? Because when I updated CD Audio plugin to the latest 12 version, XMPlay 3.8.5.91 although shows plugin itself, but "Config" button was disabled.

And just (now almost irrelevant) cosmetic bug regarding latest ALAC plugin - being recently updated to "revision 3" it still displays "(rev.2)" in "Options > Plugins > Input" of 3.8.5.91 but correctly "rev.3" in "Options > Versions" of 4.0

[Ian @ un4seen]

Where is the balance? Is it completely gone from the new interface and now only in the bottom of "Options > DSP"?

Yes, because most people rarely use the balance slider, it was decided to leave it out of the new skin to reduce clutter. There are quite a few skins that don't include a balance slider, but those that do will still work with 4.0, and the balance can still be adjusted quickly with keyboard shortcuts. A shortcut can also be used to open the DSP options, to access the balance slider there.

Bug. "Internet streaming" is messed up - in Options, set, for example, "Timeout: 5" "Buffer: 10" but in xmplay.ini it become completely opposite - NetBuffer=5 NetTimeout=10

Oops! That's sorted for the next update.

Bug? After manually  adding in xmplay.ini some "Secret settings", on next start player completely ignores xmplay.ini and starts like first time and strangely append fresh new settings to the end of the already existing xmplay.ini. Are there now some strict order in which values appears in xmplay.ini? Some settings are incompatible with the new version?
Generally, how many "Secret settings" are not "secret" anymore? Which one invalid? Too bad Jimmy Neutron stopped updating this list back in the 2016 and few secret settings and their descriptions now lost somewhere in the depth of the forum.

The order of the settings in XMPLAY.INI doesn't matter, but that "secret settings" list is quite old now and some have since been added to the options window. I've updated the list on the support site, removing the options that are no longer secret/available and adding a few new ones:

   https://support.xmplay.com/article.php?id=82

How critical were API changes? All new plugins will now be incompatible with the last 3.8.5.91 version? Because when I updated CD Audio plugin to the latest 12 version, XMPlay 3.8.5.91 although shows plugin itself, but "Config" button was disabled.

The CDA plugin update is using a new 4.0 feature that allows plugins to have their own config page in the options window instead of a pop-up window in the "Decoders" page. It is possible for plugins to support both methods, but the CDA plugin update doesn't bother because it has no other changes, so there's no reason to use it with an old XMPlay version.

[yoba]

I've updated the list

Nice!

Many plugins don't show their versions in the "Versions" page:



But some of them show their versions in "Decoders":



And almost all show their versions in "Plugins" > "Input" of the old 3.8.5.91:



That new "Versions" page seems not very useful.

[guest]

‣ In addition to the skin hue, it would be nice to be able to set the saturation and lightness.

‣ In addition to the big 2× skin, it would be useful to be able to set other sizes, e.g. 1.5×, 0.75×.

[andutrache]

I have updated to the new XMPlay 4.0 and I have random crashes (sometimes it happens 1 min into playing a file sometimes 5 mins in) all I found in Event Log is:

Faulting application name: xmplay.exe, version: 4.0.0.0, time stamp: 0x67698a4f
Faulting module name: xmplay.exe, version: 4.0.0.0, time stamp: 0x67698a4f
Exception code: 0xc0000005
Fault offset: 0x0003ee41
Faulting process id: 0xa4c
Faulting application start time: 0x01db5ab477d7a946
Faulting application path: E:\Music\XMplay\xmplay.exe
Faulting module path: E:\Music\XMplay\xmplay.exe
Report Id: 32c9f3d8-9ab4-48b6-ade6-ff9f3076e54b
Faulting package full name:
Faulting package-relative application ID:

The fault offset always stays the same between crashes.

When it crashes I hear the audio stuttering for 1 sec and then it just disappears with no error message other than what I found in event viewer.
This was not happening with 3.8.5

L.E: .vgz files also do not play anymore with the in_vgm plugin, no matter what I do I cannot get those files to play on 4.0 on 3.8.5 it works...
L.L.E: Not even ZXTune can play .vgz files anymore...

[Ian @ un4seen]

Many plugins don't show their versions in the "Versions" page:
But some of them show their versions in "Decoders":
And almost all show their versions in "Plugins" > "Input" of the old 3.8.5.91:
That new "Versions" page seems not very useful.

There were a couple of reasons for adding the "Version" page: It allows you to check all loaded plugins and their version numbers, and XMPlay's version number too. And because the version number is shown there, it can now be left out of input plugin names, which makes the "Decoders" list cleaner. It's a good place for the update checking option too.

The version info is taken from the file's VERSIONINFO resource, which is also what the update notifications use. Some old plugins didn't include VERSIONINFO, but if they ever get updated then they would need to add it to be able to give an update notification. I can't see the images that you posted, so I don't know which in particular you're referring to, but it seems to be mainly Sebastian Andersson's AAC/AC3/MPC/SPX plugins that are missing VERSIONINFO? I do have the source code for those, so I may rebuild them to add it.

‣ In addition to the big 2× skin, it would be useful to be able to set other sizes, e.g. 1.5×, 0.75×.

The main issue is that the control positions/sizes are defined (by the masks) on pixel boundaries, which can't be properly preserved with fractional resizing, so they could end up looking slightly wonky. But there was a skin resizing script made by Rahdick a while ago that you could try. It can be found in this thread, along with discussion on this subject:

   www.un4seen.com/forum/?topic=17350.msg127704#msg127704

I have updated to the new XMPlay 4.0 and I have random crashes (sometimes it happens 1 min into playing a file sometimes 5 mins in) all I found in Event Log is:
...

It looks like that crash was in getting data for the level display. Please provide a dump file for more info. If you open the "%LOCALAPPDATA%\CrashDumps" folder in File Explorer, you will hopefully find some there. Upload one (after ZIPing) here:

   ftp.un4seen.com/incoming/

To see if it may be triggered by something in your config, please also try renaming your XMPLAY.INI file for a fresh config and see if it still happens then. If that stops it happening, then also upload your original XMPLAY.INI file to have a look at.

L.E: .vgz files also do not play anymore with the in_vgm plugin, no matter what I do I cannot get those files to play on 4.0 on 3.8.5 it works...
L.L.E: Not even ZXTune can play .vgz files anymore...

It looks like VGZ files are GZIP archives, so I suspect the problem is related to the new built-in GZIP support, ie. that's decompressing the file before those plugins see it. I'll look into that.

[andutrache]

Uploaded the file on the ftp as instructed (name is xmplay.exe.2636.zip).

Crashes seem to have stopped after I deleted the [XMplay] category from the .ini and let the player regenerate it from scratch (uploaded the old one if you want to take a look).

I also did other steps but that post was lost because the forum is stupid and just decided to drop my post because I uploaded the XMplay.ini then told me to wait 30 seconds after I zipped it and tried to repost only to then tell me that I already posted the post even tho there was nothing on the thread :/.

[yoba]

I can't see the images that you posted

Oops! 
Attached.

Nothing in "Versions" of 4.0:
xmp-8svx.dll
xmp-aac.dll
xmp-ac3.dll
xmp-acm.dll
xmp-arj.dll
xmp-digi3.dll
xmp-gme.dll
xmp-mmcmp.dll
xmp-modpacker.dll
xmp-mpc.dll
xmp-ofr.dll
xmp-pp.dll
xmp-spx.dll
xmp-stm.dll
xmp-tta.dll
xmp-wad.dll
xmp-xpk.dll
xmp-ym.dll
xmp-zxtune.dll

But of the aforementioned, shows their versions in "Decoders" of 4.0:
xmp-digi3.dll
xmp-stm.dll
xmp-ym.dll
xmp-zxtune.dll

And almost all shows their versions in "Plugins" > "Input" of 3.8.5.91, except:
ASAP
OptimFROG
Speex
The True Audio
and all archive plugins

[guest]

...But there was a skin resizing script made by Rahdick a while ago that you could try....

http://rahdick.at/sonstiges/xmplay-skin-scaler
Could a default skin be available in a form for use with this script?


Could MOD pattern - Solo channel be available by e.g. ALT + middle-clicking in channel column (and assignable keyboard shortcut)?

[Ian @ un4seen]

Uploaded the file on the ftp as instructed (name is xmplay.exe.2636.zip).

Crashes seem to have stopped after I deleted the [XMplay] category from the .ini and let the player regenerate it from scratch (uploaded the old one if you want to take a look).

Thanks. I think I know what it is now, and here's an update that should fix it:

   www.un4seen.com/stuff/xmplay.exe

This should also fix your VGZ problem. Those plugins seem to simply check the file extension to decide whether a file may be playable, so the GZIP decoder in this update repeats the current filename when the original filename isn't stored in the GZIP file, ie. you end up with playlist entries like "path\filename.vgz|filename.vgz". But this update also extends the plugin "priority filetypes" option to have priority over archive plugins too, so you could give those plugins priority for "vgz" to prevent the GZIP decoder seeing the file before them.

Nothing in "Versions" of 4.0:
...
But of the aforementioned, shows their versions in "Decoders" of 4.0:
...

The plan is for new input plugin releases to only include a version number in a VERSIONINFO resource and not in their name, which is already the case with archive/dsp/output plugins. The "Decoders" list removes version numbers from plugin names (assuming it's in brackets), but this update will then display that in the "Version" list when a plugin doesn't have a VERSIONINFO resource.

This update also fixes the internet timeout/buffer options reversal and a regression affecting translucent skins (eg. seen in the Rated White Glass skin's pause button).

[andutrache]

Thank you, I have downloaded the new version set the priority and now.vgz files work.

Happy new year .

[Ian @ un4seen]

‣ In addition to the skin hue, it would be nice to be able to set the saturation and lightness.

Here's an update that adds saturation adjustment:

   www.un4seen.com/stuff/xmplay.exe

Regarding lightness, the light/dark switch inverts that. A straight lightness control doesn't really work well on skins (it just moves everything towards black or white).

This update also tweaks the "Version" list again. When a version is found in a plugin's name and VERSIONINFO resource, the version in the name is preferred. That's because some plugins have a different format in their VERSIONINFO, eg. "0,0,18,2" vs "rev.18.2" in xmp-ahx.

[yoba]

This update also tweaks the "Version" list again.

Now xmp-alac.dll shows wrong version again - rev.2, not the correct rev.3, and xmp-libxmp.dll shows version of libXMP 4.6.0 library (on which it based), but not the version of the plugin itself, 1.0.31 in this case 
In xmp-alac.dll case it's plugin's fault, looks like when you updated plugin you leave the old rev.2 version in the name

I wish someday there will be truly working Petite unpacker 

Also, don't forget about the "Version" page's "Description" field, it shouldn't be empty too.

[Ian @ un4seen]

Now xmp-alac.dll shows wrong version again - rev.2, not the correct rev.3, and xmp-libxmp.dll shows version of libXMP 4.6.0 library (on which it based), but not the version of the plugin itself, 1.0.31 in this case 
In xmp-alac.dll case it's plugin's fault, looks like when you updated plugin you leave the old rev.2 version in the name

Oops. That's the problem with having the version in 2 places ... I'll put up a new XMP-ALAC.DLL build this week with the version only in the VERSIONINFO resource. It'll probably be "1.3" now rather than "rev.3", as I'm thinking of switching to using "1.x" instead of "rev.x". That'll match what's shown in File Explorer, so the version can be checked there too.

Hopefully, XMP-LIBXMP.DLL can be similarly updated.

Also, don't forget about the "Version" page's "Description" field, it shouldn't be empty too.

The "Description" field is read from the VERSIONINFO too, with the "XMPlay" part omitted (eg. "MIDI Plugin" instead of "XMPlay MIDI Plugin"). I suppose the plugin name could be shown there when VERSIONINFO is missing, but it'll usually be apparent what the plugin is from the filename anyway.

[saga]

Not a bug with XMPlay itself but the website's menu still claims that 3.8.5 is the latest XMPlay version

[Ian @ un4seen]

There's that pesky version in 2 places issue again

Sorted now.

[redneonglow]

When songs are played from the Start menu, the default now is to wipe out the playlist, replace it with the song, and automatically start playback. Is there any way to go back to the old behavior of enqueuing by default?

[Ian @ un4seen]

Oops, that's a bug that was introduced in the 4.0.0.3 update (affecting the "Integration > Default action" option). Here's another update to fix it:

   www.un4seen.com/stuff/xmplay.exe

[redneonglow]

Oops, that's a bug that was introduced in the 4.0.0.3 update (affecting the "Integration > Default action" option). Here's another update to fix it:

   www.un4seen.com/stuff/xmplay.exe

Works again, thank you!

[AstralSoup Design]

All this time there was an easy way to resize oversized skins?!? :mindblow:

...But there was a skin resizing script made by Rahdick a while ago that you could try....

http://rahdick.at/sonstiges/xmplay-skin-scaler
Could a default skin be available in a form for use with this script?


Could MOD pattern - Solo channel be available by e.g. ALT + middle-clicking in channel column (and assignable keyboard shortcut)?

[piovrauze [offline]]

Just upgraded to Xmplay 4, makes me happy to see it improving every day.
New skin is nice, but I'll stay on Innocuos - after I had some tweaks implemented I won't ba able to stop using it!

Now, I noticed the "Tools" menu entry: since it's customizable it's useful... but there's a little improvement that I'd like to ask for an improvement.
I have some softwares that installs itself in AppData; Xmplay, when saving the command, "unpacks" it, which means that if I move around Xmplay that command won't work anymore.
I'd like to ask if it would be possible to keep it like "%appdata%/localNow/.../bin.exe", basically what I type before it gets "converted.

[Ian @ un4seen]

That sounds strange. XMPlay shouldn't change the tool command-line that you enter, but it also doesn't currently support special variables like "%AppData%" in that. So I guess what you want is that "%AppData%" is supported?

[yoba]

About "Tools" by the way

If add MediaInfo CLI and set "Console: keep open", XMPlay starts crashing randomly, not always, when stopping playing, when changing track, when adding track from the library -
in ntdll.dll with the most generic 0xc0000005.
That's absolutely not a problem at all, because cmd /K MediaInfo works fine, and maybe not related to the player but to my system itself, but just want to let you know.

[Ian @ un4seen]

Can you provide dump file(s) from that to have a look at? If you open the "%LOCALAPPDATA%\CrashDumps" folder in File Explorer, you will hopefully find some there. You can upload here:

   ftp.un4seen.com/incoming/

[piovrauze [offline]]

That sounds strange. XMPlay shouldn't change the tool command-line that you enter, but it also doesn't currently support special variables like "%AppData%" in that. So I guess what you want is that "%AppData%" is supported?

Correct.
Right now I have: ""C:\Users\secretusername\AppData\Local\ocenaudio\ocenaudio.exe" /f"
I'd like something like: "%AppData%\Local\ocenaudio\ocenaudio.exe" /f"