Messages

Thank you, RenatoPhoto. Your help is greatly appreciated.

My apologies if this has been covered, I have been unable to find a workflow solution..

I recently recorded RAW video using DUAL ISO, without realizing that there might not be a workflow to de-interlace the frames. To my knowledge, Dual ISO video is possible with time lapse / stop motion, as the CR2s can be deinterlaced (CR2HDR) and then the sequence can be batched for video rendering. However, since RAW video is recorded in a different format/extension, I'm not sure if it's currently possible to correctly resolve the video sequence. Is this correct? I've run it through RAW2DNG, which still works, but the video files aren't usable because of the interlacing.

Would it be possible to create a program similar to CR2HDR for Dual ISO RAW video?


Thanks for your time, and many thanks to all the Devs

[Is it possible limit the max ISO with AETTR and/or Dual ISO?]

My apologies if this has been covered, I haven't been able locate enough information about it. I intend to try out the practices in question, I'm just curious if anyone has had previous success.

I've been trying to utilize AETTR + Dual ISO for daytime / astro time lapse and am having a few problems. My goal is to be able to complete a 24+ hour time lapse incorporating a 5 axis slider while maintaining proper exposure. Ideally, I would like to get around 2900 dual ISO frames in a 24 hour period, and end up with 1450 merged files. I'm having trouble with synchronization and exposure, though, so I've only been patch together 6-9 hour segments at a time.

First, I can't seem to expose the scene properly at night. The auto exposure immediately jumps to ISO 12800 in dark scenes, which usually overexposes my shot by more than 3 stops and blows out elements of fine detail (stars, etc). Is it possible limit the max ISO with AETTR and/or Dual ISO? I'd like to take advantage of faster glass and longer exposures to pull out as much detail as possible, but at 30" / f2.8 ISO 12800, the night sky is overexposed beyond recovery.

Second, I'd like to time the moves on my slider to be at consistent intervals between shots. I haven't found an issue when the unit stationary; AETTR and ML's intervalometer can be set to cap at a 32" exposure and, say, a ten second interval. The camera will continuously calculate exposure and take pictures. However, I'm not sure how to time the motors on my slider to move during each interval. For instance, if AUTOSNAP is engaged, the camera might need to take three or four pictures to find exposure. If I'm taking a 32" picture, the delay has to be set to over 2 minutes between shots so the slider doesn't move while the shutter is released. For a 24 hour sequence, that results in 720 pictures, or 30 seconds of film. The problem at night, again, is that my shots end up too overexposed, so only about 15-20 seconds of that film is usable.

Most Recent Settings:

Trigger mode. Auto Snap
Slowest shutter: 32"
Highlight ignore: 0.1%
Allow clipping: OFF
Midtone SNR limit: 6EV
Shadow SNR limit: 2EV
Link to Canon Shutter: OFF
Link to Dual ISO: ON
Shadow metered areas: ON
Show debug info: ON

Dual ISO (enabled)

Intervalometer / Slider: Exposure: 32", Interval - 1:40m (to allow for AUTOSNAP)

Post Deflicker:
Sidecar file type: Adobe XMP
Deflicker percentile: 50%
Deflicker target level : -4EV

Does anyone have advice as to better improve this workflow? I will continue to try out different settings, but I would love it if I could shorten the move interval to 1 minute and double my number of exposures. Not sure if that's possible with AUTOSNAP engaged, and I'm not sure if I need it engaged, so let me know if that's the case. Like I said, the main goal is 2900 dual ISO frames with 1 minute delay between moves (every other frame). It's okay if the frame pairs are ISO 100/100, etc. before merging, I'm just trying to capture greater dynamic range when possible.

Thanks in advance, and thanks to all the devs for your hard work.

I posted a workflow in this thread that I believe solves the "neon pink" photo issue.. Hopefully it's beneficial for you.

http://www.magiclantern.fm/forum/index.php?topic=8237.0

Just wanted to update this workflow with the fix, thanks to @1%...

Please correct me if you spot an error.

This is a Mac workflow, and is intended to fix the problem with the pink DNGs caused by a corrupted file sequence. Corrupted files often occur when the video sequence takes up more room on the CF card than is available or when there is a problem saving the sequence to the card. In order to recover the salvageable data, you need to apply the correct footer in the hex code for processing in Raw2DNG, Son of a Batch, etc. This also covers how to stitch together 4+ gig files, how to calculate your total frame count, and how to covert that number to hexa decimal code.

- import the desired .raw +.r00, etc. files from your cf card to your drive (I prefer a new folder on my desktop that I can relocate upon completion)

- open the .raw file first using 0xED to view the hex code .. available @ https://www.macupdate.com/app/mac/22750/0xed

- open the sequential .r00 +.r01, etc. files in 0xED and copy and paste the hex code (located on the left side) below the hex code for the .raw file in order to create a sequential batch

- apply the appropriate footer to the end of the batched hex code. To determine this you will need your total frame count and the corresponding hex code for that value.

       - to determine frame count, multiply the gb of the total file by 1024 and divide by your DNG file size in MB (i.e. 40.25 gb * 1024 / 3.7 MB = 11139.45 -> 11140 frames)

       - to determine the corresponding hex code, use a decimal to hexa decimal converter: http://easycalculation.com/decimal-converter.php

       - the hex code is applied backwards in the footer where "XX XX" is: 11140 = 2B84 or "84 2B"

