Loading...
Logo
Processing Forum
This release solves a number of issues and adds some new functionality. Follow this link for more detailed information.

Replies(10)


It seems this version is not affected by memory leak I notice in past..

Which codec is better handled by gsvideo? i tried quicktime full hd video and in quicktime is played without problem, but the same video in gsvideo runs at 15/16 fps.. 
I've only just updated yesterday but generally it looks like gsvideo 0.8 is performing much better than 0.7 both on linux & mac

I'm getting fairly good playback with 720p h264 video in a high-loading program (@60% cpu usage on my iMac 9,1), but 1080p h264 plays at about 35fps and audio not syncing -- this is with gstreamer-ffmpeg. 

I'm trying to get gstreamer-vaapi or fluendo working but no success yet. I wonder if the google team used any hardware acceleration with their project? 


As far as I know, the google touchscreen uses clips at relatively low resolutions for the "thumbnail" mode. Not sure what is the resolution of the videos that are played in full screen mode, but I don't think they are doing HD.

As for getting better framerates in gsvideo, specially for full HD, the OpenGL plugins in gstreamer are probably the best alternative. Although it requires some work to get opengl, gstreamer and java nicely talking to each other.
Do you think this will change in the new 2.0 version of Processing? I mean, they're changing the way Processing deals with OpenGL, right?
I don't think this will change in Processing 2.0, as it is more of an issue of integrating Gstreamer with OpenGL through Java.

Anyways, I found another method to better combine GSVideo and GLGraphics in order to reduce CPU usage. Still debugging it, but playback of HD videos seems better, at least on OSX. The test packages for GLGraphics and GSVideo that include the new method are here and here (build date 2011-04-11). Try the Movie/GLPlayback example with some HD clip. Using the xvid codec appears to be give better results than h264, at least for now.
Ok, so I tried the newest library with Processing 0195 on my Linux netbook. Almost all problems I had before seem to have been solved (no crashes whatsoever), except when I try to capture an image with the PS3 Eye. All the images come out overlapping and jumping as if the code reads:

Copy code
  1. set( int(random(-width, width)), int(random(-height,height)), cam);
(Using your moviemaker class I managed to make a small movie showing what happens, but I'm not writing this from my netbook, so I can't upload right now.)

The weird part is that the PS3 Eye works fine if I open it as a capture device in other software (say, VLC), and that the built-in webcam also works fine with the library. So there's something specifically going wrong with the combination of a PS3 Eye with GSVideo (at least on my netbook, running Linux).

I get the feeling your library isn't to blame, especially considering this problem somehow emerged last year after GSvideo had worked with the PS3 Eye without any trouble before. However, I don't really know where to look. Any thoughts?
What is the last version of GSVideo your camera works fine with?

It would also be good to check if you can get the camera working using gstreamer directly from the command line, in order to rule out any low-level issues (note that VLC is not based on gstreamer).
Well, that's the thing: the old versions stopped working as well, which makes it highly unlikely that GSVideo is to blame.

I'll see if I can get the camera running from the command line, like you suggested.
ok, so maybe something changed in gstreamer. let me know how it goes with the command line tests.