Device Details

Thank you! This works pretty well.
The VST inside the device does however not accept MIDI in messages.
Do you think, this would be possible?
I tried only with Cherry Audio Voltage Modular so far.

hey! great, and thanks for this. ive been searching for / hoping for something like this since i first got instacomposer

@aoxomoxoa23 That's a great idea, shouldn't be too hard to implement.

@soaria! I just tested with Reason Rack Plugin and it is the same.
IF you could implement it, that would make it the most handy tool for these application! ThX!

What I meant: yesterday when I tested .. :)
seems like you added changes already!

Thanks for the update! MIDI in now works with the VSTs I tested! Great!
Two minor things, I would welcome:
1. The VST does not keep its preset when re-opening a project. (not sure if Instacomposer does, but VM does not)
2. ability that the windows stays open even when clicking somewhere else in the Live window.

But these are really minor things. Happy that the MIDI in works now.!

Excellent absolutely excellent. This needs to rocket its way to the top 20 utilities for ableton. Should be included with live. No issues so far using cardinal. Before this cardinal was basically unusable midi wise in live. Thank you so much.

Once I load it my ableton crashes.... live 11.0.12

Hi there.
Thanks a lot for this device.
I just upgraded to InstaComposer2, because it can now sync with Live's start/stop state.
This is a massive feature for me, as I can have a drum track etc running in sync with InstaComposer2.
However, Live's transport start/stop state does not seem to be relayed through your wrapper to InstaComposer2.
Would this be possible to implement?
(I would gladly make a donation for this functionality.)

tried this with rapidcomposer v5 - seems to load in small window which cant be resized so cant see the whole GUI of rapidcomposer...

also tried with Vital - the winodw top part is clipped...

I love that this thing I made on a whim is helping many, and sad that it's got some issues for some. Live isn't my primary DAW these days though, I'm waiting for 12 beta or release to start working on these again, probably.

Also, stuff like the window clipping and resizing is probably a Live/Max thing I can't fix in the device. :| But who knows, maybe Max is hiding some kind of cached sizes or positions in its depths.

I didn't see the start/stop issue in IC2, myself, but that sounds like it might be fixable.

If anyone wants to fix any of the problems before I get to it again, I'm happy to take a look and update this device entry, though.

Hi soaria,

Your wrapper is really the missing piece for me to start enjoying working with IC2.

Thats why I am really sorry that the wrapper does not seem to relay when I press spacebar og click the transport start/stop buttons, which was the last piece of the puzzle.

Again, if its fixable, I would love to make a donation to your effort via Paypal or otherwise. Just let me know. I can also help beta test.

Hi again,

Just a clarification - I just re-tested it in the latest Live 11.

IC2 does not respond to spacebar presses (transport start/stop) when the IC2 VST window is open and in focus, and the track has your Wrapper on it.

It does respond to spacebar presses when focus is on the Live window, and the IC2 VST window is out of focus (minimized).

However, on a track without your Wrapper on it, just IC2, the IC2 VST responds to spacebar presses, even with the IC2 VST window open and in focus.

Hope that helps ;-)

@antifrost - ahhh okay, yeah, that makes sense. Probably something I can't fix unfortunately, as what's happening is that M4L itself is hosting the VST, and so it has its own keyboard handling, window handling, etc. I wonder if some tweaks could be made to work around it though, like listening to space bar and sending the transport commands.

I do appreciate the offer :) but I'm less money constrained than time constrained these days. I'll definitely get back to it sooner or later, since I'm planning to do more Live in the near future, and this lack of channel support is still a ridiculous thing in the DAW. I don't get it... *shrug* I'd pay Ableton to add some MIDI channel support :P

@Soaria,

I had hoped that Live 12 would have this MIDI multi channel routing capabilities, but that does not seem to be the case, so I might be skipping that release.

Which means that your 2 M4L devices are really useful and ingenious pieces of code. Big thumbs up!

Well, heres hoping that you find a way to pass through spacebar, but in the meantime - thanks a million.

I spent a bunch of time looking at the various issues today, and first of all, Max makes me just want to scream and tear my hair out. 😹 It has this really bad habit of having tons and tons of documentation, but the thing I actually need is either buried in some Reddit post or is impossible to search for because of too-basic terms like "Max". (Did you know 3DSMax has scripting? I do now...)

Also it kinda wants to be a programming environment but is really awful at it?

Okay, that complaining aside, it appears that whether a VST's internal state will be saved is a question of author. I tested a bunch, and here is what I found:

- Does work: IC, IC2, Kontakt 7, Pigments
- Doesn't work: VM, Captain Epic plugins

Those last two are truly regrettable, because you do a lot of creative work inside the VST itself. :( Pigments had the full preset I'd loaded still, and Kontakt went as far as having the sample libraries still loaded.

I tried saving the parameters instead of snapshots of the internals, but a lot of plugins simply don't expose parameters, or very few. ICx for example, exposes one parameter called ParamChange. :eyeroll:

So, as much as I'd love to fix that stuff up... I don't see a good way. Put together with the keyboard stealing, window size issues, etc, it seems Max really doesn't have very good VST hosting support, either. I really wish I could just talk to the VST hosted inside Live itself, but the Live API doesn't seem to handle stuff like MIDI data. If anyone has ideas, feel free to comment!

That "?" near the beginning was suppose to be a cat cry-laugh emoji. Oh well. Laugh and cry, that's a good way to represent it. :D

@Soaria

"I spent a bunch of time looking at the various issues today, and fi..."

Well, Soaria - thanks for trying and thanks for a great device ;-)

I'm definitely missing something here. I can get the midi to multiple instruments using the wrapper but I'm not able to record the midi to any of their respective tracks. So great to have a way to route multiple midi tracks from Instant Composer2 and RapidComposer, can someone point my thick head in the right direction?

This is perfect for Harmony Bloom where you can have different channels for the Trigger Bars but I was having the problem where you can't record the MIDI coming from the M4L Device. A workaround I found was having another Midi track recording from one of the tracks with the receiver devices. It may take up more space but you can at least still recording the midi and to save space keep your midi recorded tracks in a collapsed Group channel.

Thanks!

hello guys I want use maschine 2 with this sofware. I love your idea but I think that wrapper not work with the vst 3 pluggin

how fixe this problem

thx for you work!!!

sorry vst3 work with kontakt 7

consol say
dict: doesn't understand "int"
Maschine 2.vstinfo: no format VST exists
dict: doesn't understand "int"

I don't know how fix the problem

but it would be a revolution for the user maschine 2