Hey guys - I can see that VE Pro is only recognizing my AU's, and DG, of course I trust your answer since you know the software intimately. However, I'm confused why I see this in the specifications for the software:

"Plug-in formats RTAS (Mac PPC & Intel), AU (Mac PPC & Intel) and VST (PC and Mac PPC & Intel) for use with a host sequencer: 16 MIDI channels per instance."

(saw this information HERE)

Any thoughts as to why VSL claims to support VST plugins? It would be really nice to be able to use my VSTs, of course.

Thanks!

-Alex

I'm wondering the same thing here. Hoping for an answer! If there is a way of integrating VI Pro into old projects, so that I don't have to painstakingly recreate all of my files again, I would be very happy

 I have been forced into 44.1 because of all the issues between Kontakt/LASS/VEPro/Sonar, and would much prefer to be working at 48. I'm happy to hear that the latest build has fixed the issue for some of you, but it has not for me!

Everything runs flawlessly at 44.1, but LASS is not useable at 48. I've tried reloading the samples, but that doesn't seem to work either. Running Sonar 8.5 on a fresh install from Windows 7, VE Pro is on a separate Mac Pro running Vista x64.

Thanks,

Alex Davis

Ha! simple. Nothing about VSL is ever SIMPLE, but the super quality makes the learning curve worth it for sure. I'm wondering, specifically what new samples from Appassionata Strings are included in EPIC?

Thanks!

I really do hope that the update will show up soon! Have been waiting (trying to be patient) to build my template from the ground up with the 64-bit version, and I'm quickly running out of time.

+1, I'm up the creek until I can get the elicenser working!

there it is, thnks!

Hey all,

A while back I remember seeing a post on the VSL forum that helped users find the perfect levels for every instrument, so that dynamic ranges were appropriate and levels never maxed out. Does anyone remember where to find that guide? Was it a forum post or an official VSL document?

Thanks,

I think this is one of my favorite pieces of yours. Really beautiful work Guy!!

Dear VSL Community,

I'm simply wondering if anyone has done this, or knows about the possibilities here. If I could decrease latency by purchasing a switch capable of link aggregation, I will do so!

(Other terms for link aggregation include "Ethernet trunk", "NIC
teaming", "port channel", "port teaming", "port trunking", "link bundling", "EtherChannel", "Multi-Link Trunking (MLT)", "NIC bonding", "Network Fault Tolerance (NFT)".)

and here is an article on it: http://en.wikipedia.org/wiki/Link_aggregation

Thanks a mil!

--BUMP-- Christian, pls check out these last questions! thx,

Alex

I've been looking forward to this software for such a long time. There has been a need for something like this for a long time, and a few weeks won't make a big difference. I'm disappointed but really appreciate that the developers at VSL are constantly keeping us in the loop! Thanks VSL!

Thanks so much for the detailed response, Christian. The questions never end Hope you could withstand a few more questions...

1) To beat the DirectX question into the ground... So running DirectX 9 is possible, just not recommended. I don't think I have the hardware for DirectX 10, nor do I want to pay for a video card that supports it.

2) When you say "MIR is an Application", I wonder if you can clarify for me- Does it run from within Vienna Ensemble? Does it run as a standalone application? If standalone, how does it interface with everything else?

3) It's great that I could run MIR from either my slave or host computer. Which is recommended? Have you found one to be beneficial over the other?

4) It's too bad about the Mac Pro's (Nehalem) design flaw, limiting my RAM usage to 24GB... I believe my older Mac Pro runs DDR2 667MHz RAM. Would I see a huge performance drop if I used the older Mac Pro for VI? And, could I load more instruments with the older Mac Pro (32 GB of DDR2 667 RAM) than I could with the newer one (32 GB of DDR3 1066 RAM), given the design flaw of the Nehalem machine.

5) I hope, at some point, to hear an A/B comparison between a "with MIR" mix and "without MIR". It'd be REALLY cool if you could show us how MIR compares to a more traditional sort of reverb as well, such as Altiverb.

