Author Topic: Suggestions for 3.9 (Read 224387 times)

sveakul · « **Reply #375 on:** 16 Jan '18 - 19:39 »

Thanks saga, never really looked at that window very closely, gave it a good read at the support site now. I had anticipated the usual "save settings" choice on the EQ preset drop-down, which would be more intuitive with that particular DSP, but this will do the job!

mortstev · « **Reply #376 on:** 26 Jan '18 - 20:03 »

Quote from: saga on 28 Oct '17 - 00:19

... the latest "in development" XMPlay build (that saga is referring to) is available here:

www.un4seen.com/stuff/xmplay.exe

"404 Not Found"

saga · « **Reply #377 on:** 27 Jan '18 - 17:37 »

That's most probably because there is no newer test version than the latest released version, which you can get from the main XMPlay site.

mortstev · « **Reply #378 on:** 13 Jun '18 - 22:44 »

anyone know why the stuff version is triggering a virus warning?

signature: ws.reputation.1

sveakul · « **Reply #379 on:** 14 Jun '18 - 02:28 »

The link at https://www.un4seen.com/stuff/xmplay.exe works for me and is delivering version 3.8.3.8 as of today; the package linked at the main XMPlay site still has 3.8.3.4.

No virus warning for me, probably a false positive.

saga · « **Reply #380 on:** 14 Jun '18 - 13:40 »

"reputation" typically hints at the "popularity meter" that many AV vendors seem to use these days; essentially this means that if only few people (using the same AV as you) have downloaded this exact version of the executable before, it will think that the executable is suspicious becuase why would you be such an invidiualist who uses software that is not used by thousands of other people. If the "reputation" of the executable is low, it has nothing to do with its content at all, it just means that it's not very commonly downloaded. Ignore the warning and/or submit the executable as a false positive to your AV vendor.

garson · « **Reply #381 on:** 29 Jun '18 - 21:36 »

Any chance to implement auto splitting of lines wider than info window?

yoba · « **Reply #382 on:** 30 Jun '18 - 01:00 »

garson

Options and stuff => Appearance => Info window => Maximum text width:... (0 = no limit)

Make it 0 or what you want

garson · « **Reply #383 on:** 8 Jul '18 - 21:03 »

Quote from: yoba on 30 Jun '18 - 01:00

garson

Options and stuff => Appearance => Info window => Maximum text width:... (0 = no limit)

Make it 0 or what you want

Thanks yoba.

garson · « **Reply #384 on:** 8 Jul '18 - 21:06 »

Hi Ian.

I have small suggestion. In File Info window, size is in bytes, which is not that convenient. Maybe add .ini setting to make it in KB/MB?

saga · « **Reply #385 on:** 8 Jul '18 - 21:18 »

And another suggestion while we're at the info window: Show ID3v2 tags before ID3v1 tags. The better information source should be shown first.

mortstev · « **Reply #386 on:** 10 Jul '18 - 22:15 »

I have a question about how random play works...

I had about 200 files loaded and it seemed to me that some files were played twice maybe even three times before other were even played once.

Does random keep track of what was played so that all files are played once before going back and playing them again?

TIA, Mort

saga · « **Reply #387 on:** 11 Jul '18 - 13:08 »

As long as you do not replace the playlist, XMPlay keeps track of played/unplayed files and won't repeat them until all files have been played.

Sajadi · « **Reply #388 on:** 22 Aug '18 - 15:11 »

Native Opus playback support would be great

saga · « **Reply #389 on:** 22 Aug '18 - 15:42 »

Isn't xmp-opus native enough?

sveakul · « **Reply #390 on:** 23 Aug '18 - 00:56 »

Sajadi: what saga said! And note that the current xmp-opus.dll supports the latest release libopus 1.2.1 decoding library

Enjoy!

saga · « **Reply #391 on:** 23 Aug '18 - 12:21 »

Quote from: sveakul on 23 Aug '18 - 00:56

And note that the current xmp-opus.dll supports the latest release libopus 1.2.1 decoding library Enjoy!

That's misleading, you do not need the most recent decoder to decode files saved with the latest encoder. Encoder updates are backwards-compatible.

sveakul · « **Reply #392 on:** 23 Aug '18 - 17:19 »

Um, my intention was not to make a "misleading" statement, I was merely making the point that Ian's plugin is kept completely up-to-date.

saga · « **Reply #393 on:** 12 Sep '18 - 19:03 »

I'm currently using my music collection (including song-specific settings and library information) two devices, but the base path to the collection is different (and it's not just a matter of different drive letters). I wonder if "check other drives for missing files" could be extended to arbitrary path, or if a different way of just moving the entire library including song-specific settings to a new root path. If not, I could write an external tool for that, but for that I'd need a specification of the .set format (for xmplay.library I already have code).

saga · « **Reply #394 on:** 6 Nov '18 - 18:41 »

I think it would be useful if XMPlay could (optionally) save the current song position when WM_QUERYENDSESSION, i.e. close with position saved on system shutdown.

Ian @ un4seen · « **Reply #395 on:** 7 Nov '18 - 17:46 »

I think the position should be saved if the "Save playback position upon closing" option is enabled (in the "Miscellaneous" page). Do you have that enabled and still find that the position is not saved when you shutdown?

saga · « **Reply #396 on:** 7 Nov '18 - 19:13 »

I do indeed not have this option enabled, what I was thinking of was mostly using this e.g. when having to quickly shutting down my laptop, or in case Windows updates decide to restart the computer. But apart from these cases, I don't think I would usually want to keep the playback position unless I specifically choose that option from the menu.

Cosworth · « **Reply #397 on:** 21 Apr '19 - 13:01 »

Hi. Could be an option that can change scroll lines of volume change? For example, right now we have 1 scroll=3 lines(volume).

Ian @ un4seen · « **Reply #398 on:** 22 Apr '19 - 17:09 »

You can reduce the mouse wheel volume adjustment by adding a "VolStep=1" or "VolStep=2" line to your XMPLAY.INI file (under "[XMPlay]").

Cosworth · « **Reply #399 on:** 22 Apr '19 - 19:52 »

Quote from: Ian @ un4seen on 22 Apr '19 - 17:09

You can reduce the mouse wheel volume adjustment by adding a "VolStep=1" or "VolStep=2" line to your XMPLAY.INI file (under "[XMPlay]").

Thank you