MLVFS - a FUSE based, "on the fly" MLV to CDNG converter

[Slasheal]

Hello.

MIRAWviewver allow lens correction
MLVFS doesn't yet
MLVMystic doesn't yet too

Maybe you should ask for help.
You've got and answer on adobe forum:

"Camera Raw / Lightroom needs to know the sensor area (or crop factor) to map the pixels of the source image to the physical model of the lens profile. ACR calculates this from the EXIF (not DNG) metadata. You can do this in one of two ways:
 
1. Use the FocalPlaneXResolution, FocalPlaneYResolution, and FocalPlaneResolutionUnit tags.
 
2. Use the FocalLength and FocalLengthIn35mm tags.
 
Of these two options, I recommend #1 because you'll have more precision. (For #2, FocalLength has tag type rational, which is fine, but FocalLengthIn35mm is an integer. That's an issue for short focal lengths.)"

Hope it will help.
If any more samples needed, don't hesitate to specify.

[dmilligan]

I know, I saw that, it's the information I needed. When I have time I will work on it, it's a lot of work (figuring out what the focal plane resolution actually is, is not trivial, there are 3 different video resolution modes, and many supported ML cameras that all have different pixel pitches). Anybody is welcome to contribute code at any time.

[gmfotografie]

after convertingi get the dng files in the specified folder.
 my browser then opens and gives me a error message ... localhost:8000 -> could not opend.

using osx system

[cmccullum]

I can't get this to work at all  @deafeyejedi has been trying to help me troubleshoot the problem, but still no luck. I keep getting safari can't connect to server "localhost". error

As far as I can tell, I've followed all of the correct steps, but I'm afraid I'm missing something

Running
OSX 10.7.5
OSXFuse 2.8.0

Any help would be great

[reddeercity]

I keep getting safari can't connect to server "localhost". error
As far as I can tell, I've followed all of the correct steps,
but I'm afraid I'm missing something
Running
OSX 10.7.5
OSXFuse 2.8.0
Any help would be great

Not to sure about mlvfs running on "Lion" OSX 10.7.5 , I know it runs on Maverick(10.9.x) & Yosemite (10.10.x)
You may have to up-grade your OSX.

Even thou you don't have a web interface working  do get a mounted mlvfs folder ?

[cmccullum]

@reddeercity nope, I don't get a mounted folder either. Anyone else think I might need to upgrade? I'd like to avoid this if possible

[reddeercity]

Another thing I just thought of , I'm using a older version(2.7.3) of osxfuse and a older build of MLVFS back from Nov/2014
Maybe try a older version of OSXFuse & or see if there is older build of mlvfs still available .

If I have some time in the next few days I have a old MacPro 1.1 that's on "Lion" OSX10.7.5 I see if I can get it working on it.

[cmccullum]

If you could check that out, that'd be great. I tried older versions of OSXFuse, but didn't have any luck. I didn't think an older mlvfs would make any difference since it's a set of Automator actions. I'm thinking there's something I'm missing with OSXFuse or some deeper issue

[dmilligan]

MLVFS is not set of automator actions. The automator actions are there just make it easier for users who don't know much about command line to run it. There is an executable named 'mlvfs' embedded inside the automator package. That is what does all the work. The automator stuff just fills in the correct command line parameters and calls mlvfs for you, and then opens up the web browser to the correct address for the webgui.

If you want to figure out what is going on, you need to run that executable from the command line and see the output (the automator actions just throw away the standard output). If MLVFS is crashing, there should also be logs in ~/Logs/DiagnosticReports.

I would not recommend using an older version of MLVFS, it's not going to make a difference, other than probably being less stable and having fewer features (also, please do not share older builds here, I delete them for a reason). I would highly recommend upgrading to the latest version of the OS if you can; I'm definitely not going to be able to support old OS versions. If you really want to use an old OS version, you may have to compile MLVFS yourself.

[cmccullum]

@dmilligan sorry about that. I was half asleep when I wrote that response and had forgotten that I did open the Automator package and find the executable [facepalm] I don't know how to run it from the command line though :\

[dmilligan]

Run it with no parameters and it should tell you what the options are.

[cmccullum]

