76
Chronos User Discussion / Re: Introducing Chronos 2.1 HD!
« on: April 26, 2019, 01:47:52 PM »
Yup thread was somehow broken before, no I can fullfill my lust for reading new forum 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.
I have forgot to insert the SD card several times, luckily only one shot was lost.Please don't do this, if it would block the recording. It's better to insert a storage device afterwards than loosing a shot because the recording got delayd/siterrupted/whatever by a popup warning!
Quick idea: a popup message if recording is started without an active storage device?
A big request for future firmware would be the ability to pinch and zoom on the screen to enlarge objects to make focusing a little easier, plus maybe a "temporary max exposure" button to brighten the image temporarily for focusing purposes without resetting the resolution/framerate.I second that! Great idea and it would be sooo handy!
As far as I recall the timer changes depending on the trigger method which is used for the specific shot. You used the default variant where the trigger marks the end of the sequence and therefore the camera counts down towards the zero point, which was the trigger time. You could switch this around and the counter will count up as you'd expect.
BTW:
It would be nice, if the time stamp would show the time 0.000 (+ whatever exposure time you set) at frame number 1 and for the last frame +4.xxx sec for example. In the moment it shows minus 4.xxx seconds and goes to zero at the last frame. Just my personal opinion but... I would like it the other way.
For example: If I film something fast... like an explosion... And the action starts at second 2.986085 I can see that it would take for example 10 frames and end at second 3.032764 or so... So I can very quickly see that all this happend during roughly 0.05 seconds.
It's just a nicer more normal way (at least for my brain ) to see something start at a positive time (or zero) and ends at a later time / bigger number instead of something starts at second minus 1,013915 and ends at second minus 0,967236.
As a rough estimate, for a color camera, you'll need about 7 lux per fps at f/2 and 360 degree shutter.
So at 4000fps, you'd need about 4000fps * 7 = 28,000 lux. If you want to run f/4, you'll need 4x as much light, so 110,000 lux which is about noon day sunlight
As far as i know, there is an Limitation on ANY Highspeed-Camera out there in the whole market, that the fastest shutterspeed must not be shorter than 1us.If there is such a legal speed limitation, it would most likely be due to ITAR. For example, thermal (IR) cameras are limited to be below 10 fps and/or 640 x 480 px to be exempt of ITA-regulations. So if you see any IR camera above those limits, the manufacturer got a specific permit from the US government to do so and the sales are very likely restricted to certain regions and so on.
There is some kind of limitation, and i was always interrested why that is... If it goes slightly faster than that on some of the Presets, i think its still kind of borderline ok for that.
If you want faster Shutterspeed, you need some kind of special permission and a good reason, why you would even need to have such a camera... (or just hack /Modify the firmware on your own...?)
.
Please dont quote me on that, this is just from what i heard other people say and as good as i could remember, i never did the acutal research myself.
.
I think i´ve seen someone of the Kron-Staff say here in the forum, that the chronos Camera itself ist capeable of way shorter/faster shutterspeeds per frame, but it is not enabled due to this (legal?) Limitation. If i remember correctly, the talk was about reducing the resolution to actually just a single Line of pixels at some kind of crazy framerate to create some kind of line-scan-camera. In such a mode the chronos should be able to push tons of frames (lines) per second...
#Edit: Sorry if Bad english BTW...
re.yes but not a qt app. it will be a webinterface as I understand it
- Standalone daemon to operate the video system, with DBus API.
Does that mean we will get a QT app soon that runs on the PC to control the camera?
I am trying to update from 0.2, but it seems it can't find the update. When I try to backup the calibration data, it says "Error: no device is mounted to /media/sda" and if I try to update it says "No software update found".Seems like you are trying to update from a SD Card. This is not supported (yet).
In the Save settings it says the save Location is "/media/mmcblk1p1 (SD Card Partition 1)". I can save clips just fine to the card and they show up in the root directory.
The card was formatted in FAT32. The update file was extracted to the root of that card.
What am I doing wrong here?