So, one of the things I like to use MGP for is switching between instrument articulations and controlling parameters (CC control). If you’re familiar with VST orchestral instruments you’ll be familiar with all this.
I’m in the process of having Claude Cowork build me grids for all the instruments in my template. It (if it works) will read the manual for keyswitch and CC controller info, also read the Babylonwaves articulation info and create grids accordingly.
By connecting Claude to Obsidian, I’ve also created a ‘vault’ for Claude to store it’s ‘memory’. Those familiar with AI tools know they have no memory as such. The data vault retains information on how to build grids, what formatting to use etc etc.
I’m running into some problems, and wondered if anyone is also doing this/has done this successfully. If it works, it will be amazing. Normally, when adding a new VST library to my template, I need to budget a half/full day just to get the MGP pro grid set up. I’m not particularly interested in the built in AI feature in MGP, from what I can tell, it has amnesia, just the same as all the rest of the AI tools, I want to have my grids in a certain way, and for that information to be retained.
If anyone is also in the process of using Claude for anything like this, let me know? I’m after best practices/ideas/ways to make the process less painful etc etc.
I’m in the pre-process…I tried successfully getting Cowork to write me an articulation map for DP for a very simple case. Haven’t had time to take it further but hoping to find time next week.
The best way to do this would be to have a feature in MGP that allows users to store templates of grids and other elements in a way that could be imported back into Claude for reference when building something new. It solves the amnesia problem, the code shell stays proprietary, and Claude has something to work from. If you were able to do that, you could build new grids for VIs in a snap if you have a set framework.
Claude has built grids for me based on existing ones. It knows what I want when it comes to button size, which CC controls I want and where they’re mapped.
all this data is held in Obsidian and I’ve created a ‘skill’ in Claude that will build a new grid for me. I supply Claude the VST manual and it does the rest. Not without its issues but it’s now working pretty well.
I was thinking about this just the other day, but my knowledge of AI is very minimal at this moment. I work in IT, but primarily in Infrastructure Management. Any lessons learned or tips on this would be great. I started building a ‘like-for-like’ ‘Art Conductor for Cubase’ of sorts, some months back, but got stuck once I tried to work out how I would change through the different libraries and pages of articulation maps.
The credit goes to someone here for inspiration of the second concept design, who has something looking very similar in colour schemes and depth of shadows. Cannot remember his tag right now, but I will be sure to put it here once I find out.
Happy to share any templates or files to understand this more and give Claude some scope to build from it
