Forums > Jitter

feature request for jit.qt.record

May 26, 2006 | 5:20 pm

Hello,

I have a small (hopefully) feature request for jit.qt.record – to
have it output some sort of message out of it’s right outlet when the
user has selected a file via the file dialog, or if they haven’t.
Something like "writing FILENAME.mov 1" if the user successfully
chose a filename via the OS dialog box or "writing 0" if they
canceled it. Is that even possible? (some creeping suspicion in me
thinks that it isn’t)

This comes up a lot, and I noticed that Randy Jones wrote js to get
around it, but it’s a little convoluted and would be so much more
useful and simple if it was all in the jit.qt.record itself.

Plus, it was my birthday 2 weeks ago… c’mon Jeremy, can I please
have this as a belated present? Please please please? :)

-evan


May 29, 2006 | 11:08 am

This is possible. I’ll add it to the list of things to ponder.

jb


May 29, 2006 | 4:40 pm

Great!! Thanks, Jeremy.


June 5, 2006 | 12:22 pm

Until this feature makes it into jitter, I found another way to
accomplish this (e.g. to get a bang/event when the file is actually
being written to disk, or if it was canceled). It uses the "gettime"
message, which only seems to report the currently recorded frame #
when a file is being written, or it reports a bang otherwise.

-evan

max v2;
#N vpatcher 10 59 610 459;
#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P newex 383 275 70 196617 s QTRecStart;
#P window linecount 2;
#P newex 383 241 50 196617 select 0 bang;
#P window linecount 1;
#P message 160 139 29 196617 stop;
#P newex 331 209 114 196617 route codeclist time;
#P message 141 119 64 196617 getcodeclist;
#P newex 331 306 60 196617 print codec;
#P newex 331 278 25 196617 iter;
#P newex 435 241 83 196617 s QTrecordMsgs;
#P window linecount 2;
#P message 218 121 156 196617 write photojpeg lossless 600 , gettime;
#P window linecount 1;
#P newex 208 178 108 196617 jit.qt.record 640 480;
#P window linecount 7;
#P comment 462 274 100 196617 < -- will bang when qtrecord starts
actually writing to file – if file dialog is canceled , time will
send a "bang" instead of a frame #;
#P fasten 2 0 1 0 223 169 213 169;
#P lcolor 1;
#P fasten 6 0 1 0 146 169 213 169;
#P connect 8 0 1 0;
#P connect 1 1 7 0;
#P connect 7 0 4 0;
#P connect 4 0 5 0;
#P connect 7 1 9 0;
#P connect 9 0 10 0;
#P connect 7 2 3 0;
#P pop;


June 5, 2006 | 1:11 pm

my last solution doesn’t seem to work in some cases – if the file
already exists, and you try to write over it, gettime reports nothing
instead of 0.

Bug report:

"gettime" msg doesn’t properly report the correct number of frames
recorded to disk in some situations.

Expected behavior:

A "write" message to jit.qt.record followed by a "gettime" message
should report "time 0" (the start of the file, no time recorded).

Problematic behaviour:

This works properly UNLESS the file already exists and would be
overwritten.

Steps to reproduce:

See patch below – send "write, gettime" message, and see that "time
0" message is received. Then send "write, gettime" again, selecting
the same file name in the OS file dialog. "time" message will be
received.

Best,
Evan


June 5, 2006 | 7:07 pm

I can’t reproduce this on Mac. What OS are you using? You’re missing
a framerate in your write message, btw, so your patch doesn’t
actually work.

jb


June 5, 2006 | 9:19 pm

sorry, i copied/pasted that patch from another. sloppy of me.

i’m on 10.4.6 with QT 7.1.1.

i tried reproducing it again, and realized that this only happens
when you have finder open and the movie selected and the little
preview open in the finder window (the right-most preview pane of the
finder window). otherwise it works in all the other situations that
i tried. i had a few windows open with previews, and this must have
been the cause of the trouble. this seems like more of a mac/finder
issue than a max one, I’m guessing. but is there anything that can
be done to test for this case?

-evan


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