Is PSE9 Organizer compatable with PSE6 Bridge?

I've just bought PSE9 to update my PSE6. When I install PSE9, will the files in PSE6 Bridge transfer to PSE9 Organizer or will I lose them?
Thank you, Steve

No files are "in" Bridge. Bridge is just a file browser: it shows you the current state of any folder you point it at. If you mean will you lose your metadata keywords, no those are written into the files themselves, so no worries there. You will lose any stacks, though. You can continue to use PSE 6 bridge with PSE 9 if you don't like organizer, also. You just won't have a button in PSE itself for launching it.
If you want to remove PSE 6, it's maybe best to do that first before installing PSE 9, since the way the installer for PSE 6 is written, it removes some shared files, so if you decide to remove it later, you'll need to reinstall PSE 9 afterwards (this won't affect your photos in any way, though).

Similar Messages

PSE 8 compatibility with Adobe Bridge CS 5 Camera Raw

I have Photoshop Elements 8 installed with Camera Raw 5.5 on a Windows 7 64-bit platform. I recently purchased Photoshop CS 5 which came with Camera Raw 6.2. I think both products work well independently, with the exception noted at the end of this posting. Where I'm encountering an issue is when I use Adobe Bridge to access an image file for processing which invokes Camera Raw 6.2. -- the changes made to the file show up in Adobe Bridge, but are not observable when the same file is viewed in the Photoshop Elements Organizer. When I look at the file properties I can see that Camera Raw 6.2 updated the file and the updated date does appear in the file properties accessible through PS Elements Organizer. However, the items listed in the Camera Raw metadata are different in the two products (PS vs PSE). Since the sidecar .xmp files are a form of XML, I'm wondering if Camera Raw 6.2 is writing data in a structure that is not supported by Camera Raw 5.5? I've tried to update PSE Camera Raw to version 6.2 following the instruction that appear on line, but it does not seem to install. Durring installation there are no error messages, but after the "installation" PSE Camera Raw still shows version 5.5. I noticed this first when editing a large number of "legacy" .jpg files, but I also have concern when editing Nikon .nef files.
It's a bit hard to tell, but when editing .nef files in Camera Raw 6.2 the changes may migrate to PSE once I tell PSE to update the thumbnail view. But what I observed was a very distinct differece in file's visual appeared when viewed in Adobe Bride CS5 vs PSE 8 Organizer. The PSE 8 images had greater color saturation. This leaves me wondering what's going on.

On my Windows 7 64 bit system the original version of Camera Raw.8bi was found in:
C:\Program Files (x86)\Common Files\Adobe\Plug-Ins\Elements8\File Formats\ and had a size of 11,781 Kb shown in Windows Explorer. The file properties listed the size as (12,063,088 bytes). The digital signature was signed Thursday, September 03, 2009 3:34:37 PM. To the best of my knowledge this is the version that shipped on the PSE 8 disk which I installed in December 2009.
There is another copy of Camera Raw.8bi found in:
C:\Program Files (x86)\Common Files\Adobe\Plug-Ins\CS5\File Formats\ and had a size of 11,856 Kb shown in Windows Explorer. The file properties list the size as (12,140,496 bytes). The digital signature was signed Friday, August 20, 2010 3:30:03 AM. This date post dates the installation of Photoshop CS 5 on my system so it must have happened through some (automatic?) update.
The Camera Raw.8bi file that I've down loaded from Adobe for ACR 6.2 is the same size and has the same signing date as the one identified immediately above in the CS5\File Formats\ sub folder.
When I copy the down loaded file into the Elements8\File Formats\ sub folder PSE still indicates that ACR is version 5.5
I also have a copy of ACR in C:\Program Files\Common Files\Adobe\Plug-Ins\CS5\File Formats\ with a length of 14,526 KB shown in Windows Explorer. The file properties list the size as (14,874,576 bytes) and the signing date as Friday, August 20, 2010 10:39:07 AM. I presume this to be the copy of ACR used by Adobe Bridge and Photoshop which I installed as a 64-bit application. Since the signing date (but not the time) is the same as the date for the file in CS5\File Formats\ I'm guessing that it is also the result of an automatic update to version 6.2.
Something that's not making sense to me is that the down load was approximately 50 MB and I'm messing around manually moving a 12 MB file into a specific sub folder.

Sharing PSE7 Organizer keywords with Bridge?

I want to share my existing PSE7 Organizer keywords with Bridge. I searched the forums and found an some answers to use PSE7's "File/Write Keyword Tag and Properties Info to Photo" menu option. I did some tests with that option, and it appears to only do what I'll refer to as "additive writes," meaning it will add keywords in PSE7 Organizer for a particular photo, but it will not remove any keywords which are presently in the photo file but not in Organizer's informaton for the same photo file.
I'm guessing this is the case because PSE7 Organizer cannot assume the keyboard already in the file originally came from Organizer itself, or that the user (regardless of where an existing keyword came from) wants to remove a keyword if it's not in Organizer for the same file. It would be nice if there were a preferences option which one could select such as "Replace all keywords when writing to file" so that a user like myself could make Organizer's keywords the main keywords.
Does anyone happen to know if I understand this correctly, or is there a way to remove a PSE7 Organizer-written keyword from a file (based on its non-existence in PSE7 Organizer for the same file)?
If there is no way around this, I'm wondering if it may be better to do things the Bridge-way (which seems more like the general standard) since it seems to always keep the current info in the file, so the state is always with the file itself. Even if some features are missing, it may be better than dealing with this sort of PSE7-only feature. Any comments on this would be great to hear.
Thanks for any insight on this,
Tom

Okay, that makes sense on the Albums. I wasn't aware that Albums were ordered.
I was using Bridge some more after my post yesterday, and I was seeing that with PSE7, both Albums and Keyword items seem more readily accessible regardless of location of the items (photo files) because there isn't an extensive file system search required since the DB provides a quick search (assuming first-searches and no pre-existing caching in Bridge).
I started testing Collections with Bridge, and realized that it was sort-of doing that. This is another aspect of Bridge which is sort of a "db" aspect of Bridge in that it requires the browser to persist data seperate from the photo file. .
What can be a little frustrating about any browser-persisted informaton (such as that for Collections) is to not find anything in the docs about how to ensure one gets a good backup of that info. PSE7 does a great job of providing a feature to do just that. Recall this is one thing I really liked about PSE7 when I was unaware of the benefits of Bridge's "minimalist db" approach (where a "db" in Bridge is anything persisted by itself such as Collections).
The "how to" backup app-persisted information (aside from docs a user saves, where the user knows the location) is a must for any pro-am or pro person, if not an end user. People don't want information that is key to something they're building over time to be persisted in some mysterious unknown location. I couldn't find what I wanted in Bridge docs, so I did my own hunting, and found Bridge Collection information hiding in "%APPDATA%\Adobe\Bridge CS4\Collections" (i.e., c:\Users\<user_name>\Roaming\Adobe\Bridge CS4\Collections" on my laptop) in files named "<collection_name>.filelist". But even with that info, I, as a user, would still have to test to ensure I could get a backup good enough for disaster recovery / restoration. I'm a relatively technical user so I cannot imagine what "Dad" or "Mom" would do. This sort of thing is bothersome only because it's remedied with at least a small paragraph in the docs. What would it take to say "Backing Up Bridge Information: If you have a backup program which backs up the "%APPDATA%\Adobe\Bridge CS4" you will have all necessary data to restore the information that Bridge maintains. You must ensure you backup your photo files..." etc. etc. Without that, I have to do a bunch of hunting and testing.
All that said, I see how Collections, maintained by Bridge, offer some of that PSE7 power where you don't have to search for files in various locations to find what is already noted in a central Bridge file or "db" such as a Collection for which Bridge has a list of files in the Collection itself. (If Collections could contain other Collections, that would be a nice touch. I didn't see that ability.)
What I still like about Bridge's approach is that while Albums don't exist, and while Collections are hierarchical, there's a feeling that Bridge is not taking things over where you are forced to use that app. It persists some items relating to its organizational features, but keeps the rest of the info right in the photo file. Still a nice balance. Another nice thing about this minimalist approach is that there's no importing per se. Everything is browseable/maintainable since the file system is the photo db.
All that said, I can see where PSE7 does things for the non-power user such that they can just use, say, an Album, which has a familiar name, and behaves like an Album with ordering and whatnot. A user like me doesn't need that since I can use tools to create an Album like effect, so the Bridge approach wins since I can fend for myself in areas were I don't see PSE7 to hand hold.

