Great suggestion but I get the same problem as when I use the Cakewalk Generic Surfaces Plug-in.

Don't use that either (Generic Surfaces Plug-in). Sorry if I wasn't clear about that.

Options->Controllers/Surfaces - Highlight everything and delete them ( or hit the red X ).

The midi-learn function is a part of Sonar itself. It may even conflict with ACT or Control surfaces so it best to remove those two first. Then do the learns...

Put mouse cursor on Sonar fader, right click and select "remote control", click "learn" and move Yamaha fader. Click ok. Repeat for as many faders as you want.

If your 16 Yamaha faders all transmit midi, this should work.

Then save that file as an empty song. You'll open that as your starter/template.

ORIGINAL: DayDrumFour

Great suggestion but I get the same problem as when I use the Cakewalk Generic Surfaces Plug-in.

Don't use that either (Generic Surfaces Plug-in). Sorry if I wasn't clear about that.

Options->Controllers/Surfaces - Highlight everything and delete them ( or hit the red X ).

The midi-learn function is a part of Sonar itself. It may even conflict with ACT or Control surfaces so it best to remove those two first. Then do the learns...

Put mouse cursor on Sonar fader, right click and select "remote control", click "learn" and move Yamaha fader. Click ok. Repeat for as many faders as you want.

If your 16 Yamaha faders all transmit midi, this should work.

Then save that file as an empty song. You'll open that as your starter/template.

Thank you DayDrumFour for your input as it is most appreciated.

Here is the behavior of Cakewalk Sonar and the Yamaha 01V96 in regards to Remote automation which you suggested.

1. I open Sonar without any MIDI Plug-in controller surface.
2. I see my Midi input/output/Activity light pulsing steadily on the left and I have no Midi controllers on except the 01V96 and I haven't touched it.
3. I set up a file template with audio.
4. Midi input/output/Activity light is off now.
5. Remote does not work at all.
6. I click on Options-Midi devices and I see my Yamaha USB port is selected already so I click okay. Now the Midi input/output/Activity light is pulsing again steadily on the left. Huh!
7. I right click on the fader(s), select Remote, click learn, move my fader(s) and I get random sporadic movement in Sonar's console view like sometimes the fader will do nothing, other times it will move an eighth of the way, and sometimes it will move up and down four, six or 8 times, and many times the wrong faders will move etc. etc.

Again, I have tried the ACT Midi Controller Plug-in and it works perfectly but only on 8 channels.

I have tried Cakewalk’s Generic (Geriatric) Plug-in and all 16 faders work but Sonar’s faders go spastic and convulse up and down hundreds of times as I raise the fader over the course and duration of a one 100-mm fader rise.

I have tried the Remote function (see above).

I have tried setting up the 01V96 to transmit in a myriad of ways using the Pro Tools protocol, along with Nuendo, Cubase and the General Daw and User Defined settings.

Thanks, Joy

I have tried the ACT Midi Controller Plug-in and it works perfectly but only on 8 channels.

You can use a 2nd ACT MIDI controller (up to 16 are possible IIRC). MIDI-Learn it to your channel controls 9-16 and save as a new preset. Go about this VERY systematically, so you don't assign the same control to different cells by accident. These things are hard to trouble-shoot and it's often best to start over again if it happens.

