Compatibility with Lightroom 1.1 and Bridge cs3

I have created several stacks in LR but when I open the folder in bridge, there are no stacks in the same folder. It is like their is no compatibility at all. Is this normal? I thought the advantage of having the latest of both programs is that they were compatible.

They are, but stacks aren't stored in the XMP data. You did write out the XMP data, didn't you?
These are not stored in the XMP data:
Stacks
History states
Virtual Copies
Collection information

Similar Messages

Finder is still crashing with Lightroom 1.3 and Mac OS X 10.5.1

The problem reported with Lightroom 1.2 and Mac OS X 10.5 (Finder crashes when trying to read a JPG whose metadata contain some Lightroom specific development settings) is still present with both updates... Any hope Adobe would provide us with a way to fix existing pictures/metadata?

The Lightroom XMP data for snapshots, which is totally valid XMP data makes Leopard barf because Apple's implementation of XMP in Leopard is not capable of parsing the snapshot XMP. This is most totally Apple's fault...and only Apple can fix it...
The Photoshop CS3 & Leopard issue with text entry in certain tools is another Apple Leopard fault that Apple will need to fix...
There is also an issue with Epson print drivers running under Leopard and Lightroom 1.3 where printing is not picking up the correct data and print come out light...the same drivers will work with CS3 because CS3 is using the older, none Leopard pipeline. Also note that CS3 will NOT be able to print out using the Leopard 16 bit pipeline while Lightroom 1.3 will be able to...as soon as Epson revs their drivers...
Look, Leopard has introduced MAJOR changes well above and beyond the marketing features Apple promotes....eveybody is scrambling...but to Adobe's credit, they HAVE responded well and quickly to those issues Adobe can fix. Those Adobe CAN'T fix will have to be fixed by the companies responsible....

Exposure problem with Lightroom 4 CS5 and Raw 6.7

Hi all
I have recently upgraded from Lightroom 3.6 to the new Lightroom 4 and am genrally pretty happy with it, I tend to use it along with photoshop CS5 extended and also imagenomic Portraiture, but I have found an annoying little problem in doing this and something that I never suffered with when using Lightroom 3.6 and it is this...
when I take an image from Lightroom 4 and click Edit image in Photoshop CS5 and then use Imageonmic to soften skin etc all seems to work well I then carry out any touching up within Photoshop and once finished save it back to lightroom for any final tweaks etc which is fine and all works smoothly, except once I have saved it back to Lightroom the exposure has been pushed up about 3-4 stops at least , meaning I then have to pull it down again and this can sometimes result in extra editing I could do with out. now I know its not the end of the world and is probably just a bug that I'm hoping will be sorted within Lightroom 4 but I just wondered if anyone else has had a similar problem, is it a bug or am I doing something wrong? (although I'm doing the same with Lighroom 4 as i used to do with LIghtroom 3.6 and that worked fine)
Oh one more thing I should mention to get lightroom 4 and CS5 to work properly together I had to go into the Adobe Labs site and download the Camera RAW 6.7 software for CS5 so it could also be a bug here i guess.

There have been several posts over on the Lightroom forum, and other non-Adobe forums also, about this issue: it seems that there's a bug in ACR 6.7RC which causes the image to be over-expose, compared with the setting applied using PV2012 in LR. I guess this is the kind of thing a Release Candidate is supposed to flag up! I was all set to upgrade my own ACR to ensure that PS would recognise my LR4 edits (I normally avoid RC versions and wait for the final), but all the reports of this problem have stopped me from doing so.
In the meantime, best option so far as I'm aware is to process the image in LR (you get the option when you choose to edit in PS), meaning that it does all the rendering before passing it over to PS (otherwise, ACR handles the conversion of the raw file into TIFF). This does however mean that smart-objects and so on are temporarily out of the equation.
I'm sure this will all be resolved pretty soon.
Edit: in fact, one of the posts I mentioned is about ten posts down in this very forum: http://forums.adobe.com/thread/974963?tstart=0
M

Problems with running Photoshop CS6 and Bridge with Lightroom 4 also on the same PC

