Separate JPEG from Raw , IPad4

Hello and sorry for my english
I am an amateur photographer and always store my photos as a jpeg and raw.
If I my pictures from the camera onto the iPad safe, I also see from the photos, the two formats have been saved.
I have an external hard drive, Intenso Memory 2 Move, on which I store my images via Wifi.
If I will now save RAW and Jpeg isolated on my external drive just to keep the jpeg format and deleted the Raw.
Is there a way to send the files before to my External to separate?
greeting
AROJA

I've heard many others raising the issue of an auto-jpeg feature - kinda like auto-write xmp, except auto-write jpeg.
I agree this would be nice, obviously some sort of "stability" check would be needed so it isnt constantly writing jpegs as you edit. Lightroom employs a form of this already for the xmp - meaning it doesn't update xmp every brush stroke, but accumulates several strokes before updating, so its more efficient...
If you could define multiple jpegs to keep - with the raws, or a separate tree - even better. That would obsolete all the tree output plugins and publishers.
The publishing feature was intended to fill this need (albeit manual only), but it suffers from the inability to publish to original directory, and/or an external tree.
I'd like to see a manual mode too, that accompanies a new "Done for now" function - so when you say "Done for now", it saves xmp, jpeg(s), snapshot, and optionally locks the file so unapproved changes can no longer happen to it. Then if you could define multiple "done for now" presets that include initiating publish service and exports, then the work-flow becomes: 1.import, 2.edit, 3.done for now - and thats it (maybe repeat 2 + 3 in the future). i.e. no more manually initiating the exports, publish services, snapshots, saving of xmp, ..., and whatever else you do when you're done.
In the mean time, I may make some of this part of an up-n-coming "Sidekick" app + plugin combo when I get to it.
Presently, I dont use publishing services, and I have ExportManager to consolidate exports (which includes TreeSync), so my workflow is: 1.import, 2.edit, 3.done for now (save xmp+snapshot, and lock via ChangeManager), 4. initiate consolidated exports...
Rob

Similar Messages

Automatically export to JPEG from RAW images

RAW images are preferred form of shooting for many photographers. And, Lightroom is great at managing and developing these images. However, we increasingly use/view these images outside Lightroom and away from the PC where we do most of the development. For example, I use a DLNA server which shows off my entire image collection to big screen television (which can act as a DLNA client). The same DLNA server is used to send images to our smartphones (my wife loves to show all kid pictures anywhere she - without having to carry the pictures on the phone).
Most other applications that use these images, do not work on RAW images and JPEG images must be exported manually from Lightroom. This becomes increasingly difficult to manage and keep track of while developing RAW images. How many RAW images need to be exported? How many images did I touch since the last time I exported them?
Currently, I am using the following process to manage this:
1. I created a smartlist which contains images that are edited after "a particular date".
2. I select all images in this smartlist, and use Lightroom3's export function to export them all as JPEG, to the same folder as original.
3. Once the export is completed, I modify the smartlist to change the "particular date" to today's date.
I plan to repeat this procedure every so often (once a week or so).
It would be great if Lightroom had a feature such that it always keeps "JPEGs exported" for all RAW images (with the latest development settings of course). This could be a process that could occur in the background or at a user-specified time/event (e.g. when one closes Lightroom). User should be able to specify where the exported JPEG images should be put to and with what name (I prefer in the same folder as RAW but other users may have other preferences). User should be able to select if this is only done for RAW images or also for JPEG and other formats (in which case, should the exported image override the original or not). The exported images should be (optionally) automatically included in the Lightroom catalogue and stacked with the original RAW image.
Mainly, the entire process should be completely transparent to the user. A collection of JPEG images - corresponding to the latest development settings for the RAW images - should be always available.
Osho

