Messages

Hi Sebastien!

I really like your converter. It works great on my Mac.

I personally have two issues with it. I cannot change the temp-directory where all the conversions happen. My SSD is limited so i can only convert small .mlv-files. It would be cool so set the directory in the preferences.
It would be very cool to drag-and-drop .mlv-files from finder into the sources-list.

Greetings
Peter

Very nice!
Where did you get the music from?

OK, that's a big drawback :-(

The best solution would be to fix the mlv-bad-frame-issue. But i do not have a clue how to do that.

RAW doesn't support audio, right? Or is there a trick to get it working?

Hi Danne,

you are right! I just tried RAW (not MLV) with ALL hardware-intensive modules on (focus peaking, full-histo, full-zebras) and i did not get any bad frames within 5 minutes. That's awesome!!!

I personally don't care if i record RAW or MLV and i do not see any drawbacks of using RAW. Not having all the metadata in the DNGs doesn't matter for video.

Hi David,

do you think it's possible use a LUA-script to use focus-trap onlny when the shutter-button ist clicked and AF-assist when you press the AF-on-button. I described it in more detail here: http://www.magiclantern.fm/forum/index.php?topic=14914.msg145552#msg145552.

When deactivating all modules except MLV and Global Draw on, without peaking, without zebras, without histo i do get frameskipping.

I never tried RAW, just MLV.

Hey guys!

I documented 40 variations in which i tried nearly everything possible (different ML-builds, different 5D3-firmwares, differenct CF-cards, different 5D3-cameras, lot's of different ML- and Canon-settings). I came to a conclusion. On the 5D3 you always do get bad frames or frameskipping once in a while. Not so on the 5D2 - this model is free of that issue. The amount of bad frames can be influenced by the amount of hardware-intensive modules you use (focus peaking, zebras, histo).

The best solution for me is to use DIGIC-peaking and fast-zebras instead of focus-peaking, zebras and histogram. With these settings i do only get few bad frames (about 1 bad frame per 5 minutes).

It would be very cool if one of the devs could have a look at that. I do not think it's possible to get rid of these bad frames without coding.

Hmm, so you also do get bad frames. Could you try it again without pressing buttons in the ML menu.

If you too get bad frames that rules out a hardware issue with my equipment.

Hope your cat is getting better!

OK, i got skipped frames with your Canon-settings :-(
There must be a hardware issue...

I tried the mlv-option "Debug Trace". It might give ma a clue. Does anyone know where the log is being saved? I couldn't find it on the cards.

Thanx a lot DeafEyeJedi! Did you look at the footage after recording with MLRawViewer? Does it contain bad frames?
If this works fine with your Cam than it is either a hardware failure or my Canon settings. I am going to check them with yours now...

@DeafEyeJedi:
I copied all your files including settings, the FIR-File and all the modules to my SD-card. I noticed that you deactivated mlv-recording so i activated the following modules: mlv_rev, mlv_snd and mlv_play.
I then started recording and it looked good. I made a 6 minute test-video.

After that i activated focus peaking --> bad frames

In one other test i restored ML-defaults but after activating all necessary modules (mlv, full-raw-histo, raw-zebras, level) i got bad frames again :-(

@Markus:
Here are my Canon settings:
M-Mode, 1/50s, WB shade, normally sJPEG S3 (but also tried RAW; didn't make a difference), all NR-settings off, Hightlight-Prio off, Adobe RGB, no HDR-mode, Expo simulation on in LV-settings, some custom controls
I tried different lenses and different CF-cards. Even with a different 5D3 on firmware 1.2.3 (couldn't downgrade it to 1.1.3).
For me right now i have no clue how anybody could get good video from 5D3-ML. With my good old 5D2 i never had issues like that.

My best guess is that it's cpu-overload that leads to these issues cause the amount of bad frames seems to correlate with the amount of cpu-intensive modules i use (histo, peaking, zebras).
Can anyone try exactly my settings by copying the settings-folder provided in this post on a 5D3 with 1.1.3: http://www.magiclantern.fm/forum/index.php?topic=5473.msg150697#msg150697

Well i also tried you config and activating RGB-Zebras and Full Histogram and without peaking i do get bad frames about every three minutes. It's not a focus peaking issue. Propably it always happens when cpu-load is getting high.

OK, starting from your settings and activating focus peaking i do get the same bad frames again :-(

Btw. it is interesting that zebras are active cause in you settings you selected "only in Photo mode". But it still works during recording.
And you always have the "NOT RECORDING" sign in red and the strikethrough rectangle even though it is recording. Strange.

It WORKED with your settings!!! No bad frames for 6 minutes. Well now i have to find out which setting it is...

First, let me thank you guys for your support! I appreciate your effort!

@Markus:
My bad frames look like this: http://www.magiclantern.fm/forum/index.php?topic=5473.msg150360#msg150360
For testing i borrowed a Lexar 800x. Couldn't get any faster card. With this card i have to lower the resolution drastically. I tried to record four times for about five minutes and two out of them had frame skipping even though the writing speed wasn't the issue. I never had bad frames in this four tests. In my analysis i cluster the bad frame issue and frame skipping together. If any of these do happen it's bad.

@DeafEyeJedi:
Thanx for the settings. Are you sure the file is still online? I do get the following error "The folder you are trying to access does not exist"

I am trying one last thing:
The setting-files from DeafEyeJedi. If i still get bad frames it must be a hardware issue. First i send back my Lexar and try again with a new copy. If i then still get bad frames i have to send my 5D3 to repair.

Even with your settings i do get bad frames :-(

Did you use zebrad, raw-histrogram and focus peaking? Can you send me your ML-settings-folder? Than i copy everything on my card and all the settings are the same and i try again.

Thanx for your screenshot. I am going to test these settings in a minute. Especially with fps-override set.

Well i normally didn't use frame skipping. But i lost some videos cause i didn't recognize that the card stoped recording. Nevermind. I also tried with frame skipping off.
Same with black levels. I normally didn't use it but at the moment i tried all different settings to find what is causing the bad frames.

Yes i do save on the CF card. The SD is far too slow for 1920x1080.

@DeafEyeJedi:
The screenshots should show the whole MLV-setup.
Here is a link to my ML-Settings-folder:
https://www.dropbox.com/sh/cis7y9lpp88cy2q/AADG2PuhH2gtOoIdJjqKBmRha?dl=0

Which resolution did you choose?

@Markus:
Well mlv-recording stops quite often cause of skipped frames. I know it shouldn't cause the card is fast enough but it just does. I also tried different cards. Didn't help.
I tried ALL possible permutations of settings in the mlv-menu. This is one example. None ever worked.
And the stupid thing is i also do get bad frames on different 5D3-bodies. That's why i don't understand how anybody could get it working at all.

@DeafEyeJedi
Can you try to dial in my MLV-settings provided in the last post into your 5D3 unsing the latest nightly and see if you get bad frames?

I am kind of stuck here. I already put so many hours in resolving the bad frame issue and to me it looks like MLV is not working properly on the 5D3 at the moment. I never had issues like that on the 5D2.

Just awesome!

Here are the MLV-settings i used on the 2015-07-02-nightly:

Well to check the CF-card i copied the same 20GB file to the card via my mac four times and checked the md5checksum. They all have the same checksum so writing and reading from the card is fine.

Code Select Expand

pete:@Bot~: cd /Volumes/EOS_DIGITAL/DCIM/100EOS5D
pete:@Bot/Volumes/EOS_DIGITAL/DCIM/100EOS5D: md5 M02-1826.MLV
MD5 (M02-1826.MLV) = c6847ad57c2099c24354b3183bb6a531
pete:@Bot/Volumes/EOS_DIGITAL/DCIM/100EOS5D: md5 M02-1826\ copy.MLV
MD5 (M02-1826 copy.MLV) = c6847ad57c2099c24354b3183bb6a531
pete:@Bot/Volumes/EOS_DIGITAL/DCIM/100EOS5D: md5 M02-1826\ copy2.MLV
MD5 (M02-1826 copy2.MLV) = c6847ad57c2099c24354b3183bb6a531
pete:@Bot/Volumes/EOS_DIGITAL/DCIM/100EOS5D: md5 M02-1826\ copy3.MLV
MD5 (M02-1826 copy3.MLV) = c6847ad57c2099c24354b3183bb6a531

So it now looks like ML is writing bad frames to the card.

Here is a benchmark of my card i did some months ago:


Well, i more and more think that this is a hardware issue. Is there anyone out there who can check if he gets pink frames using 5D3v1.1.3?

I borrowed a second 5D3 for testing. The stupid thing is that this has v1.2.3 on it and i cannot downgrade to v1.1.3 cause than all settings are gone. So i downloaded the latest ML-nightly for v1.2.3, which is from April. I used the same SD and CF-card as with my own 5D3 and i got simmilar results --> frameskipping once in a while and bad frames. So either the ML-nightly from April for v1.2.3 and all the nightlies from April till today for the v1.1.3 are bricked or my CF-card is bad.

I am going to check my card now...

Hi DeafEyeJedi,

thanx for the hint. I just managed to install ML on the SD and formated the CF to exFAT. Same result, bad frames :-(