ACR VisionLog Camera Profile

[Andy600]

I mean any raw2dng app i.e. whichever one you use

[Danne]

Use this at your own risk.

You could try this script which will put in the canon EOS 650D tag to dng files after they are developed. It needs exiftool installed. You simply put the script next to your folders with dng files and double click.
https://drive.google.com/file/d/0B4tCJMlOYfircXpJNDlhakFCX0U/view?usp=sharing

If the script doesn,t work you might have to give it user priviliges. Go to terminal and write.

chmod u=rwx [drag script here] hit enter

Here,s the script lines

Code: [Select]

workingDir=`dirname "$0"`
cd "${workingDir}"

find . -maxdepth 2 -mindepth 2 -iname '*.dng' -print0 | xargs -0 exiftool "-UniqueCameraModel=Canon EOS 650D" -overwrite_original

[Walter Schulz]

Sorry, but this is too fast for me.
I was not able to reproduce newsense's error following the workflow he gave:
650D's MLV mounted to MLVFS, opening DNGs in any Adobe AE. (I tried PS, too). Exifs are just fine, profiles filled up nice and clean.

So: *I* have no troubles, *he* should repair his DNG.
I'm missing something here ...

[Andy600]

It must be profile location Walter. I have seen very rare instances where ACR got corrupted and needed reinstalling but if the meta is correct ACR will assign profiles assuming they are placed in the correct location.

3rd party DCP profiles should not be placed in the Adobe Standard or Camera Profiles folders (or they are ignored) and also not inside folders of folders of folders. I've checked some stock images and MLV from the 650D and all relevant profiles are accessible (OSX and Windows).

MLVFS source looks correct too so it's not that.

[Walter Schulz]

But this doesn't match what he told about 5D3 files he tried. Profiles (at least VisionLog) showing up, then.
That's what is puzzling me: Profiles working with non-650D files and not an explanation at hand what could be messing with his 650D's exif data.

[Andy600]

A DNG is certainly needed to verify. In my experience it will be something very simple.

[Danne]

Upload a dng file, should be enough.

[newsense]

http://www.megafileupload.com/rcoM/test.MLV
http://www.megafileupload.com/rcoO/test_000000.dng

[Andy600]

Yep, says Canon EOS Rebel T4i. Should be Canon EOS 650D. Hmmm. Need another look at MLVFS source.

[Danne]

here,s the metadata from your dng file. Use the script to rename to the other tag.

[Walter Schulz]

@Andy600: I have followed his workflow with files from my own 650D and everything is just fine.

[Andy600]

Everything is working here too (with my stock footage). This is a weird one. I don't get why MLVFS would embed a regional tag like this, in fact I'm pretty sure it doesn't.

[Andy600]

@newsense is right. Just tried his MLV and MLVFS shows a regional tag  I can't find anything in MLVFS source - @dmilligan?

[Danne]

It,s the tag that mlv_dump is providing as well. Shouldn,t it be adobe that should be able to read this tags?

[Walter Schulz]

@Andy600: What? Wasn't able to processed his MLV yet (no MLVFS around right now) but my own MLV does not give me that!
 

[Andy600]

Adobe's DNG Converter always assigns the global model (650D etc) as the UniqueCameraModel tag and a regional tag (T4i etc) as LocalizedCameraModel (if they differ). If there is no regional tag it is usually omitted.

Here, the region tag is being used for both the UniqueCameraModel and LocalizedCameraModel which is why the profiles for this camera are not accessible in ACR but are for DNGs converted from cr2 and possibly other raw2dng apps. The UniqueCameraModel tag needs to be the global identifier (i.e. Canon EOS 650D).

As a temporary fix just change the UniqueCameraModel tag to Canon EOS 650D with Exiftool.

[Danne]

Exiftool info from canon.pm file indicates that the tag could differ?

   

Code: [Select]

