Forums > Jitter

delayed output response from jit.qt.grab – is this normal or a bug?

March 3, 2010 | 4:02 pm

When my jit.qt.grab object receives a "bang", it outputs not a "fresh" frame, but the one recorded when it received the earlier "bang". This means that, the output of my jit.qt.grab i always one entire frame-time delayed. This is even the case, when i set the metro to "bang" every 1000ms. It still sends out the previous frame. Is this normal? Has anyine got the same problem?



Ad.
March 3, 2010 | 5:14 pm

It’s normal.
You want to visualise something wich is grabbed at the same time…it’s not possible !
You have to delayed the visualisation, not the grabber.

max v2;
#N vpatcher 0 44 1680 1046;
#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P newex 723 115 48 196617 loadbang;
#P button 421 439 123 0;
#P newex 629 392 56 196617 qlim 1000;
#P toggle 555 171 15 0;
#P user jit.pwindow 628 461 598 440 0 1 0 0 1 0;
#P message 629 204 30 196617 open;
#P newex 629 254 63 196617 qmetro 100;
#P newex 629 298 56 196617 jit.qt.grab;
#P fasten 5 0 6 0 615 398 605 388 605 421 576 401 563 367 552 401 528 387 540 405 540 412;
#P fasten 7 0 4 0 678 90 642 120 629 102 629 145 562 155 531 90;
#P fasten 7 0 2 0 755 170 726 155 674 116 674 137 701 158 668 147 639 158 614 173 634 196;
#P fasten 4 0 1 0 550 214 562 214 573 233 616 207 616 224 579 254 454 237 536 285 592 272;
#P fasten 2 0 0 0 670 237 681 171 701 178 724 167 733 193 733 255 704 283 646 292;
#P connect 1 0 0 0;
#P fasten 0 0 5 0 594 341 616 348 616 372 697 372 765 336 771 365 675 386;
#P connect 5 0 3 0;
#P pop;

Ad.


March 4, 2010 | 9:01 am

Thank you for the repply.
Is it possible to make the jit.qt.grab output only when it is done grabbing?, and not wait untill it receives next bang?


Viewing 3 posts - 1 through 3 (of 3 total)