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

Pages: [1] 2 3 ... 13
2
Software Dev / Re: Software V0.3 RC2 (Updated June 11, 2018)
« on: August 06, 2018, 03:21:16 PM »
I can't be the only one who has trouble with these updates.   No matter how I follow the instructions,   it still takes an hour of trying to shift files around until I either give up or get lucky and it eventually works.    I think I am still on version 2.0.   

You have one of the original prototypes which is not compatible with these updates (yet). Check your email shortly, we can upgrade your camera to accept the production firmware releases

3
This beta update adds a greatly improved demosaic for in-camera h264 saving. This brings the quality of saved MP4 files near that of externally processed RAW files. We've been using this regularly without issues, but as always with beta software, don't use it for anything mission critical where you can't recreate a shot.

This replaces the old bilinear demosaic with one based on AHD (Adaptive Homogeneity Directed), with some modifications for fewer color artifacts around single-pixel objects, and lower resource utilization.

Installation
This update must be installed over V0.3.0, if you have not installed that, follow the instructions on the software update page. Once you're on V0.3.0, you can download the attached update, the installation instructions are exactly the same as for V0.3.0 update linked above. Once installed, the application revision will remain the same but the FPGA revision will be 3.9

Let us know how it works!

4
Chronos User Discussion / Re: crash test filming with Chronos
« on: August 01, 2018, 03:37:03 PM »
I'm confident the camera will handle 16g acceleration. If it breaks we'll cover that under warranty. Small lenses such as the Computar primes should be fine but larger lenses would need a support cage.

5
Software Dev / Software V0.3.0 full release
« on: July 24, 2018, 12:28:13 PM »
Software V0.3.0 is now available on the software updates page. No real changes from 0.3 RC2, apart from the version string and some minor capitalization changes.

A 0.3.1 release is in progress to fix some bugs left over from 0.2 that were discovered in testing. V0.3.0 is still considered as stable or better than 0.2.

V0.3.0 changes relative to V0.2

Notable Changes:

    White balance can be selected from 5 common presets in addition to taking your own as you could previously.
    Custom White Balance calibration (via Set White Balance) now works as expected, and produces vastly more realistic colours.
    Colour reproduction is greatly improved, especially reds.
    Set White Balance now calculates against 80% brightness white instead of 100% brightness white.
    File size warning when saving are generally more reliable now. (eg., 4+GB file warning now FAT32-only, since only FAT32 has a 4GB file size limit.)
    Changes to video saving settings are now applied as they are made, not just when the popup is closed.
    Keyboard behavior improved; text is now selected when you tap an edit box.
    UI can be flipped upside-down, or set to display the main screen menu on the left side.
    You can configure the "Unsaved video in RAM" popup that appears when you hit the record button with an unsaved video in memory. It can be set to "Always", "If not reviewed" (default), or "Never". The previous behavior was always "If not reviewed".
    The sliders on main screen the play screen have been made larger for ease of grabbing.
    Trigger I/O's Trigger delay input was moved to the Trigger Delay screen. A slider has been added as a visual aid and an alternate way to adjust the trigger delay. The ratio between post-trigger frames and record length in frames is kept constant between resolution and framerate changes.
    Added Trigger Delay screen and Record Modes screen, accessible from Record Settings. Selectable modes are Normal, Segmented, and Gated Burst.
    Black cal duration reduced by 10s to 15s or so at max resolution.
    Use any SD card. Previously, a class 10 SD card was required. You can now use slower cards. Of course, using a slower SD card means that videos save slower too.
    You can now auto-record after saving and/or auto-save after recording. This can loop if both are used at the same time.


Minutiae:

    Playback screen has 'region to be saved' marked. Each region saved is marked in a different color.
    There is now a Settings tab in the Util pages. This can be used to backup, restore, or reset settings, which does not include black calibration.
    Play -> Settings: bitsPerPixel, maxBitrate, saved file framerate, format, filename and save location are now saved as soon as they are changed instead of when the Close button is pressed.
    Mark In and Mark Out have been renamed to Mark Start and Mark End, probably just until the video seek bar is made horizontal.
    The Enter key has been changed to say Apply, since you have to press it to apply your changes on the record settings window.


Known bugs:

    The first few frames in saved videos are from the end of the recording.
    The camera will freeze after saving approximately 45 videos.  Make sure to reboot before saving approximately 40 videos to ensure the camera does not freeze. This bug exists in all previous releases as well.
    The camera will freeze when saving a video that is over 4GB onto a FAT32 partition, or when storage is full.
    If auto-record is enabled, but auto-save is not, a new recording will not be started.  However, the camera will still auto-record after booting the camera.
    Warnings about filesize (over fat32 limit, or insufficient free space) can still be shown even if autosave is enabled (if autosave is enabled, the user is unlikely to be there to press Yes for the camera to continue saving)

6
Software Dev / Re: Software V0.3 RC1
« on: July 06, 2018, 06:28:39 PM »
- Changes to video saving settings are now applied as they are made, not just when the popup is closed.

