Messages

Relax guys... This is the same pattern they go through on a yearly basis -- everything is gonna be alright and I'm a happy swinger between 1.1.3 & 1.2.3 nightlies with no fear of destroying the 5D3!

50L 1.2 3x-crop mode MLV > ProRes 4444 via MLRawViewer 1.4.2

http://vimeo.com/113983832

Curve: HDR global tone map

3D LUT: VisionLOG To gamma neutral rec.709

Apparently I just tested out a Non dual-ISO file w VisionLOG and it comes out well than from a dual-ISO in which I guess makes sense in a way...

Since Dual-ISO ALREADY gives you that extra DR? lol

And do we tend to leave the Zebra's @ 99% or does anyone know of a sweet spot for this?

So far for me it's still in the default 99% and seems to work well for most situations.

I understand it varies on lighting set wise but just purely out of curiosity!

Since no one has replied so I decided to try and give it another shot at this thread before it hits graveyard...   

Here are other few LUT combo's comparisons that I thought looked decent & clean according to my eyes...









Yes they were all shot in MLV 3x crop mode... barely any aliasing on these frisks! lol

Just barely...

However due to just playing around the settings and I learned that if you use slo-mo (48/50/60p) and once you get into 3x-crop mode it literally cuts the framerate down to around 30fps. Since I shot this in 48fps and got carried on with the amazed of 3x-crop mode NOT realizing this particular mistake which already has been documented in this forum.

Shame on me -- but hey that's the fun part of troubleshooting and isn't that why test/practice makes perfection?

Currently uploading an example onto Vimeo...

Stand by!

@Danne -- did another test with Dual-ISO 2.5k MLV. Converted w latest app through service workflow. My question is... Do you rather adjust Tone Curve first in ACR from AE before exporting with VisionLOG.

Because after exported I wanted to try apply a certain 3D LUT that I thought looked pretty clean but for some reason the highlights looked completely drained out (like as if I did it too much but hadn't touched the highlight slider on the main page within ACR other than the Tone Curves) so I'm not sure if I am doing something odd during this process?

Thoughts?

@Danne -- Well said, agreed and exactly the reason why I don't mind swinging back and forth 1.1.3 & 1.2.3 To get the slow-mo, for the most part because you'll need to use Macboot to make card bootable if I were to go back to 1.1.3 from 1.2.3 as oppose to going from 1.1.3 to 1.2.3 which can easily be done w obviously two different SD cards w separate firmwares and not need the use of my MBP.

Perhaps one day I'll prolly find myself a 2nd body in order to install each one with different firmwares...

Now only if Santa was real -- HA!

@swinxx -- I'll see if I can give it a try again since I'm currently on 1.1.3 and will confirm to you once I can!

Plus let's try to stay on topic within this thread...

pM me if need to.

Thanks!

I second that @dmilligan -- MLV Dual-ISO in 3x crop mode is remarkably beautiful!

Right, @Danne?

Excellent point @dmilligan -- thanks for pointing that out!

@swinxx -- I understand your frustration as I am cinelog supporter as well. But I don't tend to throw it out there to others. I also do understand the fact that promises are difficult to hold on to. As long as it's not going to be a broken promise then I have no problem with it being 'late' as there may be a good reason for it perhaps to prevent all of us storming emails at @Andy600 just because one of the LUTS he provided didn't work or minimal issues that may arise which could also have been prevented. Does that make sense?

Regarding @a1ex's situation about the full res silent for 1.2.3 -- if I can recall this correctly but I was able to implement and use the Full Res silent on both 1.1.3 & 1.2.3 as far as I'm concerned.

You can press Backspace button instead of Esc to get Out of the window without closing down the app...

Can you just uninstall ML and then reinstall it again after repair, only if it does need to be repaired by Canon?

Think of it as a dictionary scrolling through in the index section in the back of a book -- however with Internet nowadays it's actually quicker to google literally everything let alone the search box within this particular forum as well...

No one was around to ask to when a1ex or g3gg0 are looking for resources trying to create this remarkably amazing Magic which is incredible, I would say.

Thanks to you all for keeping this Lantern well lit even during the off-season... 

P.s. Regarding nightlies...It's rather close to being perfect on 1.2.3 and I only go back to 1.1.3 for high speed RAW/MLV needs other than that I've been happy!

It definitely looks like a rolling shutter effect but it's not as bad as others and I've seen worse...

How exactly could this be more beneficial by using this formatter online through sdcard.org?

I'm assuming you will have to then reinstall ML every time you do this?

As oppose to doing it within inside the Canon menu when it can easily keep the ML after format.

Thanks for sharing @dpjpandone!

Not sure why RAWmagic won't work for you but as far as I'm concerned the ML community does NOT support using RAWmagic software regardless of how nice it may seem. I own one as well but there are other options...

Do you want to convert them into DNG's... Try using RAW2DNG -- http://www.magiclantern.fm/forum/?topic=5404.0

If you want to convert them into ProRes 4444 then try using MLRawViewer which can also convert to DNG's as well -- http://www.magiclantern.fm/forum/index.php?topic=9560.0

Might also want to check out MLVmystic as well -- http://www.magiclantern.fm/forum/index.php?topic=10466.0

Found these links within seconds through Google...

I would rather shoot Dual-ISO over HDR only because the workflow in post is easier and I want to be able to use fast motion objects whereas HDR doesn't cut it.

MUCH EASIER by a mile...

Do some research on these links please...

DUSL-ISO
http://www.magiclantern.fm/forum/?topic=7139.0

HDR-Batch
http://www.magiclantern.fm/forum/index.php?topic=11486.0

I second that @dubzeebass & @QuickHitRecord -- using the ETTR hint in the histogram definitely helps because I've learned that using the ETTR as always enabled doesn't always give me the exposure that I want...

Life's better when we control everything manually rather than having a computer control us.

Try deleting the .MRX files next to each clip you want to export.

I believe the bug in 1.4.2 is because I changed to using relative paths for the audio file, but didn't check all the cases where old absolute paths must be converted to relative

If that doesn't work -- Maybe try pressing Y to 'unpause' it somehow?

Results?

C,mon guys cut some slack for @Andy600 since he may be busy with life just like all of us, rightfully so.

Also it would be better for him to take the extra time to correct the minimal issues rather than give out the updates sooner and vice versa.

Just let him do his thing and we will all just be well...

Heck it ain't even Holidays yet!

Well just stand by and hopefully @baldand will get back to you shortly since unfortunately I cannot read the log file you sent.

Did you first set your destination point for your output?

Try pressing W to set your export destination...

Also check to see if it's not paused accidentally by pressing Y...

Results?

Is there a specific reason for any of the Adobe apps to NOT regconize the converted DNG's from the latest beta of MLVMysic?

I also tried importing the converted DNG's through Raw2Dng to see if it would solve the issues by applying the black/white levels but no luck yet so far...

Thanks!

Did you read two posts up from earlier up above?

Try deleting the .MRX files next to each clip you want to export.

I believe the bug in 1.4.2 is because I changed to using relative paths for the audio file, but didn't check all the cases where old absolute paths must be converted to relative