Jason Murphy
Well-known member
Note: I originally posted this as part of a reply to another post, but thought it should probably be its own thread, since it has almost nothing to do with the original thread.
I was giving some thought to both how the still function would work, and how storage would be handled. To give a little bit of context here, I've been shooting some 16mm on a Bolex (and the occasional cartridge of Super 8), and at times, I've taken to shooting sequences using a rapid succession of single-frames. I love it. (I suppose you can do certain types of time-lapse and stop-motion work this way too, so for those not wanting to use DSLRs for that, there may be application here too).
So, with all that as background, I had a few questions, and maybe some suggestions; any and all criticisms and comments are welcome:
- Will the speed at which one shoots stills be limited only by how fast one can depress the trigger (if one shoots in manual mode)? Or will there be other latencies at play that would only allow a still frame every second or so? (I would assume the former, but you know what they say about assumptions.)
- Will the stills be stored in REDCode RAW format?
- If so, will they be stored in a separate directory/location/card from the motion clips?
All that said, here's my suggestion: would it be possible, before firing off 60 or 70 still frames as part of a sequence, to specify a separate name/storage location for that series of stills, so that one could shoot and log this type of burst-frame image sequence with a minimum of hassle? So, one can simply take, say, BurstA1.r3d - BurstA70.r3d (or whatever), and easily offload it into its own subdirectory?
To extend this idea into REDCINE, would it then be possible to build in a function to say, take a subdirectory of .r3d stills, and merge them into one single clip for simpler editing/organization/image manipulation purposes?
Again, this is just a thought. Hope it makes sense. Doesn't seem like it should be a terribly difficult thing to do. Maybe, though, I'm the only person who would want something like this, in which case, eh, don't bother.
I was giving some thought to both how the still function would work, and how storage would be handled. To give a little bit of context here, I've been shooting some 16mm on a Bolex (and the occasional cartridge of Super 8), and at times, I've taken to shooting sequences using a rapid succession of single-frames. I love it. (I suppose you can do certain types of time-lapse and stop-motion work this way too, so for those not wanting to use DSLRs for that, there may be application here too).
So, with all that as background, I had a few questions, and maybe some suggestions; any and all criticisms and comments are welcome:
- Will the speed at which one shoots stills be limited only by how fast one can depress the trigger (if one shoots in manual mode)? Or will there be other latencies at play that would only allow a still frame every second or so? (I would assume the former, but you know what they say about assumptions.)
- Will the stills be stored in REDCode RAW format?
- If so, will they be stored in a separate directory/location/card from the motion clips?
All that said, here's my suggestion: would it be possible, before firing off 60 or 70 still frames as part of a sequence, to specify a separate name/storage location for that series of stills, so that one could shoot and log this type of burst-frame image sequence with a minimum of hassle? So, one can simply take, say, BurstA1.r3d - BurstA70.r3d (or whatever), and easily offload it into its own subdirectory?
To extend this idea into REDCINE, would it then be possible to build in a function to say, take a subdirectory of .r3d stills, and merge them into one single clip for simpler editing/organization/image manipulation purposes?
Again, this is just a thought. Hope it makes sense. Doesn't seem like it should be a terribly difficult thing to do. Maybe, though, I'm the only person who would want something like this, in which case, eh, don't bother.