It's not set the settings after a reboot anymore though. I set it to save @ 25fps and that works but after a reboot it saves video at the default 60fps. If I then open the save settings it shows 25fps and applies it automatically but that does mean I have to manually go to that menu again after reboot. This does not work in our use case where the camera is up at the ceiling :P

I'm still getting corrupt frames and more importantly after many sequential recordings a freeze, either just a grey image and not responding or a forever "shutting down krontech.ca" screen (after about 40 video's 1280x720, 800 frames long, using 3.0 RC2).

We've been able to reproduce this on our end as well, thanks for pointing it out. Looking into it, the fix we had reduced the problem but it appears not to be a complete solution. Working on a full fix right now, check back the next few days for RC3.

7
Chronos User Discussion / Re: Two Camera Setup. (help me)
« on: July 05, 2018, 07:41:25 PM »
The behavior you see is normal. The frame sync output is always active on the master camera, even when the camera is not recording. To sync the two cameras properly, you'll need to set up a second trigger as a record end trigger, so that both the master and slave cameras stop recording simultaneously. I would also recommend setting the record length to the same value on both cameras, so that the recordings are of the same length are lined up properly. Otherwise you'll need to sync the two recordings based on the end rather than the beginning.

You'll want to turn off the 20mA pullup on the slave camera, to avoid possible issues with signal levels.

Let me know if this works for you.

Regards,
David

8
Chronos User Discussion / Re: Trigger can just stop recording
« on: July 05, 2018, 07:12:27 PM »
Could you describe what you'd like to do with the trigger? There are usually ways to configure the camera to do what you want, even though the trigger can't start a recording directly.

9
Chronos User Discussion / Re: Dark video relative to live display
« on: June 30, 2018, 10:48:52 AM »
The on-camera screen makes things look brighter than they actually are, your video is actually just dark but being masked by the screen. More light will help here.

10
Software Dev / Re: Software V0.3 RC1
« on: June 11, 2018, 07:25:24 PM »
RC2 posted, see the first post in this thread.

Notable Changes (from V0.3 RC1):
- White balance can be selected from 5 common presets in addition to taking your own as you could previously.
- Colour calibration (via Set White Balance) now works as expected, and produces vastly more realistic colours.
- Fixed bug where corrupted frames would occur randomly (only on some cameras)
- Set White Balance now calculates against 80% brightness white instead of 100% brightness white.
- File size warning when saving are generally more reliable now. (eg., 4+GB file warning now FAT32-only, since only FAT32 has a 4GB file size limit.)
- Saving doesn't change the marked region of video. (Previously, it would advance video marks to the end of the recorded area.)
- Changes to video saving settings are now applied as they are made, not just when the popup is closed.
- Added a visual button to add more pre-record slider time in the trigger delay window.

11
Software Dev / Re: Deploying camApp from Qt Creator
« on: June 05, 2018, 12:19:49 PM »
Hi Maja,

You might try going back to the QT folder but leaving the working directory as /opt /camera, or potentially going back to the old way but copying the calibration data into the required position. Another option to try is to remove the script that starts the camApp on bootup, which should be in /etc /init.d /, I believe it's just called camera.

Generally, if you use a breakpoint, the video system will become unhappy and require a restart, is it possible that is causing your crash? The debug version of the application may they not properly restart when you restart the camera, leading to the issues you're seeing.

In regards to your second question, could you describe the timings you are seeing, what specifically you're measuring? There is a delay of about 6-8 frames from image capture until the frames get displayed on the LCD, is this what you're seeing?

David

12
Software Dev / Re: Deploying camApp from Qt Creator
« on: June 02, 2018, 01:14:46 PM »
I would recommend leaving camApp running out of /opt/camera, and just back up the original camApp (rename it something else, then rename it back later). Otherwise, in the QT creator Run Configuration, you can change the deploy path. As long as the working directory is set to /opt/camera, it will find the calibration files, the application can be run from any location. Let me know if this works.

David

13
Chronos User Discussion / Re: No storage devices detected?
« on: May 31, 2018, 08:19:02 AM »
Check that the device is formatted FAT32. Many SD cards come formatted exFAT, and this isn't yet supported. If it's already FAT32, try reformatting it.

14
Software Dev / Re: Software V0.3 RC1
« on: May 09, 2018, 01:16:40 PM »
im getting stuck in the backup calibration data please wait, its been several minutes and no buttons do anything, tried restarting several times and get the same?

Try a different flash drive, or maybe reformat your current one.

15
Software Dev / Re: Software V0.3 RC1
« on: May 09, 2018, 08:56:35 AM »
Just a quick question about the update process. If I made an image of my current OS microSD card could it be used to roll back from 0.3 if I ran into problems? I'd like to test out the new colour handling but would also like a safety net. If so I shouldn't need to reload the calibration data correct?

Correct, you can image the card and remiage it if you want to revert. You can also restore using the reference image on the Software Updates page on the website.

Pages: [1] 2 3 ... 13