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 - BiduleOhm

Pages: [1] 2 3
Chronos User Discussion / Re: Focus Aid
« on: January 17, 2018, 03:47:21 AM »
I found a focus chart helps a lot, you just adjust the focus until the gray circle is the smallest possible (the less blur you have the less the lines are mixing with each other (making some gray color) so as the lines are finer and finer towards the center it forms a circle which is the smallest when the focus is best) so even with low light and a small screen you can do a pretty good job very fast.

Chronos User Discussion / Re: 2nd battery
« on: January 14, 2018, 05:56:09 AM »
Maybe it's the battery which it's out of tolerance. I guess there's specs for all of this so we can measure the camera and battery and see which one didn't follow the specs.

Software Dev / Re: Speed boost to 38k fps?
« on: December 21, 2017, 02:29:34 PM »
Yes, if you set a lower resolution you can go up to this FPS (and I'm sure as I tested it just to see the obscene level of light it needs...) ;)

You don't need to change the file to go to this FPS, but you can if you want to put this FPS as an option in the list of course.

Software Dev / Re: Software V0.3 Beta
« on: December 21, 2017, 11:41:54 AM »
You've probably already tried but did you try to reboot the camera?

Chronos User Discussion / Re: Recording Under IR illumination?
« on: December 20, 2017, 11:34:59 AM »
It has an IR filter but it can be removed. As this involve tearing down the camera I'll let David post the details (unless it's already in the manual, I can't remember).

Chronos User Discussion / Re: Insanely high speed slit scan method?
« on: October 22, 2017, 05:39:13 AM »
Yep, software limit it to whatever the export limit is and then those who want to go higher just need to change a value or two in a config/header/whatever file and maybe re-compile the thing if the change isn't in a config file.

Chronos User Discussion / Re: external trigger
« on: October 21, 2017, 08:18:01 AM »
I don't think you can trigger the start of the recording and let it stop when out of RAM because usually you just record in a loop and stop the recording after the event occurred, that's how pretty much how all hi-speed cams work.

But, as already said by David, you can use your start signal to stop the recording and set a 400 ms delay (in frames, so, for example, if you shoot at 2000 fps you need to set it to 800 frames to record 400 ms) which will basically do exactly what you want (record 400 ms after the start signal) ;)

Chronos User Discussion / Re: external trigger
« on: October 21, 2017, 06:31:34 AM »
It's already available, see page 11 and 12 of the manual ;)

Software Dev / Re: Improving the Jog Wheel, ideas.
« on: October 14, 2017, 04:26:14 AM »
The problem is that if it's not perfectly implemented and tuned it's a nightmare to use, but I have no doubts on the skills of David so I guess it's a good idea :)

Software Dev / Re: Improving the Jog Wheel, ideas.
« on: October 13, 2017, 10:42:44 AM »
Fair enough! Then I would suggest the following based on all the above:

Clicking the jogwheel will switch between the following speed settings:

- Single-step
- Slow
- Normal
- Fast

The textual representation of the currently selected speed would be displayed somewhere on screen during playback such that one gets feedback on what the current setting is when pressing the button.

The % settings for each such mode would have a reasonable set of defaults based on testing, but could optionally be fine-tuned in the camera settings somewhere if one wants to have more fine-control over those speeds.

Having those textual representations will make more sense to the average user, while still being able to be fine-tuned in camera settings if desired (to whatever granularity needed).

That seems pretty much perfect :)

Software Dev / Re: Improving the Jog Wheel, ideas.
« on: October 13, 2017, 03:48:17 AM »
I think the press-to-hold-select speed you suggest would be even easier if just using "push to open", "Push to close" the settings window, then you don't need the dexterity to actually press-hold-rotate at the same time. As the currently selected "speed" would be pre-selected when pressing, you can always get rid of the settings easily by just pressing a second time if doing it by mistake.

I think it'll not be very pratical to select a value from a menu each time you want to switch it, I much prefer to set the values once and be able to switch between them with just a click.

But thinking about it, with the possible exception of single-frame stepping, wouldn't one always want to use a fraction of the buffer length (%) as the speed selection?

Yep, pretty much exactly what I was thinking earlier ;)

The actual % above probably are good, but real-world experience needed to nail them down

I'm afraid using percentages isn't precise enough (we might need 0.0x % values for example) but I may be wrong.

Software Dev / Re: Improving the Jog Wheel, ideas.
« on: October 12, 2017, 05:46:20 AM »
1. Yep, exactly what I was thinking ;)

2. Yes, the best thing would be to be able to chose between 2 and 5 values for example.

I guess you can always have a 'default' preset with sensible values for those who just want to use the camera as is.

3. Also it would be great to be able to use the jog wheel when focused on an input field to increment/decrement the value of the field (especially as a lot of inputs are numbers) and validate the value with a click. It would be a lot easier than with the current keyboard where you can mis-type values (even if I don't have fat fingers... :P) and you need a lot of clicks.

Software Dev / Re: Improving the Jog Wheel, ideas.
« on: October 12, 2017, 04:31:40 AM »
1. One frame per click is too-fine. Most people only care about getting close enough to the section of the frame buffer they need to save. You want to have handles on your video anyway, so you will save a little bit before the area of interest and a little bit afterwards, 5-10 seconds is what most people I have seen recommend. If people need to go over video frame by frame they will typically do this later when on a PC with a large monitor.

2. Holding the jog wheel down while turning is impractical. If this was a jog wheel on a desk or control panel there would be no problem, but this is a camera on a tripod or handheld.
I personally think push and hold needs to be abandoned, instead pushing and releasing the jog wheel cycles through the jog rates.

1. I do not agree, I like to be able to see the video frame by frame for the critical moments before saving it in case something is wrong and I need to re-shoot the video.

2. I totally agree, push and releasing is the way to go IMHO. If possible with more than 2 frame-rates (3 or 4 would be a good balance I think). I really like the idea of fractions of the buffer in addition to one frame per detent.

Instead of presets for the whole thing I guess it would be better to be able to chose a preset for each click on the jog wheel; less presets needed, more customizable and maybe no need for an advanced mode because we can already do advanced things with this simple UI.

Chronos User Discussion / Re: Recommended Lens brands...etc....
« on: October 11, 2017, 11:56:16 AM »
That's pretty much exactly my plan: using a F-mount to C-mount adapter and some Nikon lens (the first one will probably be a 35 mm prime) and also the 12.5-75 mm Computar C-mount lens ;)

I already have the 12.5-75 lens and the adapter, now I need to hunt for a cheap Nikon lens :)

Chronos User Discussion / Re: C moutn adapotor
« on: October 08, 2017, 03:13:14 AM »
Of course I already adjusted the back focus, I have the lens rotated about 90 of what it should (I guess it's better than before the back focus adjustment where it was nearly 180 out, but it's still very annoying) but I can't correct it with the back focus adjustment because it would throw off the back focus.

Pages: [1] 2 3