Karel --

Thanks for your prompt response, but I'm afraid I still am confused, as I need to know the PROCEDURE, in a little more detail than you have outlined.

There are two additional tricks:  do NOT enable instrument 1 in the multi-instrument in the Environment (that will be assigned to VE Pro track itself, which will contain no MIDI information), the remaining 2 - 16 are available for the external instrument tracks below.  These external tracks are your VI Pro instances within VE Pro.  You must ALSO (trick two) insert a transformer in between the multi-instrument and the VE Pro channel, to convert CC 7 to some other control number (enabling separate control of volume for each VI Pro instance within VE Pro).  Read the explanation in Needful Things within the VSL User tab after you have viewed the video, and you will understand these additional procedures for the Environment multi-instrument and the transformer.  You save the whole set up as a template so you don't have to keep doing it over and over again (when this template works).

So there were have it.  Now, back to the new VE Pro manual, p. 16.  Where does this new "Event Instrument Plugin" go?  Page 16 of the VE Pro manual instructs us to add it as an Insert on the VE Pro channel strip in the Arrange window (to the left of the main, large grey area where the tracks go, the vague grey plug under "Inserts").  Insert it as a plug-in within VE Pro (the first track we created, above).  I do so: "Inserts-Audio Units-VSL-Vienna Ensemble Pro Audio Input-Stereo".  A PURPLE Audio Input pops up, and I Assign it to the VE Pro server that I started before starting Logic (just as I Assigned the initial instance of VE Pro in track one to that server).

But this is not what is supposed to happen.  Recall, I am FOLLOWING a RECOMMENDED procedure to set up VE Pro in Logic (the complicated procedure using the Environment).  Recall ALSO that the VE Pro instance is NOT multi-timbral.  If I DO NOT follow this procedure in Logic, I cannot INDIVIDUALLY control volume with CC 7.  Note, further, that p. 16 of the manual, illustrating the use of a "Event Instrument Plugin", shows a GREEN "Event Input" plugin popping up, not a PURPLE "Audio Input" as I have.  If I REVERT to the setup of VE Pro as a multi-timbral instrument (with no fancy Environment and separate external instruments), I lose individual control of instrument VOLUME, do I not?  Rather limited compositional possibilities there!

Now I get that we are talking about Automation (or Track Based, rather than Region based, in Logic-speak) control.  Okay, so, again, HOW do I control, say, the violins as, say, the third VI Pro instance within VE Pro, but not all the other instances at the same time?  That is, on what TRACK does the automation control occur?  In the usual case in Logic, one uses a key command to bring up Track Based Automation for a given track for the instrument in question and automates away.  HOW is this accomplished using this new plugin? WHERE does the automation occur?  Is the "Event Input Instrument plugin" for Automation of VE Pro parameters ONLY (such as power panning), while individual TRACKS within Logic are for Automation of individual VI Pro instruments within VE Pro (as is normally the case)?

Is it the case that we can still use the old, VE Pro 4 procedure and still use CC based (Region based) control under VE Pro 5, or is this incorrect (that is, follow the recommended procedure in User-Needful Things)?  The advantage to the old procedure is that under Region Based Automation, the Event Window, at the right of the Arrange window, can still be used for precise event editing.  There IS a special Automation event window that can be used for precise Automation editing if one wishes to use Track Based Automation, but I find it cumbersome to use, as it floats about separate from the Arrange window.

Are you saying that under VE Pro 5, to get Automation in Logic, we SEPARATE VI Pro INSTRUMENT tracks (with Region Based MIDI data) from the VE Pro AUTOMATION track, which contains Automation data for ALL instruments (in tracks below) within a given VE Pro instance?  Before, Automation for each track was contained within each track, not on some different track, and it was reasonably easy to figure out which track you were automating.  Are we supposed to keep a list of which automation numbers in the VE Pro Track control which Instrument tracks?  If so, you are talking about several dozen, if not hundreds of -- given the new complexity of VI Pro 2, different parameters in ONE track which I must sort out to control the tracks below.  I can see myself deciding whether Automation parameter number 257 in the VE Pro track controls the horns or the zylophone in the 19th track below.  Under the old system, I go to track 19 and automate it directly.

