Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Erik Caretta

#2
I see! Probably the book was wrong or we didn't read it carefully. Well, we used that unnecessary precaution for all the 5 days of shooting :)
There must be another reason for the bad shots then.

Anyway a1ex, what do you think of the short? Do you think we made a good use of ML?
#3
ok I finally found the book. It is

The EOSHD 5D Mark III Raw Shooter's Guide
By Andrew Reid - First Edition

At the chapter "Chapter 11 - Raw shooting advice by Andrew Reid" it contains this part, at page 92:

QuoteShoot at these ISOs for best results...
The cleanest ISO sensitivities on the 5D Mark III are 100,200,400,800,1250,1600 and
3200. Some others such as 640 and 250 have considerable noise in the blacks.

Of course I can't prove if it's true or not, but we followed this rule :)
If you say there are no differences I trust you, but at the time we followed these indications.
#4
Just found out that v2.3 was not the version we were using.

We were using a nightly build instead, released probably on July or August 2013, running on Canon 1.1.3 firmware. I can't tell you more right now, until I'll find the book :)

#5
Quote from: a1ex on October 23, 2014, 08:28:41 PM
Proof please.

Sure! We had a book, which I can't find at the office right now, that explained that. I guess it was

http://www.eoshd.com/eoshd-5d-mark-iii-raw-shooters-guide-pdf-book-download/

but I can't tell you for sure now.
Anyway, we were using Magic Lantern v2.3, and from page 14 of the user guide:

QuoteISO
Advanced ISO control.
Color coding:
• orange = Canon ISO with good noise or dynamic range (100, 160, 200, 320 ... 3200).
• green = ISO with negative digital gain applied via DIGIC (80, 90, 160, 320 - obtained by
setting ML digital ISO to a negative value). These can have lower noise and/or better
highlight rolloff than their Canon equivalents.
• red = ISO with positive digital gain (avoid these values).

I guess this is the point. Sorry for being so vague but I can't remember more.
#6
Quote from: arrinkiiii on October 23, 2014, 07:44:44 PM
Sirius, depend of the ML version ???  ?  Uhmmmmm would like to know what is the best, im shooting with ISO 100 but i think that is not the best...     

Yes, behind the scenes, sorry =)

yep, it depended at least, not sure how is the situation now with new versions.
Sure thing anyway, we'll post something soon :)
#7
Quote from: arrinkiiii on October 23, 2014, 01:01:31 PM
Just wonderful and pleasent for the eyes, amazing!!! Good work indeed !!!

-You guys have sad "we shot them with "wrong" ISO levels"   What is the "best"  ISO ?

-Yes, please, if Mattia share the CC and grading trip would be awesome =)))

Thanks for this, appreciated a lot  8) 

PS- No BTS ??



yes, back when we shot it there were some preferable ISO levels to use, I don't remember exactly which ones but it doesn't matter since I think it really depends on the ML version you're using.

what you mean with BTS? behind the scenes?
#8
Quote from: kgv5 on October 22, 2014, 07:45:05 PM
Guys, how did you make CC in resolve, i mean did you use any flat profile like cinelog and add some stock LUTs? I love this kind of teal and orange look, i know that this was probably more complex thing but could you please tell that your starting point was?.
Explosion in the end looks brilliant, was it made in blender? Thanks

Yes there is a LUT, but then a lot of shot per shot corrections were made, and a lot of secondary CC. Mattia will give you more details, he's the colorist and I'm not 100% informed on his workflow.
The explosion is a mix of different footages, with minor 2D painting and a super rough 3D simulation for the shock-wave.

Quote from: chmee on October 23, 2014, 12:45:44 AM
chapeau, guys. marvelous work.

thanks man, and let me thank you for your work on ML ;)
#9
Quote from: kgv5 on October 22, 2014, 01:03:50 PM
Voices are really great and its very important part of MGS universum (games graphics was changing with hardware generations but voices were the same all the time).

One more question about technical side: what did you use for lighting?

That's an interesting question :)

Other than location's available lighting, we had 3 LIPO battery-powered LED lights, 27W each one. So we did almost everything with 81 W. Pretty much incredible, it would have been simply impossible with anything different from 5Dmkiii+ML!
#10
Hi guys,

I'm Erik Caretta, VFX supervisor here at Hive Division :) Thanks everybody for your kind words, but let me THANK all the ML team for the wonderful job you've done! It would not have been possible for us to reach such a quality with almost no budget. The performance of Magic Lantern were great, and definitely saved our production. I admit that on set we had some camera crash and bugs, but overall the experience was very positive. I'm sure that now, almost a year later, ML is far better.

Quote from: tonybeccar on October 21, 2014, 06:55:14 PM
Hey wow!!!!!! Amazing photography and storytelling!!!

