Messages

Not all MLV files show that error. It was an EOS-M with the 9/11 nightly build and now I've just updated to the latest firmware from last night.  Currently on the 9/27 build for both 5D3 & EOS-M. My only assumption for this issue to arise would be because the MLV files are directly from EOS-M that may not yet be integrated in with MLVFS if I'm not wrong but could that be causing the error?? I'll shoot some more quick DUAL ISO in my room at night just to see how much it can pick up without getting much noise for the heck of it! (it's 8:30pm in here my time)

but the funny thing is that the first time I used MLFVS with MLV files from EOS-M turned out just fine I thought? If you could tell from the 2nd video in this post from earlier. Maybe I ruined it from dragging out from my external drive into my macbook's SSD just to get quicker rendering??? Although I placed them back into the original location and all still seem work as normal.

Also I thought of another possibility to may have cause this issue would be because I used MLFVS with a folder that contained the DNG's which are saved in an external HD connected via firewire 800 to my macbook. Does the process from MLVFS require the folder/files to be performed directly on the system's drive as opposed to an external drive?

Maybe I'm just crazy...

Gotcha now that makes sense. Let me know if there's anything that I can do to help contribute in efforts to make your software more effective?

Perhaps would you like for me to choose the WB settings manually in MLVFS if possible?

Thanks again!

Thanks for the inputs @ayshih and unfortunately there's no windows in here, I was hoping there would be a mac version of this because I did run into this link from @chmee awhile ago (great idea but I don't have windows nor Wine BUT I have VMware Fusion installed -- although it runs awfully slow on this old macbook pro of mine) so hopefully I'll take my time today to research online for a way to make this possible on a MAC...

Good thing I am off work today.

