Zo


you can use your controller with presets that you have mapped with the editor or by pressing act , well you go to act mode !! then act off , you go back to your presets!!

Hi Zo...I need some clarification "presets that you have mapped with the editor or by pressing act".  Does pressing the ACT create the mapping presets?
 
What I'm struggling with is that with any controller and plug-in you turn ACT on IN THE PLUG-IN by clicking the ACT symbol , move the controls in the plug-in then Keyboard.  This creates a map of the plug in to the controller which is forever there when you turn ACT on in that plug-in again.  There is no ACT button on the keyboard involved in this as there are no ACT buttons on current controllers.
 
The only thing I can think the ACT button does is turn on ACT symbol in tthe Plug-in...???  Which means it replaces a mouse click in the plug-in??
 
Is this right???
 
Mick

so with act you don't have to struggle with presets and midi mapping ( like canal midid one , cc 7 for volume ...) , it dynamic !!!

yes crg i think so like on the vs700 ;) , if not waist of time and money !!

I've been following the discussion on the ACT button.  It occurred to me that I didn't really understand what the ACT button did on my VS-100, so I spent some time last night re-reading the docs and playing with it. 
 
My conclusion is that the ACT button does two things:

• It's a lighted button that tells you when the VS-100 has ACT enabled and it has connected to a Sonar control surface with ACT enabled.
• It's an On/Off button for the local ACT controls: Press button, light goes off, and Sonar doesn't get ACT data.  Press again, light goes on and Sonar gets ACT data.

As far as I can tell, the ACT button is only a local control button and doesn't do anything within Sonar. 
 