I believe I had a second question.

2.  In days of yore, with VE Pro 4, to get an additional battery of 15 (not 16) instruments, one simply instanced an ADDITIONAL software track and created the external tracks below.  I mentioned this is my original post.  This works.  How do I get additional instruments using this NEW procedure, and, even as explained, don't I have to create an ADDITIONAL instance of VE Pro, just as in days of yore?  So is the procedure simply to duplicate the original set up?  And again, on WHAT TRACK does the Automation go, and which instance of VI Pro WITHIN VE Pro am I then automating? usw.

As for the "Utility-I/O", where does one put this (VE Pro or VI Pro external track?), and how is this different from the trick of creating a phantom Audio track in Logic, so as to AVOID having a given software track go LIVE when enabled within Logic and blowing your CPU, because, when a track is enabled, Logic turns on every plug-in, all the way down the line? To avoid this unhappy result, we record enable an Audio track we never use.

A request.  Could we have Paul, as VSL Explainer-In-Chief, provide an additional VIDEO for us Logic users, speaking sehr langsam, showing:  (1) the recommended procedure for setting up VE Pro 5 within Logic (is the Environment procedure still recommended, if, as appears to be the case, use of that procedure ELIMINATES the ability to automate tracks, because the Event Instrument Plugin may not be used -- an Audio Input pops up instead), (2) where the Event Instrument Plug-In goes (which track), (3) how to use Automation within Logic for a given VI Pro instance (which track gets automated and how), (4) how to Automate VE Pro 5 ITSELF, and (5) what we do with the "Utility I/0" plug in.

For some reason at this point, and having spent the better part of a rather longish morning and several cups of coffee trying to compose this attempt to clarify my questions, the word "daunting" occurs to me.

A picture, or better a video, would be worth a thousand words.

Steve

Hello

Could you put a Logic song for downloading

Thanks

Cyril

Cyril

Happy to do so, but you will have to tell me how to do that.

Steve

The VE Pro Event Input plugin is an instrument AU, just like the main VE Pro Server Interface plugin. So instead of adding a second VE Pro Server Interface plugin, you add a VE Pro Event Input plugin and assign it to an existing connected VE Pro Server Interface plugin. That is basically all there is to it.

Hello Karel

May be it is the vapor pf the French Champagne we are having on our all inclusive holidays, It is not very clear [8-)]

Can you put a Logic song with an example of 32 VI 

If you could fix the PDF of the manual so we can zoom on the image that will help !

Thanks in advance

Best

Cyril

P.S I will be home next week and I will do trials

I've paid for the upgrade but haven't installed it yet because of this, and because I'm mid-project.

However, since the main reason for my upgrading was the proposed solution to the 16 MIDI channel limitation — and after reading all the above (and the manual) — I'm wondering if it's at all compatible with my way of working in Logic.

For each bunch of 16 instruments (VSL VIs, LASS patches loaded in Kontakt, etc) I have a VEP instance which communicates with a VEP plugin inserted on a Software Instrument in Logic. The latter plays what is essentially the NET1/2 outputs of the VEP instance. All other NET outputs are received in Logic via AUX channels.

Now, I'm *playing* each and every instrument through custom Multi-Instrument objects which are connected (in the Environment) to the Software Instrument, triggering the proper MIDI instruments in VEP. These are the only tracks that appear in Logic's Arrange Window. I only add the actual Software Instrument (or AUX objects) as a track when I need to do some automation.

From reading the above, I'm wondering how the VEP 5 solution integrates into this, as there is a very clear separation between MIDI and audio in my setup. How will the Event Input handle additional MIDI channels when the MIDI data itself is played on a Multi-Instrument track, not a Software Instrument track?

A screencast would be most helpful since apparently I'm not the only one finding this very confusing.

Thanks.

