Raw import trouble

I have latest version of LR4, just tried to import raw and jpg.'s from my card reader for a 5dMKIII. The jpg files will import but the raw do not. Latest vesion of raw on Mac Lion. Help!

In your preferences settings, have you ticked "Treat JPG files next to raw files as separate photos" ?
I assume so, because otherwise the jpgs would not get imported.
But then if you only get 1 image after import, are you sure it is the jpg and not the CR2? Because if unticked, that would be the result.
Check with a right-click on the thumbnail in Library module, and chosse "Show in Finder".
kb10101956 wrote:
Latest vesion of raw on Mac Lion. Help!
What does that mean - "raw on Mac"?
Do you import directly form the card inside a card reader or have you copied the images over to your Mac via Finder?
Cornelia

Similar Messages

Raw Import Bug

I'm having some real trouble with Aperture 3's RAW conversion. I spent hours setting up my studio for bright, happy, headshots. On my camera, the photos look perfect, exactly as I want, and the brightness makes her skin smooth and radiant. When I import the RAW into Aperture 3, they look like the photo on the right - dark, and oversaturated. The skin looks terrible, the hair is dark, it's just all wrong. I know Aperture admits that for my Nikon D700 camera it converts my raws 0.1 darker than it should (which to me is unacceptable). But why do I spend so much time perfecting my lighting if Aperture ruins the files on import?
My question is - is there any way to reset my RAW import options to be Aperture 2?
I should note that in Aperture 3, when I try to edit a photo to make it look more like I want it to look, it comes out terribly contrasty, I loose highlight detail quickly. It's also overstaturated so when I adjust the exposure, her skin looks a bit too yellow. This is a lot of adjustment to apply to the 800 images I took of her, especially considering I photographed her exactly how I wanted.

Your camera is showing you, on a very small display, a small JPG conversion done by its internal computer. It is never going to look like the default converted-from-RAW-on-a-computer-and-displayed-on-a-good-monitor version of the photo.
The better comparison would be between default RAW conversions done by Aperture, by Nikon's own software, and by an Adobe product. In all cases, however, you should see more detail, including more subtle gradations across similar areas, and a broader (or more filled-in) luminance range.
Personally, I'd much much much prefer to have the image on the right to work with (of the two you supplied). I don't know why you aren't able to get it to look like the in-camera JPG. If you do, however, applying the same settings to 800 Images is very easy in Aperture (create and apply a Preset, or Lift & Stamp). Processing studio shots should be quick work because the conditions of the exposure are controlled and identical for multiple exposures.
As I see it, you have a few practical choices:
Use the JPGs created in-camera. If they work, this eliminates several steps in your workflow.
Use Nikon's (or other) RAW converter to create TIFF files, and import those into Aperture
Learn how to set up the studio lighting so you get the RAW (and converted-from-RAW) results you want. Your goal isn't to light the subject so it looks right on the back of the camera -- your goal is to light the subject so your developed pictures look the way you want them to.
Figure out an Adjustment Preset in Aperture that gives you what you want. Aperture has robust tools for changing the look of your photos. If you post a RAW, some of the forum members here (myself included) are likely to essay adjusting it to your specifications (which, of course, you should provide).
Change the settings for RAW conversion in Aperture. This, imho, is least likely to help you in the long run.
I'm sure there are other ways 'round this RAW boulder -- those are just the ones that occur to me.
Good Luck.
Message was edited by: Kirby Krieger -- first graph clarified.

RAW import parameters in external service

Hi all,
I'm extending an application that has been written by somebody else.
I need to connect to an RFC using CAF external services.
In this RFC one of the input parameters (GUID) is of the type RAW. When I import an external service (based on this RFC) into the NWDS. I then add is as a dependencie to my Application service, generate a webservice of my application service, build and deploy the CAF project.
When I now go the the wsnavigator, open my application service and select the operation I want to test. I fill in the paramters and send submit but the RAW import parameter GUID is not being passed on to my RFC.
In fact when I look at the SOAP message that is being sent, the GUID parameter is empty (it fills in 'AA==' while I inserted '4A53589C71132123E10000009959C278' as value).
POST /CRMActivitiesWS2/Config1?style=document HTTP/1.1
Host: lumnrs61.luminus.int:54200
Content-Type: text/xml; charset=UTF-8
Connection: close
Cookie: <value is hidden>
Cookie: <value is hidden>
Cookie: <value is hidden>
Authorization: <value is hidden>
Content-Length: 416
SOAPAction: ""
<?xml version="1.0" encoding="UTF-8" ?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body>
<pns:ReadOfferData_R xmlns:pns='urn:CRMActivitiesWS2Vi'>
<pns:offerGuid>AA==</pns:offerGuid>
<pns:portalId>FOA_test</pns:portalId>
</pns:ReadOfferData_R>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
I think this has something to do with the conversion of the input field to the RAW dataformat. Does anybody know how I can solve this?
Kind regards
Wouter