I was running Photoshop and Bridge, then purchased Lightroom 4. Before installingt 4 I had no problems with Bridge, but since installing 4 all of the photo's that were held in bridge are now gone, but they are in Lightroom. With Lightroom, you are able to edit photos out of Lightroom and into Photoshop when necessary, save and close and it automatically changed the Lightroom picture.
I have two PC's, one has Bridge on it (this one) and the other without, but both have both editing prgrams installed. On the other PC I can switch between Lightroom and Photoshop with no problems, but when I try to switch with this PC, the one with Bridge installed, it will open Photoshop, but the photo will not transfer. If I close Photoshop program and go back to Lightroom, it will tell me that the picture could not be transfered to Photoshop because it would not launch. If I close that message window, it will then launch Photoshop and the picture transferes over allowing me to edit and save as normal.
My question is; does anyone know if Lightroom and Bridge should run side by side, or should I delete Bridge from this PC and see what happens. Bridge is just a holder and organizer of photos, wherease Lightroom does the same, but also has post editing capabilities. The two programs seem redundant, but if your running Photoshop, it's hard to get files out of Lightroom. It seems that you need to open Lightroom first, then you can view and chose a photo to work on, then move it back and forth between the two programs. This seems to make Bridge redundant.
Thanks for any help or suggestions.
he_b_gb1947

Hi, Yes, but that actually wasn't the problem. I start out in Lightroom,
then move to Photoshop if I have something that can't be fixed in
Lightroom. The problem was that when I tried to edit, out of Lightroom and
into Photoshop, I was getting an error message that Lightroom couldn't
prepare files for transfer because Photoshop wouldn't open. But, it had
opened, the picture just wouldn't transfer. If I closed Photoshop,
Lightroom would try again and it would open and transfer the second time. I
ended up going to the Adobe help, chat line, and they looked into my PC and
located the problem, it's now working fine. Thanks to everyone for your
inputs. Most appreciated.
Gary

How do I get Photoshop CS3 and Bridge CS3 to show and open camerea RAW files?

I am not able to see or open Raw files from my Canon 40D in either Photoshop CS3 or Bridge CS3. At first I was able to open RAWS in Photoshop and then I followed directions on the internet at how to manually replace a Camera Raw Plugin so I could open it in Bridge and now neither of the apps work with RAW. In photoshop It says that the file is not supported.
I looked up what plug in I needed and it said 4.2 for a Canon 40 D. I also followed the instructions in the read me file that was with the plugin download. No results from it. I even tried to switch it back to the old plug in to see if I could atleast get back the capiblility of opening it in Photoshop even though bridge was not working...still can't open it in either. What am I missing?

You should install Camera Raw 4.6.
Visit this page and follow the instructions carefully:
PC: http://www.adobe.com/support/downloads/detail.jsp?ftpID=4040
Mac: http://www.adobe.com/support/downloads/detail.jsp?ftpID=4039
-Noel

Suddenly PSE 6 And Bridge CS3 Started Crashing

I've been using PSE 6 along with Bridge CS3 on an iMac for about a year and a half now with almost no problems what so ever. Yesterday Bridge crashed and today PSE 6 crashed twice inside of 20 minutes. Idid an update to iTunes and Quicktime about a week or so ago and an update to Flash a couple of days ago. Other than that nothing has changed on my Mac. Has anyone else suddenly starting having problems or is this just my own problem?
Thanks,
lmb

No, I haven't done that. I have never repaired permissions after installing auto updates. I'm not the sharpest on a Mac which leads me to this question:
how do I repair permissions?
Thank you much!
lmb

Keywords, iPhoto '08 and Bridge CS3

I've got a bunch of photos (10,000) with keywords added with Adobe Bridge CS3. When I import these into iPhoto (with "Copy items to the iPhoto library" checked/enabled), the keywords import.
But when I use iPhoto to add new keywords, these keywords do not get written to the file! They seem to exist only in the iPhoto database. And Spotlight keys off the actual file, so none of my newly added keywords are searchable in Spotlight, only the IPTC keywords on the file. Which is not what I want.
However, if I import a file to iPhoto that has no IPTC keywords on it, and then I add keywords with iPhoto, iPhoto will write these keywords to the file. So it appears that iPhoto won't write out IPTC keywords if the file already has them. That *****. Big time.
Does this mean that if I want to use iPhoto exclusively (abandoning Bridge CS3) to manage my photos etc that I have to somehow strip off all IPTC keywords and then re-import to iPhoto, and then re-tag all my 10,000 files with keywords? Please tell me there is an easier way.

