Hi there.

I'm having some issues with JMyron. It's the latest build, on Processing 0115 (tried on the latest P5 but it's still the same).

Anyway, the images is scrambled somehow. Like a region of the image is multiplied 5 times and put one next to eachother. This doesn't happen with the normal QT+WinVDIG setup.
http://www.10megatons.com/zzztemp/processing/crap.gif

The camera is a Sony VX2100E via firewire.
http://www.globalmediapro.com/video/products/Sony_DCRVX2100E_DV_Camcorder_PAL--1139.html


The thing is, I don't need anything special from JMyron route, but the performance of VDIG is utter crap, it's about 2-3 fps and a delay of about 0.5s. It's unusable. I don't get it, I don't know what else I could do. (*pulls hair*)

If you have any ideas, solutions, links, a hug, please let me know.

Thanks.

P.S.
How's Flash's video thing? Any good?

i have a Logitech QuickCam Chat and had the same problem using jmyron when i just discovered the use of this line in a sourcecode :

println("Forced Dimensions: " + m.getForcedWidth() + " " + m.getForcedHeight());

it gives you the real sized used by the webcam in order to get the good result with JMyron lib in Processing !!!

so i discovered i was obliged to use 352x288 instead of the usual 320x200 or else and now it works just fine!

Right, this happens because it's getting the wrong dimensions when copying to the pixels array. Note that you can avoid the problem entirely if you avoid generic references to width and height and manually copy over pixels, which may actually be useful for some projects when you want to creatively interpret that pixel data (as in a number of the Processing video library examples).

Note that getForcedWidth and getForcedHeight will not work on Mac; it'll throw an exception. So take those lines out when going to Mac.

Incidentally, I find it's worth playing with 0125 as the capture examples, etc., have been updated and expanded.

I've used Flash video, as well. Input is great and it's what you'll need if you're deploying to the web. But you won't be able to do nearly as much with the data once you've captured it, and what you can do is much, much slower in ActionScript than in Java.

I do think Flash should be a model for the kind of basic capture and playback Java should support, and I'm not alone.

http://www.oreillynet.com/onjava/blog/2006/12/rebooting_java_media_act_i_set.html
http://www.oreillynet.com/onjava/blog/2006/12/rebooting_java_media_act_ii_de.html
http://www.oreillynet.com/onjava/blog/2007/01/rebooting_java_media_part_iii.html

That goes into some Flash vs. Java issues, and further illustrates that part of the frustration here is that there's stuff you can do with Java that you can't with Flash. (Worth reading, in fact, if you're playing with JMyron just to get a broader perspective ... and with Processing, anyway, you could duplicate and perhaps improve upon that Flash example, just not easily in a browser!)

But anyway, go enjoy JMyron -- you'll find it and Processing's native libraries to be FAR more fun and satisfying than Flash, which only underlines Chris Adamson's argument about why media is cool!

Although this topic is old, here is a tip:

when using processing video lib, don't forget to include the P2D argument in the size method to get faster response.

ex.:

size(640, 480, P2D);
cam = new Capture(this, 640, 480, 30);