Displaying 2 results from an estimated 2 matches for "pipeline_error_decod".
Did you mean:
pipeline_error_decode
2018 Apr 18
2
Intro & Chrome v. 65.0.33.25.181
Hi there,
Any other versions of Google Chrome and all version of other browsers are working.
I have done my best to set up the intro to match the live stream.
http://185.139.168.34:8000/yleisohjelma
- intro is 256 kbits/s 48 kHz ISO-MPEG2 L3
- live is 256 kbits/s 48 kHz ISO-MPEG2 L3
http://185.139.168.34:8000/vara
- live is 128 kBits/s 48 kHz, possible ISO-MPEG2 L3
- there is no intro
Of
2018 Apr 19
0
Intro & Chrome v. 65.0.33.25.181
There should be no issue with the varying bit rate. For an MP3 stream, you
can change bit rates mid-stream all you want as long as you keep the sample
rate and channel counts the same.
If you check chrome://media-internals, you'll see that you're getting
a PIPELINE_ERROR_DECODE. Since Chrome v64, it has been a lot more picky
about the streams it accepts.
I suspect that Icecast is simply dumping the buffer for the file out to the
client, and then needle-dropping into the middle of the live MP3 stream
without re-syncing to a frame boundary first. (Someone more familiar...