PSE wish list - Auto stacking RAW + JPGs

I'm using PSE V10 and have a 'wish list' item for suggested improvements to the program.
A feature that would be extremely valuable to many users would be the ability to auto stack photos where there are the RAW + JPG images present in the Catalog. The JPG would end up on top of the stack.
This can be done manually but is tedious when there are many photos to deal with. Failing an automatic feature a single action shortcut to access the 'Stack | Stack selected photos' command would be useful.
a forum discussion on this topic is here: http://forums.adobe.com/message/4585792#4585792

As reported above I THOUGHT I'd found a shortcut suitable for stacking a JPG over a RAW.
However, the stack command in the main menu, which has the shortcut Ctrl+Alt+S will stack the RAW over the JPG whenever the RAW thumbnail is ahead of the JPG in the Catalog. I want the reverse to happen.
I found I can get the JPG to stack over a RAW, if the RAW appears before the JPG, by selecting the RAW first then with the Ctrl button down select the JPG. Then using 'Stack | Stack selected photos' in the mouse right click menu. However, this fails when using Ctrl+Alt+S whenever the RAW is listed before the JPG. Am I missing something?

Similar Messages

How to handle RAW+JPG?

Hi guys,
Just downloaded LR4 trial, and there is something I can't quite figure out.
I have a lot of RAW+JPG pictures (shot as RAW+JPG or previously converted from RAW to JPG with other programs), when importing them to Lightroom, I can choose to treat them as the same picture or as separate pictures.
At first glance, they should of cause be treated as the same picture (because they are the same picture), and they do indeed appear as "RAW+JPG" in LR, but how do I:
- View the JPG? (not critical, but it would be nice to be able to compare the JPG with the LR results)
- Add metadata (tags, title, caption, etc.) to the JPG file and not just the RAW file? (I have enabled "write metadata to file")
If treated as separate pictures, they behave as one would expect, but it is not that convenient to have two of the same pictures side-by-side.
- Can I auto-stack RAWs and JPGs?
- Can I write metadata (tags, title, caption, etc.) to the entire stack in one go?
And please don't give me the same answer, I keep reading over and over again, when other people ask the same question: "Why would you have RAW and JPG of the same image?" That is not the question, but I will answer it anyway :-)
1. I need JPG versions of my pictures for e-mail, web, viewing on my TV etc.
2. I REALLY don't want to be dependent on LR in the future. If I have spend hours and hours fine tuning my pictures, and only have them saved as RAW, I would need LR till the day I die. And it doesn't end there, my kids, my grand kids and so on, would also need LR to view the pictures (at lease in the quality I would like them to be viewed).
~Frank

That was also my feeling, that Lightroom's support for such is pretty little.
Because it is not LR's concept.
Frank,
what you could do in order to further make up your mind to which extent LR might suit you:
Use an alternative picture viewer (e.g. Irfanview) to compare JPGs.
Copy your existing JPGs to a folder, but do not import them into LR (that means do not LR have creating pointers to them and records in the catalog-database).
Import your raws into LR (that means you need to have some safe storage space for the image files themselves), and do your developments there. When you think you are ready, export** them as full-sized JPGs, renamed e.g. by a suffix -LR, into your JPG-folders. Do not add such export to your LR catalog.
Use the alternative picture viewer to compare how you did, compared to your camera's auto-conversion.
To further ease your mind regarding dependancy on LR: most of your develop settings can be written back to the raw file's xmp-part (that is a sidecar-file for a proprietary raw format such as Nikon's .NEF or Canon's .CR2, or embedded for a DNG, PSD or TIFF).
This xmp can be read by many other other programs.
So you would have your raws enriched.
Plus you could decide to store your exported JPGs *forever*.
Pretty independant from Lightroom, no?
Should you want to ultimately rely on raw-conversion results, I would go for different software, e.g. DxO.
Cornelia
**exporting means: LR is making use of its records as rendering instructions and writes a completely new file, in the format you specify for this export, e.g. JPG.
LR is a database, that contains records ABOUT images. It reads from them, it writes to their xmp-part if tell it to do so (choice is continuously or upon separate command for selected images), it can write other output, e.g. a PDF working as a slide show, a web gallery, a print, a book.

Auto Stack JPG's in Front of Raw

