Understanding VE Pro

[Jack Weaver]

Hi VSL,

I think it's about time that you give all of us a bit of understanding about the implementation of VE Pro. I understand that all details are not yet worked out but I'm sure that some general guides lines can be given by now.

For example:

Which 3rd party manufacturers' virtual instruments are likely to work?

What operating systems do you recommend?

What is the overall Graphic User Interace and how might a user typically employ it with a slave computer?

What is the general timeline for its release?

I don't really mean to try to pin you down on all details. However, there are a lot of us who have been expecting this by now and either have made other purchases or are putting off other purchases until we know exactly how to go with this. Knowing some of these basic facts will allow many of us to get ready more effectively for this breakthrough product.

Thanks,

Jack

[timkiel]

Jack

I can't answer for VSL team  but my understanding having seen an earlier build is this...

Which 3rd party manufacturers' virtual instruments are likely to work?

Pretty much any VST/AU - so you should even be able to host Kontakt 3 with 16 channels in one VE channel, although how this works in practice and what CPU overhead this places on things I have no idea.

What operating systems do you recommend?

I don't quite understand this but I would guess OSX, WinXP and Vista will all be supported - VSL probably won't recommend a single O/S.  Now whether or not they go down a Leopard/Snow Leopard only route or a Intel Mac only route I have no idea...seems unlikely as they already have VE working on both Intel and non-Intel macs though...

What is the overall Graphic User Interace and how might a user typically employ it with a slave computer?

Probably exactly the same as VE but with a Add AU or Add VST button as well as the Add Instrument button

What is the general timeline for its release?

Now if only I knew that one! [^o)]

Regards

Tim

[civilization 3]

VSL are moving away from PPC Macs. Already the convolution in Vienna Suite isn't supported and won't even install. Apple has already indicated that UB will be a matter of history.

I'm a big Kontakt 3 user. I'm awaiting VE Pro with bated breath, and have plans and RAM a'ready. Kontakt 3.5 is a 64-bit application. It utilizes multi core extremely well. The Memory Server handles RAM via the 16 cores of my machine to treat >4GBs of content as if it's 400MB, spreading out the load in virtual memory with all these cores, at over 9:1 in favor of virtual memory, absolutely even distribution. My problem right now is that Cubase isn't dealing with multiprocessors optimally. With nothing plugged into it, it doesn't have to. So, my thought is that using this big machine as a slave w. K3.5 in VE Pro, I can sequence from my MacBook Pro and get away with murder.

I'm not heavily invested in VSL simply due to the lack of being able to (micro) tune it. I love the matrix, and I'd like to get into the VST expression in Cubase 5. But for the money outlay, that's rather a deal breaker for extended libraries. I got into VSL by way of Vienna Suite, which is fantastic.

[Jack Weaver]

Thanks Tim & civilization3,

However there's no relacement for hearing the official VSL word on this as I think that many of us out here would like to know something beyond conjecture.

Best regards always,

Jack

[cm]

@Another User said:

What is the general timeline for its release?

probably a VE 3.1 version will arrive before VE PRO since we are waiting for a few components supporting 64bit (on OS X) - however no scheduled release date which could be announced, sorry. please subscribe to the newsletter ...

christian

[Jack Weaver]

Thanks CM,

Regarding the GUI (and this dovetails with my earlier question about which virtual instruments will be qualified by VSL at the outset of delivery of VE Pro) are multi instruments working with VE Pro? If so, how are they incorporated within the interface?

What new automation features are there in single instruments and with multi instruments? Are the multi instruments' split across different cores of a multicore computer?

I certainly do understand VSL wanting to wait for release of it until all is resolved with the new Mac OS and 64 bit. 

VE3 has changed so much for our workflow. We look forward to VE Pro whenever it is finally everything you guys want it to be.

[DG]

@cm said:

probably a VE 3.1 version will arrive before VE PRO since we are waiting for a few components supporting 64bit (on OS X) - 

christian

 

Please don't delay the Windows version because of the delay with OSX. After all many Mac users have PC slaves, so it would benefit users of both flavours.

DG 

[gerdkaeding]

My question is if PPC Processors are still supported by VE PRO on the Mac ?

Would be great if my current G5 could still be used as a slave with VE Pro.

Thanks in advance,

Gerd

[timkiel]

Gerd raises an interesting point here.  I've an Intel Mac so am probably safe but if VSL are waiting for the public release of Snow Leopard (as semi-alluded to earlier in this thread) then as we know this is Intel Mac only so does this mean no VE PRO for PPC users?

Tim

[cm]

IMO (as already posted several times) it doesn't make much sense to throw too much energy on every detail of further PPC development - this is a dying platform.

generally we can see a huge difference in performance between PPC and INTEL slave computers, so throwing additional load on such systems is maybe not the best of all ideas ... also we can't say how far those third party apps will support 64bit on the PPC platform.

PPC support for the host side will be provided (thinking on logic and PT users running specific configurations) but don't count on full PPC support on the slave computer side ... similar to Vienna Suite convolution reverb not everything might work on PPC.

christian