Branch: refs/heads/master
Home: https://github.com/mltframework/mlt
Commit: ca97ca2f37ce048d00587e149883ba7472e15fce
https://github.com/mltframework/mlt/commit/ca97ca2f37ce048d00587e149883ba7472e15fce
Author: Brian Matherly
Date: 2015-02-25 (Wed, 25 Feb 2015)
Changed paths:
The purge will still work.
As designed, the parent consumer keeps a buffer of pre-rendered frames. By
default this buffer is 25 frames. When the SDL consumer retrieves a frame from
the parent buffer it plays the audio and then pushes the frame into a second
(smaller) buffer for the video thread
I am worried about this change. "if the audio was displayed for
a frame, the video should also be provided for the display" as-stated
violates the concept of frame-dropping, but I think you mean only in
certain situations because this consumer does not call
mlt_frame_get_image().
Does this consume
Dan,
This relates to my recent Shotcut changes. I'm very open to comments on this
change. I feel like I did a pretty thorough analysis before making the change -
and a fairly rigorous test after the change. But there is always a risk of
regression.
If you have any concerns, let me know.
~BM
Branch: refs/heads/master
Home: https://github.com/mltframework/mlt
Commit: 15f397deea19ded69bd068d6b7eb9be9d7b27806
https://github.com/mltframework/mlt/commit/15f397deea19ded69bd068d6b7eb9be9d7b27806
Author: Brian Matherly
Date: 2015-02-25 (Wed, 25 Feb 2015)
Changed paths:
