|
|
It seems to be related to the situation, where audio device does not support format of the original track, in my case 192000Hz 24bit audio. Then it works for the first time (played correctly as 32bit audio), but when e.g. I double-click the same track again and in fact restart playback of the same file, it plays distorted. So when testing, you need to find file, which manifests this bug for your system and audio device. It seems 24bits are problem, I have similar problem with 44100Hz 24b. It is not regression, MM4 has the same problem. |
|
|
Fixed in build 2600. |
|
|
Original problem is fixed, but when user enables crossfade, it is back. It is caused by the fact, that if the next file has different sample size than the previous one, we cannot do crossfade in this exclusive mode, we can play only one output format at once. It could be probably fixed only by not doing crossfade in this case. |
|
|
Fixed too. |
|
|
Reopen Not fixed. |
|
|
Going from 192 -> 48 fails, but going from 48 -> 192 looks like work. image.png (17,231 bytes) |
|
|
I cannot reproduce, tried 3 different outputs, the same settings. |
|
|
There were some significant adjustments in WASAPI. Please retest with 2602, if you still reproduce it, I am not able at all. Btw. crossfading output of different output formats is not possible (your setting). |
|
|
It doesn't Garble in 2603, but Crossfading from 48->192 works (if set 8s crossfade starts at 4s) but When going back from 192->48 New track is loaded on crossfade time and stays at 0 till previous track ends. Is there way to check if sound card correctly set exclusive mode and freq? |
|
|
I cannot reproduce, for me the same settings lead to waiting for the next track always for both combinations. As it should because of different exclusive output formats. I can probably only add info to debug log, what output format was successfully set. Will do it to see what is exactly going on for you. |
|
|
We have it already there, see debug messages like "WASAPI: Initializing buffer for 192000/2/32", the last message of this kind before "WASAPI: Open() successfully finished" is the output format set. |
|
|
Resolving unable to replicate in past few versions of 5.0.3. Verified 2615 |
- Anonymous
