Messages

I'm having trouble using mlv_dump to decode the compression. Any help appreciated. (sorry, I know this is a development forum. what I am I doing here if I can't use Terminal properly?)

37 minutes at 3072 x 1286?! Wow. How many GB was the whole clip?

@reddeercity, Yes. Maybe it is the audio. But don't be misled by the crunchy audio distortion on the clip, because coincidentally I had my cheap-o "b" mic on while I shot b-roll and learned from this shoot day that it needs immediate replacing.

Here's a link to the .mov file that causes Premiere Pro errors:
https://www.dropbox.com/s/2akg6wp7t58zchj/M07-1402.mov?dl=0
And here's a link to the .MLV file:
https://www.dropbox.com/s/1s0too2lzwemmtt/M07-1402.MLV?dl=0

I was able to do more testing. The footage was shot with a 5Diii using a recent nightly build. Using most recent: OS X and Premiere Pro CC versions running on a 2013 Mac Pro with dual D500 video cards.

I cleared caches, deleted preferences this afternoon. Also ran disk repair. I'm not going to have time to delete my Adobe CC from my system and re-install.

It's not every clip is causing the error. I took one of the MLV clips that was causing the error, imported the DNGs into Resolve and exported it. I had no problem with it in Premiere.

Just now, I re-exported the clip with the latest build of Footage. I exported 4444 and 422. The 4444 clip gives me the same error. The 422 clip does not.

I was able to export the timeline that had the error prone clips. It plays fine. It also re-imports into Premiere and plays in a timeline without error.

I'm getting an error in Premiere Pro CC (2017) when I use ProRes 444 footage exported from Footage. It's playing back and looks fine but I keep getting this error:
https://www.dropbox.com/s/zfga7wc3875bbo8/Screenshot%202017-03-14%2020.23.37.png?dl=0

Great work so far!  The fact that I can just add the MLVs directly is such a relief. And the inclusion of the WAV audio on export! It's very early, but this feels how an intuitive Mac app should work. I have a lot of gripes about Premiere and Resolve's clumsy and space wasting interfaces. Lots of great suggestions so far for improvement.

I'm already using it to process b-roll from a shoot last week. An outdoor shot with a blown out background was easy to correct. Looks good enough to be the final look. I worked in Adobe RGB. Another shot indoors was a bit trickier. I tried to work with SLOG 2. Seemed most appropriate. I thought it was going to go well, but I hit a wall. I couldn't manipulate the tone how I'd like. I tried again and again. I went back to Adobe RGB and it went a bit better but I couldn't get the tones in her hair to my liking.

I have a suggestion of referencing Lightroom's Tone Curve section.
https://www.dropbox.com/s/d6kqcxopwog1uh8/Screenshot%202017-03-12%2021.55.32.png?dl=0
Besides how well it handles the each of four sliders, I love how it has the three sliders under the curve chart that lets you dial exactly where you want the four slider controls to work. I work a lot in Premiere, Resolve and Lightroom. I am always most comfortable with Lightroom's controls. Of course they have things that the others can't. Resolve is super powerful, but not what I need for my commercial work.

Question... if I wanted to export an ultra neutral ProRes 444 file from Footage, what do folks suggest we set things to? These files would be corrected later with Premiere's Lumestri panel.

Keep up the good work.

Would love to try it out. Will it work directly with MLV files or does it need converting first?

Thanks for sharing what you're working on.

Shooting RAW obviously takes up a lot of space. Shooting standard video does not. I often switch back and forth from RAW to standard video as I switch from shooting b-roll to interviews. It'd be great if it were possible to specify where standard video and RAW video gets recorded to. It would be very beneficial to be able to specify that RAW records to the CF card and that standard video records to the SD card.

@DeafEyeJedi --- you rock. thanks.

Hey all. I've installed FUSE and MLVFS. I see the command file is in the Services folder, but MLVFS doesn't show up as a service when I right click on MLV files. No services show up. I tried re-installing. No help. Any suggestions?

With a faster the shutter speed you capture less of the motion. The result is less motion blur. During playback it might not be too noticeable. It depends on the action in the shot. If there are quick motions of subjects and you are shooting at 1/240 or faster it could give you a jittery look. Even at 1/120 it can sometimes change the feel. Some filmmakers use a faster shutter for specific effect, but the reason 1/48 or 1/60 has become the norm is because of the natural feeling the motion has to the eye. There are no rules, but just be aware of the effect it gives in the context of what you're trying to achieve.

It's not perfect and I'm always wanting improvements too, but I use the April software with 1.2.3 so I can use an external monitor (focusing without it is to hard) and rarely have an issue.

I assume the lack up updates is because they are working on some big new things, which may or may not have anything to do with the 5Diii.

New 5D3 firmware on June 9th. Change log seems to be blank. Anyone who about this release?

I don't have a cropping issue with my Ikan 7" monitor and 1.2.3 firmware. Without it, I'm hopeless trying to get sharp focus with a 5D.

I shoot with 64GB cards. When I shoot long take scripted, we can shoot an 11 minute long take in RAW at 1080/24. But if I'm shooting interviews, I shoot h264.