I would like to second your, and my, request, for CLEAR guidance on HOW one sets up VE Pro 5 in Logic 9.  I sounds as though Talino has the same setup, with VE Pro 4, that I have, viz., the one set out in the User Area under Needful Things:  one software instrument track for VE Pro, configured an NON-multi-timbral instrument, a multi-instrument set up in the Environment and cabled to the VE Pro channel strip just set up, and then, back in the Arrange window, additional, EXTERNAL tracks that are assigned to the multi-instrument just set up in the Environment, each of these tracks having its own MIDI channel, using the Library tab to do the assigning.

I cannot understand whether this VE Pro Event Plug-in gets (1) its own, separate track (the way we used to do it in VE Pro 4, when we put in another instance, as a non-multi-timbral instrument, of VE Pro, in order to create an additional 15 instruments, of (2) whether the Event Plugin is inserted, as a plugin (not a separate instrument with its own track), to the EXISTING VE Pro instance.  If the latter, (2), do I then create an ADDITIONAL multi-instrument in the Environment to get my additional External Instrument tracks?  To WHAT is this new multi-instrument in the Environment cabled?  Just as important, WHERE is the Automation to take place, that is, in what track?  All in ONE track -i the VE Pro Track, or, as it should be, in each instrument track, so that there are up to an equal number of External tracks for instruments and Automation tracks? And another Automation question, where does the Automation for the VE Pro ITSELF take place? If (1), then on the Event Plug In Track, if (2) on the Ve Pro track?

Finally, again, IF I am to insert the Event Plugin as a Plug-In (not as an instrument with its own track) into an existing VE Pro instance, then, under the set up I describe above, and which I believe Talino has as well, the Plug-in pops up as an "Audio" plugin, NOT an EVENT plug-in as it appears in the VE Pro 5 manual.  This occurred on a new, otherwise empty project which I set up for testing purposes.

Perhaps Paul could provide an explanation that users like me could more easily follow.  Again, a VIDEO would be VERY helpful (hint).

I have not reached the stuttering and silence problems mentioned in another post, because I am reluctant to commit projects to this new software until some clarification (and possibly a maintenance release of VE Pro 5) made available.

BTW, I, too, paid for the Upgrade, site unseen, based on VSL's reputation and my prior experience with the company.  I am sure this will be sorted out, even if it turns out that there are no software issues, just an "understanding issue" by some users like me.

Steve

Hi,

I´m showing the Event Input Plug-in at around 4:20 in the VE PRO 5 Overview Video.

There is not more to it....

All relevant information for Logic Users can be found on the pages 16 ff and 33.

Of course there will be more demos to come, but unfortunately the day only has 24 hours....

I´d be happy to hear about better explanation for this feature from fellow users!

Best,

Paul

Thanks a lot for taking the time to write this very clear explanation. Can't wait to check it out but I'll wait until my project done... [sigh]

Cool. I hope it helps you. I also hope it's clear enough. English is not my mother language :)

Post your results to see if there's something else I can do.

The I/O Utility plugin is required if the I/O buffer size and Process Buffer Range setting are not identical in Logic (which is almost always). Process Buffer Ranges: Small = 512, Medium = 1024, Large = 2048. Otherwise you will get artifacts and dropped MIDI messages depending on which track is selected in Logic.

Cojoncio --

Thank you for your clear statement of the set up.  I did, indeed, get 30 channels to work.  The inability to individually control volume through CC7 remains, as ALL instruments for a given instance of VE Pro (or the VE Event Input) are controlled at once.  It is for this reason that I use the envirnonment approach, rather than the multi-timbral approach.

Unfortunately, problems of SILENCE have emerged, with NO tracks providing audio output.  I installed the latest (9753) version of VE Pro, and all was well, UNTIL I tried to install a 3rd set of 16.  The VE Pro Manual provides no guidance on this (in case you want more than 30 tracks), so I tried repeating the process for a second set, as you did with the first two, making the second instance of the Event Input plugin a MIDI in 4.  In this configuration, the third set of 16 (with the VE Pro 5 itself instanced), was silent, but showing input from the VI Pro instruments in the track, while the FOURTH set of instruments produced sound! 

Then, for some reason, I got no sound at all, although If I open up the VE Pro interface, I can play the keyboard window and hear sound!

So, at present, I am stuck using no more than 30 tracks and dare not try more.

We could use a little more help here.

Again, thanks for your very helpful post.

Steve

Did you correctly put the Logic track that has the Event Input plugin into Live mode?

Karel

On BOTH Event Input plugins, I added the Utility-I/O and set it for output 1-2 (clicking on the radio button to light it up), and then Bypassed both.

This is what I did:

To test things out, I started with a new, blank project.  I followed the advice of poster Cojoncio in this thread and got things to work -- at least for a while.  As stated, what I did FIRST was set up a VE Pro instance as a multi-timbral software instrument and then add an additional 15 tracks, and SECOND add ANOTHER multi-timbral software instrument, but instance the Event Plugin (instead of a VE Pro instance) and set it to MIDI in 2 (which your directions in the Manual do not discuss), THEN I get the full 30 channels (since I reserve channel one on both Instruments 1 and 2 for the VE Pro and Event Input plugins), and they work properly.  In other words, I had TWO groups of 16 tracks, the first 8 labled "inst 1"; the second labled "inst 2".  The VI Pro instances within VE Pro were set to MIDI In 1 and MIDI In 2, and each instrument was properly set to its own channel, e.g., MIDI 1, channel 2, MIDI 1, channel 3, MIDI 2, channel 2, MIDI 2, channel 3, etc.

I then tried to add additional tracks by adding additiona AU instances.  First, I tried to use just the Event Plug in to create my additional groups of 16.  That didn't work, as explained below, so then I decided to just duplicate what I had done to get the first 32 track, but use MIDI In 3 and 4.

I first tried to get a THIRD group of sixteen by setting up the multi-timbral software instrument, by instancing the Event Plug-In only, but found that when the green Event Plugin window opened there was nothing to Assign it to.

So I tried another approach.  I tried duplicating what I had done with the first set of 32 tracks, but using MIDI IN 3 and MIDI In 4:

Again, the procedure was:

1.  Software multi-timbral instrument - VE Pro with 16 tracks

2.  Software multi-timbral instrument - Event Plug-in Assigned to the first instance in the VE Pro Server (shows up as "[1]"), Input to MIDI 2, an additional 16 tracks gained (32 so far).

3.  Third Software multi-timbral instrument - VE Pro with 16 tracks  (I now have a total of 48 tracks) (unable to assign to MIDI 3 when the VE Pro popup appears, unlike Event Plug-In windows).  ==> I cannot figure how to assign to MIDI In 3 for this AU.

4.  Fourth Software multi-timbral instrument - Event Plug-in Assigned to the second instance in the VE Pro Server (shows up as "[2]"), Input to MIDI 4

5.  Added Utility-I/O Plug-in to 2 and 4, above, clicked radio button to activate output, and Bypassed.

6.  Added VI Pro instances within VE Pro and assigned to MIDI 1, 2, 3, 3.  I had trouble here, because one of the VE Pro windows did NOT have the VI Pro instances I had set up in (3) above -- the second VE Pro instance.  So I added ADDITIONAL VI Pro instances and set them at MIDI IN 3 (for the second VE Pro instance).

I recorded a short strip of music in a Region.  I played the Region in 1, 2, 3, and 4.  For groups of 16 1, 2 and 4, in each case, ALL instrument volume meters in every track (i.e., in each group of 16) showed a signal in the small meter that appears at the beginning of each track, and I could hear sound in the track being played. All 16 lighted up at once in each group.  So in the 1, 2 and 4 groups of sixteen tracks, it appeared to work (I could hear the Region played).

In 3 (the one with the second VE Pro instanced), the track in which I inserted the Region with MIDI notes showed the meter at the beginning of the track working, but I got no sound.  Also, NONE of the OTHER instrument 3 tracks showed activity in the meters.  In other words, the other 15 tracks showed no sign of activity.

When I opened the VE Pro Mixer windows for 1, 2, 3 and 4, and then opened up the VI Pro instances I had added within each, I was ABLE to play the keyboard window with the mouse and hear sound.  In other words, until I tried to record and play something,it appeared that all was well in each of the 64 tracks.

At some point, ALL tracks STOPPED sounding and there was SILENCE, even though I had not changed any of the setup.  It had something to do with playing the music.  Even the FIRST set of tracks did not work.  HOWEVER, when I opened up individual VI Pro instrument instances within VE Pro the keyboard still played when I used the mouse and I could hear sound.

At the present time,I don't know how to set the SECOND instance of VE Pro to MIDI input 3, and am generally at a loss as to how I am to exceed the limit of 32 tracks.

System:  OSX 10.6.8.  2.8 GHZ Intel Core 2 Duo IMac, 6GB RAM,   VE Pro 9753 (latest version from your website).  Logic 9.1.5.

I would be happy to upload some screenshots if that would help.  You will have to provide me with an email address or show me how to add a graphic file to one of these posts on the forum.

Karel -- I know you have your hands full.  Rather than responding to my specific problem, it would be more helpful to me (and perhaps others), to either AMEND the VE Pro Manual or, better, put together a VIDEO, showing the SUCCESSFUL set up of, say 64 tracks within Logic, making sure to tell us, as Cojoncio did, EXACTLY what specific steps need to be taken and buttons need to be pressed to get the system to work.  Part of the problem is language -- this is why pictures of the various steps would be best, then everyone knows what you are talking about.

I have more than abstract interest in this, because I have just ordered an Apple Mini Server for the spefic purpose of handling VE PRO and the Vienna Instrument library.  It arrives in a few days.

Thanks for your attention.

Steve

I also use the enviroment approach, I usually take a long time to upgrade, since I can't afford to have down time. I made the mistake of upgrade, so now I have to go back to Pluge Bidule and musiclab midiLan! The horror!

VE Pro 5 can still be used exactly like VE Pro 4 and is completely backward compatible. You don't lose anything by upgrading. I will try to reproduce the strange issues in Logic based on your description, but so far everything seems to work well.

Well, this is crazy.

Despite the long post I wrote trying to carify things I have to admit that the Event Plugin DOESN'T WORK. Period.

Using the environment approach I set up a multi instrument with 15 channels. Everything worked fine. I added an Event Input  connected to this first VEP instance and loaded a few kontak instruments. Of course the I/O plugin is inserted as required in the manual.

Try my sounds. Fine. It works great. Press the start key, play the master keboard and get a horrible latency even with the setting is none in the VEP plugin window. Stop Logic and GET NO SOUND PLAYING MY MASTER KBD!!!

Go back to the arrange window in Logic. Select any of the first 15 channels and play. Good. There are sound. Then choose any of the channels belonging to the Event Input instance. Get sound too with no latency. Great. Start the sequencer and play. Again latency. Stop the sequencer and get no sound, even when I try to play in the screen keyboard.

So I guess the Event Input is a GREAT idea. Too bad is not working in Logic. The only reason I upgraded was to use this nice feature but still I'm stuck with 16 channels per instance. Don't know if the other users affected by this problem have some kind of solution.

Any ideas from Vienna?

Thanx

Cojoncio --

I can't comment on using VE Pro 5 with the external approach, but I did have problems with it also.  To explain:  as I introduced additional Event Input non-multi-timbral instruments in Logic (and thereafter set up External Instruments, after having set up other "multi-instruments" in the Environment), what I discovered was that Logic would NOT select the appropriate External instrument.  For ease of discussion, I'll call this arrangement the "External Instrument Set Up."  In other words, when SEVERAL Event Inputs were set up, Logic would select the MOST RECENT set of External Instruments, even though I had selected a track that contained an External Instrument associated with an EARLIER instance of the Event Input. Only the MOST RECENT External Instruments would be selected, regardless of the Track chosen in Logic.  Put otherwise, when I selected EARLIER tracks with EARLIER Event Inputs, as I watched the Library to the right of the Arrange window, the correct External instrument was not being selected.

I CAN offer one suggestion that did help me however.  After I had originally set up an External Instrument Set Up, I was having pops and crackles with the instruments that DID work, as well as significant LATENCY problems that I could NOT cure by increasing latency settings in logic and VE Pro.  I DISCOVERED that I was using the WRONG network instance of my Slave computer.  I do not know enough about network set ups to explain this, but when I tried to CONNECT the VE Pro 5 instrument to the Slave, I was given TWO choices, that is, TWO IP addresses (e.g., "10.0.1.9" and "169.255.43.102") for the SAME Slave computer.  I tried an experiment.  What I did was give the Slave computer a FIXED address, NOT using DHCP in the Network settings of System Preferences of the SLAVE computer. Thereafter, I selected the FIXED address for the Slave computer when I CONNECTED the VE Pro 5 instance in Logic, and the clicks and pops and latency issues, which you seem to be describing, disappeared!  I have tried this on the simpler multi-timbral software instrument set up with equal success.

The folks at VSL are not in the business of teaching us how to set up networks, but it WOULD help, if they could provide a SIMPLE network setup involving one Mac Airport setup, one Master computer and one Slave computer.  I think I have a typical OSX set up, with my Mac Airport for Internet access, my Master computer, and the Slave computer, ALL capable of providing DHCP service in their respective network settings.  So, at one point, I had THREE DHCP servers going at once (I think).  I believe that what DHCP does is provide IP addresses within a local network, so that the various computer members of that network can communicate via the address provided.  Perhaps having THREE DHCPs turned on leads to confusion and latency issues I experienced.  A user on another forum, who uses the Mac Mini in Logic as a Slave computer, suggested that I TURN OFF the WIFI network (the fan at the top the screen), so that the ONLY network the Mac Mini is communicating with is through the ETHERNET cable.  Again, in the Slave Computer I opened up Network in System Preferences and assigned the Slave Computer a FIXED IP address, turning OFF DHCP.

All this said, I have NOT gone back to TEST the External Instrument Set Up, using my new network settings.  At some point you like to get back to the music!

Hope this provides some help.  I have tried to be REALLY clear in my explanation to help others who are not as far along in computer and Logic knowledge as you are.  I have enough trust in this forum, that if I have made mistakes, they will be SWIFTLY corrected.  :)