Harper The Explorer
Welcome to the Apple Discussions.
these keywords do not get written to the file! They seem to exist only in the iPhoto database
This is correct. You can write them to the file on export (File -> Export).
iPhoto is your photo organiser, so the idea is that you don't search in Spotlight but in iPhoto or in a media browser that hooks into iPhoto. Remember, if you're using iPhoto you can't really access the files via the Finder anyway.(* See Below for more)
You do need to choose between Bridge and iPhoto. They do the same job but surfing the iPhoto library with Bridge is one of the more common ways of damaging it.
However, if I import a file to iPhoto that has no IPTC keywords on it, and then I add keywords with iPhoto, iPhoto will write these keywords to the file. So it appears that iPhoto won't write out IPTC keywords if the file already has them.
I'm afraid that I'm not sure the point you're making. iPhoto will read the IPTC tags and add to them on export.
*There are many, many ways to access your files in iPhoto:
For 10.5 users: You can use any Open / Attach / Browse dialogue. On the left there's a Media heading, your pics can be accessed there. Apple-Click for selecting multiple pics.
To upload to a site that does not have an iPhoto Export Plug-in the recommended way is to Select the Pic in the iPhoto Window and go File -> Export and export the pic to the desktop, then upload from there. After the upload you can trash the pic on the desktop. It's only a copy and your original is safe in iPhoto.
This is also true for emailing with Web-based services. If you're using Gmail you can use THIS
If you use Apple's Mail, Entourage, AOL or Eudora you can email from within iPhoto.
If you use a Cocoa-based Browser such as Safari, you can drag the pics from the iPhoto Window to the Attach window in the browser.
Or, if you want to access the files with iPhoto not running, then create a Media Browser using Automator (takes about 10 seconds) or use THIS
Other options include:
1. *Drag and Drop*: Drag a photo from the iPhoto Window to the desktop, there iPhoto will make a full-sized copy of the pic.
2. *File -> Export*: Select the files in the iPhoto Window and go File -> Export. The dialogue will give you various options, including altering the format, naming the files and changing the size. Again, producing a copy.
3. *Show File*: Right- (or Control-) Click on a pic and in the resulting dialogue choose 'Show File'. A Finder window will pop open with the file already selected.
Regards
TD

Windows 7 Compatability with Labview 8.0 and missing files while interfacing the FPGA with LV

I am trying to use an FPGA (PCI-7830R) with Labview 8.0. The computer has Windows 7 OS. I installed LV 8.0 in the proper order with the FPGA Module and labview is able to see the FPGA when I open a .lvproj (the FPGA is in the tree) however there is a warning symbol next to the FPGA selection and when I try to open a .vi file that is used on the other stations in my lab (it works on all the other stations), labview is unable to find a whole bunch of files. There are some pictures.
Missing File (there are a bunch more but this is the fist one).

According to this LabVIEW Compatibility LabVIEW 8.0 is NOT compatible with Windows 7
Visualize the Solution
CLA
LabVIEW, LabVIEW FPGA

Font compatibility with Office (for Mac and Windows)

Hi,
Despite extensive searching, I'm struggling with a font compatibility issue between my Mac and my colleagues' PCs. The main points in order:
The fonts work correctly on both my Mac and other PCs.
The font in question is HelveticaNeueLT Std, rolled up into which are several different weights. The files are OTF files. The same files install without any problems on all the computers in question (and show up in Font Book). And the font can be used successfully:
- in Keynote, I select Helvetica Neue LT Std, and underneath choose whichever weight I want
- on PCs, the font and weight can be selected from the drop-down list in MS Office.
- in Office for Mac 2016 (Preview), I cannot select the font from the drop-down list, but can hit Cmd+T, and then select the appropriate font and weight under 'Latin text font'. What is odd is that in the dropdown list, only a particular weight/typeface is shown:
As this is a preview version, I wouldn't expect Office to work perfectly just yet...
When a file is created on a PC, it works fine on my Mac.
Every file I have attempted to open that was created on a PC, and using these fonts, works fine. The fonts display correctly (i.e. including the correct weights), and I can work with the document without any problems. The only odd bit: sometimes in the dropdown box on my Mac it then says (null):
Whereas at other times, the font name shows correctly:
Both of those examples were created using the 'Thin' weight of HelveticaNeueLt Std. I can't see any pattern as to what causes this inconstency.
The problem is that what I create on my Mac shows incorrectly on a PC.
If I create anything using Office 2016 or Keynote, selecting the preferred weight as described above, it shows just fine on my Mac. But when I send the PPTX file to a PC, all weights look identical (it looks as though the PC has just displayed everything in a standard weight). This is the problem I am trying to solve.
To try to get around this, I tried the process of removing the Helvetica/Helvetica Neue .dfont files that come with the Mac - but this didn't work and caused several other problems. Besides, the font I'm trying to get to use as intended has a different name.
All help would be greatly appreciated - my thanks in advance.
John

