(In reply to pea.berberian from comment #6) > Hi, > > Sorry for the bump but any news on that issue? > > Knowing if this has been confirmed as a Firefox issue (or at least suspicions of it) and/or if a possible fix is under way will help us find the right solution on our side. This is indeed a firefox bug. What I can suggest you do in the mean time, is before sending a new init segment, call abort() (https://w3c.github.io/media-source/#dom-sourcebuffer-abort) ; this will force the re-creation of the demuxers. This solution will work with all browsers too ; we likely never saw that bug before because most players would send abort before sending a new init segment ; as it makes it easier to deal with partial media segment.
Bug 1679283 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to pea.berberian from comment #6) > Hi, > > Sorry for the bump but any news on that issue? > > Knowing if this has been confirmed as a Firefox issue (or at least suspicions of it) and/or if a possible fix is under way will help us find the right solution on our side. This is indeed a firefox bug. What I can suggest you do in the mean time, is before sending a new init segment, call abort() (https://w3c.github.io/media-source/#dom-sourcebuffer-abort) ; this will force the re-creation of the demuxers. This solution will work with all browsers too ; we likely never saw that bug before because most players would send abort before sending a new init segment ; as it makes it easier to deal with partial media segment. Edit: it's actually not going to work, ignore this. What could work is send a dummy init segment significantly different to the first one (like using a different sampling rate or number of channels) ; and then send the actual init info you want.
(In reply to pea.berberian from comment #6) > Hi, > > Sorry for the bump but any news on that issue? > > Knowing if this has been confirmed as a Firefox issue (or at least suspicions of it) and/or if a possible fix is under way will help us find the right solution on our side. This is indeed a firefox bug. What I can suggest you do in the mean time, is before sending a new init segment, call abort() (https://w3c.github.io/media-source/#dom-sourcebuffer-abort) ; this will force the re-creation of the demuxers. This solution will work with all browsers too ; we likely never saw that bug before because most players would send abort before sending a new init segment ; as it makes it easier to deal with partial media segment. Edit: it's actually not going to work, ignore this. What could work is send a dummy init segment significantly different to the first one (like using a different sampling rate or number of channels) ; and then send the actual init info you want. Or not send a new init segment if the content is in fact identical like here (same sampling rate, number of channels and format)
(In reply to pea.berberian from comment #6) > Hi, > > Sorry for the bump but any news on that issue? > > Knowing if this has been confirmed as a Firefox issue (or at least suspicions of it) and/or if a possible fix is under way will help us find the right solution on our side. This is indeed a firefox bug. What I can suggest you do in the mean time, is before sending a new init segment, call abort() (https://w3c.github.io/media-source/#dom-sourcebuffer-abort) ; this will force the re-creation of the demuxers. This solution will work with all browsers too ; we likely never saw that bug before because most players would send abort before sending a new init segment ; as it makes it easier to deal with partial media segment. Edit: it's actually not going to work, ignore this. What could work is send a dummy init segment significantly different to the first one (like using a different sampling rate or number of channels) ; and then send the actual init info you want. Or not send a new init segment if the content is in fact identical like here (same sampling rate, number of channels and format). On Android the latter will behave better as it can take 2s to re-create a new audio decoder)
(In reply to pea.berberian from comment #6) > Hi, > > Sorry for the bump but any news on that issue? > > Knowing if this has been confirmed as a Firefox issue (or at least suspicions of it) and/or if a possible fix is under way will help us find the right solution on our side. This is indeed a firefox bug. What I can suggest you do in the mean time, is before sending a new init segment, call abort() (https://w3c.github.io/media-source/#dom-sourcebuffer-abort) ; this will force the re-creation of the demuxers. This solution will work with all browsers too ; we likely never saw that bug before because most players would send abort before sending a new init segment ; as it makes it easier to deal with partial media segment. Edit: it's actually not going to work, ignore this. What could work is send a dummy init segment significantly different to the first one (like using a different sampling rate or number of channels) ; and then send the actual init info you want.