@Danne -- was the 'tint' being off the chart due to conversion being done with different programs or due to using a color profile in EOS-M (which was Technicolor CineStyle and I've never really had any issue with it) or could it be affected after adjusting the black/white levels in Terminal?

@dmilligan -- how could WB be wrong if we shoot it in RAW? Unless you're referring a different WB issue that I don't know about?

Sure I am currently uploading the original MLV file but not sure how to cut it into 20mb or so? Ive tried copying and paste and wait until it reaches 20-30mb and cancel it -- it won't save parts of it and the original size is about 930 mb which would be too big for you, correct?

any suggestions on how to gets part of the MLV file without compressing it? Otherwise I can just post a link from the original MLV file...

Perhaps you can cancel the download once you get to about 20-30mb (or would that not work?  )

https://dl.dropboxusercontent.com/u/24998329/Dual%20ISO/M20-1628.MLV

Thanks for the inputs @mjneubrander but I think I'll just stick with the MLVFS along with the 20-bit cr2hdr plug-in. Much quicker I think? Also I'm more of a Mac Guru but thanks though!

@Danne -- Thanks again for your responds. Yes I did try to export it through MLRawViewer (which did not produce the pinkish effect) and sure here are the links to each DNG (all the same file) from all four different exports...

MLVFS: https://dl.dropboxusercontent.com/u/24998329/Dual%20ISO/MLVFS_DNG/M20-1628_000000.dng

MLRawViewer (w/ AmAze enabled): https://dl.dropboxusercontent.com/u/24998329/Dual%20ISO/MLVRAWVIEWER_AMAZEon/M20-1628_000000.DNG

MLRawViwer (straight): https://dl.dropboxusercontent.com/u/24998329/Dual%20ISO/MLVRAWVIEWER_DNG/M20-1628_000000.DNG

RAWMagic: https://dl.dropboxusercontent.com/u/24998329/Dual%20ISO/RAWMAGIC_DNG/M20-1628_C0000_00000.dng

According to my eyes... It seems that MLRawViewer is producing really bad aliasing for some reason and not with either MLFVS nor RAWMagic. Thoughts? (Although I love the idea of being able to add LUT's along with 3D LUT's combined as well prior to exporting as DNG's from MLRawViewer -- I wouldn't want to export as a .MOV because of the 10-bit limitation unless the producers want the footage right off the bat!)

@dmilligan -- I just did an update right now with your latest MLVFS from your bitbucket site. Still comes up Pink. I think I may have somehow corrupted the RAW file itself?

So what can I do to prevent this from happening again?

The pinkish occurs before I even go into LR5 so I wouldn't say it is an issue with LR5 nor MLVFS because I did try to copy the files out of MLVFS folder into another folder on my desktop and yet it did still produce the exact same pinkish effect.



Is this normal for this to occur even after converting more than once on a single DUAL-ISO RAW file?

Very well said @epicphate. Baby steps are usually the best ways to learn and actually enjoy doing what you do. Good job on the video, brother!

  Although this worked fine just the other day after following Danne's suggestions and here I am about to give up on with this particular RAW file and probably going to end up shooting another DUAL-ISO test some time tomorrow. perhaps outside of my work area or nearby the beach.

This is what I am dealing with so far...




Anyone notice anything odd or familiar from this kind of behavior? I wonder if it's an MLVFS issue... PROBABLY NOT!

Shame on me...

so I started the whole process again with the original RAW file -- my question now is... is it possible for the RAW files to become useless after being used with MLVFS? Because after the MLVFS conversion which produced all of the DNG's into a strange pinkish look in every frame. I was hoping that it would go away once I use LR5 to export the DNG's with cr2hd2 20-bit plugin but I keep getting the pop up window with nothing stated that the DNG's have been converted. Nothing happens!

So does that mean the RAW file is somehow useless or am I missing something?

These hot/dead pixels basically show up whenever my lens is facing the sun and somehow it goes away (kind of) when it doesn't have the flare coming in...



and you're right it won't let me export as DNG's... nor as .MOV either.

So should I start with the Original RAW DNG's through with MLRawViewer and export them as DNG's prior to doing the MLVFS?

or afterwards?

ugh sorry for all the questions but I would like to get the proper workflow done first before I go ahead and shoot some 2.5k DUAL ISO videos... 

Speaking of MLRawViewer... I'm currently exporting the converted DNG's them as DNG's (not Quicktime .MOV) with the Quality enabled as well as the Status of Stripes correction.



Let me know if this is the correct set up?

@Danne -- good enough for you to know (obviously this has happened to you before) in which I find it odd and after going through the commands again it just somehow made it readable to both ACR & LR5. So strange but thanks again.

So for this workflow I used the same original RAW file from the first video in this post.

Workflow as it follows:

MLVFS>Adjusted the Black levels in Terminal commands (Thanks Danne!)>LR5 (color grade) & then export as 16-bit TIFF's> Open as Image Sequence in QT7 to export as Quicktime 422 HQ.

Ideally I would rather use Davinci Resolve for the shorter and easier workflow but my old 2006 Macbook Pro (even with the new upgrade memory ram and SSD drive) and yet it's not able to playback smoothly. *grunts*

Here's Take 3-
http://vimeo.com/107067504

***Even after getting the Blacks level adjusted somehow made the HOT/DEAD pink/green pixels slightly more visible (which is a known issue for EOS-M owners and I am aware of the fix can be made with RawTheraPee -- but I'm currently still searching on the net for a way how to apply the fix for all files rather than doing them one by one. Perhaps anyone know a shortcut key regarding the software to make that possible?

Just got home. Terminal went well -- Thanks again Danne and now I am facing this pop up window again after attempting to export DNG's into ACR (same applies for LR5) and Last time it was due to MLVMystic but this isn't the case.

Any thoughts?

@Danne -- Thanks for the follow up regarding these instructional videos. I could swear I followed these instructions precisely and yet I'm still getting these odd errors.

Will definitely try them again as soon as I get home from work. Thanks again for your kind support as always! 

Now that's even more embarrassing. Yes, again you are right. However, per Danne's suggestion that I tried to use the command in terminal to set the black levels... This is the errors that I am getting in Terminal. Thoughts?

@a1ex - That's right I read that somewhere in the forums recently, unfortunately I went ahead and shot this video in RAW without the Post Deflicker enabled. So I don't have the sidecar file (XMP) to use in post. My fault on that!

Will shoot another test with a new RAW/MLV file in order to add the XMP file to match the black levels.

Unless it is possible for me to adjust the black levels solely in ACR and perhaps just sync them up? Thoughts?

Take two...

http://vimeo.com/106903984

cr2hdr: a post processing tool for Dual ISO images

Last update: 0eabcb0 on 2014-08-29 12:42:54 UTC by a1ex:
cr2hdr exposure matching: when all else fails, brute force prevails...

Active options:
--amaze-edge    : use a temporary demosaic step (AMaZE) followed by edge-directed interpolation (default)
--cs2x2         : apply 2x2 chroma smoothing in noisy and aliased areas (default)
--wb=graymax    : set AsShotNeutral by maximizing the number of gray pixels (default)

Input file      : /Volumes/LaCie/EOS-M first TEST/M20-1628_C0000/M20-1628_C0000_00348.dng
Camera          : Canon EOS M
Camera model    : Canon EOS M
Full size       : 1344 x 538
Active area     : 1344 x 538
Black borders   : N/A
ISO pattern     : BddB RGGB
White levels    : 14045 14882
Noise levels    : 8.00 8.00 8.00 8.00 (14-bit)
ISO difference  : 4.06 EV (1663)
Black delta     : 21.37
Dynamic range   : 10.55 (+) 10.65 => 14.70 EV (in theory)
Looking for hot/cold pixels...
Hot pixels      : 502
Cold pixels     : 129
AMaZE interpolation ...
Amaze took 0.22 s
Edge-directed interpolation...
Semi-overexposed: 37.09%
Deep shadows    : 35.24%
Horizontal stripe fix...
Full-res reconstruction...
ISO overlap     : 3.5 EV (approx)
Half-res blending...
Chroma smoothing...
Building alias map...
Filtering alias map...
Smoothing alias map...
Final blending...
Noise level     : 8.00 (20-bit), ideally 8.00
Dynamic range   : 16.55 EV (cooked)
AsShotNeutral   : 0.51 1 0.62, 5107K/g=1.04 (gray max)

Excellent Video @Danne and I will definitely need to upgrade my LR5 plugin because I do not have the extra features that cr2hdr 20-bit gives you... THANKS for the wake up call that I absolutely need. 

@A1ex -- thanks for referring NOT to use MLVmystic as I've just noticed that it is technically out of date and won't be maintained! My fault on that...

@Danne -- I do have the Cr2hdr plugin to use in LR5 but maybe I keep telling myself that I'm not quite sure if it compresses after the converts? I'll check and see if the plug in is up to date since I installed it sometime late last year after the holidays? It may need to be updated and I'll give it another test with the same exact RAW file that was used in this video.

I'll see if I can get this to work again while at work today. Thanks all for your feedbacks!

I shot in RAW resolution 1344x538, 1/50, 24p (FPS Override set to 24.000) w 22mm STM, Dual ISO (100/1600) and closed the iris down to f12 for ETTR effect.

Workflow:
originally I convert the RAW files with MLVMytic (Beta 0.5) with the Dual-ISO settings on. Worked well but couldn't figure out why ACR couldn't read the DNG files from the MLVMystic (Beta 0.5) version? (probably because they are technically CinemaDNG which should work fine with DaVinci Resolve but my old macbook pro doesn't hold up with the real time playback very well.

So I went back to the good old fashion way of exporting the CDNG through Adobe LightRoom5 to fine-tune & color grade them and then export as TIFF files.

THEN Open IMAGE SEQUENCE in Quicktime 7 and exported as quicktime format in 1920x720 422 HQ.. (I'm starting to think I could have not stretched it out as much) but oh well its just a test!

p.s. I tried to use RAWTHERAPEE to try and get rid of the hot/dead pixels that the EOS-M usually produces... SO FRUSTRATING! I can only open one file at a time to get the effect to work and Im not sure how to batch them all together to make it quicker. Probably will get this task done on the next test!

I am still seeing a bunch of aliasing going on... 

http://vimeo.com/106783237

as far as I know... I noticed the audio meters are working actively. You just have to remember to turn off MLV audio after you are done recording in either RAW or MLV otherwise once you record it in h.264 without disabling the MLV Audio first...You won't get any audio as it has been mentioned in this forums as well!

It's a bit tricky but there are ways to work around it...

as long as you enjoy troubleshooting like 90% of us users are?

SJ

Just got the EOS-M and as soon as I got home... ML was installed. All went well and so far I'm loving all the features regardless of its minimal flaws!

Love the two-finger tap to get into the ML menu...

I'll be on the lookout for updates.

*cheers*

@swinxx... White balance? Probably I should have but again I was just going through each LUT to get the look of it. Each LUT can create the warm look just like how it does with film. But Thanks for the follow up.

@budafilms... share my logs? you mean LUT's?

Just having fun testing out the LUT's...

Special Thanks to Baldand, A1ex & eVeryone else on board!