Not sure I'm doing it right, but I get:

Illegal instruction: 4
logout

[Process completed]

[dmilligan]

http://stackoverflow.com/questions/14268887/what-is-the-illegal-instruction-4-error-and-why-does-mmacosx-version-min-10

You will have to compile MLVFS yourself or update to a more recent version of OSX.

[DeafEyeJedi]

Update to at least OS X 10.8.x and upward...

[cmccullum]

Updated my system, and everything is working now. Thanks everyone for your patience and help!

[dmilligan]

RE: automatic lens corrections

I have implemented the tags necessary for this (FocalPlaneResolutionX, FocalPlaneResolutionY, FocalPlaneResolutionUnit), but only for my camera (60D).
I need the default values for these for all other cameras.

Here's how to get them:
1. Download and install exiftool
2. Take a normal raw still with your camera (CR2)
3. Run this command:

Code: [Select]

exiftool -v <image_filename.CR2>
(where <image_filename.CR2> is the actual filename of your CR2)
4. In the output look for the FocalPlaneResolutionX, FocalPlaneResolutionY, FocalPlaneResolutionUnit tags. It should look something like this:

Code: [Select]

  | | 18) FocalPlaneXResolution = 5728.176796 (5184000/905)
  | | 19) FocalPlaneYResolution = 5808.403361 (3456000/595)
  | | 20) FocalPlaneResolutionUnit = 2

I need the two ratios (ex: 5184000/905, 3456000/595) and the unit.
Once I get these values for all the cameras, I will update the code and release a new build.

[DeafEyeJedi]

5D3:

Code: [Select]

  | | 26) FocalPlaneXResolution = 3942.505133 (5760000/1461)
  | | 27) FocalPlaneYResolution = 3950.617284 (3840000/972)
  | | 28) FocalPlaneResolutionUnit = 2
70D:

Code: [Select]

  | | 26) FocalPlaneXResolution = 6086.76307 (5472000/899)
  | | 27) FocalPlaneYResolution = 6090.15025 (3648000/599)
  | | 28) FocalPlaneResolutionUnit = 2
EOSM:

Code: [Select]

  | | 26) FocalPlaneXResolution = 5798.657718 (5184000/894)
  | | 27) FocalPlaneYResolution = 5788.944724 (3456000/597)
  | | 28) FocalPlaneResolutionUnit = 2

[Slasheal]

7D:

  | | 26) FocalPlaneXResolution = 5715.545755 (5184000/907)
  | | 27) FocalPlaneYResolution = 5808.403361 (3456000/595)
  | | 28) FocalPlaneResolutionUnit = 2

Great!

[Mehmet Kozal]

650D:

  | | 26) FocalPlaneXResolution = 5798.657718 (5184000/894)
  | | 27) FocalPlaneYResolution = 5788.944724 (3456000/597)
  | | 28) FocalPlaneResolutionUnit = 2

[vertigopix]

6D :

Code: [Select]

| | 26) FocalPlaneXResolution = 3810.584958 (5472000/1436)
| | 27) FocalPlaneYResolution = 3815.899582 (3648000/956)
| | 28) FocalPlaneResolutionUnit = 2
Thank you !

[Danne]

Should be for the rest of the bunch. Otherwise please tell.
*updated with a complete list of cameras.


5D mark 2

Code: [Select]

| | 24) FocalPlaneXResolution = 3849.211789 (5616000/1459)
  | | 25) FocalPlaneYResolution = 3908.141962 (3744000/958)
  | | 26) FocalPlaneResolutionUnit = 2
50D

Code: [Select]

| | 24) FocalPlaneXResolution = 5315.436242 (4752000/894)
  | | 25) FocalPlaneYResolution = 5306.532663 (3168000/597)
  | | 26) FocalPlaneResolutionUnit = 2
500D

Code: [Select]

| | 24) FocalPlaneXResolution = 5315.436242 (4752000/894)
  | | 25) FocalPlaneYResolution = 5342.32715 (3168000/593)
  | | 26) FocalPlaneResolutionUnit = 2
550D

Code: [Select]