Hi,
I shoot everything JPG plus Raw. I have a number of reasons why, but would rather not make this post any longer..... I would like to be able to view everything in my library with all JPG's stacked in front of the RAW with the same file name. I have been able to Auto-Stack by time (setting time to Zero Seconds) does this. The Problem is that the NEF's appear first in the stack. I want the JPG's first, always. I can figure out any way to do this automatically. It looks like I would have to manually change which file is first. I shoot thousands and thousands of files, I need to automate this. How can I do this?
Secondarily, does anyone know how I could apply a star rating to just the jpg and have it also apply to the raw file?
Thanks

impactsystemsDT wrote:
Thanks for the question. Here is an example of why
Yesterday - Easter Egg Hunt at my House. I shot about 300 pictures. Raw plus Jpg. I want to go through them and I'll choose about 25-35 shots to document the event and perhaps make a photo book that I can keep for us and send to a few friends. I want the JPG's for this purpose. My JPG's generally look quite good. I do pretty good job with my in camera capture and settings. So, I want to be able to either spend zero time on these 25-35 shots or perhaps just 30 seconds to 1 minute on some or all to crop, vignette or some very quick adjustments, make my book and I'm done. My wife is happy, my friends are happy and I have somehting to remeber the event.
Then I will then have 2-5 really nice shots that I'll want to really work on. I might spend 10-20 minutes on each of these. I will generally process the raw file for the purpose. Occassionally the JPG's are just fine, so I'll just process those a bit further. I'll end of with a 2-5 "Hero" shots of the event. I might use these to add to the photo book or to print or add to my portfolio. Often I might just tag them to work tomorrow or next week or even next month when I have more time.
So I want to go select my 25-35 shots from the 300 with a simple pick off the JPG's, then the one's I really want the very best quality and versatility I.d like to be able to click on the stack (JPG in Front, Raw behind total of just 2 shots) and work the Raw file (the Negative). I don't ever have time to process more than a handful of Raw shots from any one shoot and frankly 95% of the time the JPG's look as good as the Raw files even after a fair amount of processing, so I really only need to process the Raw file on certain types of files. Having said that I am a very competent at processing and use combination of lightroom, photoshop, NIK, OnOne and Topaz. I just don.t need to do post capture and pre-out sharpening, cloning, healing, content aware fill, gradient filters, advanced color processing etc... on 98% of my files. The JPG's I create are good enough most all the time.
It seems that many people would want to work this way. I don't to rate all of the JPG's and the Raw's. I just want the Raw's (negatives) behind the JPG's so I can dive into them if I need to for the 5% or so of the files that I really want to spend time on. That doesn't mean I won't use the the other 95% (well more like 10%), it just meanst that the jpg's are just fine to email to friends or make photo books. Not every file that comes out of Lightroom is supposed to be the cover of Sports Illustrated. Raw and the JPG that I captured are the same file and it should be treated as such. Importing as the same file doesn't give you any access to the JPG so I don't see the purpose.
agree with your workflow and raw+jpg should be linked as same file (as in aperture)

Script to automatically make a stack with a RAW+jpg pair of images

While on my last trip, I accidently setup my camera to take Raw + small jpg. No big deal, that isn't too much memory, so I didn't really worry about it. When I got home, the jpg files were copied to my hard drive along with the raw files. So, I went to delete the jpgs and I realized something. Bridge runs very fast when it's drawing thumbnails and previews of small jpg images. I got to thinking. Wouldn't it be cool to make a script that would take your raw+jpg from the camera and convert each pair into a stack with the jpg on top. This would enable bridge to run much more quickly since it wouldn't need to render all those raw image thumbs and previews.
Hmmm....now where to start....I looked around at the scripting language for photoshop. since I have written a little bit of javascript, I thought I would start there, but I can't find where the stack property is kept in metadata or the DOM.
Any ideas of where I might turn from here?

