Messages

Definitely interesting facts regarding your graph -- Thanks for sharing @QuickHitRecord!

Looking forward to your new LUTS soon hopefully @Andy600 

SmartScript2 has been treating me very well lately... Thanks @SteveScout -- However, now I am curious what would be the best solution to get audio synced up properly for 50/60fps MLV files? It's literally almost half the size (although Audio sounds normal but it may be in 24/25fps length as oppose to the length of a 50/60) because stretching out the Audio file in the timeline doesn't help.

Thoughts?

This is quite interesting... Definitely will be following this thread from here on out...

Thanks for sharing @kihlbahkt!

This is purely a genius type of an idea...

This definitely would be a nice addition as well...

Thanks & I noticed that as well -- Hopefully there'll be a fix for the 50/60fps Audio issue sometime soon...

Probably related to ML coding & hopefully a1ex or g3gg0 will implement a quick update!

Actually after watching the test clip several times and noticed it was slightly under exposed. Went into ACR via AE and noticed I didn't have the ToneCurve shadow slider all the way up to +100 (it was at +83) when the Highlight was still at +100.

My fault on that guys...

Here's the correct take...

MLV > cr2hdr-r > AE > ProRes 4444

So it is in fact okay if I upgrade to Yosemite and still be able to use MLVFS, MLRawViewer, Smartscript2 in AE and PP without any hiccups -- correct?

I'm just anxious to know because I don't want to be stuck with an upgrade that doesn't really do me any good...

Thanks again @dmilligan!

Thanks @dmilligan for the quick follow up on the update -- will check as soon as I get home from work.

Good call @dubzeebass!

*feedbacks*

I just ran the latest MLFVS w a Dual-ISO MLV file and seems to look better with the thumbnails looking cleaner than ever! Great job on that @dmilligan -- however I ran into this odd pop up window after trying to export through with smartscript2 in AE...





same AE error-code as @danne posted from earlier BUT this MLV file was produced directly from an EOS-M body...

thoughts?

Any luck w your situation yet @rick_ford55?

Hmmm... Is this even worth to try and test it out on the 5D3 1.2.3?

Without frying up our sensors?

Pretty tempting I would say..

It's a known issue for EOS-M (I own one) and this usually occurs during RAW/MLV shooting -- I've learned to try avoid sunlight (flares) since they usually bring them out more which is not what we want.

There are a few ways to correct them in post but they aren't my favorite things to do... You could try using ACR or use CS (Chroma Smoothing) with @dmilligan's MLVFS or @baldand's MLRawViewer apps which may help some but not completely as far as I'm concerned or perhaps check out RawTheraPee which is a open source app that can handle pink dots as well.

Heck even I am still trying to find the best workflow to work around this particular issue directly from EOS-M...

Did you first set your export destination in prior to? Try pressing W to set your destination folder and then try exporting again.

Results?

I couldn't get 1.4.2 to render out anything on my 2010 MacBook last night, neither raw nor mlv to dng or mov. It seemed to work well on my 2012 27" iMac, though. I'll try to post the log after work and test some more.

Try deleting some .MDX files next to your RAW/MLV and try again.

Results?

Just watched the first clip and it also seems to have some problematic skies. I think were good.

Agreed.

What sliders did you mess with in acr?

I just touched the Tone Curve (Dark/Shadows @ +100).

Not quite sure. I duplicated the workflow in ACR (highlights/shadows) as previously done in earlier test. Only difference was the fact that I didn't use AE last time so could that play a factor in this so called flickering issue? (I thought it looked good until the sun starts causing the flares which makes it look a bit flickering so I wouldn't know which to blame it on?)

Perhaps I should open the DNG's in PS and export as Tiff's like how I did before and see if that would make the differences? I don't think it would...

This is one of the main reasons why I refused to update to Yosemite regardless how much of a tease their updates may seem.

Unless we're missing something here...

anyone else running on osx Yosemite with any issues or no?

MLV > cr2hdr-r > AE > ProRes 4444

Yes of course I know all of this wouldn't be possible if it weren't for a1ex, g3gg0 and everyone else including DEV's on board in the ML community. Thanks again!

It only makes me wonder how much faster could this be if I were to use a latest model of MBP's because my current 2006 15inch MPB is modified with 250gb SSD along with a mere 6gb of ram.

Stay strong...

LoL

Is Alex the only person here capable of making a .fir?  I mean, it's almost seemed like he's been oddly against even the idea of a 70D port from the beginning for some strange reason. Doesn't make sense, but his early comments seemed to give off that vibe.  I think he's also kind of drifted away from working on ML as a whole lately, like he was fed up with it or something.

Cut some slack for @a1ex -- obviously he has already done a whole lot for all of us (along with the help of others DEV's such as g3gg0 & everyone else on board) & please let him enjoy as life as much as we all do, respectfully so.

Time we only tell if the ML crew feels the need of a ML for 70D and I know it'll come sooner rather than later.

*cheers*

Is it technically possible to have Magic Zoom triggered by the half-shutter press as it was on the MKII?

This feature works well on the 7D and would definitely be a +1 if it were to be implemented in the nightly for 5D3 one of these days...

Dude... this app seems to be a bit quicker on the renderings. It pushes 40-45 dng's per second before the dual-iso gets converted (which does about 4 dng's every 5-6 seconds!)

Holy Smokes... 

Makes me want to shoot more Dual-ISO with ease on my mind!

Thanks, Danne!

SJ

p.s. +1 for the workflow service!!!

That the Number one reason why I only use After Effect with ACR and not Resolve, never seen good skin tones for resolve yet from ML Cdng's.
You need to per-grade the file first .

I was actually suspecting similar effects and thanks for confirming @reddeercity -- another reason why I can't stop myself from using ACR within AE.

@kaco -- how would you disable this warning in AE?

I'm asking because it works fine with certain converters and sometimes w few others which shows missing frames error pop up window but I know I'm not missing a frame. Annoying at times!