Thanks Kappy and apologies if it is inappropriate - but just to clarify, my main question is whether fonts used in Keynote should be compatible with other software (in this case Office running on Windows). The Office for Mac Preview is a bit of a red herring but I thought it should be mentioned.
I tried to clarify my first post, but it didn't work. What I wanted to add was simply whether Keynote handles fonts in a way that other pieces of software struggle to read - despite the font itself working perfectly in both environments.

After years of never a problem with lightroom started with lightroom 5 yesterday and today all of a

After years of never a problem with lightroom, yesterday i started wiith Lightroom 5 and today all of a sudden in development mode everything just stopped working. No matter what I do none of the sliders have any effect on the picture whatsoever.
Please help Duncan

you'll need both serial numbers to install the lr 5 upgrade.
if you purchased and downloaded lr 4 from adobe or registered with adobe, you may be able to find your lr 4 serial number under the account used to make that purchase/registration (not necessarily your current adobe id), Adobe ID
and adobe support may be able to help you, contact adobe support by clicking here and, when available, click 'still need help', https://helpx.adobe.com/contact.html

Logic Pro X compatibility with mbox 2 mini and 2009 core duo macbook

I currently have Pro Tools LE 8.0.3 and an Mbox2 Mini, both of which amazingly still work on Mountain Lion 10.8.4. I'm interested in learning Logic and am trying to confirm compatitility with the Mbox2 Mini on a first generation core duo Aluminum Macbook (2.4 Ghz) running 4gb of RAM. The system requirements just say 10.8.4 or later with a 64 bit processor. The Macbook runs fine, and I primarily just record stereo piano tracks, so it's not like I'm going to have 16 tracks running on it. Anyone using an Mbox2 Mini, and any issues with the hardware?

It's not an external device's compatibility with LPX that matters...
It's your external hardware's compatibility with whatever OS X version you are using to run LPX in.... that is important.
Im guessing you upgraded OS X about the same time you switched to LPX?
So....
Make sure you have installed the drivers and software from this page....
http://www.apogeedigital.com/support/quartet#tab-id-1
Failing that, contact Apogee support for further assistance
http://www.apogeedigital.com/support/contact-support
Note: Why is it showing Duet and not Quartet briefly? Are you sure you installed the correct drivers or did you, at one time have a Duet?
Additional: You might want to try this.. though I doubt it will fix things... but this can cure all kinds of weird issues...
Delete both the main plist and the CS file...
Delete the user preferences
You can resolve many issues by restoring Logic Pro X back to its original settings. This will not impact your media files. To reset your Logic Pro X user preference settings to their original state, do the following:
Quit Logic Pro
In the Finder, choose Go to Folder from the Go menu.
Type ~/Library/Preferences in the "Go to the folder" field.
Press the Go button.
Remove the com.apple.logic10.plist file from the Preferences folder. Note that if you have programmed any custom key commands, this will reset them to the defaults. You may wish to export your custom key command as a preset before performing this step. See the Logic Pro X User Manual for details on how to do this. If you are having trouble with a control surface in Logic Pro X, then you may also wish to delete the com.apple.logic.pro.cs file from the preferences folder.
Restart the computer.
Note: if you cannot find either of these files you didn't follow the instructions exactly as described

When is Firefox 4.0 going to be compatable with my AVG Antivirus and toolbar????

I upgraded to Firefox 4.0 and it said that my AVG is no longer compatable with this version. When is the new version going to be compatable, as now I do not have my AVG toolbar and dont feel secure using Firefox 4.0.

