SOLVED :

to allow the Audio Input RTAS to keep the data when I relaunch the session, the instance of Vepro 5 where all the RTAS audio inputs are routed must be inserted on an instrument track in Pro Tools 9, and NOT on an aux.

Hello all, I want to report what appears to me a bug.

Simply put, if I route the audio out from an instance of VEPRO 5 (which gathers midi instruments) and on a group of auxes (where the sound is routed) I load for each track a Vienna Audio Input RTAS (setting each plugs to be assigned to another VEPRO instance (which is not 64bit, but 32bit, for the lighter fx), and connected all the inputs properly for each RTAS), having created another group of auxes which receives the audio outputs of the fx instance (by setting the inputs in PT , accordingly to the audio outputs of the vepro5 fx instance), once I click on the record button in the main instrument (where the former vepro5 instrument instance is), the sound passes without problem.

The audio generated by the main instance enters in pro tools via the auxes (each one with a audio input RTAS) then thru the plug enters in the fx template, plays the effects and goes again in pro tools via the auxes. So I save the whole project from pro tools.

the issues comes when I reload the session and click again record on the main instrument track: NO sound passing.

So I'm forced to restore one by one the Vienna Audio Input RTAS plugins for each auxes anytime.

I'm on Snow Leopard 10.6.8, Pro Tools 9.0.2, and the last build of Vepro5. 

Thanks for giving a look to it.

I haven't one but this effort to keep the owners warned is very commendable, thanks !

I want one immediately

looks like a fridge with the freezer and the vegetables compartment...simply wonderful....

you are welcome !

hello !

only one 64bit server (or/and one 32bit server) which keeps the less possible instances of Vepro / plugins, each one which keeps the less possible instances of Kontakt, each one maxed out to 16 instruments / midi channels.

you max out the Kontakt instance's 16 channels first, then you do the same with a 2nd Kontakt one, and so on, till you max out what you set for your Vepro instance, and only then you open a new Vepro instance, following the same method.

have the same machine as your, maxed out ram (96 Gigs,used 86), 4 sample drives with 115 Mb/s read speed each (2 sata, 2 esata with pcie card) and oc 1 sata for os/apps plus 1 sata for projects:

if I don't choose 16 cores of multiprocessing in K5, I can't barely stream less than half of the samples I've loaded in my  template.

Mem server is off, while the preload buffer size is maxed out to 240 kB (not having ssd but enough ram, I took this lane).

If you max out the preload buffer, you'll see how easy you are going to eat up your ram...these are the heads of the samples, the rest comes from drives...but this way they have more breath, being them not as fast as ssd, and in my case performance is improved, because the ram is stressed as hell...

thanks Bill for the reply, very appreciated..

I think I'll go along with the 4 SATA / eSATA drives detached as usual, and I'll add the 2 WD My Passport Studio FW800 drives where I'll put the libraries I use the less...my only doubt is that these 2 drives might not be 7200 rpm (it's not written anywhere if they are so), found out some reviews about in which they say they are 5400 rpm...but in the end I think that if I access to them less frequently, they will cut the job flawlessly, and I gain audio streaming access to 6 drives overall, which becomes quite empty then...hehe..

please please don't drop support for 10.6.8, it's the most stable os I've ever work with (just my opinion...)

sorry, I bump this just once, because I cannot find objective informations around, especially for what regards vepro.

Thanks for any suggestion

Hi there !

I just bought a MaxPower 6G PCIe eSATA card and 2 nice external drives for the mac pro, getting rid of fw800, so I decided to organize at the best all the 4 audio drives ( 2 intenal wd black caviar, 2 external OWC Mercury, 1Tb each).

My questions are:

- let's say I have 4 VEPRO big instances, containing Kontakt's ones, called "Percussions", "Drums", "Orchestra" and "Keyboards & Synths".

Is it better to address each one instance' s samples to a single drive (for instance "Audio 1 - Percussions" , "Audio 2 - Orchestra", and so on), or is it better putting all the samples all across the 4 drives randomly, balancing the weight for all the instances ? (so Audio 1, and any other drives, feeds more or less equally all the instances) ?

- can I make a raid 0 of all these 4 disks together, and if there is any advantage in doing so, rather than keeping them detached?

- if I decide to keep also 2 extra FW800 hds (which are 2x 1Tb "WD My Passport Studio" , and I doubt they run at 7200 rpm) , can I make a 1st  raid 0 for the internal drives, a 2nd raid 0 for the eSATAs and a 3rd one for the firewire ones? Or again, it's better keeping all the 6 detached?

In other words, having 2 internal SATA, 2 external eSATA, and 2 fw800 drives, what would be the best configuration for performance ?

Sorry for such dumb questions, and thanks for your time,

beatlesforever

posted also on kvr forum, might be Urs' fault

sorry Paul but don't have the report anymore, as when it happened, I just tried another time to see if it happened again, and then reverted back to the previous disk image backup

my specs are mac pro 12 core, 96 gigs ram, osx 10.6.8

Forgot to say I'm not using last vepro build because when you change pro tools hw buffer size (for instance, from 256 to 1024 samples), vepro crashes

Hello,

Pro Tools 9.03, VEPRO v5.1.11548 and Uhe Diva v1.1.1.

CASE A)

- in Pro Tools, auto read mode enabled, all parameters are ready for automation (checked right-clicking VEPRO RTAS plugin, Automation Dialog) in the instrument track where VEPRO RTAS plugin is.

