MPE layer bug(s) - GTX 480 and CS5 trial

Question

Hi All,
Due to some strange MPE-PPro behaviour, I am now having some last minute doubts about whether to jump up to a full version of the production suite - or perhaps wait for a .1 patch.
Please advise if any of you can spot where the cause of these problems might lie...
These are fairly easy-to-repeat MPE-related bugs in the trial version of PPro CS5, so far I have found issues both with scaling and when duplicating clips to new layers.
Current hardware is as follows (will be looking for a new i7-920/X58 mobo combo if CS5 is purchased)
Mobo- Asus Striker Extreme
CPU - QX6700 C2Q@ 2.66Hz
RAM 4G
Win7 Pro x64
So for testing purposes, I have "enabled" MPE using a GTX 480 and all seems fine for basic cuts-only or opacity fades on multiple layers. The bugs I have found seem to be related to adding more than 2 effects (even on just a few short clips...)
Scenario 1:
1) DV clip on layer 1, second DV clip on layer 2 scaled to 25% and positioned top left corner. Yellow line - playback behaviour is OK so far.
2) With MPE enabled, if I add some fast CC to layer 2 clip then the footage plays back as though scaling is reset to 100% (although the slider still shows 25%)
3) Switch from MPE to SW preview and the clip correctly returns to 25% scale (still with CC applied). Switch back and the scaling is again lost.
Scenario 2:
1) DVCPRO 1080 25p clip on layer 1, duplicated to layer 2 with a gaussian blur and 15% opacity (creates a basic glow effect).  Yellow line - playback behaviour is OK so far. Repeat for a second clip on to layers 3&4 with a simple opacity fade-up at start on each, overlaying the last few secs of 1&2 for the length of the fade.
2) With MPE enabled, layers 3&4 only show when the layer 1&2 clip has reached the out point, ie the fade up on layer3&4 is "ignored" and the second clip only cuts in when the first clip has reached the out point. All the time with a Yellow line.
3) Switch from MPE to SW preview and everything works as it should (after preview render is generated of course).
So my questions are, can anyone with a GTX 285 or (certified) Quadro repeat either of these bugs? Am I better to wait until the GTX 480 is officially certified in a few months (possibly including a patch) or is there another cause elsewhere in my current hardware?
MPE is really nice (in theory at least) but it worries me that it fails to calculate opacity occlusion and scaling correctly for such relatively simple sequences.
Any suggestions/opinions/comments welcome!
Cheers,
Dave.
Broader Pictures

Answer 1

Hi Harm,
I've created a fresh test project and recreated a timeline similar to scenaio 1 (sticking to DV to rule out demanding codec issues)...
Here's the OK intial version of the timeline:
LAYER4: PIP clip scaled to 25% pos. top left, no other effects just an opacity fade-in-out
LAYER3: PIP clip scaled to 25% pos. top right, no other effects just an opacity fade-in-out
LAYER2: PIP clip scaled to 25% pos. bottom right, no other effects just an opacity fade-in-out
LAYER1: Simple clip no scaling full screen (backdrop), fast cc effect w/ default values
Preview bar is yellow and play back is fine with MPE on.
THEN, if I add any other MPE-enabled effect to any layer, the preview goes red and the top-most layer disappears from the preview monitor!
The rendered preview also omits layer 4, as soon as I turn off MPE, the timeline returns to red and layer 4 pops right back on the monitor!
Is this just a trial limitation of the MPE module, rather than restrict the 'extra' effect/layer to render-only you lose it altogether? This just seems a bit of a strange way to promote such an important feature, it certainly hasn't helped me decide on if/when to purchase, or perhaps it has?
Any more thoughts?
Thanks,
Dave.