- Audio plugins in pro tools first with plogue bidule software#
- Audio plugins in pro tools first with plogue bidule Pc#
I am willing to put a lot of work into that, but I would rather abandon that, if it would mean struggling with the functionality forever. And just loading some Kontakt patches sometimes made Max crash.
Audio plugins in pro tools first with plogue bidule software#
Yet, I did this test with just a few software instruments something like two years ago. I have never done anything involving video as well as a lot of other aspects of Max.
I happily admit that I do not have a lot of experience in many aspects of max. I have been using it to successfully build a standalone app to process all incoming midi including Lemur and a complex template control, that updates the control surface dependent on what track is selected in Cubase. That would make some really unsolvable problems (due to limitations of both Cubase and VEpro) doable.
Audio plugins in pro tools first with plogue bidule Pc#
:-) The most prominent advantage of a DIY host would be that I could make the midi bidirectional, meaning, Midi (and OSC) could also be routed from the host to the main PC or Cubase. the thing is, I do want more than VEpro can offer me, but not at the price of being unstable or not running as efficiently. wouldn't updates of the VSTs force you to revisit the whole thing time and time again? Is that a waste of time to even expect a self-built system to work as well as a dedicated host? Even, if it was possible to get it to work as well. So, all of this has to be very stable and be as effective in voice streaming as VEpro. I need the ability to activate and deactivate Kontakt instances remotely (via Midi or OSC). I am referring to load a huge bunch of Kontakt instruments and those samples will easily use up 80% of 128gb of Ram on that PC. Is it worth trying this once more? I am not talking about merely loading some synths or samplers. Now, with the arrival of Max 8, I read there are a quite some enhancements regarding the efficiency of the code. It would, however, still offer a lot of advantages to be able to do this. That is whyI abandoned the idea of hosting the VSTs inside a self built host and kept using VEpro. Secondly, it was not as reliable and caused crashes from time to time. Firstly, playback stressed the computer resources way more than a dedicated VST-host, although I tried to play with the settings. It turned out, however, that the outcome cannot match something like Vienna Ensemble pro.
I have been trying to build a VST-host Standalone app with Max 7.
0 kommentar(er)
