Fastrawviewer compatibility
![fastrawviewer compatibility fastrawviewer compatibility](https://mac-cdn.softpedia.com/screenshots/FastRawViewer_1.jpg)
![fastrawviewer compatibility fastrawviewer compatibility](https://www.fastrawviewer.com/sites/fastrawviewer.com/files/clapperboard_0.jpeg)
No change! But wait: horizon:2$ ls -lO image.dng Then I star the file in Photo Mechanic, and check the XMP file again: horizon:2$ diff -u old.xmp image.xmp I make a copy of the XMP file for further investigation: horizon:2$ cp image.xmp old.xmp Notice how the XMP file is newer than the DNG file, and how the DNG file is locked (uchg flag). Here's what's happening, these are the "original" files, after I have processed them in ACR: horizon:2$ ls -lO It appears Photo Mechanic does not support external XMP sidecar files for DNGs, even though if DNGs are locked (read-only). Photo Mechanic is configured with Adobe compatibility, as instructed here. And I am using DNG files because I am using a 3rd party RAW convertor for my RAF (Fuji X system) files. I am using locked DNG files, because my backup/version control system doesn't bode well with constantly changing DNG files. If I label in FRW, I can see the rating/color in Adobe Bridge (but NOT in Photo Mechanic), and the file opens up correctly, with edits applied, in ACR.Īlso, things seem to work fine with normal, unlocked DNG files, though in that case the DNG file itself is modified (even though I set ACR to always generate XMP file). I believe Bridge, unlike ACR, is trying to apply those settings to the DNG directly, which fails because the DNGs are read only, instead of just restoring the association with the XMP file.Īll this starring and labelling works fine if I use fastRawViewer instead of Photo Mechanic. If I instead use Adobe Bridge to reset previous settings, Bridge errors out with "The Camera Raw settings could not be applied because there were no Camera Raw files selected or selected files were read-only.". All my edits are lost unless I either manually load the XMP again, or if I click in ACR on "Previous Conversion". If I later star, or color label my DNGs in PM, ACR loses the DNG←→XMP association. I then cull these DNGs in Photo Mechanic, and then I edit them in ACR, which creates a sidecar XMP file.
Fastrawviewer compatibility software#
Most software just use the arrow alone(more intuitive).Ĭtrl + arrow would make more sense for something like navigating across/up/down when viewing an image whilst zoomed in.I use Photo Mechanic and Adobe Camera Raw. One thing I'm not impressed with tho is the need to Ctrl + right/left arrow to navigate from image to image If you have issues, just for the sake of assisting the devs, it would be highly recommended to let them know of any issues you've experienced(such as the slowness of the software). I don't use PS/CS of any type to comment on.Īlso on the issue of the software's editing ability, it must be remembered that it is still only beta software. not to mention the slow and convoluted workflow in getting those images into the develop module. x4 955 AMD processor, 35-50(ish) Mb/s mechanical HDD, on board graphics chip(Radeon HD4290).īy comparison, LR4 takes what I consider an incredibly slow time to open and display any raw images.
![fastrawviewer compatibility fastrawviewer compatibility](https://photographylife.com/wp-content/uploads/2014/12/FastRawViewer-Keyboard-Shortcuts.png)
Fastrawviewer compatibility Pc#
Note that this is on a PC that is now considered old and slow by modern standards. Once the program shortcut is induced, FRV takes approximately 5-10sec to fully load(but no file loaded into the display window).Ĭlicking on a link to one of the last folders viewed takes approximately 2-3sec to load the last viewed image of that folder. VNX2 is still my speediest raw viewing program by a mile (maybe even 2 miles), followed by FSViewer.įRV is quite speedy relative to them tho. On my now 5yo slow as hell AMD x4 with old slow RAM(8Gb) and now slowing HDD setup. One would have to say most likely a problem at your end. FRV is incredibly slow to load does not accept Custom Camera Profiles, is not Colour Managed and, worst of all, shows only a single image at a time.