View Single Post
Posts: 1,163 | Thanked: 1,873 times | Joined on Feb 2011 @ The Netherlands
#1106
Originally Posted by Copernicus View Post
Ok, version 1.1.30 is now making its way up to extras-devel, with mostly fixes to the intervalometer. I think what may have been happening is that I didn't have enough of a delay between the simulated button press and the simulated button release. (Then again, it could just be that Qt timers just aren't reliable when you lock the screen. I'm probably going to have to do some more homework here.)
Well, I've done both -- I've put the hardcoded delay feature back onto the "Camera" panel, and added a configurable initial pause to the Intervalometer panel.
This has happened in the past when Pierogi's control thread gets swamped with command requests, and ends up becoming a zombie process in the background. I thought I had all that fixed, but odds are that playing with the intervalometer is causing that to happen again. (It shouldn't be anything to do with the vip1853 keyset...)

What happened is that every pierogi stalled sending commands, after trying the not on my samsung TV not on my receiver then indeed I tried the camera but not with the intervalometer but just the openshutter command and it gave me that message...

Oh and about the unlocking thing, unlocked/locked doesn't actually matter I think. For now it seems it does what it wants, sometimes shoot like it's a Machine Gun, sometime acting like a sniper as it should... I don't know, I am reading me into MagicLantern to see if I want that on my camera (:
__________________
N900 loaded with:
CSSU-T (Thumb)
720p recording,
Pierogi, Lanterne, Cooktimer, Frogatto
N9 16GB loaded with:
Kernel-Plus
--
[TCPdump & libpcap | ngrep]
--
donate
 

The Following 2 Users Say Thank You to mr_pingu For This Useful Post: