Paul P
Beepster
Not trying to diminish the problems of those actually having problems with this but is a rollback to B and/or not using the CE (or whatever causes this... still didn't get an answer on that) and/or simply unticking the 64 bit option as you work until the patch is released not an option?
Well, if your project had a bunch of mono interleaved tracks with the CE on each and you count on the functionality of the 64-bit engine, you'd probably be a bit annoyed. Apparently, the EQ doesn't work properly in this situation either.
Ah... this is the recipe? Do the tracks have to be Mono Interleaved? I'll investigate... and yeah if it was absolutely imperative that that particular recipe was required I would indeed be annoyed. However I would try rolling back or if there was no urgent need to push something out the door (which I know some of our pro members need to do like GIM) I'd just disable the 64 bit engine and wait for the patch.
But as I mentioned earlier... for the heavy duty pros who this would/could be a major issue for is the CE really that outstanding? I mean it's a nice/interesting tool but it seems to me for that level of production those types of outfits would use one of the more powerful emulators. If a mix is in progress and you've already mixed into it that would definitely be a problem but again there is the rollback or if the project was started in X2 it could be done there (I've never had problems mixing in X2... just editing and tracking weirdness).
So with all that we kind of widdle down the pool of people where this is a CRITICAL issue to be rather small AND we have been guaranteed a fix with the next patch which seems to be taking a little longer than expected but seems to be imminent. I'm going to take a guess and say at the latest we'll see it before the new year like we did with the X2a patch. That feels about right.