HydrogenAudio

Hosted Forums => foobar2000 => Support - (fb2k) => Topic started by: yakuman on 2012-06-02 03:32:51

Title: 1.1.12a: manually seeking to start still fades in + sometimes glitches
Post by: yakuman on 2012-06-02 03:32:51
I just noticed a bug in v1.1.12a portable with seeking to the beginning (time position 0:00) of an MP3 file after it's already started playing.  Even with all fading options disabled in the Output screen, whenever I manually drag the seek bar to the beginning of a playing file it would still fade in.  With some files, I get the fade in plus some unwanted sudden bump in the audio as if it was skipping for quick split second.  This is even more noticeable for songs that start immediately versus those with a couple of seconds of silence.

I quickly re-tested v1.1.11 to confirm it doesn't exist with that version.
Title: 1.1.12a: manually seeking to start still fades in + sometimes glitches
Post by: yakuman on 2012-08-17 22:48:02
Bug continues through to current v1.1.14
Title: 1.1.12a: manually seeking to start still fades in + sometimes glitches
Post by: Peter on 2012-08-21 10:38:03
Sorry, cannot confirm the bug. Please follow instructions in foobar2000 Tech Support Forum Rules (http://www.hydrogenaudio.org/forums/index.php?showtopic=67779) and post more details about your configuration, thank you.
Title: 1.1.12a: manually seeking to start still fades in + sometimes glitches
Post by: yakuman on 2012-08-21 12:01:43
I found the cause.  After testing many of my mp3 files, it only affects those that I trimmed off the silence part at the beginning using a tool called mpTrim.  To further test it, I re-added a mere 0.2 seconds of digital silence to the beginning of one of those files with mpTrim and the problems stopped.  This didn't exist in v1.1.11 and prior.  It seems to suggest that foobar now doesn't like files without at least a reasonable amount of silence padded in front.
Title: 1.1.12a: manually seeking to start still fades in + sometimes glitches
Post by: Peter on 2012-08-21 13:53:34
Sounds like it is related to MP3 decoder fixes made sometime around 1.1.12a; not related to fading functionality. Thanks for the report.