Hi All,

Just wanted to report a fix for an issue that I previously reported regarding the Jog/Shuttle control. 

While continuing to investigate this problem... which was driving me crazy... I went through the MIDI Preferences again. I discovered that the issue was in the "MIDI > Playback and Recording" Section. Under the "Record" heading There are a series of check boxes such as;
 
Allow MIDI Recording 
Notes
Key Aftertouch
Controller
Patch Changes
......... etc.

Now one would think that this is applicable to "Recording" MIDI information. NOT SO! 

I found that if the "Controller" checkbox is left unchecked, you loose the Jog/Shuttle control on the VS700.

Could someone (Mully maybe??) Check to see if they can duplicate this functionality by changing this setting? So... Unchecked ... no Jog/Shuttle... Checked - All is OK!

Next question would be... WHY?

Thanx Guys and/or Ladies

_________________________________________________________________________________________________________________
AMEK/TAC 24x16x2 console, MOTU 24I/O, QUAD Core XEON (16GB Ram, 1 TB), VS700 System, SONAR X2 , yamaha NS10s, Yamaha HS 8s, Axiom pro46, Ensonic ESQ10

I just checked the Master list of fixes. Very impressive. I was quietly hoping to see a 64 bit VC-64 Channnel strip plugin. One of my favorites. And I wonder if they will fix the workability of the Fantom Synth in 64 bit Sonar and Windows. Is a 64 bit Fantom V Synth Editor possible? Though it is workable now, the bit-bridge hook-up is less than finished.

John T


Well, it's a lot better, but it's still not working properly. I'm cycling through ProChannel modules right now using the EQ button, and I can't get it to select the Saturation Knob. I can get the the saturation knob to appear to the console if I click it with the mouse, but the controls don't do anything. I've got to say, I am extremely exasperated and disappointed with this. As much as I hate to be raining on the release day parade, this is a frankly poor show. Four grand, relatively new proprietary hardware set up. What should I do, wait for another patch or just sell off this stuff while it's still got some remaining shred of value? I'm not kidding.

Hi John,

I don't want to jump the gun, but can we figure out if what you're seeing is system specific first? Let's try to work together. There could definitely be a case of it being unique to you (much like many other reported things in this thread).

I'm able to select the Saturation Knob from the console. Can you force-wipe your VS-700 settings and give it another go to see if it resolves it?

Try doing this:

1) Open the Run Prompt by holding the Windows Key and Pressing R
2) Type in the following: %appdata%\cakewalk\sonar x2 producer
3) Click [OK]
4) Locate and rename "TTSSEQ.ini" and "ctrlsurface.dat". Rename them "backupTTSSEQ" and "backupctrlsurface" or something similar
5) Re-launch SONAR and re-configure the VS-700 in Edit > Preferences > MIDI - Devices and Edit > Preferences > MIDI - Control Surfaces.

At this point, give a fresh project a test and see if you can cycle through as intended.

It's very easy to recreate in a new project. Start with a blank project. Insert an Audio track, then a MIDI track, and do this three times, so you've got six tracks alternating Audio / MIDI. This is a fairly typical pattern if you're using separate MIDI and playback tracks for soft synths. Then add a saturation knob to the last audio track. select different tracks from the console and use the EQ button to cycle. All is well.

I'm not quite sure what you're hiding, the midi tracks associated with the audio tracks which are the outputs for the hidden Midi tracks?

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.

John, were you able to try out the recommendation from Ryan?

So are all the hardware functions working for the console now? Is X2a now working as great as 8.5 did ? What's the overall verdict?

To John T,

I'm able to replicate the behavior you reported. I just wanted to acknowledge it since it appears to not be specific to your setup.


To Frick,

Thanks for updating everyone with your experience. I wanted to reply to some of your topics with some information that might be of use.


Fantom VS - "MIDI Devices Aren't Set Up Correctly" Error

Give this article a look: http://www.cakewalk.com/s...X_Troubleshooting.aspx

You'll most likely need to reconfigure the Fantom VS's settings to work properly. This isn't a new issue to X2a, it's really just setup related. It was most likely exposed, however, due to the changes with the Plug-in Manager and resetting/re-scanning. The article above should get you back up and running to avoid that error.