Steve

Hi Steve.

Thanks for the info. At this point I'm using VEP on a single computer, so I have no network issues, but I'm sure your clear explanation will help other users using several computers networked.

Regarding our prblems, I've been digging around this forum and found this very useful thread:

http://community.vsl.co.at/forums/t/30297.aspx?PageIndex=1

There is a solution for the muted Event input. The trick is to insert an I/O plugin in every single instance of VEP, not only the Event Input but also in the VEP instance where the Event Input is connected. You just need to do the same I/O set up as described in the manual. I've tried it with the environment multitimbral setup and it works!! No latency, no muted tracks [:D]

Karel (from Vianna) reported that it's a good workaround but the downside is that Logic throws all Live mode tracks processing on a single CPU core. At this point I'm working on a small project with two VEP instances, the first one with an event input attached with another 15 midi channels plus Vienna Convolution Reverb, Vienna Multiband (in the master bus), a few Logic instruments and a few audio tracks in the arrange window and it really works fine. There is one node reaching up to 50% while two or three others don't go beyond 5-10%. Also the readings in the CPU VEP meters are about 25-30%

I'll be able to push the system in my next project but as for now is working OK.

I'm also waiting for a final solution to this problem as Karel said he's gonna focus his efforts in this issue, making it one of his priorities.

BTW, I also support the idea of getting some feedback from Vienna on how to set up a simple network. Just a PDF would be enough [;)]

What is advantage has the Event input  compared to IAC ?

Looks like we are having the same problems