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

Pages: 1 [2] 3
16
Chronos User Discussion / Re: Introducing Chronos 2.1 HD!
« on: April 07, 2019, 05:58:43 AM »
If you would just open a store in the EU ... That would be awesome. :'D

Hehe, I second that wholeheartedly!! :D (Maybe not the UK though...no offense  :) )

Or some Trade-In option for current Chronos owners, which "made it all possible"  ;D ;D ;D
(For a smaller HW-upgrade fee, of course ;) Since all its hardware seems to be VERY recyclable?)

Or why not both proposals? :D

All the best!
Martin

17
Chronos User Discussion / Re: SSD rig parts list
« on: March 16, 2019, 08:28:07 PM »
Hi,

since the Chronos has an esatap port and seems to be fastest when saving like this, finding a portable/compact case with esatap seems to be slightly more difficult..

You can see the differences between esata and esatap ports here:

https://i.stack.imgur.com/wITiZ.jpg
(esatap seems to have those 4 holes in the middle, which is most likely just a visual guide. More recent laptops sometimes have those, esatap is always a combined USB/esata port.)

I only found 3 external casings with esatap support doing a quick search and ONLY for 2.5" HDs, no M.2/NVME cases with esatap... ;(

I'll be ordering this one and will report back:

https://www.fantec.de/produkte/speicherprodukte/festplattengehaeuse/25-zoll-festplattengehaeuse/produkt/details/artikel/1692_fantec_225u3esatap_6g/

Hope that was somewhat helpful.
Martin

18
Chronos User Discussion / Re: Infinity focusing in the dark
« on: March 16, 2019, 07:29:04 PM »
Hi,

also, don't use fullframe DSLR lenses with simple mount adadpters :)

You'll lose A LOT of light that way. You'll just illuminate the area around your sensor.. ;)
I started like that as well, but, for example, speedboosting lenses more closely engineered to your sensors dimensions (iirc it's a ~2/3" sensor or ~8.5x6.5mm) like MF43, Nikon1, Pentax Q(?) OR using native C/CS-mount lenses will make things quite a bit brighter :)

You can get good, not too expensive, f/0.95 native lenses for CS-mount, I paid 190 Euros/~214 USD early last year for a Schneider Xenon 25mm. Image quality improved simply because of more light hitting the sensor!

Have fun!

19
Chronos User Discussion / Re: Maximum save speed
« on: January 16, 2019, 11:48:17 AM »
Hello,

yes, eSata to SSD would be fastest.

Foobar replied to some speedtests I made in this thread, recently:

http://forum.krontech.ca/index.php?topic=442.msg2321#msg2321
(My tests are somewhere above his answer)

and shed some light on the Chronos' internal limits.

Basically, since most RAW formats are saved as image sequence, the size depending on recording speed and how big the section you want to save is: the smaller the files are, the faster the camera writes those sequences e.g. to a fast SSD.

USB sticks or SD cards usually get into serious trouble if they have to write say a 100kbyte file times 20000, as fast as possible.  ;D

All the best
Martin

20
Hmmm... ok, I think I found the reason..

The HDD used has 74Gbyte capacity, I formatted the whole drive in FAT32 using a tool (h2format in this case) which circumvents the Windows 7 limit to 32Gbyte partitions when formatting FAT32.

I found my whole second test batch in shambles  :'(  Each folder contained only the first raw file and each file- and foldername was truncated to the 8(.3) limitation.

During my test I had some troubles manually specifying the folder name, I often got "Filename already exists" and had to use a different combination of characters each time, some were quite long, all were cut to 8(.3) with a random character at the end (the first 7 were how I tried to name them, the 8th was a random one, maybe the last character of the longer filename, not sure).

So I repartitioned to 2 x 32Gbyte and 1 x 10Gbyte, formatted FAT32 using Win 7, and now it works. Even the automatic naming works if you leave the field blank :D

FAT32 seems to be slower than EXT3 as well, when saving RAW? Not much, but it's a difference, mostly on the smaller filesize writespeeds..

Would like to get some feedback on this, if it's just me or if it's reproducable. Thanks :)

All the best
Martin

21
Chronos User Discussion / Re: Workflow - Time
« on: January 05, 2019, 10:09:23 AM »
Hmmm.... well... that clarifies the speed issue.  If I need faster turnaround from shot to shot, I'll probably just have to purchase a second camera.

