Messages

saw your video before you had to put on a password and I thought it looked extremely good!

Looked sharp and couldn't see any noise as of what I remember.

But now that I'm prohibited from seeing it again, I really wanna see it

I updated my original post with the password.

[Update:]

Hi all, here is a short video shot inside the Hanted House of LaRonde, a Six Flags amusement park in Montreal, were I worked in October for the Halloween Event.
The light condition where less the ideal but the result is pretty good (at least by my standard).
It's all shot with the same lens and hand held without any gear (it can be a bit shaky in some places but it still work all right).
I choosed to do it in these conditions to try to see how far the ML can go in terms of usability in real gigs.
The edit might look a bit cheesy (and I agree) but it was mostly fooling around with the music.

Workflow I used was .RAW->RawMagic->AE (Proxies/Grading/FX)->PPRO (trough Dynamic Link)->Vimeo
This workflow is extremely fast and efficient and ensure optimum quality of image throughout the process (no transcoding).

BTW, for people who says that proxy take to long to setup in AE to be usefull, there is a little but extremely helpful (and free) script that does it all in a few click. It's called rd_approximate_v1.0

Appreciate the comments!

Update: had to put password because of copyright things, sucks!

Update 2: Oupa, Sorry, forgot to put the password: professionnel

@Lokki19

You can Change the settings of RAW2DNG. Just load the app, and then pick the app again, and drop it in the same way you do with the raw files. With that, you can choose not to have proress files.

Nice! Thx, will try that. Also, I realised that my Raw2dng is making ProRes 422(HQ) instead of 444, any clou why or how to change that?

Great Analyzation thanks it will help a lot through my future work with ML RAW. Are you saying from your research RAW2DNG is the best or consistent converter, also what do you think about RAW2DNG to Adobe Camera Raw to QuickTime to FCPX? What are some stable UpRes conversion you were able to achieve without compromising the Quality?

Didn't try anything in FCPX yet. Personally, i don't really like this version. When I started to use it, i felt like a repair man trading it's tool box for a swiss army knife. But that's my opinion, if you feel comfortable with this editing suite, who am I to tell you otherwise.

But your workflow seam fine. If you shoot in 1880x you can up scale to 1080p without any problem in FCPX. If you want to reach 2k, you would need a upscaler like Instant HD from RedGiantSoftware. You might also want to check for a temporal denoiser like NeatVideo, it help's cleaning high iso artifact and color noise, and make your image look sharper and cleaner.

Great, thanks for your tests.
Though, just in color correction topic, i guess that you have so much room in raw that it's not so important the tool you make your conversion.

Cheers.

For sure, you can do extensive correction to the colors, I just find it a bit odd that there is a considerable difference in color interpretation. This difference could be link to the difference in the noise appearing, or vice versa.

Hi everyone,

I've been using the Raw video feature on my 5DmkII since May and I just love it! (My thanks to everyone who worked to make this append). The builds are getting better and more stable every time but I feel that the post is still a bit sketchy. There are many different ways to convert the footage and I found that each have strong and weak points.

It is in no way a critic and I have no right to complain about it since I have 0 knowledge or skill in programming. I'm only stating facts observed and issues reproduced.

I'm working mainly on a Mac and the 3 most popular importer on that platform seamed to be raw2dng, rawmagic and Ginger HDR plugin. While using them extensively, i noticed that those 3 methods interpret the same Raw file very differently. So i decided to do a little comparative video with the 3 methods in a somewhat controlled environment.

After seeing the results, it was clear that i needed to separate this video in 3 segments to better see and understand the differences because i found out that the amount of light and ISO setting vary the result considerably (meaning that a high iso does not have the same result in the 3 methods if the image has strong overall shadow or is just low in light). In words, this might sound silly, but if you look at the image, you would probably understand what i mean.

The Specs for this test:
5DmkII
Transcend CF 32GB 1000x.
ML Raw build: July 12, fixed 24fps, noise reduction ON, 1880x940 (2:1) down scaled to 720p for export.
RawMagic: Beta7b
Raw2Dng: July 14
Ginger HDR: June 12
Picture style: Canon X-video
Footage conformed in AE CC
All footage are taken as shot, no grading, no denoiser, no levels correction, no fancy music.

Video 1: At ISO 1250 and in pure darkness, Raw2dng give the best result overall, Ginger HDR is extremely noisy and RawMagic is full of vertical lines.

