Stretchincanada
I don't know what happed on dec 3 I did the update and my controller went nuts. It has never had a issue like this ? has anyone else had this happen. I know webedge had it happen to. I need it sorted out asap as im going to spin a huge set next month for the hell of it in the desert!
Inviato Wed 07 Jan 15 @ 6:48 pm
PhantomDeejay
What controller(s) do you refer to ?
If you're talking about Akai APC 40, what's changed is that the device is now natively supported. Therefore any custom definition you may have been using for it won't work anymore.
You have two options:
1) Use the new built in support to rebuild your mapper to your needs
2) Use "force-" on your old definition file to force it over the native one.
If you're talking about Akai APC 40, what's changed is that the device is now natively supported. Therefore any custom definition you may have been using for it won't work anymore.
You have two options:
1) Use the new built in support to rebuild your mapper to your needs
2) Use "force-" on your old definition file to force it over the native one.
Inviato Thu 08 Jan 15 @ 6:18 am
Stretchincanada
what a mess...
Inviato Sat 10 Jan 15 @ 2:57 am
Stretchincanada
please explain a few things. 1. is this normal for it to no longer see my work. 2. why is it not showing and why wasn't this a choice instead of over riding my script? I would like a better description of how to get my original script to work . the thing is im using a apc 80 and the apc 20 works fine.
Inviato Sat 10 Jan 15 @ 2:59 am
groovindj
See this thread for details.
Inviato Sat 10 Jan 15 @ 7:08 am
Stretchincanada
got it fixed , was way easy, it was the first setting in the controller section!
Inviato Sun 11 Jan 15 @ 6:23 pm