Version with some changes. Try fix some bug. Try increase speed. If you found some bug or make changes or fix, please post it to this forum. -== [start of script] ==-- /////////////////// /// Name: Auto stacking files /// Description: This script enable auto stacking files by name /// Author: Tyzhnenko Dmitry /// E-mail: [email protected] /// Version: 0.32 /////////////////// /* @@@START_XML@@@ <?xml version="1.0" encoding="UTF-8"?> <ScriptInfo xmlns:dc="http://purl.org/dc/elements/1.1/" xml:lang="en_US"> <dc:title>Auto stacking files</dc:title> <dc:description>This script enable auto stacing files by name function</dc:description> </ScriptInfo> @@@END_XML@@@ */ function AutomaticStackingFiles() { /** The context in which this snippet can run; Bridge must be running. @type String */ this.requiredContext = "\tAdobe Bridge CS3 must be running.\n\tExecute against Bridge CS3 as the Target.\n"; $.level = 1; // Debugging level this.version = "0.32"; this.author = "Tyzhenenko Dmitry"; /** The unique identifier for the new menu item command @type String */ //this.menuID = "AutoStackFiles"; this.menuCommandID = "GoAutoStackingFiles"; } function RunAutoStacking() { var doc = app.document; var thumb = doc.thumbnail; var vthumb = doc.visibleThumbnails; var currSort = doc.sorts; function StackPhoto() { doc.chooseMenuItem('submenu/Stack'); doc.chooseMenuItem('StackGroup'); } function CollapseStacks() { doc.chooseMenuItem('submenu/Stack'); doc.chooseMenuItem('CollapseAllStacks'); } function getFileExt( t) { var dot = t.name.lastIndexOf ('.'); return t.name.substr(dot,t.name.length); } function getFileName( t) { var dot = t.name.lastIndexOf ('.'); return t.name.substr(0, dot); } CollapseStacks(); var SortObj = {}; SortObj.name = "name"; SortObj.type = "string"; SortObj.reverse = false; var SortsArray = []; SortsArray.push(SortObj); doc.sorts = SortsArray; for (var len = 0; len < vthumb.length; len++ ) { doc.deselectAll(); doc.select(vthumb[len]); doc.reveal(vthumb[len]); for ( var k = len+1; k < vthumb.length; k++ ) { //alert(k); if ( getFileName( vthumb[len] ) == getFileName( vthumb[k]) ) doc.select(vthumb[k]); else { if (doc.selectionLength > 1) StackPhoto(); break; } if (k == vthumb.length-1) { if (doc.selectionLength > 1) StackPhoto(); } //if (doc.selectionLength > 1) // StackPhoto(); } //delete vthumb; //var //vthumb = @doc.visibleThumbnails; } doc.sorts = currSort; doc.reveal(doc.visibleThumbnails[0]); delete currSort; delete vthumb; delete thumb; delete doc; } AutomaticStackingFiles.prototype.run = function() { var retval = true; if(!this.canRun()) { retval = false; return retval; } //app.document.chooseMenuItem('submenu/Stack'); var AutoStackCommand = new MenuElement("command", "Auto stacking", "at the beginning of submenu/Stack", ); AutoStackCommand.onSelect = function(m) { //alert('start'); RunAutoStacking(); //alert('stop'); } } AutomaticStackingFiles.prototype.canRun = function() { // Must run in Bridge if(BridgeTalk.appName == "bridge") { // Stop the menu element from being added again if the snippet has already run if(MenuElement.find(this.menuCommandID)) { $.writeln("ERROR:: Menu element from AutoStackFiles already exists!\nRestart Bridge to run this snippet again."); return false; } return true; } // Fail if these preconditions are not met. // Bridge must be running, // The menu must not already exist. $.writeln("ERROR:: Cannot run AutomaticStackingFiles"); $.writeln(this.requiredContext); return false; } if(typeof(AutomaticStackingFiles_unitTest) == "undefined") { new AutomaticStackingFiles().run(); } -== [end of script] ==--

RAW + JPG Stack

I'm new to all things Bridge. I shoot RAW + JPG and have been using my camera manufacturer's proprietary application to manage files. This application allows me to work with the RAW + JPG file pair as one file, all sorts, deletions, copies, pastes, etc effect both the RAW and the JPG file. As I begin the learning curve in Bridge CS5, I'm wondering if there is a way to duplicate this feature in Bridge. I've read a couple of threads about using a script (which is also very new and foreign to me) that will stack my RAW and JPG files together. The two threads appear to be pre-Bridge CS5. I'm wondering if the CS5 version of Bridge has a feature that will let me work with my RAW and JPG files together. If not, what would a complete newbie have to do to utilize the script option discussed in some of the privious threads?
Thanks