The best bet would be to contact the add-on developers and let them know you'd like to use their extensions on the new version.
You can use [https://addons.mozilla.org/en-US/firefox/addon/15003/ Add-on Compatibility Reporter] to do this.

Report Generation Toolkit Compatibility with Microsoft Office 2013 and LabVIEW 2012

Hello community,
on this page there is shown the Report Generation Toolkit Compatibility with Microsoft Office and LabVIEW.
In our company we use actually LabView 2012 and it works perfectly with MS Office 2010.
Has anyone ever tried the "Report Generation Toolkit" of LabVIEW 2012 with MS Office 2013? Does it really not work? Has anyone an emirical value for this topic?

Hi digital_badger,
as you sure have seen in the link it is not officially supported by NI, which means to you one of the following things:
1. You could upgrade your LabVIEW and your Report Gerneration Toolkit to Version 2014 and use MS Office 2013
2. You could just try it with MS Office 2013 which might work but if it's not working you don't get any support from NI.
Even if someone tried it already and it worked for him does not mean that it will work on your machines. It is possible that on some of your machines it could work but not on others. Their can be a lot of problems while playing around with unsupported setups.
3. You could leave your setup as it is and stick to your MS Office 2010.
I hope I could give you a good answer to your question

Mac Pro Compatibility With Older SATA Drives And DVI Connectors

I soon plan to replace my 5 year old G5 with a new Mac Pro and need two questions answered so that I will know what options i have for the transfer of older data and apps. The Apple web site for the Mac Pro includes the following paragraph which gives me reason for concern:
Your Mac Pro includes four drive bays, allowing you to configure it with
up to 8 terabytes of storage using 7200-rpm Serial ATA 3Gb/s drives, up
to 2 terabytes of storage using high-performance solid-state drives, or
any combination of each type of drive. Configure each drive bay
separately.
Does the phrase "using 7200-rpm Serial ATA 3Gb/s drives" mean that the Mac Pro will ONLY work with 3Gb/s drives or that it performs best with 3Gb/s drives?
I currently have two internal SATA 250/300 GB Maxtors (Maxtor 7Y250M0 and Maxtor 6B300S0... both are 7200 RPM but I don't know the data transfer speed). Ideally I would get a Mac Pro with a single 1 TB drive, move one or both of these older SATA drives to the new computer, one temporarily and the other permanently in order to transfer data and Apps to the new machine. If this is not possible then the new machine will need to wait until after I get a new larger FW external drive to use as a data transfer medium (I had planned to do that anyhow). I need to do some advance planning for this so I need to know what to expect in advance. I noticed this possible wording ambiguity on Apple's description of the Mac Pro long ago, but now I need to find out the answer for sure. Apple, you need to be more specific with your words.
Can anybody answer this question for me?
My second question regards display connectors. Does the standard (no bucks added) display card include a standard DVI connector or only the newer Mini-DVI connectors. I think I see a standard DVI connector in the low res picture of the back of the Mac Pro but am unsure. My 5 year old Apple display bit the dust a year ago and I had to replace it with an HP 2009m display (mumble grumble) which does use a standard DVI connector. A new Apple display is too rich for my blood so I plan to continue using the HP display for now and need to find out if I will need a display adapter to go with it.
Many thanks to anyone who can answer these questions authoritatively.
For anyone who asks why I still run 10.3.9 on my G5, I can only answer response speed. New OS versions always act like a lead anchor on a machine with their added overhead and Tiger really does feel like a ball and chain tied to me... it just does not reaspond as fast as I do. I look forward to the speed of a new machine.
Phil Rogers
--

Does the phrase "using 7200-rpm Serial ATA 3Gb/s drives" mean that the Mac Pro will ONLY work with 3Gb/s drives or that it performs best with 3Gb/s drives?
Any commercial sATA drive will do just fine. 7200 RPM is not a requirement.
WD "Green" drives have caused user complaints about "long delay until ready" when installed inside a Mac Pro, but are fine for backups.
You are making the leap from PowerPC to Intel Mac. Eventually, you should re-initialize your old drives to GUID partition table for best responsiveness.
Migrating your System will not be possible. Use the pre-installed System or Install a new System on a GUID-partitioned drive with the release DVD in the box.
Migrating your Applications is a Bad Idea. You should plan on re-installing all your third-party Applications from their release discs.

Fuji Xt-1 compatibility with Lightroom

Hello,
You know the approximate date in which Fujifilm Xt-1 camera will be compatible with lightroom?
Thanks

http://forums.adobe.com/thread/1418130

Compatibility with Lightroom 1.1 and Bridge cs3

Similar Messages

Maybe you are looking for