Messages

I would hardly call that solved. An on camera solution like we had in the early builds would be the ticket.

If they were frame-for-frame duplicates, having an H264 copy for immediate offline edits would be fantastic. Obviously the roundtrip might be a bit of a headache to reconnect everything in Resolve to the CDNGs, but as long as we could figure out a way to get the filenames/reel names to line up, I'd see this as a major workflow boost.

Plus, having something to play back on set with sound would be HUGE for performance reviews.

I love the new double beep when something goes wrong and the recording halts.
Along those same lines, for audio syncing purposes, it'd be great to have a double beep when we stop recording manually to help get audio synced with dual audio sound in case of drift.

If anyone is interested, I just had a bash script put together for raw2dngOSX to automate the DNG extraction process. Read more and download here.

Personally, I've been using this, then Adobe Bridge's ACR and "Export to Hard Drive" function to create a JPG image sequence which I bring into compressor to create ProRes files. Not the most elegant workflow, but it's the best looking finished product I've been able to muster. As much as I love the speed of the Cineform workflow, I just can't bring myself to use it's terribly soft debayering. It's just so bad.

[raw2dng-batch BASH Script for raw2dngOSX on the Mac]

raw2dng-batch BASH Script for raw2dngOSX on the Mac
Version 1

I had this bash script put together to automate the extraction of DNGs from my .RAW files. I realize it's similar to scrax's raw2dng gui app, but I wanted something with a little more automation to help on an upcoming shoot I have. And I also needed the ability to set the output directory.

If someone knows how to turn this into an app, have at it.

I open up terminal and type "bash" then drag and drop the script into the window

It asks for the following:
1. The folder containing the raw2dng unix executable (drag and drop the folder)
2. The source folder containing the .RAW file(s) (drag and drop the folder)
3. Where you would like the DNGs extracted to (drag and drop the folder)
4. What roll number you would like to use. If no roll number is specified, it see's the last one used, and adds 1.

To make things even more automated, you can alternatively add the variables right in the terminal like this:
> bash raw2dng-batch [raw2dngDir] [sourceDir] [outputDir] [rollNumber](optional)
This is very helpful as you can simply press "Up" "Enter" in Terminal every time you insert a new card, and the script will go to work (works great if you don't specify the roll number, and let it decide for you)

When processing, it creates the following directory structure:
[specified outputDir]/R001/R001_S001-[original .raw filename]/R001_S001-000001.dng
R001="Roll" number (automagically counts up each time processed)
S001="Shot" number (starts at 001 for each "roll" and goes up for every additional shot)

You'll need the raw2dngOSX unix executable to run this script.

Hopefully someone finds this useful.

I'm getting a couple errors that cause the app not to function if it's in a directory leading up to it's containing folder that contains a space in the name. For example: If have the app here "/Applications/RAWApps", it's fine. If it's here "/Applications/Magic Lantern/RAWApps" (space in Magic Lantern", no dice. This didn't occur with earlier versions. Aside from that, still handles the .RAWs like a champ.

Keep up the good work!

Awesome! Can't wait to try out your tool! 

I've got 3 short shots uploaded here.

These are Tungsten, 1920x1080, ISO 500. Unfortunately, I've nuked all of my daylight RAWs I shot earlier today. Let me know if you'd like to see something specifically.

Any chance we'll see a shell tool for Mac to take RAWs to Cineform RAW MOVs? Thanks!

I've noticed a strange set of 2 black veritcal lines followed by 1 slightly over-exposed line on left side all of my 1920 pixel wide DNGs (seems to get cropped out if I shoot any less wide than 1920). I'm running the 5/25/13 build, though I've seen it on older builds as well. raw2dng beta 0.8 was used to convert the RAW files.

Here's a 1200% zoom of the top left corner: (and here's a link to the full DNG)

I should note that this DNG in particular has been processed through Adobe's DNG converter to reduce the file size, though this problem persists in the original DNGs as well.

Edit: I'm just realizing that I'm not alone in this. It seems most of the demo videos I'm seeing on YouTube and Vimeo suffer from these vertical black lines as well.

This is fantastic! It's been able to handle everything I've thrown at it.

I would love to be able to set a destination for the output. That way I could read the RAW files straight off of the card and send the DNGs right into my hard drive. With the command line app, I would simply browse to the directory I wanted to files to be dumped into, and run the app from there. Worked like a charm.

are any of you running raw2dng on a mac? Does it work on wine or vmware fusion?

Works great for me in CrossOver. "Programs - Run Command" drop in the raw2dng.exe, then the .RAW file. Spits out a stream of DNGs.

[cleared camera settings]

What exactly do you mean when you said you cleared camera settings?

He means "Menu - SET UP4 - Clear all camera settings".

Good luck on your project!

i cant find an option on this ML for my 5D3 for an auto restart.
Is that option available?

+1 for Auto Restart

I'd love to see an auto restart option in ML, even if it means there's a couple second gap between the clips. I've become so accustomed to having auto restart on my ML 60D and T2i. I miss it so dearly. 

Did you notice any of them with the alpha 3? If yes, any hints on how to reproduce?

I've had the "no response from buttons" issue happen at least 3 or 4 times out of at about 400 boots. Each time, the only way to reboot was through a removal of the battery (power switch did not work). To me it seems random, as I'm unable to reproduce it with a certain set of variables.

I've never had a black frame issue, though I've only been doing video work with ML.

Just because so many people keep asking for auto-boot to be added, I thought I'd post a screen shot of my custom menu. Having firmware as my first option makes it extremely fast to boot into ML. And I think A1ex has said this before, to save power, just switch to photo mode in between shots rather than a full power down.

I do a lot of run and gun commercial shooting, and these are my most used settings:

Have you tried it without your battery grip?

I'm not seeing a BMP of the overlays when I take a screengrab, though I still get a working .422 file with the image. Coming in a later build perhaps?

I'm talking about basic ML functionality on HDMI - like zebras aligned with the image etc.

I haven't had a chance to fill out the survey yet, but here's the only issue I've had on my last 4 full day shoots. I've been using alpha one almost exclusive via HDMI with my SmalHD DP6. Everything I've tested works great; audio meters, fast zebras, focus assist, histogram, vectrascope, an even the manually enabled "Not recording" warning. Here'a what I've had enabled on my long day shoots: "not recording" warning, audio meters, histogram (with gradual warning), and LumaFast Zebras over 99%. The only time I have a problem is when I leave the camera on but power cycle my monitor. When the monitor comes back up, the 16x9 crop bars scale down a bit, slightly covering what should be the proper visible area and revealing part of what's actually not recording.

See this photo showing what I'm saying.


Other than that, I've had no alignment issues with any of the features (zebras, focus assist, etc).

Edit: I should add that to get around this, I simply reload the ML firmware.

HDMI is causing trouble - anyone needs 720p? I hope not.

Are you referring to 720p HDMI output? Versus 1080i?