194,453 users have contributed to 42,922 threads and 257,971 posts.
In the past 24 hours, we have 5 new thread(s), 14 new post(s) and 73 new user(s).
Can someone from VSL clarify this. I understand the VST3 spec, but for MAC Logic users that does not help.
If indeed there is an 8 instance limit per server this is quite a problem as there would be no way to access the amount of Kontakt's I need on farm machines. Can someone clarify? I hope this is just a bug.
Thanks
I too cannot connect to more than 8 instances. This is kind of a downer as I had hoped to replace Plogue running 16 instances of Kontakt on my slave Mac Pro 2.8gHz slave machine.
Any word from the VSL team on this?
Exactly.... I need to replace many many Kontakt instances, way more than 8. Until there is a way to go more than 8 instances this will not help enough to revamp my template. Hopefully this is something they can change easily. Can anyone from Vienna please comment on this issue if it is possible?
Thanks
@dlpmusic said:
Exactly.... I need to replace many many Kontakt instances, way more than 8. Until there is a way to go more than 8 instances this will not help enough to revamp my template. Hopefully this is something they can change easily. Can anyone from Vienna please comment on this issue if it is possible?
Thanks
the current limit is 8.
However, there are ways around some of the problems with using multiple Kontakts, for example.
If you load the VST3 version of VE Pro, you can get up to 32 MIDI ports. Therefore each instance of Kontakt that you load, can itself address 16 MIDI channels, giving you 512 MIDI channels per instance of VE Pro. The snag is that each of these Kontakt instances can only use one audio output. However, if you were going to bus some of the Instruments anyway, then put them in the same instance. this should help temporarily whilst Martin looks at the possibility of an increase in the number of VE Pro instances allowed to connect to the server.
DG
Yeah but one has to buy Cubase right? The problem remains for the logic users. =( I wouldn't like to wait 2 more years until Logic brings out a new AU format with vst3 capabilities. Therefore for us logic users dreaming of using Kontakt since a long time it would be an extremly good news to hear from the vsl team a statement that a solution is on it's way.@DG said:
If you load the VST3 version of VE Pro, you can get up to 32 MIDI ports.
@DG said:
I'm using Nuendo 4.3, but I don't get a crash with 128 audio Outputs.
Thanks DG, that's very interesting.
May I ask you if you have the problem that saving a song project is very slow if you are connected to VE Pro? I have a VE Pro instance with 20 Kontakt instances (~ 10 GB). If this instance is connected to Cubase saving of the song project takes about 45 second. If it is not connected saving only takes 1 second.
@MS said:
Try instantiating 20 Kontakts in your sequencer, and see if you get the same saving speed.
Thanks, Martin. I'm so stupid that I have not tested this simple case. I will try this this evening when I'm back at home.
Anyway, do you think it would be an idea to implement a button "Disconnect/Reconnect all instances" in the server instances window (see below). Of course this button should remember which instances (of VE Pro Server) belongs to which VST instances (in the sequencer). But then you could easily disconnect (for very quick saving and loading) and reconnect.
I was more thinking about an option which decouples saving/loading. This way, a save could be pretty much instant - all that would be saved in the project would be the preserved session name and the IP address of the server, instead of all data belonging to the VE Pro instance (which in the case of 20 Kontakt instances, can be ALOT of data). I'll see if I can add that for an update.
@MS said:
I was more thinking about an option which decouples saving/loading. This way, a save could be pretty much instant - all that would be saved in the project would be the preserved session name and the IP address of the server, instead of all data belonging to the VE Pro instance (which in the case of 20 Kontakt instances, can be ALOT of data). I'll see if I can add that for an update.
Thanks, Martin. That's a brilliant idea. I can hardly wait to... [:D]
I'm puzzled whether this is a real problem or not.
Isn't it true that you can, even without VST3, run 16 instances of Kontakt (one for each MIDI channel) inside each instance of VEPro, and then run 8 instances of VEPro?
Therefore even with this 8-sever limitation you can run 16x8 = 128 instances of Kontakt on each PC or MAC.
And then, given that you could run the 64bit server alongside the 32bit server, you could put 64bit Kontakts in the former and 32bit Kontakts in the latter.
And therefore you can actually run 128 x 2 = 256 instances of Kontakt on a single machine, even without VST3.
Isn't that so? Isn't that enough?
The problem with your math dag, is that if you run 16 instances of Kontakt in 1 instance of VEpro, you still only have access to 16 different patches because you still only have 16 midi channels to use per VEPro instance. This is the same as if you only had 1 instance of Kontakt loaded with 16 patches. Either way, you only get 16 patches per VEpro instance.
Then, if you are using a mac, Kontakt does not register as a 64bit plugin, so you are unable to use the 64bit server as well.
In my case, I was running plogue with 16 instances of Kontakt each with 16 patches loaded on a MacPro.
VEPro now limits me to having 8 instances of Kontakt each with 16 patches.
DP and Logic users unfortunately do not have access to VST3.
However, the forums are all a buzz with what doesn't work, and I have to say that this is an absolutely AMAZING piece of software that will single-handedly revolutionize the way large-project-workflow happens. I just can't (as I had dreamed about :) replace my current setup quite yet, but am looking forward to further refinements in VEPro.