My guess is that the ACT button on the new controllers will behave the same.  The only scenario that I can envision where the button might be useful (other than the indicator light) is if you had the controller connected to Sonar and some other MIDI-controlled device at the same time.  The button would let you toggle between controlling Sonar with ACT and the other device with MIDI.  (I'm assuming that the controller will send controller messages for all of its controls.)   Then again, the button's purpose could be as simple as just giving you a way of allowing you to disable ACT.
 
Murray

MurMan

• data.  Press again, light goes on and Sonar gets ACT data.

As far as I can tell, the ACT button is only a local control button and doesn't do anything within Sonar. 
 
My guess is that the ACT button on the new controllers will behave the same.  The only scenario that I can envision where the button might be useful (other than the indicator light) is if you had the controller connected to Sonar and some other MIDI-controlled device at the same time.  The button would let you toggle between controlling Sonar with ACT and the other device with MIDI.  (I'm assuming that the controller will send controller messages for all of its controls.)   Then again, the button's purpose could be as simple as just giving you a way of allowing you to disable ACT.
 
Murray

Magic Murry.  Great info...
 
GT...not sure what you mean...??
 
Mick

gtgarner

mick@itc

Crg


Good question mick. Yes I think you have to turn it on in a plugin. Then there's the Dynamic Mapping button on the PCR 800 that is supposed to automatically remap your ACT parameters to the topmost window i.e. when you pull up a plugin. I assume the 500 has this also? Perhaps the ACT button on the A series is a Dynamic Mapping button?

Hi Craig...Ya..that's what I think, it turns on ACT in the topmost plug-iin, just like dynamic mapping button.  Is it a rename of a button or is there somethign REALLY REALLY cool that is happening.  Hope a baker chimes in.
Thanks Craig.
Mick

 
What if Sonar is in the front? What' if Sonar is the topmost app?

THERE ARE ONLY 8 BUTTONS THAT YOU AN USE at any one time in ACT. 
 
The new controlers have these transport buttons on the top:
 
1. Record  (L8)
2. Pause   (L7)
3. Play   (L6)
4. Stop   (L5)
5. Rewind   (L2)
6. Forward    (L3)
7. Beginning   (L1)
8. End   (L4)
9. Hold button   (L9)
 
OOPS there are too many buttons. How in the world will we be able to use all of the buttons? No room for anything special.  You can't run more than one bank at a time in Sonar. 
 
Why would Sonar make a controller with all of these buttons and you can't use them all?
 
 

When sonar is the topmost window ACT will control the veiw you are in. You must enable ACT in the project  and/or do a midi learn on the functions you want to control. I'd bet there is an ACT preset for the VS100 or you can enter it as a control surface like the V 700 Console in the controllers/surfaces window. 

MurMan


Craig,

Yes.  Installing the driver will install a control DLL for the VS-100, like the VS-700.

M.

But what about for the new "A"series controllers? 
 
Again, ACT only controls 8 buttons at any one time as it stands right now.   Can anyone dispute this?  I hope so.

ACT certainly supports more than 8 buttons or rotaries today. The VS-700 requires more support than that along with other control surfaces. In the Control Surface dialog there is a drop-down to select which bank (of 8) you want to work with.

So even in the generic state you get:

32 rotaries
32 sliders
46 buttons

And that's just the generic template. Then you can decide how the different banks behave, are they locked to ACT or a specific value set, are they jump or match, enabled for ACT and so on.

ACT is extremely powerful and flexible and can be easily customized too.

Robin

MurMan

gtgarner

But what about for the new "A"series controllers? 
 
Again, ACT only controls 8 buttons at any one time as it stands right now.   Can anyone dispute this?  I hope so.

We're discussing a new product that was just announced last week.  Until the controllers / docs become available or someone from Cakewalk chimes in, we're guessing. 
 
Because ACT is a Cakewalk technology, they should be able to extend it as needed. 

Act is a product of SONAR not the controllers.   I use ACT now with my  Axiom 61's.  The only reason I can use ACT is because SONAR lets me. It's not a function of my M-Audio Axiom 61 keyboards.
 
I understand that the VS-700 and VS-100 have special relationships with Sonar that somehow allows for additional buttons to be used.  That's why I'm not asking about those specialized controllers. 
 
Everyone keeps missing my question.
 
With that said - using Sonar - WITHOUT the VS-700 or the VS-100 -  How does one utilize 9 buttons at once?  ACT (in Sonar) only allows  1 bank (8 buttons) at any one time to be active?   Even if Sonar had 1000 banks, Only one can be active at any one time - thefore - on ly 8 buttons at any one time. 
 
I believe Act is powerful and flexible and nice and all of the things that people are saying. 
 
My question is simple: Can a person program more than 8 buttons (using ACT) at any one time using these new controllers - or any controller like the M-Audio Axiom 61?   
  
 
 
 
If someone says "yes", then please point me to the book or anywhere that tells me how to do it.  even with my Axiom.

...wicked


Given how many posts and frustrations vented regarding ACT the one thing I would not call it is "easy".  That's like saying flying the space shuttle is easy....once you have astronaut training. 

I really hope v2.0 of this comes out next version, it was needed just as much if not more than Audiosnap, and Audiosnap got it's upgrade.  

I understand it's not easy, being somewhat at the whim of the hardware one is attempting to attach to, but it's confounding, and never was thoroughly implemented.

Thanks for your reply.  I understand what you are saying. 
 
The problem for me though is that ACT IS EASY.  That's wha'ts so frustrating.  You assingn a controller button to a Sonar function. That's it!!!!  
 
I'm only asking - how do you assign a 9th button and use it with the 1st  8 buttons active. 
 
Maybe it's me. 
 

MurMan

gtgarner

... Everyone keeps missing my question. 
 
... My question is simple: Can a person program more than 8 buttons (using ACT) at any one time using these new controllers - or any controller like the M-Audio Axiom 61?    
   
... If someone says "yes", then please point me to the book or anywhere that tells me how to do it.  even with my Axiom.

Maybe you're in the wrong thread.      This one is on the new controllers. 
 
Why don't you start a new one on your Axiom problem?

You are right.  So I did open an Axiom Thread.  On this thread, - I'm asking about the new controllers before I commit to buy one. 
 
When I created this thread I really only had 2 questions.
 
How much are the new controllers - Answered
How will we be able to use all of those transport buttons at once (with SONARS limitation) - on the new controllers - 
 
 
 
 
 
 

Lanceindastudio

gtgarner

...wicked


Given how many posts and frustrations vented regarding ACT the one thing I would not call it is "easy".  That's like saying flying the space shuttle is easy....once you have astronaut training. 

I really hope v2.0 of this comes out next version, it was needed just as much if not more than Audiosnap, and Audiosnap got it's upgrade.  

I understand it's not easy, being somewhat at the whim of the hardware one is attempting to attach to, but it's confounding, and never was thoroughly implemented.

Thanks for your reply.  I understand what you are saying. 

The problem for me though is that ACT IS EASY.  That's wha'ts so frustrating.  You assingn a controller button to a Sonar function. That's it!!!!  

I'm only asking - how do you assign a 9th button and use it with the 1st  8 buttons active. 

Maybe it's me. 

I would imagine that since you have 8 banks as Robin noted, you can switch banks in which another 8 buttons will be assigned. So, a certain amount of buttons/sliders or pads or whatever per bank, so multiple number of banls by the number of controls each bank has, and that is how much sonar ACT can control- more or less 

 

You are exactly right.  All of your math is correct. I can confirm that you can switch banks. I actually did it myself.  What about that 9th "active" button though. How are these new controllers going to utilize all of those buttons (8+) with the current ACT - 8 button limit.
 
All in all - I don't want to buy something and can't use all of the buttons.  I really like the boards. I mean I really like whats being advertised. I just can't see how Sonar is going to support all of it.  These boards are exactlly what I'm looking for.  I play sonar live every week. Those buttons would be absolutely perfect on stage - if they could work. 
                                I mean look at this:
1. Record  (L8)
2. Pause   (L7)
3. Play   (L6)
4. Stop   (L5)
5. Rewind   (L2)
6. Forward    (L3)
7. Beginning   (L1)
8. End   (L4)
9. Hold button   (L9)
                        That's absolutely beautiful - but how can I get all of those buttons - plus additional ones to work at once?  - with the current version of ACT.

Just noticed a new forum in the Hardware Products section called Keyboard Controllers.
 
edit: I tried to post the first thread, but new posts are not yet enabled.   Bummer. 

Robin is there a way to clear some act mapping or assignement ?

thomasabarnes


gtgarner:

I don't see why any assignable controls on the new Cakewalk controllers should go unused. All you have to do is "Remote Control" assign any other buttons, such as the 9th button you keep referencing, to some button function in SONAR. For example you can Remote Control assign one of the other buttons not assigned through ACT to a certain track's Mute, Solo, or Arm Track function.

Remote Control assigning is done by right clicking a control in SONAR, such as a fader or button, selecting "Remote Control" from the rightclick menu, clicking the "Learn" button, and moving the control on your MIDI controller that you want to assign to that function.
 
A SONAR control you assign by Remote Control will be assigned to the hardware controller you assign it to until you remove the assignment. Also remote control assignment is independent of the control assignment selected through the ACT MIDI Controller Plug In GUI, as I understand it. 
 
But it may be that Cakewalk considers the Remote Control feature a part of Active Controller Technology.
For more info, search for Remote Control in the SONAR Help Topics.

I'm checking this out now.