Chronos > Software Dev

Software V0.3 Beta - Updated May 3 2018

<< < (11/18) > >>

nik282000:
Did some more fiddling with the the segmented memory mode and still had no luck. For the sake of having a small video file I set the record frame-rate to 30fps, set the "Record Lenght" to 300 frames and set 2 segments of 150 frames each. I filmed at timer and pressed the external trigger at 10s and 20s then stopped the recording at 30s. I added frame numbers to the result and made the following gif.



The recording ended up only being 157 frame long and contained mostly the video that occurred after the second external shutter press. Some of the jumpiness can also be seen. Any idea?

tesla500:

--- Quote from: nik282000 on January 16, 2018, 06:05:24 PM ---Did some more fiddling with the the segmented memory mode and still had no luck. For the sake of having a small video file I set the record frame-rate to 30fps, set the "Record Lenght" to 300 frames and set 2 segments of 150 frames each. I filmed at timer and pressed the external trigger at 10s and 20s then stopped the recording at 30s. I added frame numbers to the result and made the following gif.

...

The recording ended up only being 157 frame long and contained mostly the video that occurred after the second external shutter press. Some of the jumpiness can also be seen. Any idea?

--- End quote ---

Apologies, segmented memory is implemented in a slightly counter intuitive way. Segmented memory is basically a ring buffer of segments, each segment being a ring buffer of frames. The camera continuously records into the current segment, overwriting any old frames. So, if you set it to two segments and cause two triggers, you've filled all the memory, but because the segments are a ring buffer themselves, the earliest segment is overwritten, awaiting a new trigger, which in this case never comes because you stopped recording. Therefore, your earliest segment in RAM (frames 1-150) is the second trigger (the one you did at 20s), and frames 151-300 (or possibly fewer frames) are whatever happened just before you stopped recording.

There was going to be a "disable ring buffer" mode in this release, which would terminate record automatically after your second trigger, avoiding the above problem. There's a bug present in the FPGA right now that prevents the required record termination at end of memory from working, that's on the todo to fix but we're just starting up production on the next batch so it will be a week or two until I can get around to it.

As a workaround, always select one more segment than needed.

nik282000:
>_< Thank you, that make my results make more sense. Good luck with round two of production!

John Delonghi:

--- Quote from: Dan D ---I found a temporary workaround to be to format your drive for Linux ie. ext3.  You just have to install some 3rd party software on mac/windows to read the files off. Another way around might be to partition to the drive into lots of 8gb fat32 segments, which would probably give faster saving, although you'll still get hit with the 4gb file size limit and it'll be a pain to use.  Devs can correct this if I am mistaken.

--- End quote ---

Hey Dan, I've tried this but couldn't get it to work. I used EaseUS Partition Manager to format a USB stick Ext3, but when I put it in the Chronos it isn't recognised.

Can you reveal what utility you used to format ext3 and also what you use to read the files? I'm using PCs here.

Dan D:

--- Quote ---Hey Dan, I've tried this but couldn't get it to work. I used EaseUS Partition Manager to format a USB stick Ext3, but when I put it in the Chronos it isn't recognised.

Can you reveal what utility you used to format ext3 and also what you use to read the files? I'm using PCs here.

--- End quote ---

I stuck the stick in my Mac, and used the e2fs tools (installed with Homebrew) to format it - i.e. the mkfs.ext3 command, which works the same in Linux as it does on the Mac. I read the contents off the stick either from my Linux PC, or using the Paragon ExtFS for Mac (paid) software. I've never tried to format or read a linux drive in Windows. You could try using a Linux virtual machine to do it?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version