P: Hanging, requires force quit

Jeremiah, you say in one post "It is funny how the Adobe tag team works. Haha." and in your very post "Of course they don’t even monitor this forum. Oh man it just gets better and better." So which is it, whos is the Adobe tag team you mention that doesn't monitor this forum?

I think Aaron makes some valid points in his posting when he says "...let's all be clear here, it isn't like the program doesn't work, only the updates have caused the issue. You can roll back (like i did to 7.2) and everything is fine, I just don't have the new features working, and so what?

We aren't paying for NOTHING we are still getting a very robust software that has some bugs in the latest updates, which we can circumvent EASILY by their own software."

I am upset we havent seen any movement on this too, but them offering you to be a part of the solutio nadn you denying them seems vindictive and unhelpful, and i dont see why you woudlnt want to help remedy the situation.

And let's all be clear here, it isnt like the program doesn't work, only the updates have caused the issue. You can roll back (like i did to 7.2) and everything is fine, i just dont have the new features working, and so what?

We arent paying for NOTHING we are still getting a very robust software that has some bugs in the latest updates, which we can circumvent EASILY by their own software. I dont see how anyone's workflow could have been hampered so much by these bugs in the newest updates, seeing as they didnt offer MUCH that wasnt working well in 7.2

Should we be seeing more action IMO, yes. Should we get more communication, yes.  Should the have rolled out an update with bugs, probably not if they werent going to answer problems quickly.  But that doesn't mean we have to be spoiled brats about not having functionality, and not getting our money out of our subscription fees.  They need to be more careful, yes.

It is annoying, it is kinda disrespectful, but not to the level that we should be vindictive to the point of making the problem last LONGER by not helping out of spite for not getting your money's worth on a program which you can still do 99%+ of what you could do before the update just by rolling back to 7.2 until this gets sorted out.

I was one of the 1st people to post about this issue after the update, and i was ATTACKED by other members of the forum that this wasnt even an issue at all, and it was isolated to me.  And that by even asking about the problem and demanding they do something about it was ridiculous.

Be patient, roll back, and keep an eye on the threads about updates to the situation and fixes. If they ask you for help, help them, it will only help yourself and the community.

I am upset we havent seen any movement on this too, but them offering you to be a part of the solutio nadn you denying them seems vindictive and unhelpful, and i dont see why you woudlnt want to help remedy the situation.

And let's all be clear here, it isnt like the program doesn't work, only the updates have caused the issue. You can roll back (like i did to 7.2) and everything is fine, i just dont have the new features working, and so what?

We arent paying for NOTHING we are still getting a very robust software that has some bugs in the latest updates, which we can circumvent EASILY by their own software. I dont see how anyone's workflow could have been hampered so much by these bugs in the newest updates, seeing as they didnt offer MUCH that wasnt working well in 7.2

Should we be seeing more action IMO, yes. Should we get more communication, yes.  Should the have rolled out an update with bugs, probably not if they werent going to answer problems quickly.  But that doesn't mean we have to be spoiled brats about not having functionality, and not getting our money out of our subscription fees.  They need to be more careful, yes.

It is annoying, it is kinda disrespectful, but not to the level that we should be vindictive to the point of making the problem last LONGER by not helping out of spite for not getting your money's worth on a program which you can still do 99%+ of what you could do before the update just by rolling back to 7.2 until this gets sorted out.

I was one of the 1st people to post about this issue after the update, and i was ATTACKED by other members of the forum that this wasnt even an issue at all, and it was isolated to me.  And that by even asking about the problem and demanding they do something about it was ridiculous.

Be patient, roll back, and keep an eye on the threads about updates to the situation and fixes. If they ask you for help, help them, it will only help yourself and the community.

Of course they don’t even monitor this forum. Oh man it just gets better and better.

It is funny how the Adobe tag team works. Haha.

Well JC, the program I speak of is Capture One Pro, and while very many people believe it has a superior RAW conversion (I do not think that, though), I will say that it is just as good. But I really prefer Lightroom Classic to everything else and I use the other Adobe products, as well. Also, I have a huge archive of Lightroom catalogs. So I hate to see them hack up Lightroom Classic and leave it unattended with problems that render it a complete unusable mess. So I’ll continue to harp on about it until they fix it. That is, if they ever actually do it.

If you're really not out anything, and Adobe is so screwed up now as you've argued why don't you speak with your feet and change applications/companies?

And one more thing since your curious about my workflow decisions : there is another program from a different company that I have been using in the meantime, and it is working just fine. So I’m not really out anything here. I will be glad when Lightroom is usable again, though.

They're not asking you to spend hours doing free beta testing. They're offering you early access to a build in which they believe they've fixed this issue, and they only want to know if it doesn't solve it. Or you can carry on putting up with Lightroom hanging until the official release, but you're only hurting yourself in the process.

Like I said: if they want to pay me to do their work for them, I’m open to it. If they want to waive my subscription fee while I’m doing their beta testing, I’m open to that, as well. Paying my subscription fee while I test out their beta builds and provide them with important R&D info is indeed something I’m opposed to “out of principle” because it is just plain wrong. Back in the beginning when Lightroom
was in beta, there was no charge for using it during this time. Adobe needs to get their act together ASAP.