Hallo,

I'm curious about MIR- the requirements are steep indeed, and the learning curve just to have the right hardware is... STEEP. A few questions:

2) If I have a multi-computer configuration, will MIR run on slave or host? And what effect will it have on the number of VI instances I can run?

3) I have 2008 4-core Mac Pro, 2.66 GHz, 32 GB of RAM... and a new 8-core Mac Pro (Nehalem), 2.66 GHz, 32 GB of RAM. Both machines are running Vista-64. Which computer should I use as VI slave?

4) Will I be able to access ALL of my RAM on the slave machine? I'm hoping to run as many VI's as possible (of course).

5) I'm concerned that MIR requires its own audio interface. My setup only requires one audio interface at the moment, and all audio runs back to my sequencer where I mix everything. Is it possible to elaborate on how MIR would be implemented in a two computer setup?

ah, I see. must've missed that post. Thanks!

Dear VSL,

Dear VSL,

Excellent point- that's very true. And I can't deny that OWC customer service is AWESOME. They were always really helpful. But it was extremely frustrating to receive three bad products in a row over a 2 month period. And after the third batch, OWC blamed my machine... Which was incorrect, because the OWC RAM didn't work in an identical computer either.

Also, the RAM I received from www.datamem.com had higher-quality heatsinks on them. And I can't tell you how happy I was to be up and running after 3-4 months of back and forth with OWC and Apple.

****BE CAREFUL about buying RAM from OWC!! BEWARE!****

I purchased the 32 GB set from them for my 2009 8-core, and it plunged me into a world of pain. The 1st batch did not work properly, and so they sent me a replacement, which ALSO did not work. After the 3rd batch, I spent 2 months troubleshooting the machine with Apple, until they finally gave up and blamed the RAM.

My only option was to drive 5 hours to the nearest Apple Store (one problem when you live in the middle of nowhere), and test the OWC RAM on a similar machine. IT DID NOT WORK ON THE SIMILAR MACHINE!! I returned the RAM pronto and bought slightly more expensive RAM from www.datamem.com... And my troubles are over.

Do not buy RAM for your 2009 Nehalem Mac Pro from OWC!!! STAY AWAY!

This is huge news. Say goodbye to FX Teleport! I'm very excited to get my hands on this. VSL never ceases to amaze.

Hello all,

I know that this issue has been addressed before, but I cannot find a way to search through past forum posts. Awhile ago somebody addressed the issue that VE3 needs to reload every time I close/reopen my sequence. I remember that the Vienna folks mentioned that they would look into a solution for this. Has that happened? Is it still in the works? I've been out of the loop here for about 6 months, so I'm a little bit clueless.

Thanks in advance for any help!

DG is correct. I get around this by assigning Volume to a different, unused CC in every instrument within VE.

Why Logic can't fix this issue is completely beyond me. How is it that a modern, popular sequencer has such an enormous flaw?? Very frustrating.

I don't think this is the case with most users- I've already purchased several libraries that were available for download, one of which was more than 8 GB in size. This didn't pose any problem for me! I could understand if it caused a bandwidth problem on your end, however.

 One of the main reasons I'm a member of this forum is to see how DG will respond to questions.

Thanks DG for making life interesting here :-) 

I've found that a8 is WAY too thick to play for chords. Those are too many horns flying around! I might try using Horn Triple for one or two of the notes in the chord, and a4 for the others. This will be a balance of thickness that might sound a little bit better?

If you have enough memory, you could throw the Vienna horn in there as well. However, I personally  prefer the tone of the Triple.

Hope this helps,

Alex 

EDIT: you could also simply load up a single "sus" patch, either Solo or a4, depending on your taste. You won't get the beautiful legato, but you'll have a polyphonic instrument. It would sound nicer, probably, to load 4 separate tracks of Horn triple, so that each line has the capability of playing legato.