wow Frick you're doing a very good reporting job! Nice! and thanks!  but make sure you send them to cakewalk with the problem reporter form since it's the only way it will get to them. That being said, thanks for letting us know as well.

Thanx Dyo...

Just trying to help get this thing right. Definately reported to suppport.

The SONAR platform is (can be) awesome... Someone fell asleep at the wheel tho! I'll just be patient... doesn't help getting all worked up about it. As a developer myself, I understand when things get left behind, or the adverse affects of making changes (lets blame it on QA... hahaaa... Sorry QA guys, I guess you can only be as good as your test plan ). Although Cakewalk should recognize all in this forum and provide some good stuff for our efforts

I'm heavily invested, as I'm sure most are... So I try not to ****, just help get it fixed. Although, I am speanding a lot of hours on testing, instead of doing what I want to do. I'm not going to get heavily into a project and have things blow up .  That would suck! That's why I always stage my systems.

So a general question;  Is this forum going to continue?... or is there a new one for X2a?

Regards
Frick

__________________________________________________________________________________________________________________________________
AMEK/TAC 24x16x2 console, 3M Model 79 – 2” 24 trk, MOTU 24I/O, QUAD Core XEON (16GB Ram, 1 TB), VS700 System, SONAR X1c, SONAR X2(308 - Production) , SONAR X2a (351 - Testing/Staging) , yamaha NS10s, Yamaha HS 8s, Axiom pro46, Ensonic ESQ10 ,  Ensonic TS10

John T

No, the problem isn't that the module is fundamentally unrecognised. It all works fine in a basic set up. The problems arise when tracks are hidden from the console.

Hi John, I've just tried this since the X2a release and can confirm it does exist as you've reported and as confirmed also by Cake in this thread. I don't do a lot of MIDI so it was interesting to see your workflow that found this bug.

Is it reported I wonder or does Cake's acknowledgement here negate that requirement?

Interesting also that when redisplay the MIDI tracks the EQ control returns and I didn't get a crash which was promising.
Also when you have the 700C ACT display up, it follows the reported behaviors so hopefully not too hard a fix for Cake.


Cheers.

So Is there any update on this Ryan?
Considering the shambles of X2A with the updates for VS700 (which had clearly not been tested for more than 3 seconds given the problems identified moments after release by John T)  I would have imagined that a face saving fix would have been a priority.
Its a bit like a big comedy chocalate cake on string which gets snatched away when you can already taste it!!
Poor show indeed :(

As far as I can discern, the policy is "say nothing, do nothing". I've had no response to any of my various inquiries since Xmas. I've basically given up now.

All known bugs especially the ones acknowledged by CW will most likely be fixed in the next update X2b.

kday you must work for cakewalk or have an inside scoop. If you've spent your money on this VS system (which isn't a small amount) how is it you never seem to see or ever agree with the attitude or bad taste left in the mouth of those who have spent this kind of money to get into the kind of integration promised? I think many of us here have tried their best to be positive but cakewalk/rolands reaction has thrown that out the window. Now it has left ppl with distrust.

Dahjah, that was sorta a ridiculous statement. Cakewalk just released an X2 upgrade and maintenance fix a few months ago, that fix 250 bugs. Lot of issues were fixed, ok a few still remained. How could you not see that they're trying to fix everything they can identify? 250 bugs were a lot, maybe the next fix update will get the remaining bugs that have been identified? I don't see no reason to wallow is pessimism, things seem like they are going in right direction as I personally see progress. I was just as disappointed as everyone else was about issues unresolved, but to harbor old bitterness like a gunshot would will prevent me from making music, considering most of the important significant issues has been fixed for me personally. But I sympathize with anyone who still feels they are without an important feature, due to bugs, that would have allowed them to achieve great recordings. I'm like everyone else, I paid my money so I want ALL bugs fixed. But right now the system seems workable enough to achieve my musical production goals with it. But please post up all the bugs, so they know what's still broken and needs fixing.

kday


I don't see no reason to wallow is pessimism, things seem like they are going in right direction as I personally see progress. I was just as disappointed as everyone else was about issues unresolved, but to harbor old bitterness like a gunshot would will prevent me from making music, considering most of the important significant issues has been fixed for me personally. But I sympathize with anyone who still feels they are without an important feature, due to bugs, that would have allowed them to achieve great recordings. I'm like everyone else, I paid my money so I want ALL bugs fixed. But right now the system seems workable enough to achieve my musical production goals with it. But please post up all the bugs, so they know what's still broken and needs fixing.

even though I risk getting my rear end kicked by grumpy John T I do have to say that I agree
 
I've learned which buttons not to push to avoid crashes in X2a (which are in fact X2a and not VS-700 issues as these crashes also occur when using the mouse), and I can live without locking channels or hiding some. Although I also definitely want to see that fixed, I have to admit that I don't see the VS-700 as the limiting factor in my production chain

If it works for your purposes, then good luck to you. However, it doesn't work as advertised, and support for it has steadily declined since 8.5. It's buggy as hell at the moment in X2a. I was doing a bunch of fairly intense mixing sessions over the last few weeks, and it would do some kind of freak out every day. You've got to remember, this isn't some tricksy compatibility problem with a third party product. This is Cakewalk's own control surface, and the bugs are ones that it didn't have until Cakewalk introduced them. I also don't think there's an X2b coming.