I've heard many others raising the issue of an auto-jpeg feature - kinda like auto-write xmp, except auto-write jpeg.
I agree this would be nice, obviously some sort of "stability" check would be needed so it isnt constantly writing jpegs as you edit. Lightroom employs a form of this already for the xmp - meaning it doesn't update xmp every brush stroke, but accumulates several strokes before updating, so its more efficient...
If you could define multiple jpegs to keep - with the raws, or a separate tree - even better. That would obsolete all the tree output plugins and publishers.
The publishing feature was intended to fill this need (albeit manual only), but it suffers from the inability to publish to original directory, and/or an external tree.
I'd like to see a manual mode too, that accompanies a new "Done for now" function - so when you say "Done for now", it saves xmp, jpeg(s), snapshot, and optionally locks the file so unapproved changes can no longer happen to it. Then if you could define multiple "done for now" presets that include initiating publish service and exports, then the work-flow becomes: 1.import, 2.edit, 3.done for now - and thats it (maybe repeat 2 + 3 in the future). i.e. no more manually initiating the exports, publish services, snapshots, saving of xmp, ..., and whatever else you do when you're done.
In the mean time, I may make some of this part of an up-n-coming "Sidekick" app + plugin combo when I get to it.
Presently, I dont use publishing services, and I have ExportManager to consolidate exports (which includes TreeSync), so my workflow is: 1.import, 2.edit, 3.done for now (save xmp+snapshot, and lock via ChangeManager), 4. initiate consolidated exports...
Rob

How do I delete the jpeg from raw+jpeg imported images?

Hi,
Back in the day, I shot lots of images using raw+jpeg and imported them into Lightroom. Now I realize those jpegs add no value and I'd like to recover the disk space that they're collectively occupying.
Is there a good way to:
1. Identify all images in a catalog which have raw+jpeg?
2. Remove just the jpeg for these images?
Thanks!