Of course in Pro Tools automation window the option "PLUG IN" is enlightened in red. I then write some pencil automation on the automation lane in PT9 for "Vienna Ensemble Pro RTAS, Param1".

I have in the VEPRO Automation view, "Parameter 1" associated to any of the possible parameters listed for "Diva 1", for instance "Diva 1 / Output".

Click "Play" in Pro Tools, no movements of the knobs.

CASE B)

- in Pro Tools, auto write mode enabled, same Pro Tools and VEPRO automation settings reported in CASE A)

Click "Play" in Pro Tools to record some automation, and move the knob in Diva...the resultant automation, instead of showing a wave (various knobs positions), shows a square (on/off positions like)

When you switch to auto read mode in PT, and you play this automation, the knob in Diva don't move, as in CASE A).

Tried the same with NI Massive, no issues found, and the automation written in the lane is a normal wave.

Thanks.

2112 D.C.

Another example is Mixosaurus...you are forced to load several different drum pieces which by default are set to receive from "omni" channel, because of its fixed multi-instruments layout, and you can't change that...and every piece of drum has about 30 knobs to be mapped, so you run out of midi CCs at about the 4th instrument...

hello !

I've just noticed that using Pro Tools 9.0.3 and the last build of vepro 5 ( and probably by using any other previous one) , the only way to record the automation of the parameters (knobs, faders, buttons) of a kontakt 5 instrument, which "own" its MIDI TRACK (so its single midi channel which feed vepro 5 plugin in the instrument track), be it host or midi automation, is to keep the pro tools interested midi track "record enabled" and the "midi merge" function enabled ( in order to add data and to not delete the notes recorded in the previous passages) and click "record"...(if you only click "play", even with record enable on, you see knobs moving when you move them, but once you listen back, nothing has been recorded of these movements)

...in other words, no way I can record an automation by just pressing play (NOT record) with the "Write Automation" enabled on the MIDI TRACK where the target kontakt instrument is (in the same way you record automation of any RTAS plug-in which is directly controlled by pro tools, or in the same way you can do with vepro automation parameters feature on the INSTRUMENT TRACK where the vepro plugins is as insert) ..and without the record enabled button on, there's simply no transmission of midi CCs...

...also, no way I can record an automation ,by moving the mouse on a kontakt instrument's knob, even with record enable on in pro tools midi track and clicking "record"..while you can do that on the instrument track where the vepro plugin is as insert (oc you must set the source parameter and the destination one correctly in the vepro automation mapping window)...

I've the impression that this is due to the fact that midi tracks works ONLY with midi controllers and channels, and NOT host parameters, while the instrument track where the vepro plugin is as insert work with both..  

am I doing something wrong ? I'd appreciate if someone do calmly point out what is the step-by-step procedure to set this up correctly

...another question...there are kontakt instruments libraries , like for instance "Farfisa Polychrome" by Synth Magic, which have far more knobs to be mapped rather than available midi cc to map, so you end up to run out of CCs easily lol...

...is there a solution to this ?

Thanks for any ideas my friends !

hihihihi lool !(witch's grin)

I wanna add that VSL and its engineers & staff are in my opinion the most relevant phenomena ever happened in digital audio since ever...

...if it wasn't for you, all 32 bit PT users at this moment would be in great pain, because of the limits of the daw...

..instead, because of you, and this outstanding, topless software vepro5 is, we can still benefit of Pro Tools, which is the best audio software made, NOT for the quality ( all daw are good the same ), but for the easiness of how it works !

So, let me say THANK YOU Vienna !

Sorry Martin was away all day long..

my specs are:

- mac pro 12 cores @2.93 GHz

- 96 Gb ram (template about 80 Gb)

- 1 x 1,5 Tb WD Black sata, 90 % empty (Snow Leo 10.6.8, Pro Tools 9.03 + CPTK2, Kontakt 5.0.2 and some VIs)

- 1 x 1 Tb WD Black sata (Audio sessions)

- 2 x 1 Tb WD Black sata, both 60% empty (Samples 1 & 2)

- 2 x 1 Tb Lacie D2 Quadra fw800, both 70% empty (Samples 3 & 4)

- RMI Fireface 800 sound card

Martin, I'm talking about VEPRO 5 performace, not vipro, so how VEPRO 5 performs with kontakt 5 and other VIs, like Omnisphere, as I don't own or use vipro....

...it seems to me that from VEPRO 5 build 109xx (or from the one just before it, so the 107xx) everything  performs incredibly better than in VEPRO 5 build 106xx...just like to know if indeed there has been this improvement from 107xx, because I was still with 106xx, but when I installed the 109xx, I noticed this...you told me 109xx performs the same as previous version, but MY previous version installed was build 106xx, not the 107xx...so I'm sure there's has been someway an improvement in 107xx Vienna Ensemble Pro 5..dunno about vipro...

thanks anyway!

ha !

wait a moment I moved from build 106xx to 109xx, skipping the 10738, so I now presume the improvements were in this one...can you confirm?

Hey !

Is my mind or this last vepro update has a quite remarkable improvement in terms of performance?

Did you focused in particular to this performance improvement, or it is just the ordinary one which is expected on every new update...or it's just my brain?

Please be honest because I wanna be sure (of my brain), thanks !!