This object class only works with a X11-based version of Pd. (e.g. on Linux, BSD, but not MacOS X).
Similar to
All other methods are as in
Subformat P6 only. Max-number can only be 255 (24-bit RGB).
Support for RGB-24 (3 channels) and RGBA-32 (4 channels)
Support for RGB non-progressive
Support for RGB non-progressive
Support for .mov files.
This format supports frame-seek and frame-tell.
Uses the HW-QuickTime library aka QuickTime4Linux (libquicktime.so). There is also a variant on the same library and that project is just called LibQuickTime.
Some versions of those libraries may include support for different codecs, and some also may support entirely different wrapper formats such as AVI.
On Macintosh, Apple QuickTime is used instead, but several of the following messages may not be available.
support for .mpeg files
this format supports frame-seek and frame-tell.
Two different libraries are available for dealing with MPEG files. Those have different details, capabilities and quirks.
In any case, GridFlow does not support importing audio from those files.
If you use the HeroineWarrior library, you may open several mpeg files at once, but not with the GregWard library.
Libraries may scream error messages in a rude way.
By opposition to PPM and TARGA, this format driver only allows a single MPEG stream per file (you cannot "cat" several MPEG files together).
Supports Rewind and Frame Select.
This is GridFlow's special file format. This is the only I/O
format that can hold anything that the
This is the picture format that would support TCP connections if that feature actually worked. More on this later.
When writing "raw" data, a file may be considered a long string of
base 256 digits (called bytes), but different computers have different
conventions for dealing with them:
Video4Linux-1 devices, RGB-24 only. Variable picture size.
We have been testing it using cards of the BT-848 family,
such as Miro DC10plus and Hauppauge WinTV, using the
Some hardware doesn't support RGB, so you may have to select a YUV colorspace
(see below) and then use
If for some reason there's a bug that causes a driver to produce BGR instead of RGB,
so that red and blue are swapped, you can swap them back by filtering through a RGB-BGR
converter, such as
color adjustments:
other options:
In case of mmap, the extra numeric argument sets the
queue length in number of frames, so you can select an
appropriate tradeoff between efficiency and latency.
supports 15,16,24,32-bit truecolor displays
now also support 8-bit indexed displays, using a private colormap configured as 3:3:2 RGB. When using 8-bit you can specify the "use_stripes" option to use a completely different color scheme involving R,G,B diagonal stripes, a kind of 6:6:6 RGB spread over three pixels.
If you are using Windows or MacOS 10: you will have to install a X11 server. This will emulate Unix display on your OS. (note: Unix systems also need a X11 server, but it's built-in and handles the video driver directly). In the case of MacOS 10 and QNX that both use non-X11 display technology on top of a basically Unix OS, the OS comes with a X11 server, but it may be on a "bundled software" CD.
Destroying the object (or sending "close") should close the window.
because of the design of Xlib, or if any of the connections involved crashes, then the whole program has to be terminated. (don't you love xlib). Something similar happens if you close any of the windows yourself, but IIRC this could be fixed.
only one window may be used per connection (to simplify matters; this doesn't reduce flexibility).
there is an additional argument that may be added to every
This is emitted every time the cursor moves inside the window connected to this format handler. This is also emitted when the cursor is dragging from inside to outside the window. This is also emitted when a mouse button is pressed.
The y and x coordinates are relative to the upper
right corner of the window. Specific button states may be
extracted from the button value by applying [>>
buttonnumber] and then checking whether the result is odd.
Button numbers normally are:
NOTE: This message form may become longer in the future, but the already defined parts will stay the same.
Similar to
NOTE: This message form may become longer in the future, but the already defined parts will stay the same.
NOTE: This message form may become longer in the future, but the already defined parts will stay the same.