When setting up the individual ACT controllers, open them one at a time. There seems to be a bug where changing presets on one controller will affect another open one. Even then the displayed preset name might be wrong, but the settings are correct. (that's with Sonar 6 though, maybe it has been fixed in the meantime)

There's one little downside though: The position/assignment of the controller pug-ins wrt to the track list doesn't seem to stick. After re-opening a project, all configured ACT controllers will be assigned to the first 8 tracks - one "on top" of the other. So you'd have to drag the coloured WAI indicator(s) to the correct set of tracks each time you open the project.

You can find more details about multiple ACT controllers here. HTH

werner

ORIGINAL: dreamkeeper

I have tried the ACT Midi Controller Plug-in and it works perfectly but only on 8 channels.

You can use a 2nd ACT MIDI controller (up to 16 are possible IIRC). MIDI-Learn it to your channel controls 9-16 and save as a new preset. Go about this VERY systematically, so you don't assign the same control to different cells by accident. These things are hard to trouble-shoot and it's often best to start over again if it happens.

When setting up the individual ACT controllers, open them one at a time. There seems to be a bug where changing presets on one controller will affect another open one. Even then the displayed preset name might be wrong, but the settings are correct. (that's with Sonar 6 though, maybe it has been fixed in the meantime)

There's one little downside though: The position/assignment of the controller pug-ins wrt to the track list doesn't seem to stick. After re-opening a project, all configured ACT controllers will be assigned to the first 8 tracks - one "on top" of the other. So you'd have to drag the coloured WAI indicator(s) to the correct set of tracks each time you open the project.

You can find more details about multiple ACT controllers here. HTH

werner

I have never been able to use my 01Vs to control Sonar and that is about all I want to do with them now since I use Apogee convertors, outboard preamps, FX plugs, etc.

I searched posts over at the 01V96 forum yesterday and posted. Replies came back that Sonar and this board have never gotten along. I understand this dearly. The 01V96 uses the Pro Tools protocol and is set up to work with Pro Tools, Nuendo, and Cubase right out of the box. It's a Cakewalk/Roland vs. Steinberg/Yamaha thingy ;-)

Can't we all just get along! VSTi vs. DXi, MAS, AU, RTAS ASIO vs. WDM, Mac vs. Windows, AMD vs. Intel, on and on and... etc.

Anyway a post came in from TB who had just found a link to a guy who might have programmed Sonar and Yamaha to talk to each other. You have to set up a dll file and do some tweaks to both parties, but the 01V96 will show up in the control surfaces drop down list. I can now use the 01V96 to control Sonar like never before. Hoohaaa!!!!! in my best Al Pacino voice.

Here is the link: http://www.theexis.com/utilities/01v96/

The work done by this author will help Sonar sell a lot more software and Yamaha a lot more boards in the future. Daw controllers are selling like hotcakes now and it's about time these two learned to talk.

I am personally going to thank the author right now.

Good luck, HIO out

ORIGINAL: Here In Oregon

ORIGINAL: dreamkeeper

I have tried the ACT Midi Controller Plug-in and it works perfectly but only on 8 channels.

You can use a 2nd ACT MIDI controller (up to 16 are possible IIRC). MIDI-Learn it to your channel controls 9-16 and save as a new preset. Go about this VERY systematically, so you don't assign the same control to different cells by accident. These things are hard to trouble-shoot and it's often best to start over again if it happens.

When setting up the individual ACT controllers, open them one at a time. There seems to be a bug where changing presets on one controller will affect another open one. Even then the displayed preset name might be wrong, but the settings are correct. (that's with Sonar 6 though, maybe it has been fixed in the meantime)

There's one little downside though: The position/assignment of the controller pug-ins wrt to the track list doesn't seem to stick. After re-opening a project, all configured ACT controllers will be assigned to the first 8 tracks - one "on top" of the other. So you'd have to drag the coloured WAI indicator(s) to the correct set of tracks each time you open the project.

You can find more details about multiple ACT controllers here. HTH

werner

I have never been able to use my 01Vs to control Sonar and that is about all I want to do with them now since I use Apogee convertors, outboard preamps, FX plugs, etc.

I searched posts over at the 01V96 forum yesterday and posted. Replies came back that Sonar and this board have never gotten along. I understand this dearly. The 01V96 uses the Pro Tools protocol and is set up to work with Pro Tools, Nuendo, and Cubase right out of the box. It's a Cakewalk/Roland vs. Steinberg/Yamaha thingy ;-)

Can't we all just get along! VSTi vs. DXi, MAS, AU, RTAS ASIO vs. WDM, Mac vs. Windows, AMD vs. Intel, on and on and... etc.

Anyway a post came in from TB who had just found a link to a guy who might have programmed Sonar and Yamaha to talk to each other. You have to set up a dll file and do some tweaks to both parties, but the 01V96 will show up in the control surfaces drop down list. I can now use the 01V96 to control Sonar like never before. Hoohaaa!!!!! in my best Al Pacino voice.

Here is the link: http://www.theexis.com/utilities/01v96/

The work done by this author will help Sonar sell a lot more software and Yamaha a lot more boards in the future. Daw controllers are selling like hotcakes now and it's about time these two learned to talk.

I am personally going to thank the author right now.

Good luck, HIO out

Hallelujah....Mission Accomplished!

- Registry dll update...Check
- Modifications to the O1V96...Check
- Modifications to Sonar (I used the "O1v96 v2 Studio Manager" instead of the "O1v96 v2 Remote Layer" from the drop down list to make it work)...Check

Thanks HIO, TB, Roger (the author) and everyone for all the input and the solution!

Joy

Thanks for the info. Where is the O1v96 forum.

thanks
Andy T.

Hey Joy, good to see you found a way to make it happen.

ORIGINAL: pooldude

Thanks for the info. Where is the O1v96 forum.

thanks
Andy T.

http://tech.groups.yahoo.com/group/01v96/

Thanks
Andy T.

I have never been able to use my 01Vs to control Sonar and that is about all I want to do with them now since I use Apogee convertors, outboard preamps, FX plugs, etc.

I searched posts over at the 01V96 forum yesterday and posted. Replies came back that Sonar and this board have never gotten along. I understand this dearly. The 01V96 uses the Pro Tools protocol and is set up to work with Pro Tools, Nuendo, and Cubase right out of the box. It's a Cakewalk/Roland vs. Steinberg/Yamaha thingy ;-)

Can't we all just get along! VSTi vs. DXi, MAS, AU, RTAS ASIO vs. WDM, Mac vs. Windows, AMD vs. Intel, on and on and... etc.

Anyway a post came in from TB who had just found a link to a guy who might have programmed Sonar and Yamaha to talk to each other. You have to set up a dll file and do some tweaks to both parties, but the 01V96 will show up in the control surfaces drop down list. I can now use the 01V96 to control Sonar like never before. Hoohaaa!!!!! in my best Al Pacino voice.

Here is the link: http://www.theexis.com/utilities/01v96/

The work done by this author will help Sonar sell a lot more software and Yamaha a lot more boards in the future. Daw controllers are selling like hotcakes now and it's about time these two learned to talk.

I am personally going to thank the author right now.

Good luck, HIO out

Oh,... and I almost forgot to say that I am getting bi-directionality and I am not following the author's instructions verbatim.