Code: [Select]=return call_event_proc("UI.CreatePublic")andCode: [Select]=return call_event_proc("PTM_SetCurrentItem",0x800c,0)did the trick AFTER1.I enabled "native lua calls" on the cameras 2.I single-connected the camera to chdkptp (not using multicam)But the idea was , to change the setting on all A2500s at the same time.If i have to connect each one of them , one by one , is pointless
QuoteIt's there in your photo: DISP Alt +/- Debug action Ok , seriously i feel dumb , what is the debug key according to this ?
It's there in your photo: DISP Alt +/- Debug action
Nope , there were some shootings the last days , didn't want to mess up with multicam or any other file.So for your next 2 questions the answers are obvious...no status values , no running fixedint.lua.
Testing with them is a bit delicate matter since its "production" rig and i wouldn't like to fck it up while shooting is pending
Theory says A2500s *must* have more or less the same times with ixus 160 , since they have the same specs regarding *shots/per sec*.But having different hardware/firmware times may vary.
EDIT : i am all about messing with the rig , my friend who really owns it , is not
To enable native calls, you will probably have to set it on one camera through the UI, then upload the CFG to the remaining cameras.
@reyalpFirst of all we are not shooting raw.5secs is slow...and if we lower it , we hear the shooting clicks getting out of sync.At 5secs the "clicks" are all synced.Someone could think that "hearing" isn't a sure confirmation.But it is..photos are not synced judging from the result since in some of them the person has moved....so the photos were not synced.Thing is that in between the two shots we project a pattern to the person being shot (pattern from projectors).And i wonder if the change in brightness produced by this pattern causes the cameras to re-focus or re-adjust iso/exposure and stuff like this (although we setup these values before every shoot)..so it wastes time..I may saying stupid things here...And as i mentioned before , ixus 160 shoots faster than a2500 ..maybe its partially a hardware limitation...of how fast can the camera shoot.Anyways if we can't find a solution to lead us to shoot only once (not going to happen any time soon as long as we have cheap compact cameras) , fast multiple shooting will be always an issue.EDIT : now that i am thinking of it , you are right ...preshoots only once and then shoots as many times as it has been set up.I have seen that camera struggles during multiple shots.What i mean by struggle is that shoots-photo taken remains for msecs in display-it goes back to rec mode display-shoots the next one.Something like that.So its all going down to how fast the 2 steps (photo taken remains-go back to rec mode display) are happening.I saw that in ixus 160 , this whole thing goes down faster than a2500 , thats why i said that partially maybe its a hardware thing/limitation since as you said after the first shot camera is running on its own...
Why you need to ...
Why you need to project a pattern to the person being shot ?
Quote from: cdg on 28 / September / 2016, 22:53:49Why you need to ... @cdg : if looks like you formatted part of your response with very small font that makes it unreadable for most of us. I think what you were trying to say was : QuoteWhy you need to project a pattern to the person being shot ?Edit : in case you don't get a response as the formatting of your questions made it unreadable, the pattern is projected to allow post processing of any resulting 3D image. How that post processing is done is complicated - more so than than my response implies.
Started by mrgreen4242
General Discussion and Assistance
Started by gcgc
General Help and Assistance on using CHDK stable releases
Started by waterwingz
General Discussion and Assistance
Started by simtek
Started by reyalp
Creative Uses of CHDK