52 41 57 4D 80 07 38 04 00 60 37 00 XX XX 00 00 01 00 00 00 A8 5D 00 00 48 48 04 00 00 00 00 00 01 00 00 00 00 20 15 0B 26 05 00 00 20 08 00 00 38 0E 00 00 50 34 49 00 0E 00 00 00 FF 07 00 00 98 3A 00 00 00 00 00 00 00 00 00 00 88 07 00 00 08 05 00 00 1E 00 00 00 92 00 00 00 26 05 00 00 1A 08 00 00 00 00 00 00 00 00 00 00 00 01 01 02 01 00 00 00 42 1A 00 00 10 27 00 00 85 FD FF FF 10 27 00 00 3D FC FF FF 10 27 00 00 41 EF FF FF 10 27 00 00 AC 30 00 00 10 27 00 00 EC 07 00 00 10 27 00 00 74 FC FF FF 10 27 00 00 72 08 00 00 10 27 00 00 24 16 00 00 10 27 00 00 EB 03 00 00

---------------------------
completed footer for 40.25 gig file:

52 41 57 4D 80 07 38 04 00 60 37 00 84 2b 00 00 01 00 00 00 A8 5D 00 00 48 48 04 00 00 00 00 00 01 00 00 00 00 20 15 0B 26 05 00 00 20 08 00 00 38 0E 00 00 50 34 49 00 0E 00 00 00 FF 07 00 00 98 3A 00 00 00 00 00 00 00 00 00 00 88 07 00 00 08 05 00 00 1E 00 00 00 92 00 00 00 26 05 00 00 1A 08 00 00 00 00 00 00 00 00 00 00 00 01 01 02 01 00 00 00 42 1A 00 00 10 27 00 00 85 FD FF FF 10 27 00 00 3D FC FF FF 10 27 00 00 41 EF FF FF 10 27 00 00 AC 30 00 00 10 27 00 00 EC 07 00 00 10 27 00 00 74 FC FF FF 10 27 00 00 72 08 00 00 10 27 00 00 24 16 00 00 10 27 00 00 EB 03 00 00

- save this new, completed batch from 0xED to your desktop with a new component in the name that you'll recognize.. i.e. M09-0858.RAW -->  M09-0858full0xED.RAW

       - (if you need space on your drive at this point, you can move the original files to an external drive. deletion is possible, but it is recommended that you retain the originals in some form.)

- open this file with your preferred batch processor, i.e. Son of a Batch ( http://www.magiclantern.fm/forum/index.php?topic=7266.50 ), or Raw2DNG ( http://www.magiclantern.fm/forum/index.php?topic=5508.0 ), and convert the .RAW files to .DNGs ... 000000.dng -> 011139.dng

- save these DNGs to a folder on your desktop

- once completed, select the folder containing all of your applicable DNGs and, with all of the files highlighted, double click them to open in Adobe Camera Raw (Photoshop)

- adjust the settings of your file in ACR, click "Select All > Synchronize > Save Images". Save these new DNGs to a subfolder with a new component in their name: 000000.dng > 000000ACR.dng

- once completed, import the DNG image sequence to Adobe After Effects, make sure all of your settings are applicable/as desired (i.e. frame rate, color correction, lossless format, etc.), and export the files as a video sequence for further processing in Premiere Pro, Final Cut Pro, etc.

(There are other methods that can be used for processing, such as GingerHDR and DaVinci Resolve, but I don't have much experience with these programs.)

Hopefully this workflow will be of assistance to you when trying to recover corrupted data off of your CF card. I was able to successfully pull all but the last twenty frames from my 11140 frame sequence. Again, please let me know if I missed anything or if more detail is needed.

Many thanks to all of the Developers. Your work is greatly appreciated.

@gauss256

To my knowledge, sound recording for .RAW video has been disabled at this time. There were too many issues. I believe it's still under development for the future Stable Release.

The OP is using an external recorder as an audio solution in the meantime. This is effective for capturing, but syncing with video can be challenging without a slate or reference mark as PressureFM mentioned.

@1%

Greatly appreciate your help with this. I PM'd you a dropbox link as well as some sample code with a footer from a similar, working sequence. Let me know if there's anything else that would help you.

@ 1% ...

thanks for the reply, man. That makes sense, because the pink files are often split in the preview frame for Son of a Batch, or in ACR.  I'm not sure if this is applicable, but when I'm stitching the frames in hex fiend, I noticed that broken files are consistently two digits "short" from filling up the coding line completely (and are obviously missing a footer):

i.e. {52 83 08 0D / 20 3B 83 FC / 0C 72 3D 88 / F8 20 B2 84
       1E 21 3B 85 / B4 1C 42 35 / 48 BC 21 B2 / 84 08 1A __ }

Would it be possible to cut a 50MB sample from the 4 gig .RAW file in HF for you to examine? I can send it through WeTransfer, or whichever method you prefer. And, of course, compensate you for your time.

If you have the link for the thread you mentioned, that would be great as well. I can't seem to find it.

+1 on this..

I have a 42 gig file that ran off the end of my card, so the footer is missing. Stitched together the .raw + .r00, etc. in Hex Fiend, applied the 64 gig footer, (thanks to Shield: http://www.magiclantern.fm/forum/index.php?topic=5732.0 ). I have tried to run this new file through both Raw2DNG and Son of a Batch (running on a mac), but am having the same problem as dangerh33, where every DNG is a pink mess, aside from the first frame.

As I understand it, this issue is only occurring on Mac hardware. Correct? Has anyone been able to process files like these? I believe the issue of 2gig+ files has been resolved, so could it be the footer or the way that they're stitched? I won't pretend to understand Hex code, so pardon my ignorance. I just assume that since RAW2DNG and Son of a Batch work fine with smaller files, the error is likely due to something on my end.

At this point, I'm saving the .RAW + .R00s to an external drive until there's a solution, but I would also be happy to PayPal someone who can help with this situation.

I would be happy to go into further detail if it would be of any help. Many thanks to all of the Devs and those assisting, your work is greatly appreciated.