Messages

For those of you unsure about trying the 5D mk3 in the meantime...

I used to be obsessive about resolution and pixels...always wanting to know the next best piece of kit out there with the highest resolution. Then I entered a film festival and watched, on a 20 foot screen, 1st place go to a piece shot on miniDV, beating out RED cameras.

Obviously one size does not fit all but frankly the color depth and quality of the RAW footage delivered by ML on the 5dmk3 is nothing short of stunning. I have been shooting on it for large jobs for more than a few years now. A lot of my jobs involve shooting the motion portion of a photographic campaign and having RAW sequences allows me to match the results of the photographer and retoucher. It rivals even Alexa footage and scales up to 4K beautifully. If you are on the fence, just go for it and try it. 5Dmk3 bodies are too cheap now not to at least give it a go. Just my 2c.

Also, I am not so confident that a useful version of ML for the mk4 will be released anytime soon, if ever. The reason being that existing versions of ML simply hijack the existing readout of the sensor and dump raw data. If 4K without the 1.74x is to be achieved, ML will have to go farther than previous developments have and figure out a completely new way of reading 4K off the sensor full-frame. Someone with more intimate knowledge of the process may be able to correct me.

I'm having trouble loading After Effects projects with MLVFS image sequences in them. I've been sitting here for 10 minutes and the Open Project progress bar is at 32%. mlvfs process in activity monitor shows 99% CPU. In fact, anytime I try to open sequences in Premiere or AE, the program hangs and MLVFS process revs up the CPU for 1-2 minutes before the program resumes. Is this normal behavior? I'm on a Mac Pro 2010 with OS X 10.11.2.

I updated mlvfs and FUSE to the latest version a couple days ago. I think something changed? Although performance has always been a little slow. For instance every time I want to modify source settings of an MLVFS image sequence (open up ACR dialog in AE for instance) I have to wait about 60 seconds until the window appears.

I know it's not a hard drive latency issue because it's on an external RAID that blackmagic disk speed test gives a 240MB/sec read speed. I've also accessed these files before from an external USB 3 drive and performance was actually better then. (!)

Ah! I see now. The idea of moving files into folders in order to activate certain options is a novel concept that has taken me a while to fully recognize, but I get it now. Thanks for the help.

Yea, I'm pretty sure it's converting because the fps_01, fps_02...files show up as it processes, but a movie file never actually appears.

I've tried this on two separate machines and the result is the same, clearly I'm doing something wrong. Can somebody give me some basic instructions to get to the point of converting to ProRes? The user guide never actually gives any step by step instructions.

Edit: Fixed it. Re-copied the binaries manually to ~/Library/Services/MLP/Contents/

However I still have another question! How do I convert to ProRes 422 instead? The text file specifies that ProRes 4444 is the default, and has an entry at the top, but it's pretty clearly not the command line to create ProRes 4444 files.

Shouldn't it be, for ProRes 422,

Code Select Expand

-pix_fmt yuv422p10
or

Code Select Expand

-profile hq
instead of for ProRes 4444:

Code Select Expand

-pix_fmt yuv444p10

But the default (supposedly ProRes 4444) is

Code Select Expand

-c:v libx264 -preset slow -crf 10 -c:a copy -pix_fmt yuv420p
Which I have no clue, but it looks like some kind of h264 encoder, not ProRes 4444? I'm so confused now!

I'm having trouble getting MLP to produce ProRes files. i have my clips in DNG folders through MLVFS. I right-click a folder and select MLP, then the PRORES folder shows up and after I add a LUT to the hold folder and right-click the DNG folder again, the automator wheel spins for a little and then goes away. But no MOV file ever shows up. Is there a setting I have to enable or something?

Sorry but I've poured through the user guide and page after page of this forum with no answer, it's really baffling me...

Is anyone having trouble with importing with MLVFS? Programs are hanging indefinitely when I try the open file dialog box for browsing the filesystem when an MLVFS disk is mounted. As soon as I eject the image the problem goes away. I've reinstalled MLVFS as well as FUSE. I'm on OSX.

