Hello
when I use the plugin (surface control) A-Pro, Sonar x3e has a latency to start a new project, and I do not have this problem when I turn off or delete the control surface. you have an idea?
Regards

BlackBird67
Hello
when I use the plugin (surface control) A-Pro, Sonar x3e has a latency to start a new project, and I do not have this problem when I turn off or delete the control surface. you have an idea?
Regards

I have the A-800 Pro keyboard - After turning it on, it takes Sonar 10 seconds or so to get ready.  Well, it's always slow opening, much slower than previous Sonars, but then once it looks open, with the A-Pro on, it stays greyed out on the left side and top for some time before being ready.
 
Is that what you're talking about?
 
Randy B.

I assume you have specific requirements I just use act and it's fine. If not please be aware there are drivers and firmware updates on Roland's site. Cheers.

CakeAlexSI assume you have specific requirements I just use act and it's fine...

Hey, Alex - Now that I know you use A-Pro, does ACT become engaged for you by just opening up Sonar?  A friend of mine who uses A-Pro says he turns on the keyboard, opens Sonar - and the ACT button on A-Pro lights up automatically.  That's never worked that way for me.  ACT has been pretty much a - huh? - to me.  I have some control maps programmed in A-Pro, I use those, I'm happy enough.
 
Randy B.

My A-800 Pro works great.
Make sure you have the latest drivers from Roland.
I have no latency issues. (I control that with my Sound Card)

Every time a project is opened for the first time after Sonar is launched, Sonar transmits a control map specifically designed to be used with Sonar (called "SONAR ACT MAP 2") to the A-Pro hardware to overwrite map #19 (this doesn't happen if you haven't added A-Pro to Preferences > MIDI > Control Surfaces). This is why you see the ACT button automatically turns on and see "Receiving..." on the LCD.

rbowser

CakeAlexSI assume you have specific requirements I just use act and it's fine...

Hey, Alex - Now that I know you use A-Pro, does ACT become engaged for you by just opening up Sonar?  A friend of mine who uses A-Pro says he turns on the keyboard, opens Sonar - and the ACT button on A-Pro lights up automatically.  That's never worked that way for me.  ACT has been pretty much a - huh? - to me.  I have some control maps programmed in A-Pro, I use those, I'm happy enough.
 
Randy B.

Act works for me fine on latest Roland drivers and firmware as long as I set it up like this:
http://www.procom.no/pdf/Control%20Surface%20Plug-in%20for%20SONAR.pdf
 
Don't install any Act software (ignore the installation procedure section/ first three steps in the document), if you have remove it (it's built into Sonar).
 
Cheers :).

Jlien X
Every time a project is opened for the first time after Sonar is launched, Sonar transmits a control map specifically designed to be used with Sonar (called "SONAR ACT MAP 2") to the A-Pro hardware to overwrite map #19 (this doesn't happen if you haven't added A-Pro to Preferences > MIDI > Control Surfaces). This is why you see the ACT button automatically turns on and see "Receiving..." on the LCD.

Thanks for the reply, JlienX - But none of that happens for me.  The ACT button has never turned on automatically, and there's no "Receiving" display on the LCD.  But the keyboard's controls are engaged, with the faders hooked up and controlling the track faders in Sonar, for instance.
 
Often, but not always, I'll start to work, and the keyboard isn't controlling Sonar - because in Preferences, the A-Pro has been dumped as my surface, and I have to set it up again, save Preferences - and it'll stay there for awhile, then mysteriously just disappear again on another day.
 
Randy B.

rbowser
Often, but not always, I'll start to work, and the keyboard isn't controlling Sonar - because in Preferences, the A-Pro has been dumped as my surface, and I have to set it up again, save Preferences - and it'll stay there for awhile, then mysteriously just disappear again on another day.
 

 
You know what, Randy? That's what's been happening to me as well. I first thought it was because of a loose cable connection (sometimes it was, indeed) but now I'm not sure. Do you always power on A-Pro before starting Sonar and always shut down Sonar before powering off A-Pro? If you always do that (I do) and still see the issue, I think there's something wrong with Sonar's ability to keep communicating with A-Pro.
 
 

rbowser
But none of that happens for me. The ACT button has never turned on automatically, and there's no "Receiving" display on the LCD. But the keyboard's controls are engaged, with the faders hooked up and controlling the track faders in Sonar, for instance.

 
Are the A-Pro and PC connected via a USB cable? Do you also connect other devices via a MIDI cable? To identify the cause I'd first remove all other cables and then launch A-PRO Editor and try to have the editor receive one of control maps from the A-Pro hardware and then transmit the map back to the A-Pro hardware. If the LCD says "Receiving..." then your A-Pro has no problem receiving a control map from the PC, right? If it still doesn't work, I'd probably perform a factory reset, although it resets everything including the maps you edited.
 
Is your Preferences > MIDI > Control Surfaces page set up properly as shown in the document in Alex's post? 

thank you all for your suggestions or tips.
My keyboard works fine, but when I open a new project, I have to wait about 10 seconds for the project to be usable and that if I use the controller "A-PRO" it does not make it with "ACT Midi Controller" this is not serious but boring. I tried everything but nothing works.
FYI, I used input "APRO 2" and output "APRO" as recommended Cakewalk and Alex.