[jitter] Realtime video buffer with variable speed access
Thierry Fournier
thierry at thierryfournier.net
Sat Dec 22 00:51:27 MST 2007
- Previous message: [jitter] Re: Realtime video buffer with variable speed access
- Next message: [jitter] Realtime video buffer with variable speed access
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello, Thank you again, a lot, for these explanations and the example. >> But theorically I could (in "thru 0") recall the last frame with >> "matrixoutput 0", or 1 or 2, etc and increase progressively my >> delay- but apparently these frames can be read only when the >> entire cycle is filled again. Did I miss someting ? >> > > perhaps i misunderstand, but i think you are confusing the way > matrixoutput and index works. > thru should be off, so that we only see what we call for using > <matrixoutput $1> > > jit.matrixset stores the incoming matrix at the position you > specify in the buffer through > the "index <int>" message. Yes, that was clear for me. > > "matrixoutput 0" outputs zeroth position of the buffer, not > exactly previous frame as you mention. > we need to keep track at which frame we just wrote into, so that we > can think on more or less > delay depending on that position. that's why i used the + and % > operator. it ensures the result > wraps around the max num frames, while keeping the same distance > from the frame just written. But I didn't get this point - I believed that the last frame was always at index 0. Though it's obvious that it can't be... I'm going to have a serious look at your patch, at timecube too (I downloaded it yesterday), and I come again when all these questions will be absolutely clear for me :-) Thanks very much again Andre Best Thierry
- Previous message: [jitter] Re: Realtime video buffer with variable speed access
- Next message: [jitter] Realtime video buffer with variable speed access
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
