February 23, 2004

more midterm madness

will aided yesterday and gave me some good ideas on stuff. nonetheless, max is going to be the death of me. there seems to be no good way to get the current frame of a movie - regardless of whether the movie is playing or not. wills method uses a framedump to get the current frame. but this requires a bang, which then forces a playback of the movie.

what i want is a static number, so when/whatever you are looking at, the frame number is reported. allowing a report on pause and during scrubbing.

there has to be a way to do this, but im going crazy trying to figure it out.

i though that sending the framedump out of the qt.movie, then back into a pack of framedump back into qtmovie would create a nice feedback loop that would report only on the current frame. but it seems that to send the framedump message to the qt.movie, you need a bang. so im right back where i started. arg.

why cant this program be more oo and open?

Posted by tripp at February 23, 2004 11:01 AM



Comments

first: max is by definition oo

second: it is basically open, in that you can write whatever c modules you want for it, and they provide documentation how to do that.

third: if you want help doing this, I can come in before class tomorrow and help. what you want to do sounds easy -- there are plenty of ways to do everything you are saying. I have no idea what your feedback loop thing is about -- right now, the currentframe is being spit out at every frame -- the issue I saw with your patch was the the way the movie wasn't stopping unless qmetro was off. I didn't have time to look into this, but it's most likely the problem.

Posted by: will at February 23, 2004 11:12 AM

well, i seem to just have boatloads of trouble pulling anything out of the objects provided. perhaps this is my own ineptness.

extensible, fine. but it doesnt seem easy to expose a lot of the information i know is lurking about in these objects. but then it might just be the visual nature that is throwing me off.

and id love to sit down with you tomorrow and look at it...say...2.30?

maybe then ill stop looking like such a dumbass.
wait, no thatll never happen.

Posted by: tripp at February 23, 2004 11:18 AM

yeah, the help objects are sometimes not that great -- the lurking factor is large, in that you know the answer is there somewhere, but you spend a lot of frustrating time trying to find it...

2:30 is fine. it'll be nice to take a break from the godawful collision detection for a bit.

max is a weird program -- takes a lot of manhours to start feeling comfortable.

Posted by: will at February 23, 2004 11:20 AM