Bridge CS5 and below are all 32 bit applications.  If you run CS6 in 32 bit mode under Win 8 how does it compare to operation in Win 7 32 bit?

If you use the slide show feature in Win 8 how does it act compared to Win 7?  If slower it could be the video card driver.  If so open edit/preferences/advanced and check "use software rendering" and see if that makes a difference.  If it does it is definitely the video card or driver.

When you installed CS6 did you accept the default?  If so it also installed the 32 bit version.  Open Win. Explorer and click on Programs(X86) then Adobe and Bridge.  Expand Bridge and look down list the the B icon (bridge.exe).  Open it.  Make sure no other Bridge is running.

Not an expert in computers but you may be looking at some software interaction.  The primary suspect is the anti-virus program.  Might try a temp. disable and see if that helps.  I have read some posts where they were using some small brand of anti-virus program and had to uninstall it to stop the delay in photoshop functions.  Just disabling it did not work they posted.

image_gsam wrote:

[...]

I've opened this as a case with Adobe support "technicians" but that has not got me anywhere.  I'll stick with them and see if it can be resolved.  Thanks again for your help - - George

I've posted about the same delays, a week or two ago and again today... I just noticed your post and see you are having the same problems that I see.

Has adobe responded in any way to your query?

In my case, I end up using CS5 bridge since the hefty delays in CS6 render it too slow to do real work with.

However, some things cannot be done from CS5.. an example is selecting images and sending them thru photoshops image processor.

That is normally done by an item on the tools menu... but CS5 does not have that item unless I also run CS4 photoshop (don't have CS5 PS).  So I have to revert to a CS4 version of PS to do chores involving photoshops "Image processor". There may be a way to make that item appear on the CS5 brigde menu, but I don't know it.

Fortunately that doesn't come up real often so having CS5 stand in for bridge while using all the CS6 tools seems to be the best I can do so far.

The fact that there is such a remakable difference between the performance of CS5 compared to CS6 brige is probably a hefty clue toward discovering what is causing the problem... if only soneone at adobe will look into it.

Please keep us posted as to any resolutions you may get.

I'm having the same problem under Windows 8 x64 too! Even selecting from one folder to the next without opening it, pauses Bridge for 10+ seconds. It's weird because Lightroom doesn't have this issue so I figure it must be specific to something within Bridge. I'm not on an AMD CPU either if that makes any difference.

You should use the manufacture website for the driver updates.  Microsoft may be 6 mo. behind.

Drivers for Win 7 are still having problems catching up to CS6 and Win 8 will be further behind.  That is problem with any new OS. 

I posted about the same problem although I'm running Win7/64.  The performance is U N B E A R A B L Y  slow.  Same as posted above.  Click and wait 10 seconds for a responce.

I'm on a beast of a machine.  Supermicro server running

Win 7/64

CS6 Creative Suite (Cloud)

Dual Xeon X5650

48Gb RAM

Quadro 4000 (GUI)

2x GTX 570's (Render cards for Resolve)

Red Rocket

SSD - OS

RAID 0 - Media

Seperate cache drive

External RAID for render target

Drivers are updated.

Even with all that Bridge is a total slug.  Please help Adobe!

Hi fellow Photoshop user,

It is easy for Adobe to blame other software. If one puts out a software

application (especially an entity as large and powerful as Adobe), it

better work right. Bridge CS6 does not! There is no excuse, other than

corporate laziness and complacency! I think I will skip upgrades until

this problem is resolved.

By the way, I tried the AMD/ATI driver that was last was approved for

Photoshop (I think it was released sometime in 2011) with no

improvement. Needless to say, I reverted to the current driver. By the

way, the delay on my system is around 16 seconds (I timed it) from the

time I right-clicked on a photo to when the context menu popped up.

Totally unacceptable!

Jac

My system does not have a problem with any other application. It

consists of Windows 7 Professional 64 bit, AMD FirePro V5900 (FireGL V)

with latest driver (9.003.3), Photoshop CS6, Intel i7, 3.07 GHz with 24

GB memory. BTW I still have CS5 on my machine and Bridge CS5 works

perfectly! Bou, of course if I use Bridge CS5 and click on a file to

open, it opens in Photoshp CS5. Not a problem by itself. The only

problem occurs when I want to use a "new" feature available only in CS6.

Jac

jfpmft wrote:

 

By the way, I tried the AMD/ATI driver that was last was approved for

Photoshop (I think it was released sometime in 2011) with no

improvement.

The latest ATI driver was release about a month ago Catalysis 12.10.  It fixed some problems in 12.08 but added some others.  Current advice, at least for Photoshop, is to use 12.08.

Software interference is extremely difficult to narrow down as virtually every windows machine is different.  I have read posts where disabling the anti-virus did nothing, user had to uninstall before problem went away.  Not that this is the issue, but just an example how complex trouble shooting can be.

CS5 is not the same program as CS6, basically it was just recoded from 32 bit to 64 bit.  Someone with the problem might try the 32 bit CS6 version and see if there is any difference.

What happened 3 weeks ago?  New hardware, new software, major software update, hard drive full? 

i had the same problem, bridge cs6 x64 was freezing constantly, now i'm now runing my cs6 bridge (5.0.2.4 x64) on my win8 in Vista SP2 compatibility mode and works fine

I discussed this "solution" with Adobe back in July.  Here is their response.

"There really should be no reason that running in Vista compatability mode would change the behavior of the application. Vista and 7 are so similar at the fundamental level that there shouldn't be any advantage.   Really, this is likely pointing to a lack of OS updates being installed, or installed improperly. One person mentioned that a new user account fixed things. I have a feeling that would true of more folks who are willing to try it. I'll run this by my collegues though."

But if it works it is better than the alternative.    curt

Bravo Ciwir! Excellent!

Now working normally with me.

Thanks a lot Ciwir

Setting up a new account in both the Mac and Windows environment has work on a number of vexing problems, including this one.  Why it takes a new account is unknown as in most cases every other option was tried.  It seems to boil down to some kind of a permission problem, or a default setting that does not want to be reset.  The new account sets it up like a fresh install.

Curt Y wrote:

 

Setting up a new account in both the Mac and Windows environment has work on a number of vexing problems, including this one.  Why it takes a new account is unknown as in most cases every other option was tried.  It seems to boil down to some kind of a permission problem, or a default setting that does not want to be reset.  The new account sets it up like a fresh install.

But do you concur that the fact of setting up in new account removing the problem, rules out it being an 'updates' problem as suggested by the Adobe staffer reponding to you?

Oh and please excuse the lazy request about compatability settings.  I googled up a howto in seconds.

Unplug your network cable and see if the lag goes away.

I had the exact same problem, a 10 second lag when trying to certain tasks. After a month of troubleshooting, I finally discovered that it was, of all things, a networking problem. My company (like most companies) has a group policy in place that redirects my "Library" folders (Documents/Pictures/Videos ect) from my local drive, to a network drive. Bridge adds these locations to your "favorites" by default, and for some reason, it seems to puke all over itself if they're pointed to a place on the network.

How I fixed it

1. To make sure Bridge wasn't trying to cache to the network, I had IT stop redirecting my library locations to the network.

2. I removed any "favorites" that were pointed to a network drive.

I would try step 2 first, because I think this might have been the problem. I just had IT remove the library redirect because I my files are far too large to store on the network in the first place. It seems that IT directors don't like it when you fill up the company SAN with archived RAW files

Edit: I fogot to mention that I am on Windows 7 64bit

Message was edited by: Bender8472