Forums > MaxMSP

taking an image of a running webcamera movie through jamoma?


G4
May 3, 2010 | 12:19 pm

We wanted to first take a picture of a running movie taken by the webcamera placed in the second screen that is using jamoma motion and save it.
But we were not able to grab a picture when using this jamoma object? We tried with jit.dx.record and co. but it didn’t worked. So we thougt how about freezing the movie and then take a short recording about half second so it appears as an picture. But we do not know how to decide where the movie should be saved or how long it should be? We tried also to use the object jamoma record but you have also to push the button "record" to save an movie, which is ofc not what we want ( we want to take a picture) and in our patch this button should also be triggered by a bang which is triggered again through a metro.
To describe it short: we want to make a picture of a movie that is recorded by the webcamera and saved automatical in the same folder – a bid like you know it from the webcamera programs for computer

[attachment=131511,496]

Attachments:
  1. patch.jpg


G4
May 4, 2010 | 7:30 am

Noone knows ? If someone has a tiny idea – plz help! :-))


May 4, 2010 | 8:00 am

Hi,

in Jitter I would do the following: First grab images from the camera, and then pass them to a jit.matrix and use the exportimage message to save them as images.

Using Jamoma you can use jmod.input% to grab the image from the camera, but there are no module created yet AFAIK that will help you saving the image to disk. But it should be pretty straight forward to create a module that is a wrapper for this functionality of jit.matrix. But before doing so I would ask myself if there is a need for wrapping the functionality as a Jamoma module. I would only bother to do so if I needed to be able to control it remotely somehow using OSC messages or the like.

In general it is useful to understand what the process you need will look like in Max/MSP/Jitter before moving on to Jamoma. The main point of Jamoma will be to wrap that process in a way that might easy operation of it through a streamlined interface, access to common functions such as gain, mix, mute, bypass, built-in preset system, enabling of OSC based communication to and from modules, ramping of parameters over time to new values, and mappings and cues/presets.

Hope this helps,
Trond


Viewing 3 posts - 1 through 3 (of 3 total)