I downloaded the VisionLog camera profile and placed it in C:\Users\matt\AppData\Roaming\Adobe\CameraRaw\CameraProfiles and C:\ProgramData\Adobe\CameraRaw\CameraProfiles and I still do not see the profile in Adobe Camera Raw.
You don't have to copy it to ProgramData.
Do you have a directoy VisionLog in C:\Users\matt\AppData\Roaming\Adobe\CameraRaw\CameraProfiles and do you have restarted PS?
Quote from: Walter Schulz on March 01, 2016, 08:08:19 AM
You don't have to copy it to ProgramData.
Do you have a directoy VisionLog in C:\Users\matt\AppData\Roaming\Adobe\CameraRaw\CameraProfiles and do you have restarted PS?
Yes I do and have.
It looks like MLVFS must have wrong EXIF for my camera, Rebel T4i instead of 650d.
Quote from: newsense on March 01, 2016, 01:21:15 PM
Yes I do and have.
And C:\Users\matt\AppData\Roaming\Adobe\CameraRaw\CameraProfiles was there? You haven't to create "CameraProfiles"?
Snapshot Explorer window showing C:\Users\matt\AppData\Roaming\Adobe\CameraRaw\CameraProfiles contents and link it here.
QuoteIt looks like MLVFS must have wrong EXIF for my camera, Rebel T4i instead of 650d.
Rebel T4i is the 650D. If you need to change any tags use exiftool and how that works can be found searching and reading in this forum for instance.
Quote from: Walter Schulz on March 02, 2016, 10:13:35 AM
And C:\Users\matt\AppData\Roaming\Adobe\CameraRaw\CameraProfiles was there? You haven't to create "CameraProfiles"?
Snapshot Explorer window showing C:\Users\matt\AppData\Roaming\Adobe\CameraRaw\CameraProfiles contents and link it here.
Walter, I guarantee you the dir. Is there. I believe the problem is the camera shows up as rebel t4i instead of 650d.
Download a CR2/JPG shot with 5D3 (or another non-Rebel camera but not 70D) and try to reproduce your issue. If VisionLog shows up: Yes, you are right. If not: Yes, I'm right. And Danne, too.
I'm afraid Danne & Walter are right on this one.
It was never about me being right, I just want to use camera profiles without changing EXIF data. i'd add the screenshots if I knew how but it did work with the picture I downloaded from a 5dmk3
(http://<img%20src="http://picpaste.com/Screenshot__1_-znsZxdlD.png">)
Can you upload on of the twisted files (showing camera model Rebel T4i) somewhere and link it here?
Here,s what the file could be tagged with according to exiftool documentation(courtesy dfort). Three different names for the same camera.
Canon EOS 650D
EOS Rebel T4i
Kiss X6i
There may be various tags in use identifying a cam:
Model (String)
CanonModelID (Binary)
CanonImageType (String)
http://picpaste.com/Screenshot__2_-CWRzEwqX.png
Made some experiments: PS does not identify camera types by string values. I changed string exif tags values for Model and CanonImageType: Just ignored. Changed camera entry in DCP: Nope, does not make a match with string entries.
But I can confirm there must be some kind of match between VisionLog DCP files (dedicated to cam) and file loaded into CR/LR. If not matched VisionLog profile will not show up in Camera Profiles dropdown box.
Now I need your file causing VisionLog profiles to be hidden.
You want the MLV file, correct?
Nay, I will try to reproduce this in my own environment. Already having a suspect.
Thanks Walter, let me know if you need a file.
Unable to reproduce your error using latest MLVFS for Windows and Dokany 0.8.x.
I'm wondering why you have no profile visible at all.
Just to make sure: You are running MLVFS and have a drive letter mapped to the directory where MLV file is located? And you open those DNGs from the mapped drive (using the letter assigned via "MLVFS.exe" command) with AE?
Can you upload a short MLV and a DNG generated by MLVFS?
T4i, Rebel, Kiss etc are regional. Adobe use global model numbers so 600D, 650D etc. It's the 'UniqueCameraModel' tag that calls profiles in ACR so make sure this tag is the correct one for your camera in your DNG meta. If not, contact the raw2dng's app dev. If the tag is correct it is 100% going to be due to the location of the .dcp. Make sure you have the latest CameraRaw installed or if you are on an earlier CS version, the last available CameraRaw released for that. Also, there is one unmentionable app out there that doesn't follow procedure and embeds non-standard tags making any standard camera profile inaccessible.
Quote from: Andy600 on March 04, 2016, 10:27:59 AM
Also, there is one unmentionable app out there that doesn't follow procedure and embeds non-standard tags making any standard camera profile inaccessible.
You mind mentioning the unmentionable?
It's the banned app that violated GPL.
wasn't raw2dng, I actually tried that first but had a problem so went with MLVFS which is what I used. Andy, I plan on buying Cinelog if I ever get this sorted out ;)
I'm working on uploading an MLV and DNG but my card reader went out last night while copying files.
I mean any raw2dng app i.e. whichever one you use :)
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
workingDir=`dirname "$0"`
cd "${workingDir}"
find . -maxdepth 2 -mindepth 2 -iname '*.dng' -print0 | xargs -0 exiftool "-UniqueCameraModel=Canon EOS 650D" -overwrite_original
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 ...
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.
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.
A DNG is certainly needed to verify. In my experience it will be something very simple.
Upload a dng file, should be enough.
http://www.megafileupload.com/rcoM/test.MLV
http://www.megafileupload.com/rcoO/test_000000.dng
Yep, says Canon EOS Rebel T4i. Should be Canon EOS 650D. Hmmm. Need another look at MLVFS source.
here,s the metadata from your dng file. Use the script to rename to the other tag.
(http://s14.postimg.org/ejih7hv75/Screen_Shot_2016_03_04_at_13_54_21.png)
@Andy600: I have followed his workflow with files from my own 650D and everything is just fine.
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.
@newsense is right. Just tried his MLV and MLVFS shows a regional tag ??? I can't find anything in MLVFS source - @dmilligan?
It,s the tag that mlv_dump is providing as well. Shouldn,t it be adobe that should be able to read this tags?
@Andy600: What? Wasn't able to processed his MLV yet (no MLVFS around right now) but my own MLV does not give me that!
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.
Exiftool info from canon.pm file indicates that the tag could differ?
# 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',
);
@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.
@newsense: Can you upload a CR2 out-of-the-cam?
@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.
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?
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.
@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.
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)
(http://s18.postimg.org/tku6w5q61/Screen_Shot_2016_03_04_at_15_47_26.png)
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.
Damn nice work boys! [emoji6]
Mind sharing that particular MLV file or at least a CR2 @newsense?
MLV is linked in reply #32
EDIT: I'm out here, I'm pleading incompetence! We have an issue for sure and I think g3gg0, dmilligan, Danne, Andy600 ... will come up with a solution for all Rebel/Kiss users.
PROP_CAM_MODEL returns the localized camera model. I was already somewhat aware of this, but I had not considered the implications.
I don't like the idea of some hardcoded table of camera names in MLVFS and other converters. The MLV format specification doesn't really go into detail about what is meant by "Camera Name", but there is only one field, so there's no possibility of recording both the localized and unique camera model names without changing the spec.
I am trying to change the exif with exiftool to see if that can work as a temp solution but the script that danne shared doesn't work for me. Anyone know how I can change the exif? I'm using MLVFS to get .dng's
MLVFS dngs are "virtual", you can't change them unless you copy them out of the virtual filesystem thus turning them into real files.
And the script provided by Danne is for OS X, not Windows.
After copying them to them to a "real" directory, follow this:
Open Explorer, mark the directory where your DNGs are located (and for easy use: Copy Exiftool.exe there). Press shift key and open context menu while pressed. Select "Open Command Prompt here ...".
You will see a command line interface.
Put command in there
exiftool "-UniqueCameraModel=Canon EOS 650D" -overwrite_original *.DNG
and press enter key.
Thanks, I got a lot of profiles now :) I'll figure out howto make a script.
One quick question, video seems a little noisy. Is it recommended to reduce noise in ACR or use a third party denoiser after ACR?
Hi,
I have a problem with VisionLog Camera Profile:
- when I open the .dng files with Adobe Camera Raw (7.0) through Photoshop C6 I can choose Visionlog
- but when I open the .dng files in Adobe AE CC 2015 I can not see Visionlog in the menu of Adobe Camera Raw (9.6.1)
It may depend by the different version of Adobe Camera Raw ?
Thank you