My 5 cents would be: stop means stop, this is a not slowing down car.
Hmm, tough one. For one I hate hardcoded values - at the same time 4 secs is too long while it is a good value for x-fading. So my vote would be with 2 secs.
For a given Definition of bug, no. If a bug also includes misleading the user to believe the System is not working, this might be a bug...The problem is that this is NOT a bug fix
but if user configured his system to do fadeout? as @hwahrmann already said, this is an option that can be enabled/disabledmisleading the user to believe the System is not working
Probably windows. What is the output rate set to for standard windows? What sound card is this (can you fill in system specs)- 24/96 and DTS spdif passthrough only works with ASIO. Bass player will pass through 24/96 but DTS results in noise. This indicates that there is still some re-sampling going on somewhere.
Logs pleaseWASAPI does not work for me. Everything stays silent (M-Audio audiophile PCI interface)
You have enabled this in config?- Skip steps don't work on forward and rewind when using a remote (IrTrans). I tried mapping FWD and REW buttons to F5 and F6 but that also doesn't work. I get a feeling fwd and rew commands coming in through the remote are not handled at all in the music player this build. Is that possible or am I talking rubbish? (F5 and F6 do work)
Logs might help- I've been having a lot of drop outs. Mediaportal.exe seems to be using a lot of CPU during music playback. I have no idea why (not using visualisations) This was not an issue in 1.3.0. BASS and ASIO Buffer settings all at maximum now, but that doesn't help much. Is there any way I can see what MP is doing that could be consuming so much CPU?
Probably windows. What is the output rate set to for standard windows? What sound card is this (can you fill in system specs)- 24/96 and DTS spdif passthrough only works with ASIO. Bass player will pass through 24/96 but DTS results in noise. This indicates that there is still some re-sampling going on somewhere.