Vienna Symphonic Library Forum
Forum Statistics

180,750 users have contributed to 42,140 threads and 254,362 posts.

In the past 24 hours, we have 3 new thread(s), 17 new post(s) and 48 new user(s).

  • VEPro feature request

    I should say first that VEPro is fabulous, fabulous software.  Very much a game-changer for me.  I recall struggling with many other solutions, some of which worked and some that didn't very well, and VEPro has been amazing.

    It's certainly possible that I missed this, but I don't think so.  I'd like to be able to control and edit instances of VEPro on an external computer remotely, using my main computer, without using Remote Access or the like.  Doable?


  • Without using remote access? That is not possible and will not be possible.


  • Well, this is my ignorance speaking - I figure if you can get it to push 128 audio ports and 32 MIDI channels per instance, a little thing like remote commands to and feedback from slave devices wouldn't be much trouble.  Perhaps it's a protocol/port issue?  Why couldn't it be a little proprietary data along with everything else?   (I don't mean for every plugin, of course - just the Vienna stuff and the ensemble mixer.)

    Anyway, it's still great.


  • Controlling a volume and pan here and there is not a problem, but controlling complex instruments like VIPro and other hosted instruments would be quite some challenge.


  • Can I ask why you don't want to use remote access like RDP or VNC? These protocols are well established and stable and there are already good applications out there to make use of them. Maybe if I understood your issue I could offer some solutions.


  • last edited
    last edited

    @mosso said:

    Can I ask why you don't want to use remote access like RDP or VNC? These protocols are well established and stable and there are already good applications out there to make use of them. Maybe if I understood your issue I could offer some solutions.

    The thing is, I don't want more software, I want less.  It would be great if I could program the remote instances from the main machine, in the same environment, without changing windows or launching a remote environment.  That's it.  I know about the other solutions, I just don't want to do it that way.


  • [quote=dragsquares]The thing is, I don't want more software, I want

    I see. As as user of RDC (and previously VNC) I'm well used the the process of editing VEP instances remotely, but it's never felt at all like a clunky workaround or got in the way of my "flow". Have you tried it?


  • last edited
    last edited

    @mosso said:

    Can I ask why you don't want to use remote access like RDP or VNC? These protocols are well established and stable and there are already good applications out there to make use of them. Maybe if I understood your issue I could offer some solutions.

    The thing is, I don't want more software, I want less.  It would be great if I could program the remote instances from the main machine, in the same environment, without changing windows or launching a remote environment.  That's it.  I know about the other solutions, I just don't want to do it that way.

     

    Well I guess you're out of luck then.

    DG


  •  My thought exactly...


    Dorico, Notion, Sibelius, StudioOne, Cubase, Staffpad VE Pro, Synchon, VI, Kontakt Win11 x64, 64GB RAM, Focusrite Scarlett 18i20, August Forster 190
  • last edited
    last edited

    @mosso said:

    Have you tried it?

    Sure have, though in this case RDC doesn't apply as it's Mac-to-Mac, but there are other ways of doing that.  It's not that it doesn't work.  Just not how I'd like to do it.  I love when technology is invisible - in this case, just telling the host computer that the instance I'm creating gets its juice from the machine next to it, but interacting with it in the same way.  

    If it's un-doable, fine.  I'm not a software programmer, just someone who uses the stuff.  But just from an anything's-possible point of view, I'm pretty sure it would have been cool.  Meanwhile, back to work.


  • It sounds like you want something like FXTeleport. The product already exists, but comes with a number of downsides. Doing processing on one machine and gui on another gives birth to several problems. First of all, the gui protocol is limited to a set of parameters (in case of FX-teleport, VST-Parameters). Any complex gui-core interaction like that in VIPro, or just a regular audio meter, just don't work. Second, the audio streams would have to be separate from instance to instance, which creates a network overhead and lowers total throughput. Third, the level of interaction (shortcuts, window handling etc) which is possible in a plugin window is a fraction of what a real application can do.

    The Audio Unit plugin standard was written with over-network hosting in mind, some of Logic's plugins are usable on "node slaves", while presenting the gui on the master machine. You won't see any more complicated multi-platform plugins running this way however, pretty much all developers I know uses memory pointers to gain direct access to core information from the plugins gui. Simply because it is easy, fast and works on all platforms and plugin formats.

    VEPro was actually developed with all of this in mind - to offer a greater control over plugins and instruments, since the hosting in most sequencers usually ends up in a constant-moving-around-of-plugin-windows-madness-soup. VEPro, if used properly, will definitely increase the overview of your orchestra, whether used on a slave over RDC/VNC/ARD or hosted locally.


  •  FXT doesn't present the GUI on the host machine either. The only time I've seen this sort of thing mentioned is for PLAY Pro, which doesn't exist. [;)]

    DG


  • I thought that FXT had a "local mode" which allows for precisely this.Otherwise, the Logic node-able plugins allow for this, as I wrote in the previous post.


  • While I believe that would be quite a task, I think it could be helpful.

    On the other hand I would not call it a "top priority" since most  of the time I just build a template and never look at it for most of the time doing all changes via midi automation. Only on rare ocasions I touch the VI-pro interface to build a very specific patch once the template is ready to go. For the template building I switch on my second screen to the slave using a hardware monitor switch (so, all ethernet bandwidth is still there for VEpro). For me that works quite well. 

    If this would be a gigantic effort, I would say: no, not important enough! I would rather have the option to midi automate some of VI parameters, that are currently unavailable for midi learn (e.g. in the options menu). With TouchOSC I can build my own VI parameters GUI without ever having to change a screen or clicking a button. Only for parameters that are not midi-learnable I have to switch screen. Check it out! It's really great!


  • last edited
    last edited

    @MS said:

    I thought that FXT had a "local mode" which allows for precisely this.Otherwise, the Logic node-able plugins allow for this, as I wrote in the previous post.

     

    Martin, I haven't used FXT for years, but I don't ever remember getting the GUI on my host machine. Maybe I just never found that setting. [:$]

    DG


  • last edited
    last edited

    @MS said:

    The Audio Unit plugin standard was written with over-network hosting in mind
    Hi Martin, if AU Plugs were written to comply with modern network technology, how come then that its spec is limited to just 16 midi channels? Isn't this number so 1982sh?!? 😉 I'm asking because I really love VE-PRO, but I'm forced to work with dozen of open instances for my orchestral templates. And this way (I understand from technical posts) I'm loosing the horse power that my i7 could give me with just one instance full of multiple Kontakts... Hi. Arceo

  • last edited
    last edited

    @Arceo said:

    I'm loosing the horse power that my i7 could give me with just one instance full of multiple Kontakts...

    If you're using Logic you're better off with multiple instances (thanks to the one core overload issue).

    M


  • last edited
    last edited

    @mosso said:

    If you're using Logic you're better off with multiple instances (thanks to the one core overload issue).
    Nope! I use Digital Performer as a main DAW and an Intel i7 slave that runs all the instances. So no need for me to differentiate instances to split the load, on the contrary I'd better stick with just one instance to save cpu cycles and to have a more easy work-flow. As of today I'm forced to add reverbs and daelays (on separate bus) on each and every instance I need to open and, if I need to make a change at one parameter ,then I need to replicate it to any open instance. Having to deal with just one instance, for this matter only, would be a great time saver. Cheers. Arceo

  • last edited
    last edited

    @MS said:

    The Audio Unit plugin standard was written with over-network hosting in mind
    Hi Martin, if AU Plugs were written to comply with modern network technology, how come then that its spec is limited to just 16 midi channels? Isn't this number so 1982sh?!? 😉 I'm asking because I really love VE-PRO, but I'm forced to work with dozen of open instances for my orchestral templates. And this way (I understand from technical posts) I'm loosing the horse power that my i7 could give me with just one instance full of multiple Kontakts... Hi. Arceo 

    The reason is that Apple believes that multi-timbral instruments are a thing of the past. Until this changes, if indeed it does, the AU spec won't be altered.

    DG


  • last edited
    last edited

    @MS said:

    The Audio Unit plugin standard was written with over-network hosting in mind
    Hi Martin, if AU Plugs were written to comply with modern network technology, how come then that its spec is limited to just 16 midi channels? Isn't this number so 1982sh?!? 😉 I'm asking because I really love VE-PRO, but I'm forced to work with dozen of open instances for my orchestral templates. And this way (I understand from technical posts) I'm loosing the horse power that my i7 could give me with just one instance full of multiple Kontakts... Hi. Arceo 

    The reason is that Apple believes that multi-timbral instruments are a thing of the past. Until this changes, if indeed it does, the AU spec won't be altered.

    DG

    Ah...! And what do you think they believe to be the substitute of such an archaic piece of software as a multi-timbral plugin? 😉 Arceo