Messages

Thanks for the info Andy. I've been trying to read up a little on color space etc on Wikipedia but once I hit the lengthy transform equations it starts getting beyond the scope of 'need to know' for me. So tbh a lot of it goes over my head! I've just been working with mlv and Resolve and while dng has some nice advantages, for indie rec709 stuff, it seems to me that a prores workflow could be faster, more efficent for disk and cpu/gpu and more compatible with other apps and OSX (quick look). Ideally I would drag a folder of MLVs on mlrawviwer and it would spit out log encoded prores suitable for resolve with a single 3d output LUT. That could be a film stock LUT or plain old rec709.
I've just not had any lucky with the included log luts for mlvrawviewer, I think mainly because an additional input LUT seems to be required for the Output luts to make sense. So it ends up going thru 3 lossy luts and info appears to get lost or clipped along the way.
Apologies for any naiveity there, I'm still learning:) is this what prores from BMD cameras is?
Anyhow, your luts look equally promising for this application. I'd happily let go of a few bucks to realise this kind of workflow.!

Nice. 3 x price and a bit more fiddly with extra connections, though I guess you could just solder a 3.5mm plug onto the av cable. Charging via USB is def a nice vibe though!

I've been digging around more for getting the most out of our prores exports. Some info on DCP if you should ever find the time and interest!
Here's some correspondance from VisionColor

Is there a way to get or convert these LUTs to .cube format so they could be used with MLRawViewer to export MLV video as Prores4444 with visionLog profile?

thank you for reaching out to us! Unfortunately conventional 3D LUT formats can not hold the data neccessary to convert linear light RAW sensor data to VisionLOG. AFAIK, a more complex camera profile which has Hue/Sat deltas and an independent tone curve is required for such operations.
I guess that the MLRawViewer uses the embedded camera profile to convert the raw data to images at which point it is too late in the process to use a  LUT to extract more information from the image.
Essentially MLRawViewer would need an option to load external dcp profiles for proper conversion...

But then I though I remembered..

However, I don't know how to support DCP files, since those are a binary file format intended for Adobe products. So to use VisionLOG, or CineLOG, you would need to get "simple" LUT versions of those, or else help me find a spec for the DCP file format.

So incase you never could find it....

The developer has mentioned possibly supporting dcp profiles if he could get the spec.
Could you point us in the right direction?

Sure, you can download the DNG specification and SDK on Adobe's website which lays out the dcp profile structure which should be all your developer needs. Here's the link: http://helpx.adobe.com/photoshop/digital-negative.html

[$10]

Just wanted to share the little headphone amp I wired up.
Cheap, portable, easy to solder, and decent quality components so it sounds great.

What you need:

1.$10  http://www.ebay.com.au/itm/2-X-150-mW-Class-AB-Headphone-Amplifier-Board-LM4881-150mW-Stereo-HP-Amp-/121155320773?pt=AU_Bedroom_Furniture&hash=item1c356b7bc5
2. 9V battery clip (a few cents)
3. Canon AV cable.
4. Suitable enclosure of your choice. Sweets tins are good.

I had a spare AV cable so I chose to butcher it and keep it simple but you could easily wire up RCA sockets. I also chose not to use terminal blocks but they're probably a good idea.

There's only a dip switch for low and high gain but I've found the default setting to be the perfect level as is.
You could easily attenuate the input with a pot but I find the ML headphone volume control is enough (devs: a couple a negative gain options might be handy)




Now just need a on/off switch and suitable pocket sized case that could be optionally velcro'd to the tripod.

Specs are not bad either.

Size:76.2 mm (L) x 50.8 mm (W) x 12.1 mm(H) ± 0.2mm
Thermal shutdown protection circuitry
Adjustable gain
Wide power supply range: 8V-24V
Audiophile Quality Sound:
0.025% THD+N @120mWrms 16Ω
0.02% THD+N @75mWrms 32Ω

Wouldn't cineon be the best option to choose?  It's industry log standard and Davinci was been designed to work with it since its inception.

haha well that' sorta of what I'm asking. Thanks for the tip!
Although the the film stock LUTs I was referring to list either DCI, rec709 or in the case of the link just 'log' which according to his screenshots would be log as it comes from the RED.

So If I go to Cineon, i need to get to one of those eventually before the film stock LUT.

And in terms of MLRawViewer, would c.log refer to this Cineon Log? or Canon Log, or Something else entirely?

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?

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.

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.

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