Solved on my own...

Why won't LR5 automatically save my original RAW imports from Nikon D7100?

Why won't LR5 save my original RAW imports from D7100. I can import them and process them but the originals are then lost. What am I doing wrong? With every other camera the original RAW image is saved in the library.

Another guess as to what is happening is that your Folders panel section was accidentally closed/hidden in Library.
To fix this, right-click on another section name in the lefthand panel and put a checkmark next to Folders.
The possible sections on the left in Library are:
Navigator (which cannot be closed or right-clicked on)
Catalog
Folders
Collections
Publish Services
A variation of this situation would be that instead of hiding the Folders section entirely, you've merely collapsed it.
To reveal the list of folders click the triangle that is pointing towards Folders so that it points down at a now expanded Folders section.

RAW import Sony ILCA-77M2 funktioniert in Lightroom 5 nicht. Wer kann helfen?

RAW import Sony ILCA-77M2 funktioniert in Lightroom 5 nicht. Wer kann helfen?

The A77.2 is not listed as a newly supported camera in the ACR 8.5 RC available at Adobe Labs: http://labs.adobe.com
But it could be added before the final release of ACR 8.5, sometime before July 31st, when the RC expires. Otherwise, a new ACR plug-in is released every 3 or 4 months.

RAW import won't work after OS upgrade

I used to import my digi-cam (Ricoh GX-100) RAW files into iPhoto without any problem, but since I updated to 10.4.11 iPhoto doesn't recognize these RAW .dng files anymore. What can be done about this? Strangely, this particular camera never has been on the supported camera list for iPhoto, but why did RAW import work before and why doesn't it now?
I should add perhaps that the cause for the malfunction could also derive from the usage of Onyx (which I downloaded from the apple-site), which I used for system optimization by clicking on the "prebinding" option - however, most likely this has nothing to do with above problem
thx

zoranT:
Welcome to the Apple Discussions. A lot of users have experienced importing problems after upgrading to Leopard and not just with RAW files.
Since OnyX is not Leopard compatible, there's a beta version available that is, it might have a bearing but I wouldn't bet on it. Try the beta version to re-optimize and see if that helps.
See bdorf's post this this topic on how he fixed his importing issue: http://discussions.apple.com/message.jspa?messageID=6181481#6181481. He hasn't gotten back to me on how he re-installed Leopard but I'm guessing it was an Archive and Install.
Happy New Year
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

Raw Import Preview from EOS 30d

Hi All,
I've got a question regarding RAW importing from a Canon EOS 30D. There are no previews only blank boxes with the image no. at the bottom. If I'm importing jpegs from the camera it's fine I can see the preview image. Also, is it possible to tell Aperture not to import duplicate images? Kind of like iphoto does where it gives you the option of ignoring images on the card that are already in the library.
cheers
M.

Mike,
Thanks for your response. The camera was directly
connected to my MBP in both instances (with Aperture
and Lightroom). I do, however, have a SanDisk card
reader on order. Will see if that makes a difference.
Just an update: got the card reader yesterday and did a couple of RAW shoots to test-import previews showed up right away. Hopefully this has fixed the problem.

Mail 4.5 import trouble

Mail 4.5 imports mbox files double up. The mbox files import trouble free into other mail programs, but not Apple mail? Does any one have a solution?

Actually smaller attachments are downloaded automatically, or perhaps it depends on attachment type?
Try the same with say 2MB .PPT file .. email the file to yourself. It will come through as "click to download" icon (see image above). Trash the message (before SAVE or clicking on attachment), now try opening it in the trash or pulling it back to inbox and then open it. Attachment is gone and you get garbage - clearly extra data is there but is non-readable.
Not a big issue for a single user - potentially very big issue for an admin supporting large number of end-users, some of which are recent Outlook transplants.
Btw, I'm using IMAP server and I have enabled "Store deleted messages on the server"

Page import trouble