Do you mind sharing some technical aspects?? Like lenses, post techniches (denoiser?), etc.. really it looks SO good.. even on youtube! Amazing!!!!

sure thing! We shot with a 5Dmkiii as Mattia, our DOP, said. For the lenses, we shot almost everything with a single Canon lens (Canon 24-70 f2.8 II), because we had such a tight schedule and the weather conditions were so bad that we could not afford to change lens every 2 minutes :)
The performance of 5Dmkiii + ML were good: we had a decent noise level on most shots so we didn't use any denoiser on most of the short. Some shots are problematic indeed, as you can probably see, but it was our fault since we shot them with "wrong" ISO levels. We used Nuke's denoiser when needed, anyway: since we debayered in Resolve Lite and not in Adobe Camera Raw we had not a good option to easily denoise everything, so denoise was applied ad hoc on some shots.

We used a Resolve-Premiere roundtrip. The workflow was pretty much as following:

- On-set we had Resolve Lite to debayer and create dailies
- Firstly a rough CC was done on Resolve
- Then DNxHD proxies were created in Resolve for offline editing in Premiere Pro CC, and dpx sequences were created for VFX shots
- Once the VFX work was done (mainly Photoshop+Nuke+Blender), we switched back to Resolve (roundtrip)
- Color grading in Resolve, from which a DNxHD master were exported
- Final export from Premiere, with titles, audio, etc

If you have any other question, we'll be glad to reply!

Quote from: kgv5 on October 21, 2014, 08:45:37 PM
@microsoul
Just WOW!!!! I love MGS series, i have played all parts on PS1, PS2 and PS3. Attention for detail is phenomenal! This is the first MGS movie which looks and feels exactly like games! Congratulations!
Snake is moving exactly like in games, love all those small details, voice acting is just great, did you hire David Hayter for this??? Sounds exactly like him :) From the technical side: it looks just great, love the colors, camera moves, lighting. Many thanks from a die hard MGS fan :)
BTW, i an not buying PS4 right now and thought that i will loose MGS5. The great news is it will be also on PC !!! :) What a relief :)
I hope we could see more MGS from you soon. Great work!!!

thanks man! Anyway he was not David Hayter, but another talented voice actor, Phillip Sacramento. But we had Paul Eiding on board :)
#11
maybe the header is corrupted. Try to take a look at the sticky  threads on the workflow page, there is one that explain how to repair damaged files.
#12
what is the problem? any detail?
#13
Quote from: dariSSight on October 27, 2013, 07:14:13 PM
If the highest continuous I can do on 5D Mark II is 1880x1012 should I change the clip import as 1920x1080 as default?

I would import the clips at original resolution, then upscale to full HD. The exact workflow depends on the software used.
#14
QuoteI love this workflow, but for VFX and CGI are you doing a fresh projects with the DNG in AfterEffects then exporting to Resolve as QuickTime, and are you upscaling the QuickTime video your export from RESOLVE as uncompressed 10bit and will that stay clean?  How does this workflow works with FCPX in replace of Premiere CC, I have both.

I think for VFX I'm going to import in AE my dngs, then do my stuffs and export 16bit tiff to Resolve.
Regarding the upscaling, I still have to test, but upscaling from full HD to 2K won't be that difficult I suppose. Anyway, I need to check if 10bit instead of 8bit is of any help for noise reduction. If not, I think I'll go with 8bit.

Quotefor Colour Correction like white balance, highlights and shadows I'd use ACR.

If you're going to do Chroma Key, then highlights and shadows should not cause any flickering because of the constant background. But if you got light aimed towards the lens and the light gets blocked, then you will very likely experience flickering with those sliders being used.

I shot a chroma key and abused the hell out of highlights and shadows and had no flickering, because of the constant levels of dark and white.

But don't how this will affect your workflow. I just like ACR's quality better.

I have only a couple of chroma key shots, so that's not a major issue.
I see a lot of people preferring ACR to Resolve: so far I didn't notice big differences, but I want to be sure I'm not losing quality.
I need to perform a careful test and compare the output, even if this change would completely disrupt my workflow :)
#15
Hi everybody,

I'd like to post here the workflow I'm planning to use for our next production. It's a trailer for a crowdfunding campaign we are going to launch in a few months: we shot a couple of weeks ago with 5Dm3 and Magic Lantern, and now I'm trying to find the best way to deliver the best product possible.
I read almost every discussion in this session, I hope I didn't miss anything critical. Please take a look, and any comment is welcome!

PRODUCTION
- backup of CF card
- RAW to DNG conversion, with Batchelor 3.0 alpha3 (with raw2dng)
- import DNG in Resolve, applying simple metadata (shot, reel number)
- export dailies (QuickTime DNxHD) for checking shots on set, and later to choose good takes