$$PhotoHobby wrote:
I'm very hesistant to take the chance on any 3rd party script.
Just so ya know, what the deletion feature in RawPlusJpeg does is ultra simple:
1. Identifies extraneous jpeg files.
2. Presents them for you to review.
3. Deletes the extraneous jpeg files, if you approve. (puts them in the recycle bin if possible).
It does nothing to the database nor anything else.
You sync folders with 'Treat JPEG files next to raw files separately' afterward, which is what sets the database right.
The only potential for trouble is the criteria for determining which jpegs are extraneous.
It has no direct access to the database, so what it does is check for jpegs with same base name as raw (which *must* be present in catalog, and on disk), that aren't in the catalog, which includes the jpegs associated with RAW+JPEG (imported as a unit), *and* any jpegs that were imported separately, but subsequently removed from the catalog, or had never been imported.
So, what it does will be the perfect thing to do, *if* you first synchronize folders (with 'Treat JPEG files next to raw files separately' checked) to pull any jpegs in to the catalog that were previously imported separately, but may have been inadvertently removed from the catalog (or had never been imported), before invoking the delete feature of the plugin.
Note: You must do that for any manual procedure too, or you will have the same problem, except in the manual case, you won't have the benefit of the plugin checking your work, and presenting the files to be deleted, before you commit.
It's your call, obviously, and to save Geoff the Kiwi from pointing this out: the plugin comes with no guarantee, warranty, or any other kind of tea.
Consider backing up catalog and photo files before doing this maintenance, whether manual, or plugin-assisted.
In my opinion, the plugin-assisted method is much safer than the manual method, which is the only reason it was written, *not* to save steps, although it does that too. For example, you can not, with the plugin, delete any jpegs that do not have a corresponding RAW in the catalog and on disk, period. - unless there is a bug of course, but there probably isn't , at least not one that would change the aforementioned assertion... - it wouldn't take much of a bug to cause it to barf, but it would take a big bug to cause it to delete files that weren't on the list, etc...
Seriously, I don't think you have to wait for Adobe on this one. I wouldn't (I didn't - my catalog is all clean now!...).
PS - there is *very* little recorded in the database about the jpeg sidecar - it's existence upon import (when "as a unit") - that's about it. Most of the funny business about updating that we were fumbling with above, stems from the software (and the person at the keyboard), *not* the database. Syncing folders with 'Treat JPEG files next to raw files separately' checked, once the jpeg sidecars have been cleaned up, *will* set the database straight!
Cheers,
Rob.

Unlink JPEGs from RAWs

When dealing with a folder containing RAWs and their associated JPEG files (either JPEGs processed from the RAWs or when shooting RAW+JPEG in camera), then Bridge will copy / move the JPEG images as well when you copy / move the RAW images. How do I turn this behaviour off, so it will only copy / move the RAW files that I've actually selected?

Try re-install iPhoto:
To re-install iPhoto
1. Put the iPhoto.app in the trash (Drag it from your Applications Folder to the trash)
2a: On 10.5: Go to HD/Library/Receipts and remove any pkg file there with iPhoto in the name.
2b: On 10.6: Those receipts may be found as follows: In the Finder use the Go menu and select Go To Folder. In the resulting window type
/var/db/receipts/
2c: on 10.7 they're at
/private/var/db/receipts
A Finder Window will open at that location and you can remove the iPhoto pkg files.
3. Re-install.
If you purchased an iLife Disk, then iPhoto is on it.
If iPhoto was installed on your Mac when you go it then it’s on the System Restore disks that came with your Mac. Insert the first one and opt to ‘Install Bundled Applications Only.
If you purchased it on the App Store you can find it in your Purchases List.
Regards
TD

Why does my PS work better than my Lightroom 5 exporting jpegs from raw files?

So,
I'm editing some raw files with Lightroom 5
but when I export the jpg file, the result is terrible, it looks washed out, loses contrast, noise levels are higher than the edited file on suite
However, if I do the same thing using camera raw through PsCS6, the exported jpg is perfect. Any reason for that to happen?
've been reading a lot about color spaces, and I don't think is the case, since the same doesn't happen with photoshop.
Also, it might be worth mentioning I'm exporting B&W images
Thanks!

ok
just to illustrate the problem a little better, here's the actual difference
this is what I have in Lightroom after editing:
and here's what I get after exporting

Trying to make the jump from JPEG to RAW...

Hi all, I'm trying to make the jump from JPEG to RAW, and am hoping you might be able to help with a few questions.
When I open JPEGs in Lightroom's Develop module, the settings are mostly zero by default. But when I open RAW files, some of the settings seem to have non-zero default to values.
Am I correct to think these settings are from metadata saved into the RAW file when I took the picture? eg, the camera saves the White Balance settings as metadata within the RAW file, even though the White Balance settings don't actually affect the image data itself. And so when I open that RAW file in Lightroom, it'll apply the White Balance as recorded within the file, making that a non-zero default.
Is that about right?
Does Lightroom similarly 'pre-set' other values when importing RAW files? (I ask because I seem to have non-zero settings for Blacks, Sharpening, as well as the Color slider under Noise Reduction.)
Meaning: I'm not quite sure "how much work" Lightroom is doing by default when I import RAW files, and how much I need to do to at least reproduce what my camera would do in making a JPEG.
For example, even though Color under Noise Reduction is given a value -- Luminance, also under under Noise Reduction, is left at zero. And the picture looks a bit grainy. Would my camera have processed some Luminance Noise Reduction? If so, is there a way to get Lightroom to help get that pre-set too?
Basically, is there a rule of thumb for how a novice should import a RAW file and have it reasonably "at least as good" as what the JPEG would have been?
Thanks very kindly, -Scott

Given that the camera ships with so many special effect presets -- is there no built-in preset that could be named "Auto Camera" so to speak? Or might it be possible import such a preset that somebody else has made?
Lightroom, nor any other third party raw processing program will not read the camera settings beyond simple stuff such as white balance. So you cannot do this. If you go raw, you really have to change your mindset and completely ignore the in-camera jpeg styles. Just set it to a neutral style and learn what the preview on the camera means for the actual raw data. You will find that this gives you orders of magnitude more creative freedom afterwards as you will not be stuck with a burned in interpretation.
So (for me) even just making my own presets -- let alone making separate presets for every ISO -- all that seems a bit daunting.
There really is no need to at all. I don't use presets for example. I think they are a waste of time as it is extremely rare that two images need exactly the same treatment. You really are just choosing a different starting point. I start all my raw at a relatively neutral setting (but using a camera profile generated from a colorchecker!) and blast through a shoot very quickly. You'll learn how to recognize what modifications to the Develop settings images need and just do it. Then typically I use auto-sync or manual sync to modify similar shots (say a series of head shots taken shortly after each other). I work differently as most of my photography is landscape, but a typical workflow for many photographers that do more people/style/event stuff is to import all the raw and start culling them with pick/reject flags and refine collection. You'll arrive at a subset that is worth looking at more closely and to finetune their development. The conservative default rendering helps you here because you'll quickly see what images are simply badly exposed, not in correct focus, etc. and you can reject them.
Think of your raw as the unprinted negative. It represents a nascent image. One that still has to form completely. A jpeg is like a polaroid. The image style is pretty much chosen for you by the film maker. There is very little you can do to it afterwards without it breaking down. Raw gives you much more freedom but it does come with a learning curve and it is more tasking for your equipment. Many people including many pros are simply not interested (or don't see the pay off) in this part of the creative photographic process and just shoot jpeg, which is a fine approach (just not mine). Lightroom can help you there too to quickly find the best images in a series, keyword, caption, and disseminate.

How do I process multiple files and turn them from raw to jpeg

How do I process multiple files and turn them from raw to jpeg. Ive tried and it seems to go through the files but doesnt seem to process them or store them in the selected folder

Yes that was the first thing I did. Then I used the process multiple files and selected a new folder to put them in and selected use open files and selected to turn them into jpeg. The images flash on the screen like they are being processed, but the folder never appears in library. Is it possible because there are a couple 16 bit files open that this corrupts the task. Do I need to create the folder first. Will elements not create the folder on its own.
Thanks Vince

"Error while relocating" after deleting RAW from RAW+JPEG pairs (Important FYI)

This is not a question, but something I recently discovered that I think will be important for the Aperture community.
Not too long ago, I asked a question about how to remove the RAW files from RAW+JPEG pairs. The concensus was that it couldn't be done through Aperture, but that one could delete them through the Finder. The answer I got (and that has popped up in other threads on similar topics) was "it's probably not wise, but as far as I know, it won't have an adverse effect." I don't think any response along these lines has been able to point to a specific problem that can arise from such a "hack." Well, I found one today...
It appears that if a user uses Finder to "break" RAW+JPEG pairs by deleting the RAW file and leaving the JPEG (and I assume this goes for deleting the reverse), Aperture will NOT be able to "Relocate Originals..." Instead, "Aperture will return the error: Error while relocating (File not Found): "(null)". I ran into this error the other day while trying to change my file structure by relocating all files. I regularly ran into this error, and it was only after some extensive that I was able to narrow it down 100% of the time to the RAW+JPEG pairs I had "broken." I haven't encounterd any other adverse behavior from "breaking" these file pairings, but this one, at least, could be serious.
So, for future reference, I think the response by the Aperture community when someone asks "How do I delete the RAW file from RAW+JPEG" pairs, should be "Use Finder if you must, but please note Aperture will not be able to 'Relocate Originals..
PS This should NOT be understood as a criticism of those who have responded to this question in the past. There's obviously no way to know about these little quirks until one of us stumbles across them. I hope this information will be helpful going forward, both as a caution when deleting one of the pair, and as a possible answer for the "Error while relocating" message.
PPS I don't think I ran across an explanation for this when I originally searched for the error message bolded above.
If someone has already provided this information, my apologies.

Frank Caggiano wrote:
Interesting the last post before this one you posted was back in May 2011 Removing RAW, keeping JPG?
Thanks for that thread. That helps jog ye olde memory. As such, I would edit my original thread to read "The concensus I gathered from researching multiple responses to questions similar to mine was that it couldn't be done through Aperture*, but that it was possible from Finder though highly inadvisable." I won't bother recreating my research at the time (not even sure I could, since it was more than two years ago), but suffice it to say that the thread you've linked was not my sole encounter with this problem. I do appreciate that you've reminded me that this was not something I had done solely through numerous posts on Apple Discussions. I imagine I likely spent time reading multiple posts here and elsewhere, uncovering the concensus (which i think is still a fair term) that it could not be done through Aperture*, could be through Finder, but was inadvisable.
*This is still accurate, afaik. You cannot delete the pair from a RAW+JPEG pair in Aperture. Exporting, then deleting in Finder, then reimporting is still not something "done in [entirely] Aperture."
Frank Caggiano wrote:
No one actually told you to delete anyting in in the Finder you came up with this yourself as your own solution
This comes from the critical mistake on my part of not making clear that I was paraphrasing multiple responses rather than saying "Bob told on a Monday that i should..." That is one huge mea culpa and I'd edit it if I could. To be clear, my comment that "it's probably not wise, but as far as I know, it won't have an adverse effect" is a paraphrase of multiple answers to the broad question dealing with how Aperture handles files that have been deleted in Finder. At the time, it was known that you could delete a file in Finder, that Aperture could be made to accept that, that it might cause issues further down the road, but that those issues were unkown. I paraphrased that but failed to make it clear that's what I was doing. Again, my apologies.
Frank Caggiano wrote:
So I'm not really sure what it is you are coming back here now to say? There was no 'consensus' to do this, it was your own 'solution'
In this respect, I think you've misunderstood me. At the time I made this post, I still was not seeing a direct connection between deleting files in Finder and adverse consequences in Aperture (or perhaps I should say my searches did not turn up such a connection). As such, I made this post to provide the community with clear evidence of why one should not delete one-of-a-pair files in Finder. Again, I may have simply missed the thread that detailed that to do so would result in a null error when relocating Masters. That said, in July 2013 I had been pulling my hair out trying to figure out why I was getting the null error and I did not see a thread that asked "have you deleted files in Finder" as a way to troubleshoot.
Hopefully, I've cleared up any confusion now. To bring this all back around to my original point for the thread, I intended it to (1) offer a more direct way to troubleshoot the null error on relocating Masters, and (2) to offer a cautionary tale for those who choose to delete one of the RAW+JPEG pair in Finder. There are better (though more time- and space-consuming) ways to get it done, and my original post should help demonstrate why.

Deleting all the JPEGs from my RAW+JPEG pairs

Parts of my Aperture library are only JPEG, only RAW or RAW+JPEG. I am ready to dump all the JPEGs where a RAW is available. Any idea how to do this? I'm not too great at navigating Aperture. I'd prefer to do this from within Aperture, but any suggestions would be great.
(Come to think of that, I would also like to do that with some of the pictures I have imported to my iPad with the Camera Connection Kit.)
Thanks in advance to anyone who can help...

I guess you could use the brute force option and export them as masters, delete them from the library and then re-import only the RAW files. You would lose any adjustments and metadata work that way.
With less brute force, but even more work - a slightly modified procedure of Thomas's approach.
Make sure, you have all images set to use the raw version as original (From the main menu bar: Photos > Use Raw as Originals).
Export the Raw originals, with IPTC tags included.
Flag the old versions in the library.
Import the raw originals again and create an album with both the old and the new versions, sort it by capture date, so that you have the old versions and the newly imported side by side.
Use the Lift & Stamp tool to transfer all metadata tags and edits from the previous version to the new versions.
Delete the flagged old versions.
If only a few of your images have adjustments or tags, you could use a search for "Keywords are applied" or "Adjustments are applied" to selectively stamp only the images that need readjusting.
The quick and dirty approach - simply deleting the redundant jpegs from the Aperture library - will not work - I tried with a test library. Aperture will not forget that there is supposed to be a jpeg version and you will continuously see warning messages that thejpeg is missing.
Regards
Léonie

JPEG is corrupted when saved in B&W from RAW

Hi,
today I ran into this issue when saving black and white pictures from Raw file.
Camera RAw 7.3 opens normally just like always and lets me save picture in color.
It lets me save picture in BW, but the JPEG tha comes out is corrupted file that looks like this (see below):
When i try to open that corrupted JPEG in Photoshop 6 I get an error message saying:
"The embedded ICC profile cannot be used because ICC profile is invalid. Ignoring the profile. "
After clicking "continue" on the error message I am able to load the picture in PS6- however when i go to Image>Mode picture is appearing a RGB, not a Greyscale as it should be.
Any ideas why this is gappening an how to fix it?
It seems that new Raw Plug In is casuing it- I uninstalled Photoshop, installed Camera Raw 7.2 and its seemed to be OK. As soon I upgraded to 7.3 I get the same error.
is there a way to downgrade it to 7.2 without uninstalling PS6? Manual download and rewriting 7.2 over .3 doesn't seem to work.
Thanks!

I can confirm the issue...it's been reported. In the meantime, actually opening the image into Photoshop and saving as a JPEG works...you could simply open the image into Photoshop to save as JPEG or adjust the images in ACR and then use Image Processor from Bridge. And no, you can't easily install 7.2 over 7.3. Since both are not currently offered as seperate downloads (updater only) you would have to find the 7.2 download...the Mac and Windows downloas are mentioned in this thread.

Aperture Exporting JPEG's from RAW: file size and quality questions?

Hey Everyone,
So, I'm using Aperture 2 and I've got some questions about exporting from RAW to JPEG. I shoot with a Nikon D70 so original RAW files are 5-6mb in size. After doing some basic post processing when I export the pics at "full size" with picture quality of 11 out of 12 then the resulting JPEG is about half the file size of the original RAW file. For example a 5.6mb RAW becomes a 2.6mb JPEG. The resolution in pixels per inch and and the overall image size remain unchanged. Have I lost picture quality due to the exporting JPEG being smaller in file size?
My friend who works with me prefers to edit in Photoshop and when he follows the same workflow his saved JPEG from the identical RAW file in Photoshop is minimally smaller in file size, say 5.6mb to 5.3mb. He's telling me that my Aperture edited photos are losing quality and resolution.
Is he right, are my pics of lesser quality due to being a smaller file size? I've always been told that the quality of a picture is not in the mbs, but the pixel density.
I've bee told that Aperture has a better compression engine and that the resulting files are of the exact same quality because the PPI and image size are the same. Is that what explains the much smaller file sizes in Aperture?
I tried changing the picture quality in the export menu to 12 out of 12, but the resulting JPEG then becomes larger than the original RAW at over 7mbs.
Can someone please help me understand this better? I don't want to lose picture quality if that is indeed what is happening.
Thanks in advance for your help.

mscriv wrote:
So, I'm using Aperture 2 and I've got some questions about exporting from RAW to JPEG. I shoot with a Nikon D70 so original RAW files are 5-6mb in size. After doing some basic post processing when I export the pics at "full size" with picture quality of 11 out of 12 then the resulting JPEG is about half the file size of the original RAW file. For example a 5.6mb RAW becomes a 2.6mb JPEG. The resolution in pixels per inch and and the overall image size remain unchanged. Have I lost picture quality due to the exporting JPEG being smaller in file size?
JPEG is a "lossy" file compression algorithm. Whether Aperture or PS, *every time a JPEG is saved some loss occurs*, albeit minimal at the 11 or 12 level of save, huge losses at low save levels. Some images (sky, straight diagonal lines, etc.) are more vulnerable to showing visible jpeg artifacts.
My friend who works with me prefers to edit in Photoshop and when he follows the same workflow his saved JPEG from the identical RAW file in Photoshop is minimally smaller in file size, say 5.6mb to 5.3mb. He's telling me that my Aperture edited photos are losing quality and resolution.
*Both of you are losing image data when you save to jpeg.* IMO the differences between the apps is probably just how the apps work rather than actually losing significantly more data. The real image data loss is in using JPEG at all!
Is he right, are my pics of lesser quality due to being a smaller file size?
I doubt it.
I've always been told that the quality of a picture is not in the mbs, but the pixel density.
The issue here is not how many pixels (because you are not varying that) but how much data each pixel contains. In this case once you avoid lossy JPEG the quality mostly has to do with different RAW conversion algorithms. Apple and Adobe both guess what Nikon is up to with the proprietary RAW NEF files and the results are different from ACR to Apple to Nikon. For my D2x pix I like Nikon's conversions the best (but Nikon software is hard to use), Aperture second and Adobe ACR (what Photoshop/Bridge uses) third. I 98% use Aperture.
I tried changing the picture quality in the export menu to 12 out of 12, but the resulting JPEG then becomes larger than the original RAW at over 7mbs. Can someone please help me understand this better? I don't want to lose picture quality if that is indeed what is happening.
JPEG is a useful format but lossy. Only use it as a _last step_ when you must save files size for some reason and are willing to accept the by-definition loss of image data to obtain smaller files (such as for web work or other on-screen viewing). Otherwise (especially for printing) save as TIFF or PSD which are non-lossy file types, but larger.
As to the Aperture vs. ACR argument, RAW-convert the same original both ways, save as TIFF and see if your eyes/brain significantly prefer one over the other. Nikon, Canon etc. keep proprietary original image capture data algorithms secret and each individual camera's RAW conversion is different.
HTH
-Allen

How to have iPad (iOS 5) import only the JPEG from a RAW JPEG pair?

I have an iPad 2 16 GB, running iOS 5. I also have a Canon EOS 7D. I purchased a CF Card Reader for the iPad (see http://store.micgadget.com/card-readers/280-ipad-2-cf-card-camera-connection-kit .html) so that I can view and edit photos quickly in the field, without having to lug my laptop around. To make this easier, I set my camera to shoot RAW+JPEG. I shoot with the smallest JPEG files possible, still a relatively large for the iPad 2,592x1,728, with the idea that I'd only import the JPEG files to the iPad, but still have the RAW files to work with when I get back to my computer. This works great with one exception: the iPad doesn't allow me to import only the JPEG files, but grabs the RAW files along with them. As you can imagine, this fills up my iPad rather quickly, and takes quite a bit longer to import than if it only grabbed the JPEGs.
So here is my question: How do I have my iPad import only the JPEGs from the RAW+JPEG pairs on the memory card?
One workaround that helps slightly. If I connect my iPad to my computer after the import, I can go in via Image Capture, select all the RAW images and delete them, leaving the JPEGs behind. This is an underwhelming solution, but does save space after the fact.

What you are seeing is how Safari works now in iOS 5. There is no way to get that icon in Safari now. There other much better browsers available in the App Store. Look at iCab Mobile, Mercury, Atomic, ....
I have been running iOS 5x for so long now, that I don't even remember if that icon did appear in earlier iOS versions

Saving from bridge and converting from raw to jpeg

why can I not convert from raw to jpeg in bridge (camera raw) and save to a location different from the original

Yep sure can.
In bridge select your picture(s) then edit in camera raw.
In camera raw look in the bottom left of the camera raw dialog box and you will see a save as button.
This will allow you to save your raw files as jpg, tiff or pngs.

Can I create separate events for RAW files and JPEG files of the same photo?

I recently changed the setting on my camera to take both a RAW and JPEG image. I now have a large number of photos in both formats in the same event. I'd like to separate all the RAW and JPEG photos into separate events. Is it possible to do this in a batch process versus trying to move individual files? I use iPhoto '11, version 9.4.3.
Thanks,
Peter

Yes. Create a smart album with the criteria Photo is RAW:
Then you can select all of the photos in the smart album and use the Events ➙ Create Event menu option to move all of the RAW photos into a new event.
OT

When converting an image from raw to jpeg , the jpeg can look flat compared to the original raw image . Is there anything I can do about this ?

When converting an image from raw to jpeg , the jpeg can look flat compared to the original raw image . Is there any way to prevent this ?

Hi Joe , Thank you for your quick response . I am viewing the jpeg in Microsoft Picture Manager and Flickr. It 's not always really noticeable , but for example if I shoot into the light with dew on the grass , the dew glistens in LRoom and I'm happy with the shot but when I convert it to jpeg ,it looks dull. I have changed the setting to sRGB - from Adobe 1998 ,but don't see much difference. Kind regards Alberto.

Separate JPEG from Raw , IPad4

Similar Messages

Maybe you are looking for