-
Notifications
You must be signed in to change notification settings - Fork 6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support lacing in Matroska Blocks #3026
Comments
The relevant error is "Lacing only supported in SimpleBlocks". Marking as an enhancement to support lacing in Blocks, but this seems to be rarely used so it's unlikely we will get round to it soon. (And if we do implement this, you'd need to upgrade to v2 to use it.) If you need to use lacing, is it feasible for you to change the container to use only SimpleBlocks? |
@andrewlewis thanks for your replying.So currently I will notice user not support this video format. |
just downloaded random movie and couldn't play it, got this error |
As per response above, this is low priority and is unlikely to be resolved soon. |
@ojw28 well I downloaded one more random movie (mkv) and again this error, so it's not that rarely, I believe it will happen quite often |
We've received two reports of this error in the past six months, which does not suggest this is a widely used feature. |
@ojw28 I think not many developers tested with 2-5 gb (bdrip 720p) MKVs, for me the problem happened with such videos |
The exception is thrown when I try to play a link today. |
I'm afraid we're still treating this as low priority. We can revisit it if someone can provide evidence that there is a lot of demand for playing files with this feature. I think we're also happy to accept pull requests that cleanly add this functionality to |
I am interested in this issue. |
No. We're still treating this as a low priority feature request. |
I have this issue with a number of MKV's and would love to see it fixed. Exoplayer is used by the Emby Android TV app to play movie files, and the issue has been reported on the Emby forums a number of times: Also on the Plex forums: I would certainly welcome this feature. I'm sure the users who reported their issues in the links above would too. |
Thanks for the information. We are still treating this as a low priority feature request. I think we'd also welcome a pull request that adds support. [Also tracked by internal issue: b/122814967.] |
@andrewlewis Hi there, thanks in advance |
Yes, as per what Andrew's already written above. We have no near term plans to work on this. |
- Change sampleHasReferenceBlock to a block reading variable, which is what it is (the distinction didn't matter previously, but will do so when we add lacing support in full blocks because there wont be a 1:1 relationship any more. - Move sampleRead to be a reading state variable. - Stop abbreviating "additional" Issue: #3026 PiperOrigin-RevId: 284000937
- Remove "lacing" from member variables. They're used even if there is no lacing (and the fact that lacing is the way of getting multiple samples into a block isn't important). Issue: #3026 PiperOrigin-RevId: 284152447
- Change sampleHasReferenceBlock to a block reading variable, which is what it is (the distinction didn't matter previously, but will do so when we add lacing support in full blocks because there wont be a 1:1 relationship any more. - Move sampleRead to be a reading state variable. - Stop abbreviating "additional" Issue: #3026 PiperOrigin-RevId: 284000937
- Remove "lacing" from member variables. They're used even if there is no lacing (and the fact that lacing is the way of getting multiple samples into a block isn't important). Issue: #3026 PiperOrigin-RevId: 284152447
This change constrains the use of sample state member variables to writeSampleData, finishWriteSampleData and resetWriteSampleData. Using them elsewhere gets increasingly confusing when considering features like lacing in full blocks. For example sampleBytesWritten cannot be used when calling commitSampleToOutput in this case because we need to write the sample data for multiple samples before we commit any of them. Issue: #3026 PiperOrigin-RevId: 284541942
Caveats: - Block additional data is ignored if the block is laced and contains multiple samples. Note that this is not a loss of functionality (SimpleBlock cannot have block additional data, and lacing was previously completely unsupported for Block) - Subrip and ASS samples are dropped if they're in laced blocks with multiple samples (I don't think this is valid anyway) Issue: #3026 PiperOrigin-RevId: 284545197
This is supported in |
This change constrains the use of sample state member variables to writeSampleData, finishWriteSampleData and resetWriteSampleData. Using them elsewhere gets increasingly confusing when considering features like lacing in full blocks. For example sampleBytesWritten cannot be used when calling commitSampleToOutput in this case because we need to write the sample data for multiple samples before we commit any of them. Issue: #3026 PiperOrigin-RevId: 284541942
Caveats: - Block additional data is ignored if the block is laced and contains multiple samples. Note that this is not a loss of functionality (SimpleBlock cannot have block additional data, and lacing was previously completely unsupported for Block) - Subrip and ASS samples are dropped if they're in laced blocks with multiple samples (I don't think this is valid anyway) Issue: #3026 PiperOrigin-RevId: 284545197
This is also supported in our |
when I play some mkv files,exoplayer report error below.
and this is the link of file
https://drive.google.com/open?id=0BwneL-jNaOWGMXRXN0RrYWNnUTQ
The text was updated successfully, but these errors were encountered: