No, there were many round-trips between programs before these programs were released. But realize that the total number of people working on these as members of the design/engineering team is probably fewer than you think ... and though they almost all work both Mac & PC machines regularly, it's still only a (relatively) few machines. From what I know from chatting with people involved, they do get a lot of issues that come up within the private & internal user-testing program work. And they work at solving those as the come up. It's been fascinating to find how the same software runs totally fine on say the group doing X with it, and then someone else uses the same tools/effects with just a different codec or with a slightly different hardware config ... and everything that seemed totally stable and locked down crashes. Abysmally. And the engineers are sitting there going wth ... I tested with that, what happened? Implementations of various mobo parts drivers ... OS changes & options ... let alone 3rd party things such as AJA or BM cards/devices ... all of these things can work perfectly through a bunch of testing and crap on this other slightly different rig. A bug that lasted through two "generations" that they finally nailed to the wall forever ... resurfaces suddenly. Why? Oh ... maybe it was nVidia releasing a new driver that went around their earlier fix of this effect ... but ... this only affects people on say Mac with these nVidia chipped cards running this precise driver update. Realistically, a very few people. But maybe this completely shuts down professional work for those affected by it. And along the way, judgements have to be made. There are only X team members, working Y hours/week. These are the list of problems, from some that do a slight bit of "hurt" (very annoying but you can work around it) but for a LOT of people, down to some that affect say less than 3% of the user-base, but HAMMER those folks. Now ... where do you put your time resources? That's a decision that will always be wrong for someone. Going in. And at some point, Management decrees "We're going LIVE on Tuesday, with whatever you've got." So ... you end up with making further judgements of the above paragraph, after the fact of Release. It's very public there are some problems ... but how widespread any one problem is will never be openly discussed ... and there's no communication giving a listing of exactly what's been acknowledged & when the fix will be in. Which is where we are. And why some users have a very big bone to pic with management style & practices. And yet, there are some long-time users here who work many hours a week professionally delivering to major "outlets" all the time ... who've never been shut down by anything. Wish I were one of them, but ... I also listen to them when they suggest possibles for people to troubleshoot their machines over this or that issue. They've had some luck, sure ... but also made some (clearly) wise choices. So says the guy who's writing on his laptop as his desktop ... a month old machine ... is going through hours of testing of EVERY part/driver on the mobo from CPU cores on down, to figure why this new machine has completely crashed in two different ways in it's short life. When it's run it's been an awesome machine ... but it's been ill more than healthy. My builder is ragging out with stress tests to find out what's the issue. I hope to be working again by Friday mid-day. Been down since late last Thursday. I've got disagreements with the ways some of the new 'tools' within PrPr/Sg work/interact, but at least, my machine's internal drama can't be blamed on Adobe. Neil
... View more