http://deskew.com/component/content/article/19/76.html

But yes, I have some questions…
1) How about stability? so far I had no crashes, but i heard of possible crashed while using vst…
2) How can i load a Kontakt patch already done within a standalone?
3) is it possible to have more than 2 channels out? If my Kontakt patch has for instance 4 channels out is there a way I can have them separate in GenericVST output as well?

btw, so far this is how I used your amazing abstraction:
I have one [GenericVST] object with “Kontakt 4″ as an argument…
with [t l 3] I set, for instance, MIDI channel 3 on third inlet and send a list of notes in inlet two.
I do this for each of 10+ instruments of my Kontakt patch for every single note: just one abstraction. Do you think is fine?

Last thing…:
thanks a lot for sharing! ;-)

However, I have had problems with Max hanging when a VST is loaded under Max 6.0 but have not yet pinned it down. I have also not yet tried 6.0.2

2) No idea — my mechanism completely ignores the “patch” mechanism that VSTs support and simply saves/reloads the entire set of parameters.

3) I don’t see why not. I only cared about stereo so I only created two channels. However, I routinely use multi-timbral patches with Kontakt and I just include the desired MIDI channel along with the note info (or VSTParam) for this. All output still comes back through the single stereo pair.

I am however revamping some of my work based on more recent experience. In particular, I wanted to start routing my external synths through Max so that I could use the GenericVST stuff for effects processing. So I now have a notion of a [SoftSynth], an [Effect] and a [HardSynth] abstraction, and these all use send/receive to send audio to a virtual mixer. The first two actually have the [GenericVST] inside them but the wiring to audio doesn’t use actual “wires” anymore.

I’ll post this in the next week or two.

Glad you like what I’ve done to date.

The real issue that gets in the way right now is the difficulty of keeping both 5.x and 6.x on my machine at the same time. I ran into a problem where I couldn’t get my Mac to use 5.x by default once 6.x was installed and until I am certain that 6.x is as solid as 5.x, I’m not in a position to give up 5.x.

I ran into a problem last week where I couldn’t use arguments in an adc or a dac and thought it was a shows topper. Fortunately someone gave me a workable solution to get around the problem but I don’t know what else might be there to bite me. If I could keep both on the same machine so as to be easily able to test changes incrementally, I’d be more comfortable.

“2) No idea — my mechanism completely ignores the “patch” mechanism that VSTs support and simply saves/reloads the entire set of parameters”

is it possible to load from your abstraction *more than one* set of previously saved kontakt settings?
I wish to use 1 max standalone and several (like 30 or more) kontakt presets (not necessarily kontakt patch themselves, I’d be 100% happy about the possibility of saving and recalling sets of parameters)
so, this point me directly to this very question:

is
it
possible
?
:-)

many, many thanks.
and, i mean, several, more than one :-)

one thing… is it possible that using Kontakt as a VST inside Max becomes far, far more CPU hungry?
i think I’m having some issues on that front, and it’s a shame…
btw, using max 5.1.7 and kontakt 4.2.4.5316.
i’m thinking if upgrading both would fix this problem, any friendly suggestion very, very welcommed! ;-)

for now, again, thanks!

I can’t say anything about Max6 until I get a chance to try the new 6.0.2 version which someone else claimed fixes the VST crash problem that I was occasionally seeing.

As for the new updates, if you read my blog, then you know that my goal was to replace Apple MainStage, which was just too glitchy. The one feature that I did not implement (up until now) was the ability for “songs” to automatically remember any parameter changes. So with my new version, once a song has loaded, I can turn a dial or adjust a slider on a keyboard to change a parameter. When that same song is loaded in the future, those changes will have been remembered and get sent automatically after the patch is loaded.

This has required a certain amount of redesign which is now pretty much done and being tested as time permits.