Hello all
Am in the process since Monday of installing the VI instruments 1~5,
with varying degrees of success. Heres a synopsis of whats happened me.
System:
Comp 1 runs Nuendo / 3.07 Ghz PC / 1G RAM / 9652 Hammrfall card
Comp 2 has Cubase SX/Giga 3 / 3 Ghz PC / 768M RAM / MOTU 2408mk3
Comp 3 for VI install / Athlon 64 3700 / 2G Ram / Fireface 800
Various Midi interfaces available
All run digitally into 2 Yamaha 02r desks.
Monday
The initial licence downloads, and library uploads to Comp 3 went well [had a couple of Aborts - changed to the other DVD drive/Ext HD drive and all ok]
I just ran VI in standalone initially through the fireface, to verify it was working - it was....on to
Tuesday
Tried FXTeleport to run Comp 3 VI slaved to Comp 1
Got FXTel to work, but at a very high latency [2408], with plenty of pops.
Could get quite a few instances of VI happening, but my CPU meter in Comp1 which would normally sit at 10~20% was up in flashing up to 100%...not good.
Another problem [solved for me by DG - thanks DG] was the VIs running out of Graphic resources - after 5~6 launches, the new VI reads "Not enough GDI resources...blah, blah, blah]
The solution to this is to switch of the graphic of the interface - a little edit button in each of the FXTeleport slots [or indeed Cubase/Nuendo VST instruments edit button in each inst slot]. Now I could load way more VIs.
Some work had to be done for the rest of Tuesday, so here we are at
Wednesday
Unhappy with the networking methods, I thought I would load Cubase onto Comp3 and access VIs through its VST instrument slots.
So I loaded up Cubase, went through a nightmare of losing/regaining licences because of the two dongles [Cuabse and VI] -
The respective licences were constantly on both dongles, but on loading VI as either a Standalone, or as a VST in Cubase, any combination of the 10 licences would be reported as missing, even though the LCC showed them as being present. Changed the USB slots until all appeared to work....Lunch!
Now what I'm happiest about this way is that the Cubase CPU meter is hitting 10% with five VIs running. [:D] [:D] [:D]
The next problem I've encountered concerns MIDI.
I'm running the VIs on comp3 via a midi interface from Nunedo comp 1.
Can I address a VI on seperate midi channels, or must I have 1 VI only per midi cable??
Sorry for such a long post, but I think we could help each other out with our installations in this way.
If anyone has any observations, please do reply
I'd like to finish this post by thanking Herb, Christian etc
and you the users for kaing this forum so valuable a source of information and help when [and it will!!!] all goes wrong
Best
Andy O'Callaghan
Sutton Sound Ltd.
Dublin 13
Am in the process since Monday of installing the VI instruments 1~5,
with varying degrees of success. Heres a synopsis of whats happened me.
System:
Comp 1 runs Nuendo / 3.07 Ghz PC / 1G RAM / 9652 Hammrfall card
Comp 2 has Cubase SX/Giga 3 / 3 Ghz PC / 768M RAM / MOTU 2408mk3
Comp 3 for VI install / Athlon 64 3700 / 2G Ram / Fireface 800
Various Midi interfaces available
All run digitally into 2 Yamaha 02r desks.
Monday
The initial licence downloads, and library uploads to Comp 3 went well [had a couple of Aborts - changed to the other DVD drive/Ext HD drive and all ok]
I just ran VI in standalone initially through the fireface, to verify it was working - it was....on to
Tuesday
Tried FXTeleport to run Comp 3 VI slaved to Comp 1
Got FXTel to work, but at a very high latency [2408], with plenty of pops.
Could get quite a few instances of VI happening, but my CPU meter in Comp1 which would normally sit at 10~20% was up in flashing up to 100%...not good.
Another problem [solved for me by DG - thanks DG] was the VIs running out of Graphic resources - after 5~6 launches, the new VI reads "Not enough GDI resources...blah, blah, blah]
The solution to this is to switch of the graphic of the interface - a little edit button in each of the FXTeleport slots [or indeed Cubase/Nuendo VST instruments edit button in each inst slot]. Now I could load way more VIs.
Some work had to be done for the rest of Tuesday, so here we are at
Wednesday
Unhappy with the networking methods, I thought I would load Cubase onto Comp3 and access VIs through its VST instrument slots.
So I loaded up Cubase, went through a nightmare of losing/regaining licences because of the two dongles [Cuabse and VI] -
The respective licences were constantly on both dongles, but on loading VI as either a Standalone, or as a VST in Cubase, any combination of the 10 licences would be reported as missing, even though the LCC showed them as being present. Changed the USB slots until all appeared to work....Lunch!
Now what I'm happiest about this way is that the Cubase CPU meter is hitting 10% with five VIs running. [:D] [:D] [:D]
The next problem I've encountered concerns MIDI.
I'm running the VIs on comp3 via a midi interface from Nunedo comp 1.
Can I address a VI on seperate midi channels, or must I have 1 VI only per midi cable??
Sorry for such a long post, but I think we could help each other out with our installations in this way.
If anyone has any observations, please do reply
I'd like to finish this post by thanking Herb, Christian etc
and you the users for kaing this forum so valuable a source of information and help when [and it will!!!] all goes wrong
Best
Andy O'Callaghan
Sutton Sound Ltd.
Dublin 13
