Recent Posts

Pages: 1 [2] 3 4 ... 10
11
Software Dev / Re: Chronos V0.3.1 Beta - Updated Oct 15 2018 with beta-9
« Last post by foobar on February 12, 2019, 10:03:10 AM »
Hey Dan,

This is a known issue with the beta-9 release, we recommend that you try out the release candidate software instead (see this thread). If that doesn't work, please let us know if there are issues with the 0.3.1-rc1 update.

Just rolled my camera back to software 0.3.1 beta4 and the Frame Sync Out works again. Can confirm this is definitely a firmware bug and not a hardware issue.

Quote
I'm trying out the 0.3.1 Beta-9 software and I've found a major bug. Since I updated, I can't choose any IO mode other than "Record End Trigger". If I select "Frame Sync Output", "Shutter Gating" or "Exposure Trigger" modes for either IO1 or IO2 and press "OK", the UI immediately reverts to "None"
12
Software Dev / Re: Chronos V0.3.1 Beta - Updated Oct 15 2018 with beta-9
« Last post by Dan D on February 11, 2019, 11:10:46 PM »
Just rolled my camera back to software 0.3.1 beta4 and the Frame Sync Out works again. Can confirm this is definitely a firmware bug and not a hardware issue.

Quote
I'm trying out the 0.3.1 Beta-9 software and I've found a major bug. Since I updated, I can't choose any IO mode other than "Record End Trigger". If I select "Frame Sync Output", "Shutter Gating" or "Exposure Trigger" modes for either IO1 or IO2 and press "OK", the UI immediately reverts to "None"
13
Software Dev / Re: Chronos V0.3.1 Beta - Updated Oct 15 2018 with beta-9
« Last post by Dan D on February 11, 2019, 08:59:59 PM »
Hi guys

I'm trying out the 0.3.1 Beta-9 software and I've found a major bug.

Since I updated, I can't choose any IO mode other than "Record End Trigger". If I select "Frame Sync Output", "Shutter Gating" or "Exposure Trigger" modes for either IO1 or IO2 and press "OK", the UI immediately reverts to "None" no matter what recording mode I'm in.  The same thing is happening on multiple cameras.

I checked on an oscilloscope and I'm no longer getting a frame sync output signal even if I choose it and hit "Apply". This is a showstopper - I can't synchronise my strobe light source without the Frame Sync Out and will have to roll back to an earlier version of the firmware. Any suggestions?

Dan D.
14
Chronos User Discussion / Re: Chronos 1.4 RAW conversion tool - pyraw2dng
« Last post by skronstein on February 11, 2019, 04:47:38 PM »
I can't decode 12 bit compressed RAW format.
When trying to convert it the output DNG files contain color noise and sometimes something similar to out-of-sync frames.

Tested both options '-d' and '--oldpack'; resolution specified correctly; RAW files saved with firmware 0.3

Are you able to use 0.3.1-RC1 instead? It can natively record videos in CinemaDNG format. http://forum.krontech.ca/index.php?topic=434.0

What do you mean by color noise?

The readme says that the old RAW 12bit format has bugs that cause color corruption:
The --oldpack option will attempt to decode the raw file as a 12-bit packed format generated from software versions v0.3.0 and older. However due bugs in this encoding format, there may be off-by-one pixel errors in the encoded files. This is most noticeable as colour corruption after demosiac.
15
Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« Last post by nik282000 on February 11, 2019, 12:45:35 PM »
Thanks for the update.

I am excited to see hear the HTTP API is coming along, you guys are doing awesome work!
16
Chronos User Discussion / Re: Chronos 1.4 RAW conversion tool - pyraw2dng
« Last post by himikk on February 11, 2019, 01:13:38 AM »
I can't decode 12 bit compressed RAW format.
When trying to convert it the output DNG files contain color noise and sometimes something similar to out-of-sync frames.

