Lightroom classicmac10/4/2023 ![]() ![]() Why, with your experience and your expertise would you not follow your own advice? I just don't understand your attitude. An operating system is far more sophisticated than any piece of photo software. ![]() I always encouraged my employees to stay away from new operating systems for several weeks to a month following an initial rollout for precisely these cases. If you think you understood the rollout, then why install a production piece of software on a new operating system. You warned everybody not to install it, yet you did? Did you test it in beta? I've been involved in IT since 1965 and in photography since Brownie cameras. Prioritization and a fast delivery would help - one week is a very long time for a blocking issue. The Ventura rollout is going on right now - I warned everybody I know not to install it.īuying a Mac with 1 or more TB is not the cheapest workaround, but if Adobe likes to send one to me. This is a mean bug which concerns lots of users. The issue is now one week old, the deployment is still not planned, if I understand the statements by the Adobe people in this community correctly. Opening a file on a mounted folder is not a sophisticated test case. ![]() I do not need AI teeth masking if I cannot access my pictures - so the responsible person(s) for bugfixes seem to have some prioritization problems and do not know what the customers need for their work: It is not my job to foresee the bugs ocurring between LRC and IOS - I just pay for the license - that´s the deal. In this case the rollout of LRC was to hasty - it is normal and not a user error to install a MacOS update as well as to perform a Creative Cloud update - both should be tested in all possible configurations on the vendor side before, of course focussed on the brand new MacOS - and not by the users in production. I understood the timing issue between Apple and Adobe very well, i have worked for more than 20 years in IT and IT management. Sorry, this is the price you pay for a hasty operating system upgrade. There is absolutely no way Adobe could have foreseen this problem of a very last-minute change by Apple. So, again, it begs the question of why update operating systems at version XX.0 when bugs like this are certain to arise. Adobe's fix will probably have to test for whatever Apple ends up fixing,because people who've installed the first post-release beta of Ventura are reporting the problem is now fixed. Those of us running the first RC and upgraded to LRC 12 before the final release of Ventura who ARE NOT having any problems. It is what happenedbetween the time LRC 12 was released and the final release of Ventura that created this particular problem. IIRC, Apple actually had a second RC before the final release a few days later. ![]() Then, unexpectedly, Apple released Ventura with an unexpected "fix" subsequent to the RC of Ventura. Everything worked then with LRC and the Ventura RC and LRC 12. This was the first year Apple didn't announce a precise release date for Ventura, and as it turned out, Lightroom was released a week before Ventura. Adobe Max is where Adobe releases new versions and is scheduled long in advance. Everything was fine through the first Release Candidate of Ventura, which was delayed this year. Apple didn't fix it in their subsequent betas, so Adobe devised a workaround so they could continue testing their own betas of LR. Adobe found a bug in the early beta of Ventura and noted it to Apple. I agree that LRC catalogs should open, but you apparently don't understand the issue and how it arose. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |