#116 in feeder mode MPG123_DONE is returned

0.68
closed-fixed
nobody
None
5
2013-02-24
2009-09-23
Patr3ck
No

MPG123_DONE should never be returned in feeder mode, right? We're decoding an stream.

Reason:
If a Xing/Lame/Info header is detected the length is initialized because frame_gapless_init is called in check_lame_tag with the parsed length from the lame header. This results in MPG123_DONE returns later in decoding.

Could those headers be skipped as junk if we are in feeder mode?

Discussion

  • Thomas Orgis
    Thomas Orgis
    2012-05-01

    Could you re-evaluate the situation with 1.14.0? The choice of input mode does not influence the gapless decoding (you can just disable it yourself if you don't want it overall), but there is the attempt to avoid premature MPG123_DONE if there is still data to decode (Frankenstrein streams).

     
  • Thomas Orgis
    Thomas Orgis
    2013-02-24

    • status: open --> closed-fixed
    • milestone: --> 0.68
     
  • Thomas Orgis
    Thomas Orgis
    2013-02-24

    I assume this is fine now.