Mackie C4
Mackie C4
Now that the Mackie Control Universal is supported, it only makes sense (a LOT of useful sense) to support the Mackie C4 as well. I hope this is currently in development. Thanks.
-
danlandrum
- Posts: 1
- Joined: Thu Apr 07, 2005 7:27 pm
- Location: Tennessee
- Contact:
Mackie C4
Just got a C4 and it absolutely does not work with Live. Bummer. I made the purchase after seeing a Mackie ad in the Sweetwater catalogue that said the C4 works with Live. It even has a Live logo in the ad. The ad is opposite page 40 in their latest ProGear sale mag if you want to check it out.
It does not work and is going back to Sweetwater Monday. I just wanted to send everyone a heads up so someone else doesn't make the same mistake.
Dan
It does not work and is going back to Sweetwater Monday. I just wanted to send everyone a heads up so someone else doesn't make the same mistake.
Dan
Ableton:
I'm a python programmer. One of my current open source gigs is embedding python into a groupware system (citadel). Some time back, I bumped into one of your guys probing out the python guys on embedding python into ableton for some sort of scripting.
On investigation I notice a whole bunch of PYC (compiled python) files in the Mackie directories. Inference? Your using python to script up midi interaction with the Mackie desks.
Why don't you just include the .py file, and a bit of a quick API rundown, and let it up to the open source community to generate scripts for every damn midi dingle under the sun. You still protect the secret sauce warp engine , but you let us coders play with the midi stuff.
I can guarantee it. Let open source coders go loose on something like the python scripts, and they'll produce scripts for all manner of shenanigans. I promise!
(Hidden agenda. I'd like to make a script to generate stochastic/serialist madness off my BCR2000 for experimental music).
Fuck guys, include the full python stack and let people SCRIPT THE LIVING SHIT out of ableton. Someone wants a protools export? Sure. some nerd'll script it. Someone wants a method for flibbering out a filter using an RS232 interfaced jaffle maker? Sure , some nerd'll script it.
You get the point?
Pleeeasssseeeeee!
I'm a python programmer. One of my current open source gigs is embedding python into a groupware system (citadel). Some time back, I bumped into one of your guys probing out the python guys on embedding python into ableton for some sort of scripting.
On investigation I notice a whole bunch of PYC (compiled python) files in the Mackie directories. Inference? Your using python to script up midi interaction with the Mackie desks.
Why don't you just include the .py file, and a bit of a quick API rundown, and let it up to the open source community to generate scripts for every damn midi dingle under the sun. You still protect the secret sauce warp engine , but you let us coders play with the midi stuff.
I can guarantee it. Let open source coders go loose on something like the python scripts, and they'll produce scripts for all manner of shenanigans. I promise!
(Hidden agenda. I'd like to make a script to generate stochastic/serialist madness off my BCR2000 for experimental music).
Fuck guys, include the full python stack and let people SCRIPT THE LIVING SHIT out of ableton. Someone wants a protools export? Sure. some nerd'll script it. Someone wants a method for flibbering out a filter using an RS232 interfaced jaffle maker? Sure , some nerd'll script it.
You get the point?
Pleeeasssseeeeee!