[GEM-dev] [ pd-gem-Feature Requests-1901418 ] pix_write to a PPM stream
SourceForge.net
noreply at sourceforge.net
Wed Jul 14 20:46:15 CEST 2010
Feature Requests item #1901418, was opened at 2008-02-25 14:46
Message generated for change (Comment added) made by nobody
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=507082&aid=1901418&group_id=64325
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Pending
Priority: 5
Private: No
Submitted By: ClaudiusMaximus (claudiusmaximus)
Assigned to: Nobody/Anonymous (nobody)
Summary: pix_write to a PPM stream
Initial Comment:
I would very much like if pix_write could write successive frames to a PPM stream. This would let me to do things like:
mkfifo stream.ppm &&
pd -nogui -lib Gem -open my-rendering-patch.pd &
cat stream.ppm |
ppmtoy4m ... |
y4mscaler ... |
mpeg2enc ...
At the moment I'm rendering to multiple TIFF files, which takes a vast amount of temporary disk space, and is more complicated to encode later.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2010-07-14 18:46
Message:
for writing to a PPM stream, you can already do [#from_pix, cast b] and
then [#out ppm mypipe.ppm]. why require a GEM-only solution ?
btw I don't understand what v4l1-loopback has to do with the question.
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2010-07-14 17:48
Message:
i have added an experimental support for writing to v4l1-loopback devices
to the [pix_record] class.
unfortunately, [pix_record] (and the record-backends) are badly designed
right now, i guess they need a major overhaul.
in the meantime:
- install vloopback kernel-module
- get latest Gem (svn)
- build, cd to src/plugins/recordV4L/ and run "autoreconf -fiv &&
./configure && make"
- copy the resulting ./libs/gem_recordV4L.so besides the Gem.pd_linux
- make sure you have no other gem_record* lying besides Gem.pd_linux
- start pd/Gem
- create [pix_record]
- use [file /dev/video1, record 1( (or whatever your vloopback-write
device is)
- then you should be able to access the output of pix_record via
/dev/video2
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=507082&aid=1901418&group_id=64325
More information about the GEM-dev
mailing list