Age | Commit message (Collapse) | Author |
|
the vis plugins should invalidate the extra info of the frames they output to not
interfere with the (correct) extra info which will be set by audio out
CVS patchset: 4250
CVS date: 2003/02/22 14:21:37
|
|
CVS patchset: 4152
CVS date: 2003/02/14 04:17:23
|
|
jumbo audio buffers (several seconds).
unfortunately it requires an extra data copy, but i don't think that will
make any perceptible difference.
CVS patchset: 3916
CVS date: 2003/01/14 21:00:23
|
|
to other plugins after some test/cleanup.
unfortunately we must support three cases here:
1) decoders that send data in small chunks, data must be accumulated between
multiple audio frames to generate a single video frame (eg: wav).
2) good sized decoder chucks, the naive approach of 1:1 audio/video frames
mapping usually works fine (eg: mp3)
3) very big decoder chunks. a single audio frame must generate several
video frames (eg: wma)
btw: mike, nice work on oscope!!
CVS patchset: 3787
CVS date: 2003/01/05 15:05:55
|
|
viz plguin, as well as a reference template viz plugin
CVS patchset: 3776
CVS date: 2003/01/04 20:42:47
|