Author Topic: 3.8 reports, queries and bugs  (Read 102026 times)

Dotpitch

  • Posts: 2861
Re: 3.8 reports, queries and bugs
« Reply #450 on: 1 Feb '17 - 06:49 »
What output were you using in AIMP? DirectSound, ASIO or WASAPI? Does the Windows mixer also show problems? And WASAPI in exclusive mode?

Discarding the first 0.5 seconds is indeed an annoying habit. What kind of DAC is it?

moriez

  • Posts: 115
Re: 3.8 reports, queries and bugs
« Reply #451 on: 1 Feb '17 - 10:03 »
What output were you using in AIMP? DirectSound, ASIO or WASAPI? Does the Windows mixer also show problems? And WASAPI in exclusive mode?

Discarding the first 0.5 seconds is indeed an annoying habit. What kind of DAC is it?

Thanks for responding.

In AIMP I only tried WASAPI exclusive, event and/or push of which I don't know the difference.
I haven't tried Windows mixer yet but shall play with this tomorrow.
The DAC is a Chord Mojo that is connected over USB.

Theoretically, could it have to do with that AIMP does resampling by default? As far as I can see it can't be turned off.

Dotpitch

  • Posts: 2861
Re: 3.8 reports, queries and bugs
« Reply #452 on: 1 Feb '17 - 17:02 »
Theoretically, could it have to do with that AIMP does resampling by default?
Could be, but you can make XMPlay do that as well. First try the Windows mixer.

Ian @ un4seen

  • Administrator
  • Posts: 19804
Re: 3.8 reports, queries and bugs
« Reply #453 on: 1 Feb '17 - 17:14 »
I'm  trying a new DAC that has the annoying habit to silence the first 0.5 second of a new track. Even when I load the entire album. I think I tried every single option under Output but can't correct it. Both WASAPI output set to 24 bit/44.100 (also tried 16 bit) with pretty much my entire music library being 16bit/44.100. Setting buffer to as low as 0.100s doesn't correct it either. Then, as I've been curious try out AIMP, this player has no issues at all.

Does the problem only happen when using exclusive mode WASAPI output, not when using shared mode WASAPI or the default (waveout) or DirectSound outputs? And does it only happen when starting playback, or does it also happen when playback transitions from one file to another (with the same sample format), ie. is gapless playback affected?

moriez

  • Posts: 115
Re: 3.8 reports, queries and bugs
« Reply #454 on: 3 Feb '17 - 20:00 »
Had a little time to test but too fast the battery drained. What I can report though is that the Windows mixer cuts off the same way. Tested this on Bandcamp and YT.

moriez

  • Posts: 115
Re: 3.8 reports, queries and bugs
« Reply #455 on: 4 Feb '17 - 19:30 »
Apologies. Although the problem is with ALL output options I wasn't entirely correct about the issue. AIMP does cut off the first 0.5 second :\ .. with one difference to it:

XMPlay idle in tray and three tracks are queued. I press play and the cutoff is there. The one exception is gapless playback (so without pressing any of the controls ie. 'next track')
vs
AIMP idling in tray and the same three tracks are queued. I press play and the the cutoff is there but when I use the controls ie. 'next track' it does NOT cut off.

In this scenario AIMP isn't really benificial to my situation.


Edit: This gent on Head-Fi seems to be on to something. Play silence at startup for hardware synchronization
http://www.head-fi.org/t/784602/chord-mojo-dac-amp-faq-in-3rd-post/7245#post_12179712
« Last Edit: 4 Feb '17 - 20:31 by moriez »

saga

  • Posts: 2110
Re: 3.8 reports, queries and bugs
« Reply #456 on: 19 Mar '17 - 12:40 »
I think something is wrong with S3M "Fast Volume Slides". In the attached excerpt from Purple Motion's PANIC.S3M, the sound on row 6 should be about half as loud as the sound on row 8 (same later on row 14 / 16 and 22 / 24).

Ian @ un4seen

  • Administrator
  • Posts: 19804
Re: 3.8 reports, queries and bugs
« Reply #457 on: 24 Mar '17 - 16:43 »
That problem appears to be caused by XMPlay processing the effect column before the volume column in S3M files, eg. the 1st channel's volume after the 1st tick of row 6 is 10 instead of 0 and the 2nd channel's volume is 25 instead of 13. XMPlay did originally process the volume column first (and still does for XM/MOD/MTM files), but that was changed for S3M/IT files in Dec 2013 for some reason. Unfortunately, I didn't make a note of why. Anyway, here's an update that processes the volume column first again:

   www.un4seen.com/stuff/xmplay.exe

Let me know if you find any other S3M or IT files don't sound right any more :)

Dotpitch

  • Posts: 2861
Re: 3.8 reports, queries and bugs
« Reply #458 on: 24 Mar '17 - 18:08 »
I think you changed it here because of this test file. Perhaps Impulse Tracker and Scream Tracker are slightly different in this regard.

saga

  • Posts: 2110
Re: 3.8 reports, queries and bugs
« Reply #459 on: 24 Mar '17 - 19:43 »
Thanks for the fix!
The "set volume" command in the volume column is "special" and always supposed to be processed first (also in IT), and since Scream Tracker has no other commands to which the IT special case would apply for, this fix is definitely wrong for S3M and only valid for IT. :)
« Last Edit: 24 Mar '17 - 20:00 by saga »