Is anyone else having issues using the files from MLVFS in Adobe Premiere? It takes several seconds for the image to update in the source/preview monitors and I get the "media pending" screen often. When I convert using another method, RAWMagic for instance, playback and workflow is smooth.

I liked the shot with the girl in it the most 

In all seriousness and perhaps to the testament of the subjective nature of this I liked the overexposed shot the most at first blush, by my preferred level of contrast and highlights would depend on the context of the subject!

Andy I will check out slimraw that sounds like exactly what is needed, although dmilligan are you saying that the DNGs are actually lighter if I access them directly from the MLV mount? If I understand you correctly the empty bits added become "real" when copied from the virtual drive? I have in fact converted them from the virtual disk by copying them, sounds like that was a mistake?

In any case I have reverted to making compressed proxies, I actually really enjoy "developing my negatives" in After Effects ACR, but the real reason boils down to Premiere's lackluster handling of raw video. Actually dmilligan you may be equipped to answer this: when I apply lumetri effects to a cDNG clip from MLVFS, for example an exposure adjustment, I see noise in the shadows that I don't see if I apply the same affect in ACR...is Premiere only addressing a limited number of bits? Is there a setting to address all the bits like ACR or is that a limitation set by Premiere to allow real-time performance?

I believe I may have answered my own question. Looking at the EXIF data, the difference is that BMPCC DNGs are 12-bit and JPEG-compressed, whereas MLVFS is giving me 16-bit uncompressed. Of course the MLV raw files are twice as big as the Blackmagic files (4MB vs. 2.2MB) so it must be choking on the bits.

I've converted my MLV clips to cinemaDNG sequences using MLVFS. When editing, there is a 10-second delay while the source monitor shows "Media Pending" every time I try to open a clip in the source monitor. I know this is a Magic Lantern-specific issue because the same does not happen with my cinemaDNG sequences from the Blackmagic pocket camera. Anyone else have this problem? It causes editing to be maddeningly slow and totally unworkable.

Ah! That makes sense. so I'm losing a tiny bit more resolution at these slo-mo rates. Bummer. Anyway I can recall that I also changed either a crop size or an image size tag to "1920x1080" have you tried that? It's so bizarre because Ppro is clearly reading some kind of PAR info from the file as evidenced by the Interpret footage dialog. I wish I could remember what I did to make it work.

Ah, my mistake, thanks for the correction dmilligan, you are right. However I'm not sure I understand the 3rd column/5th row skipping reasoning for the PAR of 0.6. Regardless of what pixels the camera skips, the output (at least for my 5D3) is 1728x606 which is a 2.85 AR not 3.5. A PAR of .6:1 or 1:1.667 would give a 1.71 AR, not quite the 1.7778 we want, no?

Also, does anyone have any idea why I can't change any exif info using exif tool? I keep getting "1 files unchanged" returned. Verbose mode just says "nothing changed in test.DNG"

Danne not sure if you misread my post but it's editing files in general that I'm having trouble with.

This is my command

Code Select Expand

exiftool -DefaultScale='1 0.624' test.DNG

and I'm getting

Code Select Expand

Nothing changed in test.DNG
    0 image files updated
    1 image files unchanged

Any idea why this is?

Again, the 1 1.6667 are the wrong values to use to "de-stretch," that's why we want to change it.

It's part of the DNG standard and has a default value of 1. I really thought I opened it up in TextWrangler and it was all there in XML format. Now when I open up a file all I see is gibberish. I can remember everything I did except how I edited the value in the first place! How are you all editing EXIF values anyway? Exif editor doesn't show the advanced metadata categories, defaultscale included.

Edit: So, I think the DefaultScale tag is misunderstood here. I'm not sure if MLVFS is doing this but I took a look at my 60p footage and the tag has values of H=1 V=1.6667. Not sure where these numbers are coming from. What we want to do is change this value to counter the "stretch" of 1728x606 footage, which is an aspect ratio of 2.85. We want an aspect ratio of 1.7778 (16:9) so the pixels will need to be taller than they are wide, does this make sense? That means the correct DefaultScale values should be H=1 V=0.624.