PSE6 Organizer Crash with ACR 4.5 (Vista Only?)

Hello;
I'm experiencing the following problem when I download ACR 4.5 to be used with PSE6. The problem is that the PSE6 Organizer crash when I try to open the Organizer Preferences. Aparently this only happens with Windows Vista because I know of other users with XP and they are not expiriencing this.
I did try it with the original ACR 4.2 and works well.
I did try it with the previous ACR 4.4 and works well.
It only happens when you install the 4.5 and go to the Organizer's Preferences.
Regards

Ramon,
Sorry I made a mistake, now it is Ok.
In fact as I installed the new "Camera Raw.8bi" file, I moved the old file renamed "Camera RawOld.8bi in an "old" folder created in "..\Plug-Ins\File Formats". It was not a good idea because PSE6 was always seing the old version (despite renaming and moving in an "Old" folder). Now I've renamed the old file Camera Raw.old and all is Ok.
Thanks for your help.
Yvan

Organizing with PSE9 Organizer

Hi All,
Does anybody know how to sort/organize photos by date (I want chronological order instead of most recent first) or by file type (I want to sort JPEG from RAW).
Gimme back my Bridge.
Many thanks in advance!!

Sorting by date: http://help.adobe.com/en_US/ElementsOrganizer/8.0/Win/Using/WSBEFCDEE4-D7E4-42ee-A458-B03E 4B55F71E_WIN.html
Find by file type: http://help.adobe.com/en_US/ElementsOrganizer/8.0/Win/Using/WS63916FDA-F68F-486e-A1F4-FB09 3C558322_WIN.html
If you liked Bridge, then you need a mental shift to use Organizer, because Organizer is NOT a file browser. Do not think it is a file browser, or that you can use it as a file browser, because with those thoughts, Organizer is useless. If you insist on using Organizer like you used Bridge, as simply another way to view files and folders, then you are heading down the wrong path.
Organizer is a database, it offers you superior tools to file names and folder names/locations; specifically I am referring to tags, captions and notes. If you use those tools, Organizer will allow you to find photos quickly and operate smoothly.

