I have decades of experience with programming - but none in Max for Live yet. I've been doing tons of research though and I'm an expert JS programmer, so I'm sure I can be useful. I'd be glad to help with either of these pet projects of mine:
meta-mapping (style-sheets for music)
The idea is to be able to separate the composition from the sounds, effects, etc that a required to make the song sound right. Then be able to use "style-sheets", to basically mix and match. In web dev, CSS is used to define how a page looks, and the HTML page defines the content. So the idea in Ableton would be, the notes and tracks define the content, and the new, missing layer, defines how the content SOUNDS! Another way to look at it would be an attempt to apply the MVC model to Ableton.
- snapshot of entire song as midi data, including settings of instruments in a user editable file
- apply snapshots to a new song, overriding only settings I want - EG, just the instrument settings W/O the midi notes
- ability to edit snapshot's meta-data (JSON)
- meta data should be similar to CSS
- cascading datasets - override attributes, else inherit from parent
- sounds should be broken into distinct building blocks so the LFOs, filters, etc could be applied to any instrument
- ability to save chunks of meta-data so they can be dropped on top of other tracks
Instrument/Effect Plug-in reference
I download all sorts of cool plug-ins, but I forget what they do when the time comes. I want to automate a look-up reference for the plug-ins I have installed.
Essentially, it needs to do this:
- get a list of all available plug ins, preferably in searchable list
- clicking an item in the list launches a google search for the instrument - uses "I feel lucky" functionality to present the best search result for a plug in!
- not all searches work "off-the-shelf", so the ability to customize search criteria or a specific page for each plug in.
Thanks for your help/thoughts/direction!