Hi and thanks for previous answers, but my page import trouble continues.
I have now compiled a class, myBean.class and placed it in this folder ...
ROOT/WEB-INF/classes/peters/beans/
when I use ...
<%@ page import="peters.beans.*" %>
Tomcat finds the path, but using
<%@ page import="peters.beans.myBean" %>
a class not found exception appears.
I can�t understand why, it it something wrong with the public/private properties in myBean?
This is the syntax ...
public class myBean
  ��private String sName="Pette";
   public myBean()
   public String getName()
     return sName;
Thanks for any answers.
Have a nice day / reg. PG

Jippy, I found a solution!
First I added the line - package pg; - to the testBean class and placed the file in ROOT/WEB-INF/classes/pg
The I used the following jsp-tags in my .jps-file
<%@ page import="pg.*" %>
<jsp:useBean id="theBean" scope="page" class="pg.testBean" />
/pg

CinemaDNG 4K RAW Import Needed

Hi,
I've downloaded the new firmware and my BlackMagicDesign 4k cinema camera shot in Raw.
But I can't import the 4K DNG files directly into Premiere Pro CC. It doesn't reconize it.
When will it be supported by Premiere (I really need it soon) ?
Many thanks
Jean-Michel

No :(((
S pozdravem
Martin Zeman
www.DAtelier.cz
www.RAWpictures.cz
7. 8. 2014 v 14:21, jmtari <[email protected]>:
CinemaDNG 4K RAW Import Needed
created by jmtari in Premiere Pro - View the full discussion
Hi,
do we have any news for this request ? I will soon shot an add with my BMD 4K and I REALLY need 4K raw support in Premiere Pro and Speedgrade.
Thanks
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at https://forums.adobe.com/message/6619539#6619539
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page:
To unsubscribe from this thread, please visit the message page at . In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Premiere Pro by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

Trouble with RAW import

RAW files will not import. Told the program does not recognize the file type. Worked fine before upgrading to version 4.1.

All prior imported photos can still be viewed. While selecting photos for import I can open the picture to look at it, no problems. The only problem is once I choose to begin the import it says the files cannot be read. Files have the .CR2 extension same as prior photos and no changes were made to the file format on the camera in between. The only thing that changed as far as I can tell is the update that was released.

Odd color correction on raw import

I have a Canon G9 that I've had converted to shoot IR. I'm having trouble with Lightroom on the CR2 files the camera is putting out. Example here:
http://gallery.me.com/hteasley#100119
The first one is what I expect: what I see in the camera, what the JPEG looks like, what the CR2 file looks like when I import it into iPhoto, and interestingly enough, what the CR2 thumbnail looks like in Lightroom on first import. But when I use the Lightroom loupe on the file to look at it, it gets rendered to look like the second image in that gallery, which is terrible.
To be clear, I'm not talking about having done any in-camera editing of the raw files, and I'm not talking about the JPEGs. I'm talking about iPhoto bringing the file in how I would say "correctly", and Lightroom always adjusting it to be "hideous". I've changed camera profiles, and can't find one that looks like the iPhoto version. I've worked through various Hue/Sat adjustments within Lightroom and can't recover the image to look like the correct version.
What is Lightroom doing? I can't find any setting that results in Lightroom keeping the file looking like it does in the import preview, how it looks in the thumbnail before I view it with the loupe. Any help would be much appreciated.

The image you see in iPhoto is not the rendered RAW file it is the jpg preview file embedded in the RAW file you see on the back of the camera (iPhoto does not render RAW files). This is the same as the initial image you see for a moment in LR when you import the file, until LR renders the RAW file. LR doesn't make any "changes" to the file, but imports it and renders it acording to any settings you may have made in LR. The colour settings will be found in the calibration box in the develop mode and there may be different settings availble according to the camera you are using.
See number 6 in the top ten gotchas here. .
As you have made a conversion to your camera none of the existing camera calibrations will apply and you will need to use Adobes DNG editor to create a new one

Difference in TIFF and RAW import with ACR (how to fix)?

I'm experimenting with a workflow, so whilst this may seem like an odd thing to want to make work, I have a geniune reason for doing what's described below:
I have Canon CR2 RAW files from a 7D, Photoshop CS6 13.01 64bit, with ACR 7.1.0.354, running on Windows 7 64bit.
1. I import a CR2 image via ACR, with no changes to any sliders; opening it as Adobe RGB (1998); 16bit
2. I then save the image as a TIFF file, leaving "ICC Profile: Abode RGB (1998)" selected in the Color section of the file save dialog
3. If I then close all files, and reopen the CR2 and TIFF image, they (as expected) appear to be identical
4. After closing all files again, I then open the CR2 and make an exposure adjustment (e.g. -1.00)
5. Using Bridge, I select the TIFF file, right click and select Open in Camera Raw. I make the same exposure adjustment as for the CR2
6. Now, the adjusted CR2 and adjusted TIFF are different. A colour shift is noticable, and for a severe exposure change (i.e. +4.00) the shadow detail in the CR2 is a lot lighter
Here are two cropped areas from the files (with a 4 stop push), showing some branch/leaf and grass detail respectively. The TIFF has a greener colour cast for the grass, but much darker shadows:
TIFF
RAW
I appreciate that the CR2 is still a RAW file, and as such has the original Bayer pattern data, but is there any way I can make ACR adjustments to a TIFF (taken from a CR2) to behave in the same way as the original CR2?

ssprengel, Jeff, JJMack - thanks for the constructive replies
station_two - after your use of mildly aggressive language ("What seems to escape your grasp") in your first post, I had money that your subsequent response(s) would be on the lines of "I'm too busy to explain it to people like you". Thankyou for confirming my expectations (sometimes I wonder if some people engage in forum discussions for the sole purpose of trying to get themselves [and possibly others] riled)
So... back to trying to find a construcive solution: If the algorthirms for the adjustments in ACR do operate directly on the Bayer data (before demosiacing to RGB per pixel) then operating on the TIFF (or any other demosaiced RGB data) will indeed be a non-starter. Without (probably unlikely) input from an Adobe developer however, we can't know for sure.
> So RAW numbers after debayering to RGB are linear with numbers of photons within a particular color (R, G or B), while TIF numbers are assumed to be linear with human-vision sensitivity
Understood (I'm familiar with gamma, camera sensor behaviour, exposing to the right etc). Ultimately though, it should be possible to produce an RGB file that is also linear (i.e. not adjusted for human vision) to then bring back into ACR. However, if that's simply not possible with ACR, then that's also a non-starter (and wouldn't help anyway if the adjustments operate on the Bayer data directly).
I did look briefly into opening the RAW as a smart object, but sadly I didn't think that'd help. The goal I'm trying to achieve is an experimental idea to blend parts of images together from multiple exposures; but to achieve a single RAW file with that data as if it came from the camera (thus it could be brought into ACR to get the benefit of - from my point of view - the useful and intuitive adjustment sliders). Clearly that would require reverse engineering the particular RAW format for the camera being used (and each and every camera you'd want to support) - thus, it's not really practical.
I'd hoped to be able to convert (without edits) the RAW images into TIFF (or some other lossless RGB container that I can read programmatically), do the blending to produce a single TIFF, and then bring that back into ACR.
Whilst it's more convoluted, I suppose it might be possible to generate the unedited TIFF files purely for the purposes for getting data about the images, then using that to create a set of masks. Then, as Jeff suggests, perform adjustments to the RAW files in ACR, and use the masks to blend the imported (and now corrected) RAWs into one image. Not ideal, but perhaps worthy of more experimentation.

RAW import from Lumix FZ1000 not working in new Photo app for Mac

I am not able to import from my Panasonic Lumix FZ1000 the RAW pictures into the new Photo Mac app. They are even not shown when inserting the SD card into my MBP.
I am only able to get the JPEG ones.
FZ1000 RAW is supported according Apple and was working with previous app.
Any idea?

I am able to import them, but I cannot edit them as RAW files. They behave like .jpegs. So correcting exposure for example is a horrible experience. My 5D Mark II files behave as they did in Aperture, so it is the FZ1000 RAWs in particular that are problematic.

Export/import troubles

Folks,
a ct. has exported/imported more than on page with a batch job without any errors (WOW!). But when calling the different pages they are not the same. After dropping a page from portal UI and reimporting one single page the content is okay. But when doing this for another page, he got the same trouble again. Has anybody have a similar behaviour when importing more than on page?

When we export/imported a couple of pages, HTML portlets from one ended up in the other and vice versa. This completely screwed up the application and we had to restore from backup.
Also, one page with tabs dropped the content for one HTML Portlet per tab during the export/import process. The odd thing was that the title was still there for the affected Portlet...just the content was gone. This was a consistant, reproducable error.
And one more: any images added to Portal (custom sub tabs, for instance) displayed as missing images, and had to be re-added after import. An odd behavior here was that they only dissapeared for certain users, but other users could see them. After re-adding them, all could see them again.

Raw import trouble

Similar Messages

Maybe you are looking for