Hey Markus,
Loving this update, but it seems like the Calibrate method fails with the projector resolution set on the cameras. Looks like they’re floats when calibrateCamera expects ints for the size.
Also moving away from using shift for a kb shortcut modifier might be a good idea as shift+left or right pauses the project and stars moving the timeline back or forward a frame. Not too big an issue but I’ve noticed adding points can be funky when the project is paused.
Hello,
I just tried the new camShnappr and I cannot use it for some reason
when I open the main window, there is still a N°0 there, not corresponding to any vertex
when I put number on vertices, there is a red error on the fifth, /camschnappr/main/renderPick/panelexec1
line 23 int() argument is ‘NoneType’
But I love the idea of:
working left arrow
OSC commands
Waiting for a working one,
Thanks,
Jacques
I felt like a number for the vertices on the Output Window is not necessary as you can always see in the Main Window which one is selected.
If you are missing those numbers I can put them back in.
Number on output are useful, because you dont always see the main display, going near the projection. Even more important with OSC possible command, doing a remote command on notebook via OSC or TouchIn CHOP, perhaps a sending of the chosen number via OSC would be great…
But for the moment it is not working at all…
All the best
Agree. Numbers are good. We have in the past done two people (one next to screen one at server), and the numbers are invaluable, but same with remote - you won’t see main screen.
Hello,
Now it seems to work (I just try on my laptop during breakfast, without projecting it)
I will try it carefuly tomorow with OSC.
Thanks for the work.
Jacques
now it works, no more zero on opening, all vertices selected works and calibration works, bravo for that but many problems with OSC, working with iPhone version:
select point works normally in negative : 6,5,4,3,2,1,0
but randomly in positive : 0,3,6,2,5,1,4
“position coarse” is not updated when changing point so when I touch it the point is going out of scale, making it not usable
“position fine” move the point but in totally different place, without relation to the coarse position, not usable.
My conclusion about remote OSC (I have used it extensively with Isadora to make projection mapping) 2D cursors are not very practical nor precise. It would be better to have only buttons reproducing keyboard arrows and alt/keyboard arrows, so you dont need to send back information and you can be more precise. The only useful osc return would be the number of the point.
Thanks for the work, it will be soon perfect for my use.
Jacques
Dear Markus,
Thank you for your change it works now with buttons. I have still some problems/questions:
– now “select point” works weirdly in both direction, not in numerical order.
forward : 0, 3, 6, 2, 5, 1, 4
reverse : 0, 2, 4, 6, 1, 3, 5
– in first page of iPhone touchOSC, coarse is working but fine position give very weird and unusable variations. As is it this page is not usable.
But it begin to be a very great tool.
Cheers, Jacques
I wonder if the culprit of all this is the TouchOSC option to send Touch Message (/z) I have this enabled and am actually using it in the osc callbacks.
Is it enabled for you?
Dear Markus,
I tried with /z activated and its better but not perfect (perfection is always hard to reach…)
– now position fine 2D cursor is working as expected
– when I press the right “select point” button, number are going 6, 5, 4, 3, 2, 1, 0 at reverse of the waited behavior
– when I press the left button, there is still a weird order 0, 4, 1, 5, 2, 6, 3
Thank you for your commitment.
All the best, Jacques
Another question:
In the precedent camSchnappr, it was possible to use matrix and exports DAT to configure another camera or, most useful for me, a light to simulate a video projector. I think I found the matrix (/intrisincs) but not the parameter with the camera position, rotate etc. Do you think its possible to retrieve it?
ha - yeah - fixed one side and broke the other. Tab and TouchOSC point selection is now fixed - main issue was due to /z coming in from TouchOSC and the command running twice…
I’ve added 2 more things:
Use the Mouse Wheel and Shift+Mouse Wheel on the output window to move selected points vertically and horizontally.
You can retrieve scale, rotation and translation from camSchnappr by calling the extension Method Decompose(), this will return a tuple of tuples.
camSchn = op('/camSchnappr')
s, r, t = camSchn.Decompose()
The position of the camera is in the extrinsics Table DAT represented as a Transform Matrix. The intrinsics is essentially the projection Matrix of the camera.
Thank you Jacques for your continued testing! A new version 2.0.6 has been uploaded to the orinial post.
Dear Markus,
Thanks for all! Tab are working, I am far away from home so no OSC at the moment but I found camera position and matrix. Everything perfect, alles in ordnung.
Jacques