Messages

As far as I know, the EOSM is still not supported in DSLR controller or Dashboard. I don't think the code has been cracked yet. It's been showing in development on DSLR Controller for as long as I can remember.

Read up on .Lua scripts and how you can have them run automatically at start up. Danne has already developed some for this purpose as part of his custom builds on his Bitbucket.

How about a Offline Clone device ? Looks like it can backup/Clone CF Card as will as ssd & hard drives without a pc/mac , cheap too $35.00
now whether it just reads CF & SD cards , but from the product information it should clone /backup the CF card also .

Would be interesting to hear if anyone has tried one of these. It would be great if it had the functionality to incrementally back up rather than clone.

Care to share what features of ML were used in this video?

Agreed! Very well done, thanks for sharing.

Great - very enjoyable!
What aspects of ML did you use for that shoot?

Thanks Danne,

I am testing and mainly just confused with the finer details as I am getting differing results. Totally understand HDR is for h.264 and Dual ISO is for RAW video.

Maybe i'll try and change my main question.

Is the purpose of HDR_MOV script in MLVApp designed for raw video shot with DualISO enabled? I guess i am confused because HDR is supposed to only be used with h.264 - therefore not needing to be processed via MLVApp. What does the HDR_MOV script do in MLVApp?

Hi Danne,

Just some clarification.

With switch and MLV App methods of processing both HDR (h.264) and MLV (RAW) do we still need to effectively double the framerate whilst recording?

In regards to MLVApp specifically, to process Dual-ISO. Do we need to check all the relevant boxes in the settings box ie. dual-iso, vertical lines etc. And then check the HDR-MOV_script before export? Is that the correct process? I couldn't find any explanations or documentation for MLVApp regarding Dual ISO processing requirements.

Any gimbal or steadycam usage for the movement shots? Or did you manage all handheld? Really well done by the way!

Thanks for the logic check. And that idea sounds really cool!

Thank you for the explanation @A1ex.

Would there technically be any output difference in shooting FRSP FullResLV  (.MLV output) with intervalometer set to 4 seconds VERSUS recording RAW Video FullResLV with FPSOverride set to 0.25?

On paper it should yield the same results. Is my logic right?

I was also pondering on this, as I have tried to search for an explanation before and couldn't come up with anything that would fully explain it. Would love to know. And how this also relates to FRSP with the Full Res and Full Res LV differences.

Awesome work and happy birthday! Many Happy returns to come I hope 

Good job. Love the PM style transitions.

Very, very cool!

Either that or the Unique Camera Model tag is incorrect or missing in your files. Checking the dng files that is not the case so you´re acr profiles need to be profiled also for the eosm. Solution. Ask the creators of the dcp profiles for further profiling.

Thanks Danne, this makes more sense now. Appreciate your help!

I'm wondering if anyone else has this issue, or if someone can test it for me on the EOSM (2.0.2). Or point me to a thread - i've searched, but unable to come up with anything.

Taking FRSP in both dng and mlv format - I am unable to choose a custom dcp in ACR when post-processing. All the standard ones are available to select (ie. all adobe profiles, camera matching, artistic, Legacy, B&W etc.) however the one's I have added myself like BMDFilm, ML-Log and VisionLOG do not come up. Have tried with latest nightly and latest croprec experimental builds and both give the same result.

I know the profiles are loaded and normally working in ACR because they work with dng's from my 5D3.

Here are the files I am having trouble with.
https://www.dropbox.com/s/6qf41mp47lzr124/EOSM%20DNG%20files.zip?dl=0

Tested today. Works very well.
Are we able to have a play preview anytime soon?
Any chance to label the anamorphic de-squeeze options? Or provide a matrix of what each of them do and what they are suited to?
What is the intention of this app moving forward? Will it be paid or be free forever?

@AF-OFF

your findings are the same as what I get. Seems to default to 1.67 stretch in MLVAPP too.

Thx for the clips. I found the problem very fast: the problem is that these files are <1.0fps. MLVApp was not made for clips with so low fps ... at least I forgot that it might be possible
I made a quickfix - that means: if the clip is <1fps, I set it to 1 fps. Otherwise it is very hard to show a correct timecode... (timecode was the crashing module). So you can compile the latest revision using Dannes compiler tool, or you wait for next release.

Thanks MASC - legend!

Anyone else having issues with Full-res LV files from 5D3 113 (latest experimental crop build) crashing MLVApp when loading an .mlv file? I've tried both FRSP with intervalometer (output as .mlv) and RAW 14bit lossless with FPS override set at different rates from 7 down to 0.150. As soon as I select the the .mlv it crashes MLVApp.  Tried on latest (OSX) version and with the previous version giving same result. The files work as desired on MLRAWViewer, so they don't seem to be corrupt. I can't seem to find any other mentions of this in the thread, please forgive me if this is a known issue. Not sure if it has anything to do with being 5796x3870 resolution.

Here are the files, there is a FRSP (300MB) version, the RAW Version (1GB +) and the OSX crash log.

https://www.dropbox.com/s/zzd8x93zhs089ck/FRSP.MLV?dl=0
https://www.dropbox.com/s/38ylyldopa0qx9y/M15-1511.MLV?dl=0
https://www.dropbox.com/s/g8s6krnyzhbs15s/crash%20log.rtf?dl=0

Some shots have the sky blown out as I forgot my ND filter.

To get full sensor recording of 1736x1120 on EOSM, you need to have the aspect ratio set to 1:2 in Danne's current 2018Jul03.EOSM202_mv1080p build. Ensure that crop mode is set to 3x3_mv1080_EOSM

All other crop modes and other features are not working (in this build) as he has already advised.

@ArcziPL as far as i can remember (and I could be wrong) I've never been able to enter 5xCrop or 10xCrop mode having AF turned on in the Canon Menu. As soon as I turn it off, the option for zoom comes up.

Thanks bouncyball. Further research tells me it is BMD film colorspsce and gamma.

it is intended to preserve original MLV raw data as is without changes.

I was also wondering if this was the case. Any idea of my previous question, which is a similar situation?ie. Applying the raw processing just without the curve during export to ProRes or other video codec?

Thanks for the update! LUT support is a game changer 
Is there anyway to bypass adding a curve at all? Ie. to be able use a LUT designed for straight out of camera raw as in Hunters LUT or EOSHD 5D3 LUT? These were primarily designed for use in resolve directly on the CDNGs. It would be awesome to be able to apply these within MlvApp without having any curve applied prior and going straight to ProRes export. Is this a possibility?