POST-PRODUCTION
- once good takes are chosen, export proxies (QuickTime RGB 8bit non-compressed) from Resolve
- editing in Premiere CC, with proxies
- roundtrip to Resolve: import XML from Premiere CC
- white balance in Resolve
- VFX and CGI work
- compositing on original dng sequences (mainly After Effects CC)
- import VFX shots into Resolve
- color correction and grading
- export QuickTime RGB 10bit non-compressed from Resolve
- import into Premiere CC: noise reduction (Neat Video plugin), grain
- crop and 2K upscaling if needed, titles
- export final video


What do you think? Anything wrong in your opinion?

I still have to test the importing of VFX shots into Resolve: I still don't know which file format is the best (probably 16bit tiff), and I'm pretty sure I'll have some timecode shifts due to compositing application.
And I'm not sure how to proceed for the final export from Resolve: using the same XML to re-import everything in Premiere, or generate a new EDL in Resolve? I'll find out :)

Thanks for reading

Erik
#16
it worked, simply copied a good footer from a similar clip, changed the frame number and converted. Thank you very much
#17
the problem is now fixed, thanks to Resolve 10.
#18
Raw Video Postprocessing / Re: Resolve 10 beta is out
October 20, 2013, 12:44:27 PM
I confirm, no more pink dots! That's great, because I was pretty disappointed by this problem. Now I can fully rely on a Resolve+Premiere workflow.
#19
thank you very much for the links, I'll try and let you know if it works.
#20
General Help Q&A / Corrupted clip. Anything I can try?
October 18, 2013, 07:46:22 PM
Hi everybody,

Last week we had a great and quite long shooting with 5Dm3+ML: everything was great, on 590 clips only few errors.
Unfortunately one of the only 2 corrupted clips is quite important, so I would like to ask if I can do anything to be 100% sure the file is not usable.

I'm using Batchelor with raw2dng to convert the raw files, and when it starts converting that clip I see "converting frame 1 of -613843513" and then it starts saving frames of 1.45GB each. Of course I can't open these files in any software.
My suspect is that the problem should be in the header: since the file is quite similar in size to the other takes, and I can have the jpg thumbnail in Batchelor too ,I guess the data are fine, at least some frames.

Do you think it's possible to "rewrite" or fix in some way the header?
#21
Quote from: reddeercity on October 18, 2013, 03:56:39 AM
I don't have a 5d3 but a 5d2 and on my last job with my Ninja connected i had (error 70)
Then lockup, pull battery reboot then record my footage.
happen 8 times in a row when i stop recording each interview ,  3 to 5 minute long .
But only on my 32GB cards not my 64GB cards, i guess because there are faster.
Had No corruption, all good in the end :)

yes, the same problem (probably I remember the wrong Err number), with 2 different 64GB cards. I'm not sure it's a problem due to card speed, since both our cards are pretty fast (120 and 94 MB/s writing speed with buffer=16384k)
#22
As far as I know, for a clean HDMI output from a 5Dm3 you need Canon firmware 1.2.1, but Magic Lantern only run on Canon firmware 1.1.3.

Anyway, we tested this exact setup last week during a 5-day shooting: 5Dm3 (canon firmware 1.1.3) with Magic Lantern + Atomos Ninja 2.
We needed the Atomos only for fast playback during shooting, and actually it was working pretty well, but we had a problem that finally led us to not using it at all: it seems that connecting anything to the HDMI output of the camera causes random Err 80 crashes on our camera. We could not understand the cause, maybe FPS override, I don't know, but we experienced several camera crashes while using HDMI output, with both a monitor or the Atomos, so finally we decided to proceed without HDMI output when possible.

It would be nice to know if anybody is experiencing problems due to HDMI output.
#23
ah that's the point I was missing. Sorry guys, I was sure the feature was available while shooting raw too.

OT: Anyway, last week we shot a short with you great magic lantern on 5Dm3, I'll open a thread soon to provide you some feedback.
#24
Not yet. I'll do as soon as possible.
The feature seems so basic to me that I think I'm simply forgetting something.
#25
Hi everybody,

I am new in the forum, and first of all I'd like to thank all you crazy developers for this amazing piece of software you are working on.
We've been testing ML since a couple of months ago, both on 5Dm2 and 5Dm3, and the results are simply great.

Everything for me is working properly except for the Movie Logging feature: I was testing it on the 5Dm3 few days ago but I can't find the log files anywhere. Of course the option was on, and everything else was working well.

ML version is 2.3 (22nd august 2013), Canon firmware is 1.1.3
ML is installed on a SD card, while recording on a CF card.

Any idea?
Thanks

Erik Caretta