D300 vs. New ACR

[eselby]

I use Bridge as part of my workflow. In fact, I've become highly dependent on it.

After updating ACR a few weeks ago, none of my D300 RAW files will open beyond basic thumbnails in Bridge, and I can't add or edit metadata either.

My D70 RAW files still work as promised - even new ones (yes, I still shoot with my D70).

I have not found a single thread or message about this anywhere else, so I'm beginning to wonder if its just me.

FWIW, Lightroom handles the RAW files just fine.

Any ideas?

[Jeff Perry]

Are you using the new ACR ver 4.5?

Can you open the D300 NEF files in ACR thru CS3?

ver 4.5 is not compatible with Photoshop versions earlier than CS3, so I would expect conflicts with versions of Bridge before CS3.

Jeff

[eselby]

Yeah - I can open and edit with no problem, I've just lost the ability to be able to see larger than a thumbnail and update/append metadata

[Jeff Perry]

Ed, sorry but I am not sure I understand what you can no longer do. I have D300 NEF files viewed in Bridge CS3 with ACR 4.5 installed, with no difficulty. I see them in thumbnail mode as well as filmstrip mode which displays a larger image. I can also edit the IPTC Core metadata without a problem.

When you say "I've just lost the ability to be able to see larger than a thumbnail and update/append metadata" what do you mean.

Jeff

[m332720]

Ed
I to had this problem. Last week as a matter of fact. The only way I was able to get bridge and ACR to play nice again was to totally un install CS3 and re install it.
When I say totally I mean totally. After I ran the un installer I deleted all of the CS3 folders.
I then down loaded a fresh copy of CS3 and reinstalled it.
It sucks but that was the only way I found around the problem.
Be sure that you have exported any actions you want to save and have the serial numbers for any plug ins before you do this.

Michael

[eselby]

Everything you can do - I can no longer do with any of my D300 files - and I have the same set up as up.

Actually, you answered my question - it isn't and Adobe problem. Its my problem. Now I have to figure out how to fix it.