Yes, the Br 13/14 era has brought all of these types of performance lags across the entire platform. They manifest themselves in various ways, but ALWAYS result in productivity delays in studios that depend on this tool as an asset browser to quickly move through large numbers of files.
Adobe seems ill-equipped to deal with the malfunctions, though they will dutifully tell you that they recognize the problem and will put it in the pipeline. They fail to tell you that the pipeline extends outwards of Neptune.
The short answer is to go back to Br 12.
The long answer is that Adobe has lost its way and can’t figure out how to undo the spectacular fail of a supposed modernization of Bridge in the 13/14 era. That fail has now caused legacy Adobe Bridge customers tremendous distress for almost two years.
The fundamental architecture of the 13/14 era fails as a modern replacement for a unique, state of the art application that Bridge once was.
That is both sad, and a warning.
13
Replies
AdChoices