Tested both options '-d' and '--oldpack'; resolution specified correctly; RAW files saved with firmware 0.3
17
Chronos User Discussion / Re: frame rate stored in saved video?
« Last post by skronstein on February 08, 2019, 08:08:07 PM »
Some media players allow you to view metadata.  For example, in VLC, it's listed under Tools-->Codec Information.
18
Software Dev / Re: Software Roadmap - 0.3.1, 0.4.x, etc.
« Last post by DDR on February 08, 2019, 12:00:40 PM »
Well, it's been a while since I updated what was going on behind the scenes here. While we've all been working hard, it's been a lot of behind-the-scenes sort of stuff. Nothing very showy, really.

So, some background is in order.

We decided about a year ago that we did not want to keep using the original version of the software, camApp, which ships with the camera and is updated via the betas on this forum. One of the main reasons for this is that we wanted a web api and remote control app. Embedding a web server in original camApp was impractical. An external web server could not reasonably be hacked together with the tools available¹.­ Some infrastructure needed to be built.

So, Foobar ported a newer linux kernel to our CPU, and we got access to much better tools. Porting a linux kernel is generally not considered a one-man job, so it took him a few months. During this time, I put together a virtual machine to develop the new UI, called gui2, on. After I'd completed that, Foobar promptly delivered an early version of the new linux to me. While it lacked drivers for all the camera-y parts, I was able to get a modern tech stack up and running and I used this to develop the app for the next half-year.

As this progressed, it became apparent that the tech stack I'd compiled was not one that we could safely upgrade and maintain. Foobar completed his port of the linux kernel, giving us Debian 8 as the underlying operating system, and we decided to backport the infrastructure I was using from Debian 9. This was completed, but we were still several versions behind what I'd developed the new UI on. I am currently finishing porting everything from my new tech stack to the older, maintainable versions of the tech we had. While a few bugs remain, I got the app running in it's entirety, on it's final tech stack, this afternoon.

Near the beginning of all this, Johan was hired to extract the startup logic from the current camApp. (I was hired to do the mobile app promised in the Kickstarter, which was deferred due to the technical issues mentioned above, so I wound up extracting the graphical user interface from the camApp.) Extracting the startup logic to initialize the sensor proved to be quite difficult. This was completed this morning, and the camera can now start and show the new UI entirely without having to run the current camApp!

The camera can now also run a nascent HTTP API, which plays well with the new UI. If you update a value via the API, the new value is reflected in the UI running on the camera. However, both the new UI and the alpha HTTP API are still largely disconnected from the hardware of the camera. They are running against dummy values. Since Johan has managed to bring up the camera, he is now implementing the dummy values so the HTTP API and the new UI can actually make changes to the camera. Some tasks are expected to be easy to tell the camera to do, while others will require a bit more work. This implementation is represented by box in the last progress chart posted in this thread³.

While all this has been going on, Loial has been making significant improvements to the firmware of the camera's FPGA. This has been appearing in the forum betas. We are currently in the midst of working on a testing plan for the next beta, since we'd like it to actually work this time. Unfortunately, there turns out to be quite a lot to our software, so while skronstein has been working on the testing plan it is still a work in progress. I myself may be pulled aside for a few days to complete that, so we can test and release next beta here. 🙂

If you'd like to talk to us in person and see some cool stuff, we'll be at NAB. It's April 6th through 11th in Las Vegas, though we'll be around a few days longer for setup and teardown.



¹ These tools were Ash² scripts being called via CGI.
² Ash is like Bash, but awful.
³ There has been no real progress on the chart since then since both Johan and myself have been been dealing with the underlying work of making our respective technologies run. Since this work was unforseen and unpredictable, it was uncharted.
19
Chronos User Discussion / Re: Chronos 1.4C 16GB Color for Sale
« Last post by Dan Kanes on February 08, 2019, 08:45:11 AM »
Price drop for quick sale:

$2500
20
Chronos User Discussion / Re: frame rate stored in saved video?
« Last post by BiduleOhm on February 07, 2019, 03:49:36 PM »
I don't think so but you can easily put it by hand in the file name when you save it.
Pages: 1 [2] 3 4 ... 10