In regards to the actual crash, did the Fault Reporter come up? If so, definitely send the crash through so our dev team can have it on file.


Jog Wheel 

The jog wheel will move between seconds in SMPTE mode or by Bars/Beats. It follows the current setting on the hardware itself when pressing the TIME CODE button on the surface. Moving at a finer resolution would be done with the Shuttle Wheel in this case. Scroll mode services a slightly different goal/purpose but obviously it can be used to navigate around as well.


Nav Buttons & Focus

I can't comment on Windows stealing commands (outside of my area of expertise) but this has been around for some time. If you want to have some fun, hold down the COMMAND button on the surface and move the Surround Panner around ;)

In any case, I'm trying to replicate what you're saying in regards to cycling through the Synth Rack with the nav buttons but don't quite follow. Can you give us a bit more info in regards to what you're seeing? Also, is this specific to the VS-700 at all or is it also repeatable with the keyboard arrow keys?


Console View and Focus 

The behavior regarding the ProChannel opening in the Inspector if the Console View is floating and short is exactly as intended. There's a section that discusses the intended behavior in the .pdf here: http://www.cakewalk.com/support/doc.aspx?DLID=951 .Check out the section for "Opening/Showing/Hiding the ProChannel GUI from the 700 C".

Some additional notes though.

I don't know the exact pixel count, but basically if you're below a certain threshold in Console View height it will open the ProChannel in the more helpful area to what you're viewing, which would be the Inspector. The goal with this is that if the Console View is barely visible (such as in a Meter Bridge setup), you'd be seeing the ProChannel in the area actually helpful to yourself which would be the inspector.

Also to note, if you open the ProChannel in the Console View, it will close the ProChannel in the Inspector (and vice versa). This isn't really specific to the VS-700 though.

Hi All / Ryan,

Another weird problem to report...

I was messing with the synth rack, via the 700... Just got done recording a track. the used "Select" mode via the 700. Went to location on clip that I wanted to "Split". I split the track, and deleted the latter portion. Opened and closed the synth rack a few times, pressing "Syntth Rack" to open and "Shift + Synth Rack" to close.

While the Synth Rack was opened, I pressed the Synth Rack button a few times and noticed a wield redraw to the right side of the Synth Rack, like it wanted to close. So, thats one thing... but then I went back to reset the play head to a different location in the track by clicking in the time rule... and the play head was gone... no where to be found!

I closed the project and re-opened and tried to retrace my steps... couldn't get it to happen again while following the previous steps.

Ryan: Regarding the synth rack issue that you wanted further info on, My 700 is making a liar out of me (dammit! :-)
What was happening when I reported the issue was as follows:

2 synths in the rack, rack opened, working on something else (while rack is opened) click in the rack space (not on any particular synth, but the empty rack space below the last synth). At that point, I was expecting one of the 2 synths to be selected and using the ^, V buttons on the 700, select the synth I wanted. That wasn't happening when I reported the issue, now I cant get it to repeat. I will keep a close eye on when and if this occurs again and the process prior to it happening.

Like I said, these are weird things... like the play head disappearing.

Question: What is the minimum recommended amount VRAM for this GUI to perform at its best?
I'm thinking that this may be the issue. (This is NOT specified in the Minimum System Requirements
[link=http://www.cakewalk.com/products/SONAR/X2-Producer/]http://www.cakewalk.com/p.ducts/SONAR/X2-Producer/[/link] )

I'm currently building a new facility and extensively testing software and components as I go, so X2a has NOT been moved to my production environment yet. (Still waiting to test with Eventide H3000 VST... as SONAR is not listed as being supported. Should probably fix that relationship ;-);

So my staging Machine has an ATI Radeon 3200 Graphics Chip (Shared memory), Quad Core AMD 3GHz Processor, 8 GB RAM, TB HD. My production machine; NVIDIA NVS295 Quad Monitor 2DP (256 MB DDR3) PCIe Video,  Intel XEON QUAD Core @ 3.2GHz, 16GB RAM, TB HD.

So maybe the 3200 Chip could be causing a problem in the AMD Machine???
I Look forward to hearing from you on this one :-)

Thanx,
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 X2a , yamaha NS10s, Yamaha HS 8s, Axiom pro46, Ensonic ESQ10 , Ensonic TS10

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.

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.

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.

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.

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