Not sure if there are issues shooting 20-22 minute 1080/24 clips with 128GB cards. There aren't any I know of.

Maybe if you shoot 720p you could shoot up to 30 minute RAW clips.

I'm not having any technical issues that are serious or cumbersome. Just the regular dreams for even more features, options and refinements from the incredible Magic Lantern team!

Regarding firmware 1.23 and clean HDMI out...

I shot a short last summer with 1.13 and lower res HDMI. It was challenging at times to focus. I shot most of it with a Canon 135mm and a Sigma 35mm Art. With the 1.13, at least, it was easier to recognize focus with the 135 because the fall off and bokah are very noticeable. With the 35 lens the lens softer so gradually, it could be hard to figure out when I had tack sharp focus.

After that short I upgraded to 1.23 and the focusing is way way easier. Still not always easy, but way better. The firmware has been very stable, too.


Us 5D filmmakers are relying on a beautiful challenging camera. A DP friend of mine, who shoots big TV shows, never uses a 5D cause the sensor makes focus a pain. When they throw a DSLR into the mix with the Alexa, they'd opt for a 7D. And nowadays he opts for the GH4.

If you uprez straight from the RAW data, there is actually 4 pixels for every 1 debayered pixel. Is it possible that there are algorithms that can get a sharper more accurate uprez because of that?

Push the AF Drive button and select "One shot"....maybe your camera is in AI Servo mode...

Nope. It's set to "One Shot" and the lens is set to manual focus.

Also, I have noticed that the beeps are said to be disabled in ML when MLV Sound is turned on "to prevent interference with audio recording." For me the beeps don't happen regardless of whether or not I have MLV Sound on. I don't even need a start beep (or a beep when I stop the recording), but hearing a beep to alert you when the camera stops the recording do to an error would be very helpful. 

I've been unable to turn on beeps at the start and stop of recording. I recall hearing beeps in the past. Anyone know how to turn them on? Or if it's even possible? I can play the test tones in the ML Audio settings, but they don't turn up anywhere else. I'm using a Nightly Build from August 7th on a 5Diii with the later 1.2.3 firmware.

The reason it's suddenly become a concern is that recently (yesterday) I stepped up to 1.2.3 with an external monitor hooked up and HDMI mirroring on. It's been a miracle for my being able to get good focus. I wish I had some basic overlays on the external monitor but I having them all over on the Canon screen works fine when you get used to it. One issue is that you really concentrate your eyes on external monitor while you're shooting. If the camera stops recording and there's no beep, you really might not notice. Don't want to keep a nine minute scene going if a camera blip stops recording a minute into the take.

Is this an issue for others or just something I'm doing? Searched around and can't find anyone with the same issue.

Just because the f-stop stays the same through the focal lengths might not mean that the amount of light transmitted (the t-stop)is the same.

the tmp files are preallocation files. leave them.

Always? Or until you copy all your mlv files off the card?

MORE INFO: I can take pictures. None of the Canon menu buttons work (okay, revised, the set button doesn't work but i can select menu items by pushing on the mini joystick above it. i tried reinstalling the firmware and i got the same fonts.dat retry problem). The record video button doesn't do anything.


UPDATE: I somehow was able to get it running with the Alpha 5d3 software. Then I reverted to the Canon 1.1.3 and carefully went through all the steps to get back to the nightly builds. After the last step of updating the firmware with the boot flag, the same problem happened: "fonts.dat retry". but this time even though it said that, it's working okay!! wow. harrowing 24 hours!

Found myself in a pickle today. I made the mistake of renaming my SD card today. After that Magic Lantern wouldn't load. The firmware was reverted back to Canon. I tried many things. Finally went through the whole procedure: I reformatted the SD card in the camera, i copied the latest build and the boot flag for the 5d3. I updated the firmware, but the update was interrupted by the message: "retry data/fonts.dat". I tried a few times. No luck. Well. After trying a few things, I noticed the firmware is listed as the "1.1.3-ml-v2.3.nex". But it still acts funky on boot, tells me to load ALL the ML files, says "data/fonts.dat retry", and doesn't load ML. I've looked in the ML/DATA folder. There is no fonts.dat file. I checked old builds. Nothing, no fonts.dat file. I looked in a year old build folder that I had and there is a fonts.dat file in the DATA folder. So I went for it. I copied it over. Bingo, it says "enablebootdisk, ". But ML still doesn't load. I restart it. Same thing. I can't even select "firmware ver" from the Canon menu. Hope I haven't destroyed my 5D (already had enough bad luck lately with lenses getting stolen).  Any help or guidelines?

I've been playing with FCP 7 and AfterEffects CC to get vertical only image stabilization but I've had no luck. Anyone else been thinking this makes sense for handheld footage shot at 1920x1152? 72 extra lines of resolution should be more than enough for a final 1080 image. The solutions I've been finding in FCP and AE stabilize both the vertical and horizontal and do scaling. I'd like to just stabilize vertically to get a little of the jitter out of it. Been searching internet and here and haven't found any solutions.