Yes, which would also allow for different angles on the same event, which, in research, is always nice to have.

The SSDs that I already have and use with my current camera set-ups are 240GB Intel SSD 520 Series. I would expect them to work great with whatever the Chronos could throw at them

I agree ;D

Quote from: benp
I'll typically have dedicated staff with redundant stations constantly hot-swapping the media cards and dumping the raw footage to HDDs.

In my experience, highspeed recording will always be something you can hardly automate/optimise for highest efficiency production. Each setup takes some time, much longer than the actual recorded event. But this all sounds like you may have some "playmoney", so, why not rent or buy one and see for yourself, how and if you can intigrate the Chronos into a high efficiency workflow? You'd know best :)

Quote from: benp
In short, I don't know what I don't know about high fps work.  The Chronos, I'm learning, requires a shift in my expectations... and I'm okay with that.

Very hard to answer such a question, I'll try anyway. Some of this you already knew, I'm sure.

It all depends on what your main subjects are and how you want them filmed. Most of the times, for varying subjects, the setup (direction and size of view vs scene, lighting, recordingspeed vs motion, shuttersync) and a few tests will take quite some time. The event is usually very short, so, in the end you'll have only a few hundred or thousand frames to save, which, according to Foobar (thanks for the insights!!) never exceed 230fps or 60Mbytes/sec writespeeds.

With eSata and a fast SSD you'll wait roughly 22-25 seconds for 5000 frames encoded with x264 to finish saving (when using 10k fps recording speed and faster).
RAW writespeeds really depend on framesize/filesize per image but are roughly as fast as x264 on 20k fps record and faster)
The videos duration depends how you divide those 5000 frames on playback, e.g. 60 fps playback speed results in 1 min 23 seconds playback time.
I wouldn't go past that playback speed, since older machines start to have playback issues past that mark, I'd guess.

You'll need "clean lighting", without fluctuations from either the powergrid or pulsed LED drivers, else you'll have pulsating brightness in your scene, depending in severity on your recording speed.
(powergrid pulsing becomes "invisible" again at highest recording speeds, it's still there, you just won't notice it anymore)

Shuttersync is most of the times best as close to the maximum as possible, IF you want to see _every_ bit of detail/spec of dust, which will really put your lighting situation to test :) (You might need bright spotslights for that)
But for general motion analysis, it doesn't have to be. An interesting testing field as well! (Pressure waves from my airpistol muzzle looked best/smoothest with slowest shuttersync, the projectile was just a blur though ;) )

There are tons of videos out there now, filmed with the Chronos, maybe there's already something similar to the projects you have in mind?

Quote from: benp
From reading the forums, I already understand that the RAM can be user upgraded for about 1/3 the cost of purchasing that configuration.  And, the reviews on the standard lens aren't that great. 

There are better lenses out there, yes. I've got a 25mm C-Mount f/0.95 Schneider Xenon and I'm quite happy with it. BUT the most sense to me are those speedbooster adaptors, adapting premium glass from Nikon etc to C-Mount, at least in theory: http://forum.krontech.ca/index.php?topic=123.0
RAM-Size depends heavily on your project aim. In all honesty, for single, very short events recorded, the 8Gb model is perfect :) As BiduleOhm mentioned, there are several recording modes, like segmented, where a bigger RAM would mean more segments before you need to flush to storage.

Quote from: benp
Therefore, downtime is avoided at all costs - including paying more for a system configuration I may never need/use.

Multiple cameras would actually make sense then, I'd think. Also considering repair.

Quote from: benp
There are many adapter options already available for using these lenses (with a crop factor) on the Chronos.

That's how I started as well, but crop factor (iirc 4x) isn't doing you _any_ favours here, since you may have to position your camera too far away AND you'll lose quite some light, the lens normally provides. That's why those speedboosters are a nice idea, I have to check up on that ;)
Best would be a native lens, or premium lenses with very minor crop factor difference + speedbooster.

Quote from: benp
At this point, what I probably need to do is find one of the Chronos cameras to borrow or rent that I can try out ... or see about an in-person demo.

Very yes ;)

All the best
Martin

22
Hi again,

just finishing another round of writespeed tests with RC1 and I can confirm the autoname folder feature on esata formatted with FAT32 still doesn't work.
I'm using one of these btw: Fantec QB-35US3
http://www.fantec.de/fileadmin/downloads/products/festplattengehaeuse_festplatten/QB-35US3/datasheet/FANTEC_QB-35US3_datasheet_en.pdf
It's a multislot casing, the Raptor is in slot 1 (that slot is always recognised by sata controllers incapable of recognising multiple devices per port, iirc the feature is called port-multiplier)
So, I had to manually name each folder in the save settings.

On a FAT32 formatted SD Card it does work to leave the foldename field blank.

23
Chronos User Discussion / Re: Workflow - Time
« on: January 03, 2019, 05:51:33 AM »
Maybe stay on the safe side and get the storage solution which has the lowest latency when it comes to tons of small-ish files, between, maybe 25Kbyte and 3Mbyte?

One where you can just dump all 8, 16 or 32Gbyte completely and writespeeds won't have a problem with thousands of small files?

I seem to remember that fast SLC-nand SSDs usually are among the fastest solutions for storing s...tons of small files while not breaking any sweat.

But there IS a limiting factor, in camera, not sure if the Chronos DNGs are compressed or not (I think they might be), but the camera with that software never wrote beyond 240fps in x264 and RAW wasn't too far behind when writing smallest filesizes/fastest recording speeds.

My 10k Raptor wasn't "really awake" writing around 17-18Mbytes/sec with 83Kbyte files.. ;)

IF (a big one) you plan for the 32Gbyte model (16secs realtime recording) and IF (even bigger) you often or always need to record AND dump the whole 16 secs, with a fast SSD and even with a fast spindrive you will mostly wait for the camera, not the storage, just don't use SD cards or USB sticks, they are 99% of the time NOT optimised for writing tons of small files in sequence as fast as possible.

All the best
Martin

24
Hi,

latest beta, v0.3.1 beta 9.

And I adjusted the cameras clock beforehand, but can't say for sure if only the FAT32 tests were done after (but I think so).

Thanks for your help!!
All the best
Martin

25
Yea, please ignore the second question in this thread, I just found out how to do it... I never used this, always used max fps per resolution, but it's nice to know that it works! :)
(you can enter any value in the fps field, just don't forget to "apply".... and maybe match exposure)

All the best
Martin

PS: Nikon, thanks, I know dropping frames in post is a terrible idea :) Just forgot to "apply"... I can almost feel the face inside my palm :D

26
Greetings, these question are for the developers:

- Is there a folder naming bug when exporting to eSATA when the drive is Fat32 formatted?

