Why are you opening it inside Forte?
DG
-
Doe it matter what order you load things in? What I'm thinking is that if you load VE first before your other VSTi does that work? VE uses memory outside of Forte, and with 2GB I would say that at least 6-700MB would be taken up with just the OS and your apps. I think that you would be better forgetting about VE, as there is no advantage with your set-up that I can think of.
In any case, try keeping Task Manager open whilst you load so that you can see what is going on.
DG
-
No, this happens when I load VE on its own in Forte.
@DG said:
I think that you would be better forgetting about VEIt's a bit early to be forgetting about it, I haven't used it yet! But my strong impression is that there is a distinct advantage to assembling VI's within VE rather than setting up lots of separate instances. (Much easier and quicker to switch between instruments, for a start.) Are there any Forte users out there who have come across this message?
-
Putting aside the issues of Forte, my PC's specs etc., can anyone tell me what this VE error message might indicate:
One or more active connections are present. Do you want to forcibly close these connections and shut down the server application? (This may cause application crash or freeze.)
What are the 'active connections'? MIDI inputs maybe?
-
I am not a Forte user and can't tell about the message, but: Does VE run as a standalone application on your system?
If "yes", you could address it via virtual MIDI device channels (e.g. Loopbe1, MIDIYoke etc.) and save settings in VE projects. You could still open other VSTi's in your host prog, while running VE totally independent.
The feature you'll be losing with this workaround is VE settings being saved and loaded togeher with your host arrangement, but on the other hand you can easily reuse your favourite orchestral setups for similar arrangements from saved VE project files..
If you get no reply of other Forte users it's worth considering to open a problem call both in Forte support and in VSL support. I had a VI issue with Samplitude, which took quite some time to solve, but in the end both supports investigated together and VSL support finally found a solution.
-
Thanks Carsten. Yes, VE works fine standalone and I appreciate your suggestion on how I could use it alongside other VSTi's - good thinking! However, I would prefer to run it inside Forte because it's so convenient to have everything in one place. I'll call support in a few days' time if no-one here has any suggestions about the error message - personally I suspect it's either a MIDI conflict with Forte or a latency conflict with my soundcard.
-
I'm in the same boat. I need to run GVI for the rest of my giga lib and I also need midi clock for use with NI and other synth VI. I've been using Forte on one of my 4 PC's. I haven't tried it with VE on that machine yet because, frankly, I have hard enough time getting Forte to behave as it is. Forte seems to have some issues with various VI. GVi will crash it if you try to load more than two instances with any large sample load. There is a GUI graphic issue with GVI. Also, it won't correctly pass along midi clock with some VI like NI massive. I use V-Stack with two others, which despite it's age and being discontinued, it's still the most stable of the bunch. It has no issues with VE or GVI, but it won't send any midi clock to any VI in my rigs, otherwise I would probably use it on all the machines. I also have Ableton on the third machine, (so I can send clock to NI stuff) which works with all of them and passes mid clock to all, but it's cumbersome for VI with more than one midi channel. You have to create tracks for each midi channel and re-route them to the channel with the GVI. The last one I have is Ploque, which I've had to give up on because of audio distortion on ASIO and latency issues with the other drivers. I reallly wish VE would let us use other VI. Life would be so much easier. I love VE. I think the layout is the best one out there. It's such a silly pain to have to use 3 different hosts just to be able to access all my stuff properly. I'll give VE in Forte a try later today when I get a break and see what happens.
-
Thanks for the info Tripit, I'm interested to hear how you get on with Forte + VE. I've had no insurmountable problems so far with Forte, though I haven't tried to use MIDI clock with it. The error message I get is generated by VE (not by Forte), so it would seem in this case VE is having a problem with Forte rather than the other way round.
-