Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - clkdiv

Pages: [1] 2 3 ... 10
1
Chronos User Discussion / Re: Post Chronos 2.1 clips here!
« on: May 09, 2022, 06:44:20 AM »
Made with Laowa Probe @ f14 and Metabones Speedbooster 0.64 with Chronos 2.1 @ 12db Gain. One needed a second sun for that.

Click!

2
Chronos User Discussion / Re: Exposure Trigger
« on: March 27, 2022, 05:36:44 AM »
I just can confirm that this is the same here: if the high signal duration is longer than the exposure time, it works like a gate, meaning frames are taken as long as the signal goes low. Thus the documentation is wrong here or it is a bug.

Isn't it possible for you to let the signal drop again after e.g. 100 microseconds?

3
Software Dev / Re: Chronos V0.7.0 Full Release
« on: February 25, 2022, 09:24:18 AM »
Hello! I am missing the "PLAY" button on the Play page. It was left to the "CLOSE"-Button, now it is gone. Why is this?

Thanks! Martin.

4
Ok, yet the easiest way probably, without IO-Gear, thus it works with the red record knob:

Just set the "Delay" source to "While recording" and time to eg 0.05 seconds and the "Stop Recording" source to "Delay Block". Now when pushing the red button the camera records 0.05 second. So easy...




5
Chronos User Discussion / Re: Is my software up to date?
« on: February 25, 2022, 06:08:02 AM »
Hello, I can't tell why you have the problems with the configuration you are using, I also started digging into segmented mode etc. these days.

However there might be other approaches for you:

  • You may sync the camera to a timer signal, then you have complete control when a frame starts, ends and how many frames are taken. I do this with an Arduino. That way one way also change frame rates dynamically, like so... And also record segments, of course.
  • You might also try to let the camera record all the time, but only if condition x is found at the IO triggers. I am not sure about that, but there might be a way...

6
Warning: There seems to be a bug in the REST API: When getting the the whole ioMapping configuration, the delayTime will be sent from the camera, but it refuses to accept the parameter when trying to set it.

When checking the whole ioMappings, there is an entry in the dictionary object like this:

Code: [Select]
"delay": {
    "delayTime": 0.999997,
    "source": "io1",
    "debounce": true,
    "invert": false
  },

But writing back this way is NOT possible. Instead one has to use the extra Parameter "ioDelayTime", that look like this:

Code: [Select]
{
   "ioDelayTime": 0.999997
}
I can't imagine, that this is wanted....




7
Yet I found another way to make the camera record x frames: Using the "delay" block on the IO-configuration page I succeeded to make the camera stop recording after x seconds... I attached a picture of the configuration again, and here also is a dump of the JSON object needed to put the whole configuration all at once into the camera via JavaScript.

Code: [Select]
{
  "gate": {
    "source": "none",
    "debounce": false,
    "invert": false
  },
  "toggleSet": {
    "source": "none",
    "debounce": false,
    "invert": false
  },
  "delay": {
    "delayTime": 0.999997,
    "source": "io1",
    "debounce": true,
    "invert": false
  },
  "combAnd": {
    "source": "alwaysHigh",
    "debounce": false,
    "invert": false
  },
  "toggleFlip": {
    "source": "none",
    "debounce": false,
    "invert": false
  },
  "start": {
    "source": "io1",
    "debounce": true,
    "invert": false
  },
  "combOr3": {
    "source": "none",
    "debounce": false,
    "invert": false
  },
  "shutter": {
    "shutterTriggersFrame": false,
    "source": "none",
    "debounce": false,
    "invert": false
  },
  "combOr1": {
    "source": "none",
    "debounce": false,
    "invert": false
  },
  "combOr2": {
    "source": "none",
    "debounce": false,
    "invert": false
  },
  "toggleClear": {
    "source": "none",
    "debounce": false,
    "invert": false
  },
  "combXOr": {
    "source": "none",
    "debounce": false,
    "invert": false
  },
  "trigger": {
    "source": "io1",
    "debounce": true,
    "invert": false
  },
  "stop": {
    "source": "delay",
    "debounce": false,
    "invert": false
  },
  "io1In": {
    "threshold": 2.49929
  },
  "io2In": {
    "threshold": 2.49929
  },
  "io1": {
    "driveStrength": 2,
    "source": "alwaysHigh",
    "debounce": false,
    "invert": false
  },
  "io2": {
    "driveStrength": 0,
    "source": "alwaysHigh",
    "debounce": false,
    "invert": false
  }
}

8
Chronos User Discussion / Re: Segmented mode, I don't get it...
« on: February 25, 2022, 02:43:21 AM »
Sorry for the hassle: The camera behaves exactly as stated in the manual. It stops recording automatically after x frames, but only when using the trigger IOs. I'd be really happy, if the red button at the top of the camera might be used as a switch like the BNC.

9
Hello again. Just wanted to post my findings.

It is really possible to make the camera provide the "Timing IO"-Signal only when recording: Just setup the combinatorial block as described in the images above.

However if your are connecting the camera to an Arduino, you will have to set the "Drive Strength" to "High", if your are feeding the signal into one of the analog inputs.


10
Chronos User Discussion / Re: Segmented mode, I don't get it...
« on: February 20, 2022, 12:34:55 PM »
Hello again, just to finish this here: It works as Nikon1 suggested, but only when using external triggering (unfortunately).

That's the way: Recording Mode "normal" with [X] frames as desired. Then on page "Trigger delay" Pre-Trigger=0 and Post-Trigger=[X]. Adjust TriggerIO to IO1=Toggle.

Now the first IO1 signal starts recording, the second ends it after [X] frames are recorded (Post-Trigger). Thus the whole buffer contains the lastly recorded frames.

Thanks to Nikon1.

BTW.: I'd be happy if the record button could be used like IO1 Input, and I still don't get, why in segmented mode the "disable ring buffer" seems to do nothing?

11
Chronos User Discussion / Re: Segmented mode, I don't get it...
« on: February 20, 2022, 10:18:39 AM »
Hello, sorry, I could not make any of these proposals work. In all cases the camera goes on recording...

However in the manual I found this: "This feature works while triggering with an input signal or using a BNC trigger switch cable." Do i get it right, that the normal "recording button" on top of the camera somehow "overwrites" this setting?

12
Hmmmm, I am trying to understand the IOConfig results that can be achieved via the Web-Frontend. The "Combinatorial block" seems promising. I can't test it right now, but from my understanding the configuration shown in the two images seems to do exactly what I need: Providing the "Timing IO" output only when the camera is recording. At least the red and blue triangles suggest that it does that.

If only "Timing IO" really is the Frame Sync Signal...

Very exciting...

13
Yes, exactly. I'd be happy to an in-camera-solution.  :)

14
Hey Nikon1!  :)

The camera will probably be triggered via IO2. I suppose I can also use BNC, if this helps... However my external device shall consume the shutter signal from the camera only in case only when it is recording.
Thanks! Martin

15
Hello,

I need the Shutter signal of the camera to sync some external gear to the camera, but the sync shall only run while the camera records. As far as I can see the "shutter" signal runs all the time, also when NOT recording? Is there a way to achieve what I need? Thanks!

Martin

Pages: [1] 2 3 ... 10