# NOTE: some pre-production models may have a model name of
    # "Canon EOS Kxxx", where "xxx" is the last 3 digits of the model ID below.
    # This has been observed for the 1DSmkIII/K215 and 400D/K236.
    0x80000001 => 'EOS-1D',
    0x80000167 => 'EOS-1DS',
    0x80000168 => 'EOS 10D',
    0x80000169 => 'EOS-1D Mark III',
    0x80000170 => 'EOS Digital Rebel / 300D / Kiss Digital',
    0x80000174 => 'EOS-1D Mark II',
    0x80000175 => 'EOS 20D',
    0x80000176 => 'EOS Digital Rebel XSi / 450D / Kiss X2',
    0x80000188 => 'EOS-1Ds Mark II',
    0x80000189 => 'EOS Digital Rebel XT / 350D / Kiss Digital N',
    0x80000190 => 'EOS 40D',
    0x80000213 => 'EOS 5D',
    0x80000215 => 'EOS-1Ds Mark III',
    0x80000218 => 'EOS 5D Mark II',
    0x80000219 => 'WFT-E1',
    0x80000232 => 'EOS-1D Mark II N',
    0x80000234 => 'EOS 30D',
    0x80000236 => 'EOS Digital Rebel XTi / 400D / Kiss Digital X',
    0x80000241 => 'WFT-E2',
    0x80000246 => 'WFT-E3',
    0x80000250 => 'EOS 7D',
    0x80000252 => 'EOS Rebel T1i / 500D / Kiss X3',
    0x80000254 => 'EOS Rebel XS / 1000D / Kiss F',
    0x80000261 => 'EOS 50D',
    0x80000269 => 'EOS-1D X',
    0x80000270 => 'EOS Rebel T2i / 550D / Kiss X4',
    0x80000271 => 'WFT-E4',
    0x80000273 => 'WFT-E5',
    0x80000281 => 'EOS-1D Mark IV',
    0x80000285 => 'EOS 5D Mark III',
    0x80000286 => 'EOS Rebel T3i / 600D / Kiss X5',
    0x80000287 => 'EOS 60D',
    0x80000288 => 'EOS Rebel T3 / 1100D / Kiss X50',
    0x80000289 => 'EOS 7D Mark II', #52
    0x80000297 => 'WFT-E2 II',
    0x80000298 => 'WFT-E4 II',
    0x80000301 => 'EOS Rebel T4i / 650D / Kiss X6i',
    0x80000302 => 'EOS 6D', #25
    0x80000324 => 'EOS-1D C', # (NC)
    0x80000325 => 'EOS 70D',
    0x80000326 => 'EOS Rebel T5i / 700D / Kiss X7i',
    0x80000327 => 'EOS Rebel T5 / 1200D / Kiss X70',
    0x80000331 => 'EOS M',
    0x80000355 => 'EOS M2',
    0x80000346 => 'EOS Rebel SL1 / 100D / Kiss X7',
    0x80000347 => 'EOS Rebel T6s / 760D / 8000D',
    0x80000382 => 'EOS 5DS',
    0x80000393 => 'EOS Rebel T6i / 750D / Kiss X8i',
    0x80000401 => 'EOS 5DS R',
);

[Andy600]

@Walter - you probably have a camera badged as 650D? TBH I'm not sure how this regional tag is getting into MLV in the first place. I can't find anything in MLVFS source but I haven't been through it all.

[Walter Schulz]

@newsense: Can you upload a CR2 out-of-the-cam?

[Andy600]

@Danne - Adobe does, I think, try to honor the various localizations by putting them in different tags but they are not obliged to and might not where multiple/duplicate camera profiles could be shown in ACR/Lightroom and confuse users. The basic minimum is that the UniqueCameraModel tag is populated correctly so that profiles can be accessed - with other tags they may or may not be accessed depending on what Adobe did in ACR/Lightoom. There is a logic to it all but Adobe do make things a little complicated.

[Walter Schulz]

Okay, understood (I hope). Yes, I have 650D all over in meta and nothing about KISS or T4i.
So maybe we have an issue with MLV metadata using a regional tag and MLVFS converts this - with best intentions - to Unique tag. How to verify/falsify this?

[Danne]

Get a CR2 from newsense, convert it with adobe dng converter. Mlvfs grabs metadata from MLV so I,m pretty sure that is what mlvfs is showing.
I,m not totally convinced that the unique camera model tag always is the same as according to Andy600. Will be interesting to find out.

[Andy600]

@Danne - I've looked at meta from a 650D and a Rebel, they show the same UniqueCameraModel but the Rebel also has an additional localized tag.

[Danne]

Ok, it seems MLV grabs that tag somehow.
Here,s metadata from a MLV file with the localized? camera model name tag. (Canon EOS 700D)

[Andy600]

Yes, it's grabbing the localized model header from localized models so there needs to be a function added to raw2dng to parse possible local tags before writing the UniqueCameraModel tag.

I couldn't find it in MLVFS because as you say, it's coming from MLV and I presume MLV is grabbing the header from the camera's internals.

Incidentally, this will affect ACR, Lightroom, RawTherapee and probably apps that use ICC input profiles.