Vienna Symphonic Library Forum
Forum Statistics

181,814 users have contributed to 42,187 threads and 254,604 posts.

In the past 24 hours, we have 6 new thread(s), 30 new post(s) and 50 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Template config. type: "disabled VEP" using Logic; Any naysayers?

  • Template config. type: "disabled VEP" using Logic; Any naysayers?

    MackerM
    MackerM

    I'm planning to build an everyday work template for Logic 10.4.5 and VEP7-AU3 in my one and only computer, using the so-called "disabled VEP" type of template configuration, along the lines described in Guy Rowland's splendid Youtube video, "A Cubase / disabled VE Pro Template Part 2: How To Set It Up."



    It appears to be ideal for me. Guy has about 800 or so tracks in his template, so I'm thinking Logic + VEP7-AU3 will cope and, in my more modest case, have room for me to expand later. Like Guy I'm limited to 64 GB RAM, and though I don't know what computer he's using I believe my 5K iMac (4.2 GHz 7700K i7) will manage well enough.

    I don't suppose anyone's actually producing yet with an equivalent AU3 template in Logic 10.4.5, but does anyone with experience of a Cubase template of this type in a single computer have any comments about why a disabled-VEP7 configuration might not be the best way for me to go?
  • Dewdman42D
    Dewdman42D

    Go for it and let us know how it goes!  I'm definitely curious how you go about using the new disabling features of both VEP7 and LPX 10.4.5 and how you might go about automating it between the two.

    I think VEP AU3 is working very well for me.  I made a 1270 track template on another thread, that might help you get it setup and working.

    My preferred method at the moment is to build a large template in VEP, perhaps using disabled channels or instances or folders..  then in LPX just build up projetcs one track at a time and simply specify which instance/port/channel to use for each track, which will connect to an already existing channel in VEP, that may or may not need to be enabled.  I have 128gb of ram, so I simply have not run into a need to do that, but I don't have a huge template yet either.
  • MackerM
    MackerM

    Glad to see you're up and running with AU3 at last, Dewdman42. And thanks, but I'll be building my custom template step by step around a hefty subsystem I already have in the Environment.
  • MackerM
    MackerM

    I'm glad to see my question hasn't elicited any adverse comment about the disabled-VEP template technique. I'm taking that as no news is good news, and I'll proceed with my plan.
  • Dewdman42D
    Dewdman42D

    well one suggestion I have, if you're going to be using extensive enviornment stuff in any case, you could probably simplify the AU3 side of things by using multi-instrument objects in front of channel strips.  So basically for one VEP instance with 127 tracks, you'd need 8 inst channel strips, each one set to midi channel ALL and ports 1-8.  Then put multi-instruments in front of those to channelize the midi channel.  Otherwise, I will look forward to seeing what you come up with in the enviornment in order to control enabling/disabling things in VEP.  Seems a worthy project.
  • W
    W

    I just created a setup using Dewdman42's kindly supplied AU3 template but found that even though I'd mapped every instrument's disable function to a controller key, disabled every instrument and saved the instances , server project and Logic project, it still loaded with all instruments enabled, thus filling all available (64GB) RAM and rendering the machine unresponsive.

    Is there a reliable way of having VEPro7 load the project with every instrument disabled so that I can selectively enable what I need with my mapped shortcut? Do the instances themselves have to be saved in a disabled state for this to work?
  • MackerM
    MackerM

    Hello Wader,

    I've not seen that problem, but I don't use any of Dewdman's stuff. My VEP is woken up by Logic always as expected with VEP channels and/or folders disabled or enabled as I wanted. I haven't been using the disable button on any of the VEP client plugins in Logic, nor do I use the Instance Disable buttons in VEP; they're always left enabled. No idea what the issue might be in your setup, but when I have time I'll see if I can reproduce your problem, trying out different things.
  • Dewdman42D
    Dewdman42D
    If you figure out why please let us know. The template is very simple and really just a bigger version of the templates provided by vsl. I can’t think of any reason that would effect the enabled disabled status. Are you running coupled or decoupled? Etc...
  • W
    W
    Thanks Macker and Dewdman. I'm working on it. So far I've tried loading the template in VEPro7 with no DAW connected and saving all instances again with all instruments disabled. I then closed it and opened it to find that it loaded with all instruments loaded again. Crashing my machine by attempting to shove 75GB into RAM. I'll look into the coupled / decoupled preserved thing now. Pretty sure it's nothing to do with the template fwiw Dewdman.
  • Dewdman42D
    Dewdman42D

    Well I haven't started working with the enabled/disabled features yet, but its something I want to do because I plan to setup a rather large VEP server project where most of the instances will be disabled, and like you I'd rather that when I open the project, by default its all disabled, then I can I decide which instances to load as I work with it.  So I'm very interested in whatever you figure out, I haven't had time to get that deep yet.

    If this happens even when LogicPro is not running (?), then I don't think it has anything to do with couple or decoupled.
  • MackerM
    MackerM

    Wader, I can't even reproduce your VEP server on-its-own scenario. I used an older 10-instance test VEP7 (now 7.0.834) server metaframe which has never ever seen any MIDI-controlled disable/enable from any source; it has several dozen Kontakts, VIPros, VSPs and various synths scattered through the instances; nothing huge. Without launching Logic, I've manually disabled certain channels and folders, saved the metaframe (i.e. in the "file" menu), then quit and re-opened VEP; those manually disabled items are still disabled, just as I had them before saving. I've done similar inside just one of the instances and saved it in the "instance", menu; it still works ok.

    I'm out of ideas (and time). Perhaps VSL can help you unravel this mystery.
  • W
    W

    Thanks very much for trying to reproduce the issue Macker!

    Since the server project would crash every time I loaded it, I tried using the 'Import Instances From Server Project' function to selectively bring back instances, save them with all instruments disabled, then save the whole server project again with everything disabled, actually the same in effect as it was previously but with the 'Decouple Instance' Icon lit. The same things happened when I saved it and tried to load it again. I've no idea what I'm doing wrong or whether it's a bug, but I've attached a screenshot in case that rings any bells with anyone..

    Image
  • W
    W
    last edited
    last edited

    Interestingly, when I click the Enable/Disable instance button it first unloads everything, then loads it again!

    VSL_Disable_Enable-HDU0020720p.mov-1696338594458-ighav.mov
  • W
    W

    ***Update***

    A very speedy fix from the devs! It was indeed a bug but now everything works fine with the latest installer :)
  • MackerM
    MackerM

    Hurrah! Thanks for the good news Wader. And my thanks also to the VSL devs for continuing to be world-class problem-solvers!