Problem is, exiftool returns "1 image files unchanged" every time I try to write the file, can somebody help?

Code Select Expand

exiftool -DefaultScale='1 0.624' test.DNG

Hello, couple things.

I've done this aspect ratio editing before and was successful in getting Ppro to recognize the new AR in stretched slo-mo footage from a 5D3. Unfortunately I can't remember exactly how I did it. I could have sworn I opened up a DNG in TextWrangler but maybe it was something else. However this is what I do remember:

-I used the DefaultScale option and calculated the PAR needed to counteract the "stretch"
-It was only one value I changed
-I only needed to edit the first file in the sequence. It seems Ppro gets its information from that first file and ignores the metadata in the rest. maybe this is common knowledge just thought I would mention

Also for those of you having trouble getting the localhost:8000 site to work, make sure you wait long enough. The webpage won't load until all IDX files have been created next to every MLV file you're trying to mount, and for me this took upwards of 10-20 minutes for all my files. I was pulling my hair out until I realized I just had to be patient.

Many thanks to the author. This functionality is primo, top shelf, keep up the great work.

Why not just resize on one axis?

I want raw DNG sequences playing in the preview monitor that are at their correct aspect ratio. I need to be able to edit unstretched footage. You can only resize clips once they're already in the timeline.

A final update: this doesn't work. After an hour on the phone with tech support it seems that the Interpretation Rules.txt functionality has been taken out, with no plans to address it in future updates.

What a bummer.

Hey quick update with good news!

It seems that you can edit the values of these preset PARs by editing the Interpretation Rules.txt in Applications/Adobe Premiere Pro CC 2014.app/Contents/Plug-ins/en_US

Slo-mo ML clips come in odd aspect ratios. Anyone familiar with Ppro knows this window:


With the ability to enter a custom PAR value, comes the ability to fully integrate a RAW cDNG workflow in Premiere without having to render proxies. For example, if a value of 0.6211 were allowed, 60p clips requiring 1.61x sizing would be conformed to 16:9. As it stands, there is no way to preview these stretched sequences in their proper scale without rendering out to a proxy format.

If you agree this would be helpful in Premiere, make your voice heard.

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&loc=en

Quote from: bwinter88 on Today at 04:14:36 AM

Also, is there a way to make these volumes searchable by Spotlight? Right now Spotlight can't see them, I think it's a permissions issue.

Probably not, if it doesn't work like it is now. Certain folders pretty much have to remain read only.
Using ls and grep works pretty well though (and regular expressions are way better for searching if you know how to use them, also if you don't like Apple to know about everything you search for):
ls -R | grep "search expression"

Thanks for the reply. I've read that to enable Spotlight on FUSE volumes you can use something called the "allow_other" option at mount. I won't pretend to understand FUSE or coding at all but what do you think? would it be possible to add this without affecting anything?

Hi,
the web interface at http://localhost:8000 is not working for me. I've tried restarting after installing but it is hung up on "waiting for localhost" indefinitely in firefox, chrome and safari. The FUSE disk mounts, but there are no files inside.

Edit: just realized it's still busy unpacking the mlvs and creating idx files. I will wait until it is finished and see if the webpage is accessible then.

edit 2--just finished, looks like it's all working fine.

Is there by chance the possibility of implementing a function that will fix the aspect ratio for slo-mo clips?

Also, is there a way to make these volumes searchable by Spotlight? Right now Spotlight can't see them, I think it's a permissions issue.

baldand,
Thank you so much for your work. This utility is invaluable. Two things:

-is there a way to set the default settings? It defaults to frame-by-frame playback but drop frame playback makes more sense for on-the-fly previewing, and it is a nuisance to have to switch every time I open a new file.

-The aspect ratio correction for 5Dmk3 60p is 1.61x, not 1.4x, curious why this is not an option?

Thanks
Ben