Menu

#3 Decoding causes sort-of-crash

Non-crashing_Bug
open
None
5
2000-06-12
2000-05-31
Anonymous
No

If I
1. instantiate a media reader node, reading a file with encoded audio
2. connect it to a decoder node
3. connect the decoder node to the system mixer (or any other node)
4. start the group

then the processor-load jumps up to 100% immediately, and no sound is played.

This only happens with audio, not video.

Discussion

  • Christopher Lenz

    • assigned_to: nobody --> eamoon
     
  • Christopher Lenz

    This should only happen with MPEG encoded audio, and is probably a bug in the mp3-decoder.

     
  • Eric Moon

    Eric Moon - 2000-06-12

    Yep, this is a known media kit/addon bug, likely at the extractor level. Since the extractor node was more or less abandoned in favor of the BMediaFile approach, it's not too likely to be fixed in the near future. (The problem occurs with audio and not video because it involves invalid timestamps being generated -- the video window consumer just displays frames as they're received and, I think, completely ignores timestamps, whereas the audio mixer is much pickier.)

    I wonder how hard it would be to write a new extractor/decoder node around the BMediaFile/Track API?

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.