@Chuck Green said:

One note, in the documentation it states that what opening old project, one will be asked if they wish to use VI-PRO?  In Pro Tools that isn't the case.  One has to reload in the instrument and it's matrix.  Not sure if the docs only mean while using VE-PRO and VI-PRO.  Please clarify....

Not the case in Cubase either. But I would assume it only works when using VE-Pro, as I don't see how it could be pulled of in a host not created by VSL. Perhaps if they made the VI-instrument scan for the existence of VI-Pro, but I imagine it would still be problematic to convience the host to exchange the reqested VSTi for another one.

Not in case of Logic, i've opened an "old" project and no "ask" for VIPRO or "Classic".... maybe miss something ?

-A

Hi,

thanks for the input, I have anticipated this feature, which didn´t make it to this first release version.

The manual will be updated soon, happy to hear your ideas!

Enjoy VI PRO!

Best,

Paul

Hey there Paul,

I'm one of those Logic users that's still using the 32-bit version because Altiverb isn't 64-bit yet. Any chance we'll get a feature from Vienna that's similar to Kontakt's Memory Server, where samples get loaded outside of Logic's RAM, so you can avoid hitting Logic's RAM ceiling?

Kerry

@KMuzzey said:

Hey there Paul,

I'm one of those Logic users that's still using the 32-bit version because Altiverb isn't 64-bit yet. Any chance we'll get a feature from Vienna that's similar to Kontakt's Memory Server, where samples get loaded outside of Logic's RAM, so you can avoid hitting Logic's RAM ceiling?

Kerry

This is what the legacy VI has been doing for years and Logic users have been complaining about for years. [;)]

I would suggest using VE Pro and then you can use all the memory (and cores) that Logic doesn't.

DG

Wait... so every time I open a classic instance of VI in Logic, it's loading samples into system RAM and not Logic's RAM?  No way!!  I love that!

And I do have VE Pro but no longer use it networked to my other Mac, so it's sitting here, dormant.  If I use VE Pro as a plugin in Logic, on just one Mac, it loads everything into system RAM instead of Logic's RAM?

Please say "yes" to both and you will make me one very happy composer.  :)

Kerry

@KMuzzey said:

Wait... so every time I open a classic instance of VI in Logic, it's loading samples into system RAM and not Logic's RAM?  No way!!  I love that!

And I do have VE Pro but no longer use it networked to my other Mac, so it's sitting here, dormant.  If I use VE Pro as a plugin in Logic, on just one Mac, it loads everything into system RAM instead of Logic's RAM?

Please say "yes" to both and you will make me one very happy composer.  😊

Kerry

1) Yes, as long as you're not using the 64bit version, I think. You can easily check yourself.

2) Yes.

DG

Wow!  This is by far the the greatest innovation in the virtual instrument world ever!!! It is as if Heaven has desended to earth in the form of a virtual instrument!  I'm sitting here playing this with tears rolling down my face....Everything I had ever hoped it would be, it is now...Truly unbelievable...Thank you VSL Team!!!

+1    Thanks DG  :)

I have your same setup, but I use Logic 9.1.1 in 64 bit (OSX 10.6.4)  and 2 instances of VE Pro (with 16 VI instances each) on the same computer, and a couple instances of Altiverb, that Logic accesses by a 32 bit bridge.

Back to first observations if I may...

I really like:

- The fast loading time of the plugin

- The fact that there is no "intermediate" window - at last!! Yippee - thanks!!

- The keyswitch visibilty and info is excellent

- The little yellow tool tips are most helpful

- Humanize promises to be useful

- The mixer with power pan is a great bonus

- Of course all the other new features are incredible - too many to mention

Some small issues:

- Some info in the File Browser gets cut off because the space is too small

- Similarly, long names in the Matrix list are cut off

Both of these could be fixed by making the plugin GUI a little wider or larger in general

- The GUI is a little too bright for my personal taste. I feel some areas could also have a higher contrast for better legibility

All in all.....

A ***HUGE*** round of applause to the VSL team for an exceptional new interface for an already exceptional product.

Well done.

Regards - Colin

@musos said:

All in all.....

A ***HUGE*** round of applause to the VSL team for an exceptional new interface for an already exceptional product.

Well done.

Agreed! Love the easy volume mapping and key range controls.

But why can't we have a usable ADSR envelope? Am I the only one who whishes there was one?

I think it's great too. A question though. When I load something like Violin solo Perf-Legato Speed+porta, the interval mode is by default set to poly. Is this correct? In the regular VI it 's default was always mono so that you could play mono legato lines straight away. 

@smallfry said:

I think it's great too. A question though. When I load something like Violin solo Perf-Legato Speed+porta, the interval mode is by default set to poly. Is this correct? In the regular VI it 's default was always mono so that you could play mono legato lines straight away. 

If you go to the advanced view you can set it globally to be Mono. then you can decide on a patch be patch basis whether or not to change this.

DG

How does Vienna Instruments Pro work with Ensemble Pro? I use Vienna Ensemble Pro on 2 external computers feeding into Logic 9.1

Running into an issue here.  After playing around with the new interface, I decided to make a template in Logic 9.  I have 34 tracks with 34 instances of VI-PRO.  Currently only the first two are loaded with a single patch.  I have the reverb shut down on all instances.  Currently - no reverb at all.

The first track, Piccolo plays fine until I exit Logic and then reload.  When I reload, there appears to be an overload on my Apogee ensemble sound interface.  The only way I found to get out of trouble is to dump the first instance and reload.  Then everything is ok until I exit and restart Logic.  

It doesn't have to be the first track.  The second track is loaded with 3 Flute Sustain only.  If I play that track first after a restart, the same thing happens.  Again, dumping VI and reloading it solves the issue until the next exit and restart.

Any ideas what might be happening here?  I've tried buffers 512 and 1024 with no difference.  Project currently set at 44.100 kHz and I've also tried 48.000 kHz.  No change....

MacPro 16GB, 3.0 Ghz.... 

Hi Paul, Vi pro seems really great. I had some time to play with it for a couple of hours today. Still wondering why Vi pro is not supported in MIR yet? this seems super strange for me. Am I missing something in the installation?? thanks

@hose said:

Hi Paul, Vi pro seems really great. I had some time to play with it for a couple of hours today. Still wondering why Vi pro is not supported in MIR yet? this seems super strange for me. Am I missing something in the installation?? thanks

 I think that you're missing the fact that there are a limited number of hours in every day. Even software developers have to sleep. [;)]

You can current;y load it as a VSTi, in the same way as you would load Kontakt or any other VSTi

DG

Hi any comments from VSL concerning CPU usage for the new VI Pro? With all the new features, I'm sure that it can get pretty hungry!

Also any comments about multi-core support? Is that dependent on the plug (VI Pro), the program (Logic, for example), the system (OSX 10.6.4), or other? [D]

Hi,

I´d say, simply give it a try with the free demo license.You will be surprised.

Best,

Paul