Hi all.
First of all, hats off to Paul Steinbauer and co. - VE Pro works great here. Good job guys!
I see two issues here; the first a GUI thing - really nothing more than a slight annoyance, and seeing as tho there is a not-too-complicated workaround, it's nothing major. Second, is actually a functionality issue.
First - here is what I am running:
Master: Windows Vista Ultimate 64-bit, SP1, 6GB RAM, 3.0 GHZ core 2 duo, Cubase 4/5 64-bit, Kontakt 3.5 64-bit, M-Audio 24/96 Delta audio card, VE Pro client
Slave: Windows Vista Home 64-bit, SP1, 8GB RAM, 3.0 GHZ core 2 duo, Kontakt 3.5 64-bit, VE Pro server
Both are connected to a Lynksys router (ports 1 & 2, respectively); both can communicate and share files and folers with each other.
The GUI thing has really nothing to do with the setup; here it is:
Note that Kontakt's ch 16 is missing; this happens when you try and select a ch on an instrument that is near the bottom of the rack. Workaround: temporarily move the instrument higher in the rack.
The functionality thing is this:
When receivng commands from Cubase on the master, the Kontakt volume fader is slightly off when runnning inside VE Pro.
Sequencer (local) Kontakt: Instr options > controller > MIDI controller > 12 db: Cubase fader 80 = Kontakt fader 0.0
VE Pro Kontakt: Instr options > controller > MIDI controller > 12 db: Cubase fader 80 = Kontakt fader -0.3
Sequencer Kontakt: Instr options > controller > MIDI controller > 6 db: Cubase fader 80 = Kontakt fader -6.0
VE Pro Kontakt: Instr options > controller > MIDI controller > 6 db: Cubase fader 80 = Kontakt fader -6.4
Sequencer Kontakt: Instr options > controller > MIDI controller > 6 db: Cubase fader 64 = Kontakt fader -11.8
VE Pro Kontakt: Instr options > controller > MIDI controller > 6 db: Cubase fader 64 = Kontakt fader -12.2
So, there is something a bit strange going on here. Seeing as tho the 0.0, -6.0 and -11.8 levels are true not only of locally loaded Kontakt, but while wrapped in FX-Teleport as well, the odd man out here is VE Pro, and that's where the problem seems to be. Not sure if anyone else see this in another sequencer, but it is consistantly true in Cubase. A small anomoly, and certainly not a showstopper, but I was wondering if you VSL peeps could kindly look into this?
Thank you!