lists@lowfrequency.or

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 

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? :)

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? :)

feature-request-for-jit-qt-record

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

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.

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.

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 

"gettime" msg doesn't properly report the correct number of frames 

A "write" message to jit.qt.record followed by a "gettime" message 

should report "time 0" (the start of the file, no time recorded).

This works properly UNLESS the file already exists and would be 

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 

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.

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

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

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

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.

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 

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.

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

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 

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

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?