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.


Messages - TequilaKez

Pages: 1 2 [3]
51
Raw Video / Workflow for MLV->Prores444->Resolve with film LUTs and Log?
« on: October 17, 2014, 03:42:07 AM »
I realise that DNG is the best way to go for MLV but for the scope of what I’d like to do, the 1000s of files and disk space is overkill.

I really just want as much sensor info as possible, squeezed into a tidy Prores4444 file that is easy to work with, doesn’t suffer the drawbacks of H.264 compression, and allows me some extra headroom for compressing highlights in a more aesthetically pleasing way.

I also realise that full manual grading is the ultimate, but for my needs, I’d like to start with some film stock emulation LUTs in Resolve and tweak from there.
I’d like to be able to use the Resolve film emulation, and/or the ones found here http://juanmelara.com.au/print-film-emulation-luts-for-download/

Does anyone have any recommendations for the best way to do this with regard to tone mapping / log gamma etc?

There seems to be a lot of options between exporting from MLRawViewer and input and output LUTs in Resolve, and the naming convention doesn’t seem universal.

Some examples:
MLRawview -> Prores Linear -> Resolve -> input LUT ‘Linear to DCI’ - > output LUT ‘DCI-P3 Kodak2383’
MLRawview -> Prores rec709 -> Resolve -> input LUT ‘none’ - > output LUT ‘Rec709 Kodak2383’

Now the LUTs linked above say the only requirement is that the input be in 'LOG' format, but there are so many LOGs!

Eg.
MLRawview -> Prores Log -> Resolve -> input LUT ‘none’ - > output LUT ‘LC3DL_Kodak 2383’ … the gamma is way too high, so ‘log’ from MLRawView is obviously not the Log he is talking about (by the screenshots I think its from RED).

If I instead use his input LUT (Video2Log_HR_150) like this, 

MLRawview -> Prores sRGB -> Resolve -> input LUT ‘Video2Log_HR_150’ - > output LUT ‘LC3DL_Kodak 2383 …

…the gamma looks about right, but going through LUT transfers 3 times doesn’t seem very purist :)

To try and understand conventions better, how do the curves relate?

MLRawViewer has things like, Log, HDR, sLog, sLog2, C.Log, Log.C etc
Resolve has things like DCI, ‘Canon Log’, Cineon etc.

There’s also the visionLog LUT which seems like it would be a good choice to squeeze MLV into prores, but how does that fit into the workflow via MLRawViewer and Resolve?

Anyone gone down this path already with some insight?

52
Quote
Now the only other idea that popped into my head is, what's the possibility of porting some of this code to a quick look plugin?
Quick and nasty lo-res preview would suffice, just something to make navigating heaps of arbitrarily named MLVs a bit more visual.
I can help with the quicklook framework side though I'm not so good with plain C.

Ok so maybe no ned to reinvent the wheel. Perian is dead but this is semi working, probably just needing a little tweak. Looking at the source it's just using VLCKit so once it's updated for new ffmpeg, this may work for MLV thumbnails and quicklook previews.

https://github.com/Marginal/QLVideo

EDIT: Ok on deeper inspection looks like this might only be good for thumbnails / static previews due to AVFramework. I would personally find even thumbnails helpful. Another option could be %50 snapshot for thumbnail and then a 4up static quicklook preview with 0%, %25, %50, %75. The workflow advantage being: with a folder full of MLVs, we can quickly tell which need to be transcoded and which need to be trashed.

53
Firstly, Wow! I've had a 70d since they came out but patiently waiting for ML. just picked up a used 550d and ML'd it straight away to have a mess with mlv.
Not seeing this thread at first, I was fumbling with old tedious workflows and was thinking, what we need is a simple utility to squash 14bits into Prores 4444 with a log curve. To my surprise, you'd already done it! And a stellar job too.

Now the only other idea that popped into my head is, what's the possibility of porting some of this code to a quick look plugin?
Quick and nasty lo-res preview would suffice, just something to make navigating heaps of arbitrarily named MLVs a bit more visual.
I can help with the quicklook framework side though I'm not so good with plain C.

54
Archived porting threads / Re: Canon 70D
« on: July 08, 2014, 02:46:01 AM »
I have a 70d and I wan't ML on it real bad.

I know a little c++ but my only experience with ASM was on Amiga 500!
But I'll throw some hours in if it speeds the process.

Someone PM me and give me a task.

Can QEMU be run on a mac?
Me and windows parted years ago and I cringe at the thought of it :)

Pages: 1 2 [3]