jmod.input%: Several issues and potential improvements
|Assignee:||Alexander Refsum Jensenius||% Done:|
I've been looking at jmod.input% lately as Marieke at BEK might be using it as part of a setup for an installation in Netherland next month. I'd like to suggest a number of changes to the module:
All the different generators (cam, video, desktop, noise) should be run by the same qmetro¶
I see a comment in the "turn-off-metros" subpatch of jalg.input% regarding this:
"Not very elegant, but this ensures that only one metro is running at a time. This was easier to implement than trying to have one main metro."
Are there reasons for using separate metros that I am not aware of, or would it be OK to shift?
A second inlet should be added, used to pass "bang" to the module.¶
It should be possible to choose whether the internal qmetro is used or if generators are rather driven by an external qmetro. This is necessary to be able to control and synchronise the sequence of execusion among several video sources used in the same patch, or when feeding sources to OpenGL rendering.
For camera input there seems to be some issues:¶
On a laptop with built-in camera and no other cameras connected, create a new patch, and connect left outlet to right inlet of message:
Start changing device in the uppermost umenu.
Device is output as number rather than symbols, e.g: /camera/device 2
As long as you choose a device that have no camera connected, the lower menu remains empty. When i choose "USB Video Class Video" "Built-in iSight" shows up. So far so good.
Let's choose "Built-in iSight" from the 2nd umenu. Nothing get output from the left outlet of the module, so this parameter doesn't seem to be set correctly. We also have to look into @priority settings for /camera/device and /camera/camera to ensure that device is selected first.
Another option would be to embed both in the same parameter, so that we would have e.g:
/camera "USB Video Class Video" "Built-in iSight"
IMHO /camera/camera is not a great OSC address...
So, let's go back to one of the devices that do not have any camera connected. "Built-in iSight" continues to show up, and if the metro is running, we still get images.
I am fearing that jmod.input% for these reasons will not work very well with cue scripts.
Alexander, if you can report back on this, I'll be happy to take a loom at the various issues and see what I can do,