CS4, reverting to CS3 (and getting a refund!) but still interested in opinions

Question

I've just spent the last 24 hours trying to muscle my way through the myriad of problems I'm finding with CS4. I've managed to alleviate some, but still can't produce my end video.
To start off, I'm running on Windows Vista. All the problems seem to centre around Media Encoder (although I didn't get far enough to play with Encore or On Location).
Initial problems where to do with installation. If CS3 is removed after CS4 is installed the link to Media Encoder fails, you then have to removed CS4 and reinstall. Uninstall doesn't work correctly or completely, it leaves a fair amount of files behind that have to be manually removed, failure to do so resulst in Error 2 on reinstall (I'm guessing because the install tries to create some of the working directories, and fails because they are already there?).
After reinstallation, the job appeared correctly in Medie Encoder when it was fired up from Export in PP, and it was also now possible to add files to Encoder directly. I tried a test run of my project with the following settings:
H264
Width : 1280
Height : 720
fps : 25
Field order : Progressive
Quality : 4.0 and 5.1 (tried to runs)
Bit rate : can't remember, but atleast 12M for target and perhaps 30M for max?
VBR 2 pass
Sound : AAC
The end video was incredibly jerky.
I tried a second time using the following settings:
Quicktime
Codec : H264
Quality : 100
Width : 1280
Height : 720
fps : 25
Field Order : progressive
Pixel Aspect : square
Use maximum bit depth ticked
Bit rate : 1k (I tried to move this to 5k however it kept reverting back)
Sound : AAC
Export from PP initially failed, the job appeared in the queue, however nothing actually happened, it just sat there. I read on another post that updating Quicktime to 7.5.5 fixes that (does PP rely on Quicktime for the codec?), tried and the job then started.
Upon completion, the video played smoothly, although quality was low (low bit rate?). However the video to audio sychronisation was completely out. 30 seconds of play, and the sound was around a second behind the video.
I then tried applying all of the updates. As with other people, the Encoder portion failed initially (even though I started the update process from Encoder), but then succeeded the second time.
Upon completion of the updates, the problem reverted back to the initial, i.e. the job started OK, but didn't actually do anything.
The render settings I'm using are required by the web site I'm trying to create this video for, and also worked without issue in CS3.
It would seem to me that the Media Encoder portion in CS4, on the Windows version atleast, is seriously flawed (and no, I'm not going to buy a MAC ;-)).
I would like some answers to these problems, despite all the issues, I did like the overall look and feel of the product compared to CS3, and I also now need the AVCHD support.
Forgive any innacuracies in the phrases used, settings etc, CS4 has been removed from my system for now, so it was all from memory.

Answer 1

Stuart,
Maybe I'm just too old and have seen too many "revolutions," to get onto that wagon.
However, the more I follow CS4 threads, the more I am starting to question whether I will upgrade from CS2, or not. Some things look useful to me (more than with CS3), but then there are the problems.
Adobe IS listening, as evidenced by a few of the folk on the team dropping by to give info on updates, etc. Having some major "fixes" so soon upon release, indicates to me, that they are working on it.
I didn't move to CS3 for similar reasons. Also, it really did not offer ME much in the way of useful features.
Whether it's through bug reports, posts in the forum or direct correspondence with Adobe, the best way to get their attention, and provide them with useful data, is to offer as much detail on the specific problem(s) as one can and demonstrate repeatability. General posturing might make one feel better, but does little to get improvements in the program.
As you state, some of the problems are probably OE. Some are system specific, and others are related to 3rd party software. Still, there do seem to be a lot of issues that ARE CS4-specific. These worry me. These are the issues that I would like to see Adobe address. So far, they seem to be, albeit maybe not quickly and efficiently enough for many users. CS4 does seem to be more of a "work in progress," than I am willing to take on just yet, especially as it would also likely mean a new workstation and new OS (one that is not without some problems of its own and a new learning curve also).
I'm fortunate enough to have CS2 and a rock-solid group of systems to use it on. It does 95% of what I'd like for it to do, and that extra 5% has yet to intice me, especially with the "problems" that I've been reading about.
As for the Adobe faces in the forum, they have shown up, when they could actually tell us something. I view that as a very positive sign. Even when they have dropped in, too many people demand to know "WHEN?" something will be fixed. If they knew, they'd tell us.
I'm sorry that CS4 has not gone more smoothly, upon release. It saddens me greatly. However, it is also why I will be waiting and keep reading. For me, this will be an upgrade that will be very expensive, because it's not just the software. I hope that Adobe does get it all running and running smoothly.
I would anticipate, and hope, that the next update fixes most of the issues. I anticipate, and hope, that Adobe will provide us with the same sort of info on it, as they have done with 4.0.1 & AME's update. I also hope that the forum subscribers will concentrate on the info provided and cease with the "WHEN?" The Adobe posters do not know yet, as the coders are still working on it. It *seems* that rushing to meet a product release date might have gotten us into this trouble to begin with.
My fingers are all crossed. Maybe 4.0.2 will signal that it's time for me to make the jump.
Hunt