Skip to main content
e.reed.rogers
e.reed.rogers
Inspiring
October 16, 2023
Question

WHAT IS YOUR MAJOR MALFUNCTION !!!???

  • October 16, 2023
  • 2 replies
  • 704 views

Once again Adobe does not dissappoint: Upon updating Bridge 2023 it now just freezes and I can't even browse any folders at all SO we decided to (begrudgingly) install 2024 with all the "new improvements". Did that help, survey says???: Of course not. What were we thinking? Now we are just staring at a blue rotating circle for the past 7 minutes on a UI with a transparent white film over it (CRASH).  So our question over the past 20+ years is still this:

 

Adobe WHAT IS YOUR MAJOR MALFUNCTION?!!!

 

It's like your contracting a bunch of second graders to work on apps that hundreds of thousands of creatives use to (help) earn their living.  We've yet to see any Adobe update succesfully drop without any major bugs.

 

HERE'S OUR (seasoned) SUGESSTION: Try using some of your fancy AI (nonsense) your importing into your apps to actually debug your (garbage) code and stop depending on users to do it for you AND get your %#*t together. Enough is enough. You meant to tell us you can't accomplish the relatively simple task of sucessfully coding a file management app that doesn't crash or fail to launch on a regular basis?!

Explain why DxO, ACDSee, PaintShop Pro and others can get this right and you cant?

 

Now we can't even open two versions and have to revert back to 2022 which isn't great by any stretch but at least it launches.  It's a frikin file browser for Petes sake. Why can't you get this right?

 

Your dev team should be extremely embarassed.

    This topic has been closed for replies.

    2 replies

    photo:staats
    photo:staats
    Inspiring
    October 17, 2023

    ...what version of windows are you using?  Had the same problem, updated W10 from 1907 to 22h2 and it solved the problem.  Running it now on W11 without any issues.

    P
    polyxo
    Inspiring
    October 17, 2023
    quote

    ...updated W10 from 1907 to 22h2 and it solved the problem. By @photo:staats

     

    Well, I run Win 10 22h2 (as expected by latest Photoshop) and experience dreadful slowness in Bridge 14 too. Very fast drives, 64 GB RAM.

    Here's a (translated) thread in a German forum I found… Summary:

    Thread Opener: "Bridge 13/14 performance on my Windows machine is terrible"

    Forum Guy 1: No, it's not. On my Windows machine, Bridge is flying. Your machine is too old.

    Thread opener buys an insanely powerful Desktop machine (and, of course, installs everything from scratch).

    Thread Opener: I have a great machine now. Bridge is as slow as before.
    Forum Guy 1: Seems as if you had to search for an alternative viewer app then.
    Forum Guy 2: Just use a Mac.

     

      gary_sc
      Community Expert
      gary_scCommunity Expert
      Community Expert
      October 16, 2023

      Hi, @e.reed.rogers, I can't speak about the success of "DxO, ACDSee, PaintShop Pro, and others" as I am on a Mac; some of those are only available on Windows. 

       

      I do not question that your Bridge experience is dreadful. However, how do you explain that I'm having essentially no problems with Bridge, 12, 13, or 14? Sure, there are features I'd like enhanced and/or improved, but the overall functionality is great. I did some tests, and yes, Bridge 14 is a tad slower than (say) Bridge 12, but that's like complaining that my new car only goes 100 mph on the freeway, and I used to be going 150 mph. The extra speed is not going to be used in any real-life activity.

       

      But my Bridge has not crashed or frozen — It has performed well. 

       

      I am aware that some users are having these issues; I follow these forums every day. If the problems you point out are out-of-the-box software-based issues, EVERYONE would have the same issues. But it's not happening. Why?

       

      Perhaps if you could slow down, examine what might be happening, and work with Adobe to locate what's going on with your system such that your Bridge is a disaster, it might help discover the issue for others. But to sit back and demand that Adobe fix what they are not able to replicate is not realistic.

      e.reed.rogers
      e.reed.rogersAuthor
      Inspiring
      October 16, 2023

      I "appreciate" your response however perhaps if instead you "slow down" and re-read my post it may enlighten you as to our situation.

       

      It's a legitimate concern and complaint that, after we (and apparently others) did an update of 2023 and beta and also a clean install of 2024, those versions do not even launch. We don't consider not launching a "speed issue".  We consider it unacceptable.  I've now spend two days (lost work) trying to troubleshoot what the issue is so we can edit and proof roughly 6+ thousand images and counting. Is Adobe going to credit our (and others) subscription for those lost days?

       

      2022 seemingly works just fine with no aparent issues apart from the usual flakiness of Bridge. To have an app work just fine and then not even launch after an update with no OS updates or app installs/updates in between only points back to the app(s) itself.  We have no interest whether a car can go 60mph or 200mph but we DO have an interest in when we pay for a car and turn the key the car will actually start especially after we only had the oil changed!

       

      "If the problems you point out are out-of-the-box software-based issues, EVERYONE would have the same issues. Why?"

      Is that rhetorical? Asked and answered in the same response.  Mac and Windows are not the same exact code. Thus "everyone" will not have the same issues. That's why they removed the Shake Reduction filter which worked perfectly fine on Win and not on Mac M1s.  Adobe likes to throw out the baby with the bath water if it's not a quick and easy fix or will interfere with the bottom line.

       

      "Perhaps if you could slow down, examine what might be happening, and work with Adobe to locate what's going on with your system such that your Bridge is a disaster, it might help discover the issue for others."

      I will say this:

      Adobe does not pay us personally to take time out of our paying work schedule to trouble shoot their software. We are creatives not coders. We pay them for reliable (insert guffaw here) software that will consistently work as they have proudly and loudly promised consistently over the decades.  We have two rigs running. One Win 10 and one Win 11 and both are experiencing the Bridge issue of not launching or crashing on launch. If it were just one rig or even two with the same OS it might be more bearable.  More power to you if you have the free time to trouble shoot Adobe Inc. Cluck Ups but we are running a micro business full tilt and have not time for working for free for a billion dollar company.

       

      "But to sit back and demand that Adobe fix what they are not able to replicate is not realistic."

      I wouldn't characterize myself as "sitting back and demanding that Adobe fix what they are not able to replicate"  I've beta tested many Adobe apps over the past 30 year and have contributed (valuable) input including vast amounts of bug reports and a ton of feedback in the closed forums. We worked for them for free doing that for too long. Now we're wise to them and were not doing that anymore. They pay their employees to code and they pay them well! They also provide healthcare and other benefits. When Adobe offers beta testers and plain old users that exact compensation to troubleshoot their buggy apps then it will be a different story. Sign us up!

       

      We're truly happy for those creatives who don't have any issues with any Adobe apps, however it's definitely not part of the status quo and in reality tantamount to sightings of aliens, bigfoot, Santa Claus and the Easter Bunny.

       

      Adobe charges it's users a (no boxed choice) subscription fee presumably for products that will at least launch. When they don't people have the right to complain.

       

      If people and businesses don't call Adobe and other companies out on their failures and greed then we as creators and members of a "civilized" society are just plain lost to the corporate greed status quo that already exists and is all to prevalent and accepted by the timid.

       

      As for this topic we've aired our grievance. Wheter it's legitmately addressed is up to the users of this product.

      We've no more to add.

      Peace

      gary_sc
      Community Expert
      gary_scCommunity Expert
      Community Expert
      October 16, 2023

      Sure, Mac and Windows are different. I only mentioned my OS to point out that difference. However, I know many Windows users and none of them are having issues like you. 

       

      And since it's showing up on your two computers (both Windows 10 and 11) I again ask why? What is it with your computers, the software on the computer, and/or how it is used that is causing this?

       

      On the other hand, if all you want to do is to rant, please go ahead. I'm sure that will get to the bottom of the issue.

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices