zmoelnig at iem.mhsg.ac.at
Sun Sep 3 11:57:58 CEST 2000
> hi ,
> did some playing arounds with the pix_video object and a cheap hauppauge
> it worked surprisingly well except of the fact that i did only get a
> detail of the video to texture at all. dimen messages crashes gem and
> others doesn't seem to be available for nt.
> pix_video connects 320x240 but doesn't seem to offer to rescale input to
> it. i am able to catch scaled 320x240 in other applications so it doesn't
> seem to be a ptoblem of drivers.
> any knwon solutions to get this running?
> how does the pix_video object appear and perform on linux. is it worth to
> take the effort to try get it working?
trying as far, as i remember :
1.what does "crashes gem" really mean ?
2.of course you should only try to capture frames smaller than 320x240,
since 320x240 is the *maximum*.
gem does no rescaling at all and trying "pix_resize" won't work (is this
what you mean by "crashing gem": using pix_video + pix_resize ? i
experienced similar things : seems as if the pix_resize would be too
slow to manage the amount of data...)
1. grab only (2^n)x(2^m)-frames : this will lead to a maximum of 256x128
on your system, and will also lcapture only "a detail of the video".
2. try to make bigger frames with zero-padding : sometimes ago i wrote
an object (pix_video2) that did exactly this :: put a 320x240-frame into
a zero-padded 512x256 frame.
if you texture this to anything, you will get ugly black borders; but i
didn't mind, since i rendered the video to objects that were not
entirely seen (pe: texture to a rectangle where the black borders are
out of the visible screen)
maybe i can find the code somewhere...
More information about the Pd-list