Generate Photo Gallery XML for Spry with Adobe Bridge

Wanted to post a note to what I've discovered/worked out -- a
way to
generate a very useful photos.xml from Adobe Bridge. If you
use Bridge,
it's very easy to add titles, keywords, ratings -- all kinds
of metadata
that one might use in a photo gallery. Here it is in case
anyone wants
to use.
The script is based on one I found at the Adobe User to User
Bridge
Scripting Forum for exporting a CSV file.
Note 1: this particular script doesn't take into account
CDATA that
might exist in your metadata, like ampersands in your title.
I've just
avoided using those, but you could also have the script write
out a
CDATA node for that info instead.
Note 2: this script does not write out a thumbpath,
thumbwidth or
thumbheight attribute. But usually the thumbpath is the exact
same as
the regular "path" attribute, and the thumbwidth and
thumbheight are
just a ratio of the regular "width" and "height" attributes.
I added a
bit of JS to the gallery.js file to calculate those before
growing the
thumbnail on rollover.
Personally I'm using keywords as categories and titles as
captions and
sorting by rating (stars in Bridge), so here's the .jsx file
I created.
The script should be saved to the folder "StartupScripts" in
Program
Files/Common Files/Adobe.
Hope this is useful for others too!
#target bridge
if (BridgeTalk.appName == "bridge" ) {
// create menu
var menu = MenuElement.create( "command", "Export XML File",
"at the end
of Tools");
menu.onSelect = function(m) {
try {
// ask for the name of the output file
var f = File.saveDialog("Export XML file to:", "XML
File:*.XML");
if ( !f ) { return; }
// open filestream and write first line
f.open("w");
f.writeln("\<photos\>\r\r");
// get a list of all the visible thumbnails in Bridge
var items = app.document.visibleThumbnails;
for (var i = 0; i < items.length; ++i) { var item = items
f.writeln("\<photo path = \"" + item.name + "\"" + "\r" +
"width = " +
"\""+ getWidth(item) + "\"" + "\r" + "height = " + "\""+
getHeight(item)
+ "\"" + "\r" + "rating = " + "\""+ getRating(item) + "\"" +
"\r" +
"categories = " + "\""+ listKeywords(item) + "\"" + "\r" +
"caption = "
+ "\""+ getTitle(item) + "\"" + " \>" + "\r" +
"\<\/photo\>\r\r" ); }
f.writeln("\<\/photos\>");
f.close();
} catch(e) {
function getTitle(tn) {
md = tn.metadata;
md.namespace = "
http://purl.org/dc/elements/1.1/";
var varTitle = md.title;
return varTitle;
function getWidth(tn) {
md = tn.metadata;
md.namespace = "
http://ns.adobe.com/tiff/1.0/"
var varWidth = md.ImageWidth;
return varWidth;
function getHeight(tn) {
md = tn.metadata;
md.namespace = "
http://ns.adobe.com/tiff/1.0/"
var varHeight = md.ImageLength;
return varHeight;
function getRating(tn) {
md = tn.metadata;
md.namespace = "
http://ns.adobe.com/xap/1.0/"
var varRating = md.Rating;
return varRating;
function listKeywords(tn) {
md = tn.metadata;
md.namespace = "
http://ns.adobe.com/photoshop/1.0/";
var Keywords = md.Keywords;
var varKeywords = "" ;
for ( var i = 0; i < Keywords.length; ++i ) { varKeywords
= varKeywords
+ Keywords + ","; }
return varKeywords;

I updated the script so it exports an XML file from Bridge
with full
compatibility with the Spry Demo Photo Gallery, to use as
photos.xml.
It's at the same address:
http://www.imagicdigital.com/spry/bridge_export_xml.zip
To Use:
The script goes in the folder "StartupScripts" in Program
Files/Common
Files/Adobe.
Launch Bridge and browse to a folder that contains the files
you want in
your gallery -- the "source" folder, as it were.
Choose the menu command "Tools > Export XML for Spry
Gallery".
Type a name for your XML file in the Save dialog box, choose
a location,
and hit "Save".
In the dialog box that pops up, enter a max length/width for
your
thumbnails, in pixels. Some common sizes are "75" , "100" or
"125".
Hit "OK". You should see an alert pop up telling you "XML
file
successfully created!"

Does Adobe Photoshop Elements come bundled with Adobe Bridge? Or is Bridge a separate purchase?

Does Adobe Photoshop Elements come bundled with Adobe Bridge? Or is Bridge a separate purchase?

Apparently there was a change in Elements 9.
From the PsE forum:
Bridge is no longer included with PSE. If you buy PSE anywhere except the Mac App Store you get Organizer instead. The app store version doesn't have organizer.
and from a link therein:
A lot of Mac folks are unhappy about Adobe’s decision to include Organizer with Elements 9 in place of Adobe Bridge, which came with previous Mac versions. (The Organizer used to be just for Windows.) If you have an older version of PSE that included Bridge, you can still use it with Elements 9…

Using Aperture with Adobe Bridge: Can It Work?

I have used all the Adobe apps for ages and love them.
Photoshop and Bridge are a mainstay of our studio operation here.
I have been using Adobe LightRoom lately to deal with my RAW shooting.
I take it to a certain point with LR then I use Bridge to do other things with my files. LR and Bridge can see eachother's metadata and XMP info so they can be opened back and forth between the apps as need be.
This is critical for our work process.
What Im wondering is can Aperture be used in a similar way?
Can Bridge see Aperture's adjustment info and visa versa?
Do they read eachother's Metadata and or XMP info?
Does Aperture even use XMP data?
Reason Im asking this is I admire Aperture's interface and functionality.
I'd like to possibly use it in place of LightRoom for dealing with my RAW files.
But without the compatibility with Bridge it wouldnt work for us.
I read lots of Mac and Adobe publications and have yet to see this issue addressed in any articles.
Surely other people are in the same boat as me on this one...
Anyone have any knowledge to share on this matter?
Thanks.

Bridge and LightRoom can see each other's image adjustments because they are using almost exactly the same engine to do RAW conversions. Aperture and Bridge won't understand each other's image adjustments, in just the same way that Bridge and Nikon Capture, Canon DPP, Bibble or Capture One etc. can't.
When it comes to metadata you won't be much better off, as any changes you made in Bridge wouldn't be seen in Aperture unless you re-imported the file and vice-versa.
Basically, if your workflow is based around Bridge you are stuck with Adobe apps as they are the only ones designed to work with it.
Ian

Black images in PSE9 organizer?

I recently scanned some old B&W prints to TIFF files but they only show as black images in PSE9 organizer although they appear normally in the editor. Files that don't appear are all less than 1Mb file size. Any suggestions about how to have these images appear properly in the organizer would be appreciated. Thanks in advance

Here are the release notes for PSE9:
http://kb2.adobe.com/cps/861/cpsid_86152.html#main_Photoshop Elements Organizer notes
Specifically, this section (emphasis added):
Organizer thumbnails:
If an image has been rotated in an application other than Photoshop Elements 9, update the thumbnail before printing or using the image in a creation to ensure that the images appear properly rotated. To update the thumbnail, select the image(s) and choose Update Thumbnail or Update Thumbnail for Selected Items in the Edit menu.
Some TIFF files and files that use uncommon color profiles may appear black or as generic thumbnails in the Organizer. To fix this, select the file, and choose File Export As New File(s). This will save the file with the supported set of file tags required by the Organizer to show the thumbnails.
Very large files appear with generic thumbnails. For example, panoramas created with Photomerge Panorama return multiple layers, which, when saved, creates very large files. To make thumbnails visible in the Organizer, consider saving panorama files as flattened JPEG images
Files that are not supported in the Organizer look like broken thumbnail icons. You can import these files by saving an album containing a file in an unsupported format, using the Photoshop Elements Editor, or importing files not supported by the Organizer, using Premiere Elements.
Ken

SeriTek/2ME4-E Not Compatible With Oxford Bridge - Dual Core

Hi Gang
After weeks of extensive testing I was able to confirm; the SeriTek/2ME4-E is not compatible with Oxford Chipset 924, or 934, (OWC Quad Enclosures). The incompatibilty issue is related to my Dual Core 2.0, (perhaps other Dual Core models as well).
After weeks of back n forth, FirmTek support was not totally co-operative. Had to push toward resolution, which I later confirmed myself. Flashing to different firmware, formatting a NEW system drive, the whole 9 yards.
It appears compatibility design is geared mostly toward Mac Pro systems. Someone here pointed to the 'Bridge' as a possible 'culprit'. In my situation it's definitely true. I've taken all my drives out of OWC Quad enclosures, and will sell them on Ebay. I'll stay with DIRECT SATA connection thru dedicated dual bay enclosures, and continue using the SeriTek/2ME4-E.
This issue may not be common to others, but thought I'd post this information anyway.
Thanx
Mike

From the FirmTek Web Page; "Third Party Enclosure Compatibility - FirmTek cannot guarantee compatibility with third party enclosures." Somewhere there's also mention of 'Oxford' The tech also repeated over and over it could be the enclosure bridge.
It definitely WAS.
I tried one of these; http://eshop.macsales.com/item/Other%20World%20Computing/MESATATBE/ I REALLY LIKE IT , and for $27 you can't beat it, (getting 2 more). For my money, I don't care how much noise the fan could make, as long as it COOLS those babies. Many other OWC enclosures don't have fans. Selling all my bridged enclosures on Ebay to recoop some $$
About the SeriTek/2ME4-E; I'm stuck with it, but it's FAST, so I'll make it work. I even picked up another 2 Port FirmTek card on Ebay for $40!
I'm keeping this Dual Core running as long as I can. No intention, No money for Mac Pro.
With 7-8 large capacity drives with so much valuable data, and soooo much $$$ invested, this was my only solution.
Thanx
Mike

I am considering updating to Mountain Lion. Have checked the website Roar for compatibility with other software; some OK; some have yet to be tested. When will that testing be done?

I am considering updating to Mountain Lion. Have checked the Roar website for compatability with my existing software; some are OK, but Bridge and Picasa said to yet be tested for compatability. When will this happen?

I am considering updating to Mountain Lion. Have checked the Roar website for compatability with my existing software; some are OK, but Bridge and Picasa said to yet be tested for compatability. When will this happen?

How is compatibility with creative cloud products (Photoshop and Illustrator) with Macbook Pro? I am making a big purchase and would love some feedback

how is compatibility with creative cloud products (Photoshop and Illustrator) with Macbook Pro? I am making a big purchase and would love some
feedback

Hi Frederick,
You're spending a lot of money. I will add my 2¢ -- -- but you must, as I assume you know, fully research your options.
Environment:
Start with your workspace (inc. lighting) and your clothes.
Screen:
The iMac screens are lovely, but not, from what I hear, monitor-grade accurate. For critical color work, use NEC or Eizo monitors. I use NEC, with their SpectraView II software and an X-Rite ColorMunki photospectrometer. At the time, this was the least expensive color-calibrated workflow.
Printer:
Epson's are great, imho. I use a 3880 in my studio and rent a 9900 by the hour when needed. I have read of problems (iirc) with one of the printers in the 7000 line, however. The take-home lesson that I filed in my brain was, "If you're going to spend the money on the 7000 line, just get the 9000 line."
Aperture workflow:
Aperture is a fantastic workflow tool. Since you are adept with PS, you should set PS as your external editor. Use Apertures formidable tools for storing and organizing your Images, and its robust editing tools for either all your proofing, or all but your most demanding editing needs. That said, allow a good bit of time to get the feel of Aperture. It is not at all like Bridge. But your important choice is which RAW converter you want to use. There is, imho, no reason to use Aperture if you are going to use Adobe's (or anyone else's) RAW converter.
Good luck!
--Kirby.

Adobe Elements 9 compatibility with OSX 10.8

Is Photoshop Elements 9 compatible with OS X 10.8?

Great news! PSE 11 is such a disappointment -- Elements seems to get dumbed-down, lose features, and lose compatibility with filters every version. I do have to say, though...I used to love PSE with LR and Bridge but I'm probably going to leave the Adobe family if the prices keep going up and the need for Flash goes down! Glad I saw this post -- thanks, friends!

QtNetwork4.dll missing so PSE9 Organizer won't start

I downloaded a trial copy of Photoshop CS5, which worked fine. However, I decided I was happy with PSE. Unfortunately, when I tried to open PSE 9's Organizer I got the message "Program can't start because QtNetwork4.dll is missing from your computer. Try reinstalling the program to fix this problem." First thing I did was uninstall CS5, but the missing message still appears when I try to open the Organizer. I'm not real keen on uninstalling and reinstalling PSE 9, but I'll do it if necessary. Does anyone have any ideas about how I can replace QtNework4.dii without a reinstall? Many thanks.

I don't know if anyone cares (and why would one if one is not experiencing the same problem?), but what I did to solve the problem was go to a friend who also has PSE 9 on his computer and copy the QtNetwork4.dll file, which is buried in C://Program://Adobe://PSE9 Organizer. I then installed the file on my computer in the same place and Organizer opened again. Et voila!

OBIEE 10g compatability with IE 10

Hi
Can any one help me in Does Obiee 10.1.3.X is compatable with IE 10 rignt now we are using IE 8 we want to move to IE 10
Thanks,

While I'm not advocating to change delivered code, there is a way you can upgrade to IE10 but have browsers downgraded behind the scenes to run OBIEE 11g as IE versions 7-9 by doing the below
navigate to
Oracle_BI1/bifoundation/web/display/featuretables/
and open iecommon.xml
modify the line that shows below:
<feature name="requiredMetaTags" xsi:type="xsd:string"><meta http-equiv="X-UA-Compatible" content="IE=100" ></feature>
and change to
<feature name="requiredMetaTags" xsi:type="xsd:string"><meta http-equiv="X-UA-Compatible" content="IE=9" ></feature>
This will force the meta tag that's push with each html page to be rendered as document type IE9. You can take this all the way down to IE7.
Keep in mind, this method isn't officially supported. However, when you have no control over how IE is rolled out in your organization you're really forced to do things out the ordinary to keep the application functioning
Thanks!
-Reg

Is PSE9 Organizer compatable with PSE6 Bridge?

Similar Messages

Maybe you are looking for