Any of the scripts will work in CS5.
To install a script in Bridge:-
Edit - Preferences - Startup Scripts, click the "Reveal My Startup Scripts" button. this will open the folder where the script is to be placed.
A script is a plain text file with a .jsx extension
Extendscript Toolkit is the editor/IDE that is installed with Photoshop for scripts.
Once a script is placed into the folder close and restart Bridge so that is can pick up the new script.
Here is some code that should do the job....
#target bridge
 if( BridgeTalk.appName == "bridge" ) {
AutoStack = MenuElement.create("command", "Auto Stack", "at the beginning of submenu/Stack", "zx1");
AutoStack.onSelect = function () {
 stackEm();
function stackEm(){
app.document.sorts = [{ name:"name",type:"string", reverse:false}];
var jpgs = Folder(app.document.presentationPath).getFiles ("*.jpg");
app.document.deselectAll();
for(var a in jpgs){
var Name = decodeURI(jpgs[a].name).replace(/\.[^\.]+$/, '');
var stacks = Folder(app.document.presentationPath).getFiles(Name+".*");
if(stacks.length < 2) continue;
for(var z in stacks){ app.document.select(new Thumbnail(stacks[z]));}
StackFiles();
app.document.deselectAll();
function StackFiles(){
app.document.chooseMenuItem('submenu/Stack');
app.document.chooseMenuItem('StackGroup');

Improved stacking for dual format pictures (RAW+JPG files)

Since I couldn´t find any description in the knowledgebase, I guess these features are missing:
My DSLR (Nikon) generates two copies of each picture (NEF+JPG) and I like to keep both of them (RAW for editing and JPG for ease of use (and for better results of the camera-built-in RAW-converter in some cases).
I use the auto stack by capture time feature to build stacks of each identical pair of pictures.
However:
- Which picture (JPG or RAW) ends up on top of the stack is sort of random
- All modifications apply to the picture on top only, so basically you need to pick/flag/label them with metadata individually which is not very convenient
It would save a lot of time if handling of stacked pictures could be improved.
Thx

Olivier,
You are correct, but also note that the switch is not kept by folder but for the LR installation and affects all imports/synchronize folders you perform from then on.
The only "useful" feature I can see in keeping the JPEGs as sidecars is that file system opertions (deletes/moves) will affect both the Raw and the JPEG.
Beat

Would like to purchase PSE 12 to process Camera Raw files for the following cameras: Nikon D800, Nikon DF, Canon G9 and Pentax K-3 does the Raw Converter that comes with PSE 12 when purchased recognize the cameras listed in the question or do I need to

Would like to purchase PSE 12 to process Camera Raw files for the following cameras: Nikon D800, Nikon DF, Canon G9 and Pentax K-3 does the Raw Converter that comes with PSE 12 when purchased recognize the cameras listed in the question or do I need to download the camera Raw Version 8.3 ?

While the G9 RAW files can be read by Adobe Camera RAW and Lightroom, these file are unsupported at this time. Here is a link to Adobe's latest list of cameras that are supported and this list came out yesterday http://www.adobe.com/products/photoshop/cameraraw.html
I have not done a comparison between Lightroom and Canon's software but others have and say that Canon's software is clearly better. I am sure when Adobe updates their software again to include the G9 it will be a very good RAW converter as it is will most other cameras.

Auto-stack bracketed raw images?

When I execute the auto-stack panorama / HDR command on a directory filled with exposure bracket groups intended for HDR processing, Bridge issues a warning message "Image is missing preview data" apparently for each and every image it inspects. If I click through however many warning messages come up, eventually, the command properly stacks the raw images.
I actually tried the build and export cache feature, exporting a cache directly to the directory of raw images I wanted to stack. That did not help. Still get the same warning message over and over again.
Can anyone help me with this issue?

I actually tried the build and export cache feature, exporting a cache directly to the directory of raw images I wanted to stack. That did not help. Still get the same warning message over and over again.
Never used this before (I always first sort and rate my files manually) but tried it on a folder and first time had two of those messages (but there where a few other files- already fused using Photomatix- and some layered etc etc. that might have caused that). Then I tried it with a bunch of HDR and Panorama files (already saved as tiff for use in Photomatix BTW) that I placed in a new folder. Now the result was better but to be honest not completely flawless, it left out 1 file out of 4 stacks from total 22 files.
Then tried again on the folder before and this time no error messages but also a pretty lousy result I'm afraid. Some clearly 1 stop difference series of 6 shots divided in 2 stacks so I stick with my manual method
However it might be a cache related problem for you. If you have one folder for testing first try a purge cache for folder using the menu tool / cache / purge cache for folder and try again

Aperture 3.3 problems RAW+JPG Import

After the update on Aperture 3.3 I have the following problem: Before import everything looks normal (see picture one). Aperture imports none jpg and Raw files as picture pairs and the Raw import looks completely colour-wrong. Moreover, there is no field more than Raw treatment
Any idea for solving this problem?

Also using a Panasonic (.RW2) I have had exactly the same problem, with exactly the same "colour effects". I did some varitions of importing and observed the following. The test shots were RAW only on a newly initialized SDHC card.
In the import dialog, if RAW only was selected, no previews were shown. Same if JPG only. If RAW & JPG selected, a preview was shown (even there were no jpgs on the card).
No presets, Auto Enhance and several others had no effect (i.e. same error).
The photos imported perfectly using iPhoto, and were then perfect in Aperture.
After thinking some, I suspect the preview image is the problem (I wished I'd exported them as tiff to see, but it was yesterday and I deleted the dodgy imports).
I had some pictures (also .RW2) not in the library at all (I'd been using them to try out LR4). I drag/dropped them from a Finder-folder into Aperture, (not import) by droppong them into the Inspector panael of Aperture; they were perfect BUT said they were RAW/JPG pairs which they were not.
Come on Apple. There was a time when your software was bug-free. Nostalga isn't enough.

Duplicate (sidecar) RAW & JPG files in Organiser

Hello,
I usually store both RAW and a small JPG file for each photo I take using a Canon EOS 7D. When these are imported into Lightroom 4.4, Lightroom only shows one image, reporting that the associated JPG is a 'sidecar' image. When imported into Photoshop Elements 11 Organiser both photos are displayed i.e. every single photo is duplicated.
How do I configure Photoshop Elements 11 Organiser to only show one photo for each RAW/JPG set?
Thanks in advance,
David.

Lightroom and the Organizer have something in common : they do not contain picture files. They only store the information about where the files are physically stored. They are a list of those paths (locations). Raws and jpegs of the same shot are two different picture files. So, you can't speak about duplication from that point of view.
What Lightroom and the Organizer don't have in common is the way they deal with the 'duos' of raw and jpeg files. At the import stage, the Organizer always considers the files as distinct and imports both of them as described by 99jon. LR recognizes the fact that both files are two variants from a single shot and offers a choice of how to import : ignore the jpeg or consider ist as a kind of 'sidecar' file.
How to use the organizer so that it shows only one thumbnail once they have been imported ? That's possible if you use the visual similarity search : you can choose to automatically suggest photo stacks just after the import stage. Your files will be stacked and you'll see only one photo in the browsing space. You can collapse stacks or expand them in the browsing space. After stacking, any organizing task such as rating, keywording will be applied to both files much like in real version sets.
I don't think that you really need to shoot raw + jpeg most of the time.
It may be useful when you are getting acquainted with raw processing.
It may be to have an instant way to display the pictures on your card when you have no computer at hand. In that case, deleting the jpegs from catalog just after the import into the catalog is the quickest and simplest solution.
For viewing the raw pictures on your computer without Elements, it may be useful to have another free software able to show the thumbnails of raw files (faststone, xnview...)
Also, if shooting raw only, it's easy to export a (temporary) ad hoc jpeg version of your import batch from the Organizer to share with friends. It's best done after culling and rating and doing some quick keywording.

Auto Stack with 0 secs doesn't work!

When I put RAW and JPG together in one folder, I would like to stack them via "Auto Stack". Unfortunately the lag of "0 Secs" doesn't work. It should, because the pics have exactly the same shooting time.
When I chose "1 sec" it works, but this stacks my shoot sequences together as well.

Found this post when searching for an answer, but didn't find much elsewhere so I'll post my quick and ugly solution here. I'm sure it can be vastly improved, but I didn't have much more than 5 minutes. Note - setting .visible to false just ended up causing the autohide transition to occur over and over, so instead I'm just temporarily moving the whole sprite offscreen.
(AS3, using CS5 component... note that 'player' is the FLVPlayback instance):
//### force 'autohide' when mouse inactive
var timer:Timer = new Timer(1500, 0);
timer.addEventListener(TimerEvent.TIMER, onTimer);
timer.start();
var skinSprite:DisplayObject;
var prevMouseX:Number;
var prevMouseY:Number;
function onTimer(e:TimerEvent):void {
//get skinSprite if we haven't already
if(!skinSprite) {
 var child:DisplayObject;
 for(var i:Number = 0; i < player.numChildren; i++) {
 child = player.getChildAt(i);
 if(i == 2) { //this is the skinSprite
 skinSprite = child;
//check to see if mouse hasn't moved since last timer event
if(skinSprite && mouseX == prevMouseX && mouseY == prevMouseY) {
 skinSprite.y = -1000;
prevMouseX = mouseX;
prevMouseY = mouseY;
stage.addEventListener(MouseEvent.MOUSE_MOVE, stage_onMouseMove);
function stage_onMouseMove(e:MouseEvent):void {
if(skinSprite) {
 skinSprite.y = 0;

RAW+JPG renaming/deleting workflow broken?

I tried to shoot RAW + JPG.
LR show only the NEF files [RAW] and uses the JPGs as a "sidecar".
if I rename teh NEF the JPG gets renamed with the same filename and the proper different extension.
the problem is when I delete the rejected NEF files - the corresponding/relative JPGs don't get deleted as well
and I need to do it manually in the finder outside of LR,
am i doing something wrong? I find this behavior inconsistent and it could be annoying if I need to do that with many files at once.
I can always download the images from teh camera to TEMP download folder - move the good photos to a different folder and empty the JPGs that have not deleted.
a bit of a cumbersome workflow...
stefano
stefpix dot com
yesterday's photos
http://tinyurl.com/27fazg
or
http://picasaweb.google.com/stefpix/BedstuyFlatbushMiniHaiti300320072309/photo#s5047923753 755028194

Amazing, so it's actually intentionally 'broken'. At the very very least, mentioning this in the manual would have been nice...(or did I miss it?) I can see where they're coming from as seen from a *particular* workflow perspective, but they are making some pretty big assumptions along the way, all of which can be challenged.
Assumption (1): RAW and JPG files with the same name are *always* both created in the camera.
- I'm not sure if I'm the only one, but I have sometimes saved rendered JPGs (from RawShooter) alongside my RAW files. The upcoming(?) RawShooter settings conversion utility will not give the exact same results, so I'd like to keep the JPGs in my library.
Assumption (2): The JPG is always inferior to the Lightroom-rendered RAW.
- Not true. Sometimes the camera vendors employ some sophisticated wizardry to their JPGs that can sometimes yield satisfying final results or a good reference for raw editing. I suspect this holds even more for the newer batch of SLRs that supports 'in-camera developing', applying proprietary coloring effects, etc to the rendered JPG.
Assumption (3): People get horribly confused when they see *choose* to shoot RAW+JPG and actually see two files.
- Well, I'm probably not the target market, since I'm one of those 'organized' photographers, but ok. If I have chosen to create two files that every other imaging program considers to be different, I have consciously done so, and I do not get confused if I see different files. In fact, I *expect* all my files to show up in Lightroom. Of course having neat options to hide either type of files is a plus.
As for suggestions to improve this in future versions, I'd say:
* Make it an option (selected by default) to not import sidecar JPGs and use them only for preview. [mentioned in Podcast]
* Implement auto-stacking for files with the same name. [mentioned in Podcast]
* Even better, allow for auto-stacking with similar names (using a suffix, like '-') and images that were shot at the same time. See also http://www.adobeforums.com/cgi-bin/webx/.3bc34b40/1
* Implement a command to sort the images in all stacks in the current view. This could be used to place all RAWs or JPGs on top.
* Implement a synchronization feature that synchronizes (selected) keywords and collections across stacks. [deals with mentioned keyword problem]
* As an alternative to all stack-based options above, simply implement a viewing filter to only show files of a certain type within the currently selected category. This way, people can easily remove all JPGs from view.
Cheers,
Simon

RAW + JPG

I just started shooting RAW and imported 152 RAW + JPG today. Only the RAW are showing in Aperture. Any way to make both show up??? I drilled down in the library and the JPGs are there ...
thanks in advance for any help ...

From my website www.aperturetricks.com.
"Ben Long sent me a great script to work with RAW+JPEG imports and I posted that last week. But then several of you sent me emails suggesting additional support for RAW existed and I added that information to my own research and want to share that with you now.
Like others, I wish the RAW+JPEG workflow were better, but there’s more support than I think most people realize:
1. Aperture actually DOES import RAW+JPEG. It sees both files and brings them both into the Library. By default it only displays the RAW image. To see the JPEG too, just select any image and press Option-J, (That’s the keyboard shortcut for New Version from Master JPEG.) Now-the RAW AND the JPEG appear together in a stack. If you make the JPEG the “pick” of the stack, then you can collapse the stack and see only the JPEG.
2. Once you have both the RAW and the JPEG, you will want to be able to tell which is which. Aperture CAN (despite complaints from some reviewers who just don’t know how to properly use the software) display full filenames and file extensions You need to set up the metadata display options correctly.
- Create a new Metadata set using the Action menu on the metadata inspector.
- Click the “Other” button at the bottom of the inspector and turn on File Name as the only field to be displayed for this new set.
- Open View > View Options and set either Set number 1 or Set number 2 in either the Viewer or Browser to display your new metdata set, consisting of File Name.
Now you can toggle full filenames (With extensions) on or off the images in the Viewer or on thumbnails in the browser.
You could also just modify any existing metadta set to accomplish this by replacing the “Version Name” field with the “File Name” field."
Good luck,
Scott Bourne

PSE5 - Stacking RAW / JPEG Files

With my Nikon D80, I am starting to shoot a lot assignments using the combination of RAW + JPEG files.
I am using the auto-staking feature of PSE5 when adding files and folders, with the expectation that it would quickly stack the RAW+JPEG combinations into a single stack for each pair.
Instead, I'm getting a frustratingly wide range of results. In some cases, the RAW and JPEGs are not stacked, and the stack has to be manually created.
In other instances, I'll get 2, 4, or 3 pairs of photos in a single stack and have to divide them with the little scissors tool. These combinations are not necessarily rapid exposures. I haven't been using the multiple exposure setting on the D80.
All in all, this is adding to my workflow instead of expediting it. Is there not some way to set parameters to establish how auto-stacks are determined?
On a similar subject, is there any way to tell PSE5 WHICH of the files I want to see on the top of the stack? I'd rather see the RAW for starters, but then sometimes, I might want to see the JPEGs instead. Is there some way to set / switch the top photo for all of them at once?
Thanks,
--PS

Hi Paul,
the automatic stacking feature finds similar pictures. Most of the time it works well for RAW/JPG files but sometimes (e.g. sunset pictures with a bad automatic white balance assumption for the RAW) it won't find the pairs. You then have to do it manually as you have described it.
In the stacking window you can drag your preferred file to the first position for being the top picture. After creating the stacks you can change the top picture by opening the stack, right clicking on your preferred picture and choosing "Make top picture" (or similar, I have the german version, so I don't know the english menu text) in the stacking sub menu.
I had the same problem and know I decided to move all JPGs to an unmanaged folder, so I won't see all my images doubled and I can stack only those images that I want to stack.
Michael

My iPhoto WIsh List for '07

Just sent the following to Apple's iPhoto Feedback; figured I'd post same here just for the heck of it. Many of these feature requests might only apply to my particular (and peculiar?) workflow, but I suspect at least a few of them might strike an empathetic chord...
One User's iPhoto Wish List:
Your first priority is to contact the creators of iPhoto Diet and iPhoto Library Manager, pay them lots of money for their work, and then incorporate all the features of their shareware apps into iPhoto itself.
This would add to iPhoto features it should have had for a long time now, including:
1) An option to delete unrotated originals.
It's silly to take up space on a hard drive with copies of files whose only difference is that one is correctly rotated and the other is not. Give us the choice to dispense with the unrotated ones.
2) An option to delete the originals for any selected file(s).
I know that "always keeping a copy of the original" is a sacred cornerstone of the iPhoto app, but SOMETIMES, after I've edited, resized, or done whatever to a given file, I feel I've created the new master file, and I truly really honestly would like the ability to just dispose of the now redundant original and get the space back on my hard drive.
(If this sounds like giving the user of a "consumer app" too much control, by all means bury this kind of option behind all the Advanced Tabs and all the Warning Dialogs you want -- but please at least give us the option to manage what we ultimately keep or don't keep in our iPhoto Libraries.)
3) Ways to manage multiple libraries on multiple machines with multiple users.
I have a 12GB (and growing) iPhoto Library on my G5 PowerMac. My wife's G5 iMac has a subset of that Library (about half the size), with the same Roll designations, Comments info, and Keyword assignments, along with some of the same Albums plus some unique Albums. I use iPhoto Library Manager to do this, but I should be able to do it using iPhoto itself.
Especially since the introduction of OS X, Apple has encouraged the notion of multiple users on multiple Macs. iPhoto needs to embrace that world view, and make the sharing and management of multiple iPhoto Libraries, even different versions of the same Library on different machines, a fluid, user-friendly, and fully-integrated process. For instance, I should be able to select which images, Rolls, and/or Albums from my Library get copied to my wife's machine (with all Comments, Roll info and Keywords intact) -- AND whether or not those copies include the corresponding original files or not.
Other features iPhoto needs:
4) Ability to correct and change the actual EXIF date/time info.
One example: It is extremely common to get jpegs from other users who haven't bothered to correctly set the date/time menu on their digital cameras. You want to correct that info, but if you do that in iPhoto's Info pane, and then Export that image and in turn Import it into another iPhoto Library, the Date/Time reverts back to the original INCORRECT setting. This is really annoying, and I feel like it's insulting my intelligence. (When I change the date of a photo, THAT'S the date I should now be able to search for by using the calendar mode, NOT its incorrect "creation" date.)
The current workaround of having to export the file, use another app like Graphic Converter to really change the exif data, then re-import into iPhoto (after first deleting the originals), then recreate all your Comments and Album arrangements, is clumsy, time-consuming, and when you think about it, absurd.
PLEASE consider a User Pref to the effect of "Changing Date/Time info changes original exif data as well"? You could have it unchecked as the default; you could have all sorts of "do you really want to do that?" warnings pop up when a user does check it -- but please just give us the option!
5) Better User Pref options.
Give us the choice to NOT create a dupe original when a file is viewed in an external editor but no changes are made; likewise when just rotating an image within iPhoto.
6) Better sorting/display options.
I display my library in Rolls (each Roll being pictures taken on a particular day or at a particular event). I'd like the ability to designate how files are sorted within a particular Roll -- the pictures in some Rolls sorted by file name, the pictures in other Rolls sorted by Date & Time.
Would also like to be able to insert dividers in the Source pane to separate some of my albums into different groups, as well as a way to set bookmarks or placeholders within a Library, as a quick shortcut to an often-viewed section for example.
7) More e-mail attachment options.
Within each of the Small, Medium, Large, and Actual Size choices, there should also be (perhaps under an Advanced tab) a sliding scale of jpg quality, with an instant feedback showing what the total file size will be at that particular setting.
Also, there should be four checkboxes: one for Image Name, one for Date, one for Time, and especially one for Comments -- allowing the user to determine which of those four bits of iPhoto info are included in the e-mail attachment along with the image itself.
8) Option to have Comments included in Captions for online albums.
Those same four checkboxes also need to be options for any kind online album posting. It's crazy that right now I can't put up an iWeb photo page that automatically includes the Comments I've taken the time to enter in iPhoto as part of that photo's Caption online.
9) Option to show file extension in Title
Including or not including the .jpg or .psd or .gif extension is an option when Exporting a file; why not when displaying it as well?
10) Option to "show all layers" of an imported Photoshop file.
Or any kind of layered file which has been imported into the iPhoto Library.
11) Ability to enter partial dates.
It often happens when you import an older scanned photo into your library (or even when you're just sent a recent photo from a friend), you don't know know the exact date and/or time the picture was originally taken. iPhoto really needs a way to enter partial, approximate or estimated dates -- just the month/year without a specific day, for example -- both in the Info pane AND in Batch Change mode.
(Also wouldn't mind a user pref option to display the Time without the seconds.)
12) Ability to Import pictures into an already selected Roll.
There are many times when I'd like to be able to select a particular Roll, then Import some new pics directly into that Roll -- rather than doing the Import, then having to drag the images sometimes several months back in time to drop them into the correct Roll.
13) Ability to delete files from an Album and the Library simultaneously.
This would be some sort of Option-Delete command, where a selected image being viewed in a particular Album is ALSO removed and sent to the Trash from the Library as well -- with the appropriate warning dialog, of course.
14) Built-in support for doing INCREMENTAL back-ups of either your entire Library -- or only the files from selected Albums -- to another hard drive.
I hope that most of these features have already been incorporated into the next release of iPhoto -- and if not, that you'll give serious consideration to implementing them as soon as possible. Your users will thank you.
John Bertram
Toronto

should add ability to scan directly to iphoto.
How would I give this wish to apple?
Note that under the Application Menu (in other words, in iPhoto under the bold Menu item called "iPhoto", right next to the blue Apple icon), there's a selection called Provide iPhoto Feedback. Clicking on that opens your default browser (if it's not already open), and sends you to the specific Apple webpage set up to receive user suggestions for that particular app.
In this case, the URL is the one "Old Toad" mentioned in his post:
http://www.apple.com/feedback/iphoto.html
Many of the major Apple apps have this direct menu link; for others you can just go to http://www.apple.com/feedback/ and navigate from there.
They claim to actually pay attention to this kind of user input; and I've heard people say it actually does affect how the development and implementation of new features get prioritized.
Let's hope so, anyway.

PSE wish list - Auto stacking RAW + JPGs

Similar Messages

Maybe you are looking for