-
Notifications
You must be signed in to change notification settings - Fork 9
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
Unpacking a non-rawcooked FFV1/MKV #118
Comments
Oops... True, I should test sooner that there are issues here.
More work (I need to create the DPX header for every flavor of FFV1) but doable, just wondering how useful it is vs e.g. FFmpeg directly (if/when my decoder is quicker, it is another story... ;-) ) |
Sorry that this report contains 2 different things:
Shall I create a separate issue for no.2 - as a wishlist thing? e.g. printf syntax for filenames might be scary for some: %03d.dpx? %06d.dpx? You know... 😨 |
Would be better, true, I will not implement that at the same time.
Issue is that I'll have to decide arbitrary of the format. but true, easier for beginners.
And will not be the priority until a sponsor shows interest. |
Is this implemented in the current head? |
Not yet implemented. |
If I use normal Matroska/FFV1 file, i.e. not a RAWcooked one, then I receive the error message:
I suggest to have a more telling message. |
Crash is not a feature :). |
Especially not in the airlines industry…
Thank you! |
When starting rawcooked with a "normal" FFV1/MKV file (=not produced by rawcooked), rawcooked processes the whole file (CPU at 100%) - but only at the very end says:
Would it be possible to tell the user earlier that nothing will be output?
Or even more daring:
Would it be possible to actually output a generated DPX sequence for such files?
(But that's wishlist of course 😉 )
The text was updated successfully, but these errors were encountered: