Search found 26 matches
- Sun May 22, 2016 6:30 pm
- Forum: Testing/Bug Reports
- Topic: List of issues with CameraControlRemoteCmd.exe v2.0.27.0
- Replies: 8
- Views: 7891
List of issues with CameraControlRemoteCmd.exe v2.0.27.0
Dear digiCamControl Gods, here are some test observations. Unable to set fnumber: Get camera.fnumber List camera Returns “Ÿ/2.8” where “Ÿ” has ascii code 376. But trying to set camera.fnumber does not work: Set camera.fnumber Ÿ/2.8 Set camera.fnumber Y/2.8 Set camera.fnumber f/2.8 Set camera.fnumber...
- Sun May 15, 2016 10:16 pm
- Forum: Testing/Bug Reports
- Topic: Crash on startup if 2 cameras are connected (v2.0.27) [workaround]
- Replies: 8
- Views: 9821
Re: Crash on startup if 2 cameras are connected (v2.0.27) [workaround]
Log details added to post, full Log also sent.
- Sun May 15, 2016 9:53 pm
- Forum: Feature requests
- Topic: List of Minor GUI issues/suggestions
- Replies: 1
- Views: 4113
List of Minor GUI issues/suggestions
Refresh file list button (circular arrow atop of a drive, next to "show in explorer" button) does not work and has no tool-tip description. This function works fine from the drop down: Session > Refresh file list Selecting any options from View > Thumbnail Size crashes the application, but...
- Sun May 15, 2016 7:50 pm
- Forum: Testing/Bug Reports
- Topic: Crash on startup if 2 cameras are connected (v2.0.27) [workaround]
- Replies: 8
- Views: 9821
Crash on startup if 2 cameras are connected (v2.0.27) [workaround]
Main application (v2.0.27.0) crashes on startup (during splash screen) if launched when 2 cameras (Canon 70D) are already connected by USB. Workaround is to connect seconds camera after application starts. Both cameras work fine after that. Have not tested with other cameras or with more then 2 came...
- Mon Apr 25, 2016 5:18 pm
- Forum: Feature requests
- Topic: Accurate timelapse tied to system clock.
- Replies: 2
- Views: 5985
Re: Timelapse interval that is "start to start" of a frame.
Hello, I realize now that: The latest beta that I am/was using is indeed "start to start". (i may need to remove/move/edit the post) And the drift is constant with time, independent of exposure time. And that the "Accuracy" tab in bottom right of the time lapse menu shows the dri...
- Sat Apr 23, 2016 6:38 pm
- Forum: Feature requests
- Topic: Accurate timelapse tied to system clock.
- Replies: 2
- Views: 5985
Accurate timelapse tied to system clock.
I need the start of each frame of a long timelapse collect to occur at a reproducible time (+-0.05s) relative to the system clock, which I am regularly adjusting for drift using GPS/NTP. At the moment timelapse collects do not appear to be tied to the system clock once started, so errors accumulate ...