Project

General

Profile

Forums » Audacious »

Understanding bug 340

Added by Michael Schwendt about 11 years ago

http://redmine.audacious-media-player.org/issues/340

I get varying results trying to reproduce the issue. Okay, there's a delay upon trying to open the URL, and stream content probing is going on, but not for 40 seconds. Maybe I need to install all plugins?

Is this only related to out-of-bounds seek attempts or also related to the increased probe buffer size in 3.4.1 (16K -> 256K)?


Replies (2)

RE: Understanding bug 340 - Added by John Lindgren about 11 years ago

I would expect the delay to vary depending on the stream format and broadcast speed. As I just posted in reply to your comment on the bug report, there was some delay already in 3.4, and the increased buffer size in 3.4.1 just aggravated the problem.

The particular stream mentioned in #340 triggers a impossible seek in the AAC plugin. I've seen that plugin do similar things in the past, and I believe I came to the conclusion that it was a bug in one of the AAC or MP4 libraries, but that was some time ago and I don't remember the details. The fix I committed in core just handles that impossible seek more gracefully.

RE: Understanding bug 340 - Added by Michael Schwendt about 11 years ago

Thanks, John. We've merged the patch into our 3.4.1 test-update.

    (1-2/2)