Video 2: At ISO 640, Raw2dng is sharper and brighter then the other 2 and the color is by default more accurate then the other 2. Ginger HDR introduced hot pixel in certain shot (ex: at 3:11, near the top of the cat's ear, there is a hot pixel, unfortunately barely visible in the compressed version). These burned pixel do not appear in the other 2 methods. Ginger HDR also has more banding in out off focus sections. RawMagic has a lot less vertical lines in pure black pictures.

Video 3: At ISO 100, Raw2dng has a more balanced image and highlight retaint more informations to be recover. Ginger HDR has a lot less noise but lost a lot of information in highlight and color is shifted a little bit in the red. RawMagic color is shifted in the blue but vertical lines are barely visible in strong shadow.

Now, Raw2Dng seam to have the best result overall but a lot of footage could not be use for this test because Raw2Dng was not able to convert the .RAW file properly, every frame was pink garble noise. But where Raw2Dng failed, the others worked.

I really like the result of Raw2Dng but the UI is terrible and since it is creating automatically a ProRes file and a DNG, it is taking 2x as long to process, it take a lot more room on drive, the footage need to be renamed afterword to keep your project organized, and the result are unpredictable. RawMagic interface is great, efficient, fast,  but the result in low light is really bad and unpredictable. Ginger HDR is a incredible tool to monitor your shots live on set. .RAW files can be drag and drop directly in premiere and after effect for quick review to see if the shot is good or not. But for a post production solution I don't find that the image is good enough to work with.

RawMagic has a really sober and functional interface. It lacks a bit of customization for import, like choosing if you want to creat a ProRes or not, and witch compression you want to use (LT, 422, HQ, 444). At the moment, this methods does not work with the audio files created by the camera (.R00).

Audio is another problem in the video Raw post. I found the instruction confusing and having to go trough terminal commands could be a little bit scary for none programming guru (my self including).

In the end, if anyone out there is looking for a challenge (or has some time to kill) and a lot of talent in programming here is a few suggestion for improving post workflow.

-Choice to use DNG and or video file (ex: ProRes for Mac, Motion jpeg for PC).
-Audio conforming to footage in .wav with simple drag and drop.
-Batch process and Batch renaming options.
-Logging camera info and other metadata.
-Simple UI, like RawMagic.

I'm sure other people have there own request and suggestion, I'm just stating a few things that I think would be nice to have.

Hope you'll find some uses to all this.

Cheers.

I tested 3 time the same Raw footage to Prores 422HQ with
1- AE (with ACR)
2- NukeX (with J_Ops_2.0v1)
3- Resolve 9 Lite
Result of render time:
40 min AE 
18 min NukeX (works the same with DNG or CinemaDNG)
2 min Resolve 9
I know quite well ACR (so I used quite a lot corrections), a bit less Nuke (I didn't use any any chromatic aberration) and I don't know much about Resolve for the moment and I didn't use (and see) any chromatic aberration or any recovery exposure (for the high lights for example) but used Black Magic LUT with some other few color correction.

I have to go deeper to the investigation because as you see, it might depend on the raw settings.

Take your AE project and dump it in Media Encoder to render out your ProRes, cuts the time in half if not more.

chroma denoiser is that not available in the lite version?
Would Magic Bullet's Denoiser II work as well as Neatvideo?

Not in my experiences, RG Denoiser is softening the image a lot more and you loose more detail then NeatVideo in most cases.

Does anybody know how a workflow that uses SpeedGrade instead of DaVinci Resolve?

Thanks!

I've had success importing CinemaDNG sequences generated by RawMagic. You can also import the dng from raw2dng into AE, save the project, import the sequences in Premiere Pro and then send them in SpeedGrade. That is if you want to make sure to retain the full dynamic range of the image. Otherwise, justo export a clip from the dng in AE and do your work.

I've been using the new Adobe CC and it was working well, should work to in CS6.

Cheers.

Hi guys, first time posting.

I'v been reading a lot about the raw for 5dmkii and decided to give it a try and shooting stuff that is not plain landscape, I wanted to see how it behaved with fast movement and close up. This clip was shot in 1280x480 with forced 24fps. I could not get anything bigger do to my card speed (kingston 16GB 266x). I recorded an average of 480 frame before the buffer filled up. There is no color correction apply, everything is ASIS.

I notice that there is still a bit of noise in flat surface, the strait lines across the FOV are a bit jaggy, and there seams to be a slight purple tint. I don't know if it's cause by the built or my sensor how is showing signs of wariness.

I'll do more test with newer built as the come.