After doing some eSATA export tests yesterday, using ext3 filesystem, today I tried to redo some tests using the same drive, Fat32 formatted (it's an old WD Raptor 10k drive, 74Gbytes in size, Clustersize is set to 64 sectors == 32Kbytes).

While saving to the SD card always resulted in folders named e.g. "vid_2018-12-31_16-22-09" (and I assume the ext3 folders were named like this as well, didn't check them, but never got an error like this), with Fat32 I can save only once!
The second export always cancels with "Recording failed: File exists", the reason being the raw-file folder wasn't named with the current date/time, it's simply named "vid_2018" (reboots, replugs, etc didn't change this).

The first video is also lost in that moment, the folder only contains the first .dng-file afterwards, 0-byte sized. All .dngs from the first, successful save are gone.



My second question:

- Is it somehow possible to e.g. set 1280x720 while recording "slower", meaning less fps than the default 1500?

Or was the philosophy to skip frames in post to reduce the slow-down of motion?
Sometimes 1280x720 @ 400 fps would be nice to have "in camera", I think :)
(Maybe I just didn't find the setting?)

Thanks!
And all the best for 2019, see you all on the other side! :)
Martin

27
Chronos User Discussion / Re: Workflow - Time
« on: December 30, 2018, 04:28:53 PM »
Hi,

just did a test yesterday with the latest beta (0.3.1 beta 9), once with a Sandisk Extreme (read ~90mbyte/sec, write ~40mbyte/sec, pictured below) and once with an old WD Raptor 10k (the 74Gb one, in 3.5" casing), formatted using ext3, connected through esata.

First off, everything below is quite subjective and "ballpark".

@ 1280x1024x1057fps
Both, SD and eSATA, exported standard x264 at ~60fps (doesn't matter how you configure the codec).

Raw is quite different!

CinemaDNG was around 4-4.5fps for the SD and ~18-19fps for eSATA(!).
Filesize of each raw image: ~2.5Mbyte, size of batch/recording 1200 frames, so, saving took about 1 minute with eSata, but easily over 4 minutes with SD (slow USB sticks are probably even slower).

But you may be interested in highest framerates primarily, so I just tested again for different resolutions:

@ 336x120x31192fps (not the fastest setting, that's 336x96x38565fps)
x264 is maxing out(?) the write speed at about 180-220fps to both storage mediums.
CinemaDNG is also very fast, on eSATA at around 130-200fps but on the SD card there are again significant drops, judging only from the fps writespeed display, I'd say anywhere between 20 and 120fps (jumps quite a bit).
Filesize of each raw image: ~83kbyte ;) again/always 1200 files/frames.

@ 640x240x8819fps
x264 writespeeds don't differ much from the settings used before.
CinemaDNG drops quite a bit again, I'd say around 25-40fps on SD, about 100 - 120fps(?) on eSATA.
Filesize is 304kbyte per raw file.

@800x96x17587fps
x264 maxes out again, almost always towards ~220 fps.
CinemaDNG is in between the previous two "measurements", ~20-90fps on SD, ~120-180fps on eSATA, so no surprises.
Filesize is at 154kbyte.

RAW 16bit/12bit is still an option as well, but even though it writes one big file (not like CinemaDNG/Tiff) it's only veeery slightly faster than CinemaDNG speeds(!)

Tiff is sometimes a bit faster, often a bit slower than CinemaDNG, but I didn't include those speeds, since Tiff filesize is slightly bigger (uncompressed) BUT, obviously, only 8bit per channel.

So, if you go with SSD/USB Stick/SD-Card aim for those products which can deliver highest response time when writing LOTS of small files(!), storage reviews test exactly for that scenario as well.

All the best
Martin

28
Chronos User Discussion / Re: Chronos 1.4 Footage Thread
« on: December 18, 2017, 11:42:17 PM »
Electra, what an awesome idea! :D
And the "let's be fair" comment and continue smashing the first one in "4-year-old" mode, was funny, as was the whole video :) Thank you!

Maybe just "half press" each Lego brick? Tight enough to hold and not losing too many bits on the way, but loose enough to have the tendency to deconstruct fantastically..?
I'd recommend heavier pull weights, exact offset impact, maybe with a guiding rail solution and maybe inserting weighted inlets (lead) into the car, to increase mass (maybe only with heavier pull weights)?

Love to see more! :D

All the best
Martin

29
Chronos User Discussion / Re: Let's talk LENSES!
« on: December 18, 2017, 04:11:58 PM »
Greetings fellow time travelers,

I think this belongs here, came up again in a PM this evening.
I found this way back, when I was still waiting for the Chronos to arrive and researching native lenses:

http://www.ebay.de/itm/142138567245?orig_cvip=true

It's an f/0.7 C-Mount 50mm lens by Fujinon.

IIRC that's very close to the "practical" limit. It was too expensive to just "shop and test" it..
It "could" have been incompatible (I heard about some c-mount lenses lenses which won't work on the Chronos, don't remember the specifics. Protrusion issue into the camera body? See image 5 for example..).
AND notice the lovely "-TV" tag. Would've been too risky ;)
(It may have been vastly overprized as well.)

Here's some explanation why you won't find much faster lenses:
https://www.youtube.com/watch?v=84ZXfviMBFE

And this was just a marketing stunt without actually producing anything usable:
https://petapixel.com/2013/08/06/carl-zeiss-super-q-gigantar-40mm-f0-33-the-fastest-lens-ever-made/

;D

All the best
Martin

30
Chronos User Discussion / Re: Footage right out of the camera
« on: December 17, 2017, 03:46:10 PM »
I'm also happy to share my emailaddress by PM to get some footage per mail. I'm interested in file size (although this has been discussed) and overall image quality comparing the color and bw model.

Hi Rainer, I've just sent you a few test clips, still too dark with max shutter, need to finish my flashlight monster battery mount ;)

The filesize depends solely on bitrate, which you can set for each save. The final clip size depends again on which parts you've discarded/left in, for example, my clips average from 4 to 10mbit, but I think I always set higher values for the saving process, e.g. 15mbit. But that's just the maximum bitrate allowed, if the clips are too dark, like some of mine, they compress very nicely... ;D

All the best
Martin

Pages: 1 [2] 3