| | 24) FocalPlaneXResolution = 5728.176796 (5184000/905)
  | | 25) FocalPlaneYResolution = 5808.403361 (3456000/595)
  | | 26) FocalPlaneResolutionUnit = 2
600D

Code: [Select]

| | 26) FocalPlaneXResolution = 5728.176796 (5184000/905)
  | | 27) FocalPlaneYResolution = 5808.403361 (3456000/595)
  | | 28) FocalPlaneResolutionUnit = 2
650D

Code: [Select]

| | 26) FocalPlaneXResolution = 5798.657718 (5184000/894)
  | | 27) FocalPlaneYResolution = 5788.944724 (3456000/597)
  | | 28) FocalPlaneResolutionUnit = 2
700D

Code: [Select]

| | 26) FocalPlaneXResolution = 5798.657718 (5184000/894)
  | | 27) FocalPlaneYResolution = 5788.944724 (3456000/597)
  | | 28) FocalPlaneResolutionUnit = 2
1100D

Code: [Select]

| | 26) FocalPlaneXResolution = 4720.441989 (4272000/905)
  | | 27) FocalPlaneYResolution = 4786.554622 (2848000/595)
  | | 28) FocalPlaneResolutionUnit = 2
5d mark 3

 

Code: [Select]

| | 26) FocalPlaneXResolution = 3942.505133 (5760000/1461)
  | | 27) FocalPlaneYResolution = 3950.617284 (3840000/972)
  | | 28) FocalPlaneResolutionUnit = 2
6D

Code: [Select]

| | 26) FocalPlaneXResolution = 3810.584958 (5472000/1436)
  | | 27) FocalPlaneYResolution = 3815.899582 (3648000/956)
  | | 28) FocalPlaneResolutionUnit = 2
7D

Code: [Select]

| | 24) FocalPlaneXResolution = 5715.545755 (5184000/907)
  | | 25) FocalPlaneYResolution = 5808.403361 (3456000/595)
  | | 26) FocalPlaneResolutionUnit = 2
60D

Code: [Select]

| | 26) FocalPlaneXResolution = 5728.176796 (5184000/905)
  | | 27) FocalPlaneYResolution = 5808.403361 (3456000/595)
  | | 28) FocalPlaneResolutionUnit = 2
70D

Code: [Select]

| | 26) FocalPlaneXResolution = 6086.76307 (5472000/899)
  | | 27) FocalPlaneYResolution = 6090.15025 (3648000/599)
  | | 28) FocalPlaneResolutionUnit = 2

eos m

Code: [Select]

| | 26) FocalPlaneXResolution = 5798.657718 (5184000/894)
  | | 27) FocalPlaneYResolution = 5788.944724 (3456000/597)
  | | 28) FocalPlaneResolutionUnit = 2


[vertigopix]

5D2 :

Code: [Select]

| | 24) FocalPlaneXResolution = 3849.211789 (5616000/1459)
| | 25) FocalPlaneYResolution = 3908.141962 (3744000/958)
| | 26) FocalPlaneResolutionUnit = 2

[dmilligan]

Thanks everyone. New build is available.

[DeafEyeJedi]

Thank You!

*edit*

Just downloaded and installed... Ran a few test files and kept getting the same errors that I've never seen before. I just ran this same file last night and worked fine but that was before I updated to the latest MLVFS.

I also deleted .IDX files and tried again with no luck.

Anyone else encountering similar errors?

*edit #2*

I just downgraded to an earlier version of MLVFS and ran into the same error -- now that most likely tells me that it's definitely not due your app and probably has to do with the pathway of the codec that I just installed DNxHR recently (although it worked fine last night) but I'll confirm this with you all once I get to the bottom of this.

*edit #3*

Got home, downloaded latest MLVFS on Mac Mini, Ran test file in AE and exported all Codec's like normal. Confirmed it has nothing to do with your app, once again I apologize for the false alarm. It definitely has to do with the pathway somehow the codecs got misplaced.

Thanks again, David for your great work so my question now is does the latest updates with automatic lens corrections affect the quality a little similar to how it does if we were to do the same in ACR? If so, will there be a way to disable it? (not that I wanted to but just a thought worth asking).

[bwinter88]

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.