hey guys!
good to hear from the writing strategy.
i thought about something like this by myself. but more in a way of interlacing the image and writing it in blocks to the card.
maybe storing it randomly on the card, so the card can be written on with a constant speed continuously?
i don´t know how the dng files are actually contained as one file. if they are in sequence or already randomly stored.
is it possible to generate a mft type list in that container to restore the correct sequence in the unpacking process on the computer?
or maybe a kind of pre record strategy. you could arm the raw recording process=>buffer gets filled and rewritten for an "optimal" amount and circles for 10 seconds. then kills itself to prevent heat and to safe battery.
then you hit the fire button and the card can take the optimal data stream.
what´s the h264 coder doing? in the 50D it has to be activated to get raw recording.
this is just theory. and of course i don´t know if anything of this is possible or even already implemented.
would love to help with coding, but my coding days started and stopped with the C64...
and i did some more practice tests. wondered, what the also increased motion resolution (compared to interframe based h264. means, h264 dumps not just color and detail information by macro blocking but also motion information which is stored in vectors)
so here you have it: horrible resolution and a nightmare of aliasing but a synthesized 200 fps camera (shot 50fps)