hi anyone used gridflows #record? playback of the file in gridflow itself works but when i'm trying to play the file in mplayer i get the error message: "hmblck: image size inconsistent with data size." & mencoder neither likes to reencode it... thanks for help & greets olsen
hi olsen
i am not sure, if this helps you, but this is how i create movies using gridflow:
- 'open movie.mov' -> [#out]
- 'framerate 25' -> [#out]
- 'codec jpeg' -> [#out]
- send some grids to [#out]
- 'close' -> [#out]
note: the 'close' message is mandatory, since otherwise the resulting file is corrupted (i assume because of a lacking or wrong index). afaik, it also matters in which order you send those messages, e.g you have to first open a movie and _then_ send the specifications such as codec and framerate.
excuse me, if this seems too obvious, but [#out] behaves differently from other video writing objectclasses in pd, because [#out] can be used either to display grids, write images or write movies. that is why the order of messages is critical, whereas it isn't e.g for [pix_record].
this works for me. if it doesn't for you, tell us exactly, what you do, what messages you get in the pd-window and and probably provide us a short .mov file, that is apparantly corrupted.
roman
On Sun, 2008-01-06 at 23:54 +0100, olsen wolf wrote:
hi anyone used gridflows #record? playback of the file in gridflow itself works but when i'm trying to play the file in mplayer i get the error message: "hmblck: image size inconsistent with data size." & mencoder neither likes to reencode it... thanks for help & greets olsen
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
On Tue, 8 Jan 2008, Roman Haefeli wrote:
- 'open movie.mov' -> [#out]
- 'framerate 25' -> [#out]
- 'codec jpeg' -> [#out]
- send some grids to [#out]
- 'close' -> [#out]
note: the 'close' message is mandatory, since otherwise the resulting file is corrupted (i assume because of a lacking or wrong index).
Yes, that and because the output is not flushed, so some data hasn't been sent to the filesystem drivers yet. This requires a close. This latter operation is done automatically on normal exit of pd, but in the case of the index, you really absolutely need a close message.
afaik, it also matters in which order you send those messages, e.g you have to first open a movie and _then_ send the specifications such as codec and framerate.
Yes, it matters, because those options are specific to what kind of thing you open. If you do "open window" instead, a different hidden object will be created than if you "open foo.jpeg" or "open "foo.mov". The "close" message both closes the file and deletes the hidden object. Most settings belong to the hidden object, so if you reopen something of the same kind, the settings will still be gone anyway.
excuse me, if this seems too obvious, but [#out] behaves differently from other video writing objectclasses in pd, because [#out] can be used either to display grids, write images or write movies. that is why the order of messages is critical, whereas it isn't e.g for [pix_record].
So far, [#in] and [#out] are the only GF classes that do some kind of dynamic patching.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada
On Sun, 6 Jan 2008, olsen wolf wrote:
anyone used gridflows #record? playback of the file in gridflow itself works but when i'm trying to play the file in mplayer i get the error message: "hmblck: image size inconsistent with data size." & mencoder neither likes to reencode it... thanks for help & greets olsen
I have never used [#record], but I use [#out quicktime] sometimes, and lately I haven't had that problem, so I figured out that I have already fixed it. Is this not the case? Which version of GridFlow ?
In any case, all frames in your video should have the same size. The encoder won't complain, but many playback programs will. Long ago I had that error message even when all frames were all of the same size.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada
unfortunately on a new installation of gridflow i end up with the "i don't wanna be famous" Pd: signal 4 trying to record. so i'm not getting beyond step1 of romans cue. as soon as i give a message for the framerate pd process exited. i tried this is on an actual cvs version on an uptodate kubuntu 7.10 using the #record-help.pd patch how can [#out quicktime] be created? thanks for help & hints olsen
On Jan 9, 2008 7:53 PM, Mathieu Bouchard matju@artengine.ca wrote:
On Sun, 6 Jan 2008, olsen wolf wrote:
anyone used gridflows #record? playback of the file in gridflow itself works but when i'm trying to play the file in mplayer i get the error message: "hmblck: image size inconsistent with data size." & mencoder neither likes to reencode it... thanks for help & greets olsen
I have never used [#record], but I use [#out quicktime] sometimes, and lately I haven't had that problem, so I figured out that I have already fixed it. Is this not the case? Which version of GridFlow ?
In any case, all frames in your video should have the same size. The encoder won't complain, but many playback programs will. Long ago I had that error message even when all frames were all of the same size.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada
-
Mathieu Bouchard -
olsen wolf -
Roman Haefeli