VEPro 5 acts just like VEPro 4 in terms of dividing the application between server and standalone use.
-
Hi all, new to the forums. I have a question, which may or may not have been asked before. Will VE Pro 5 allow for connectivity of both the 32 bit and 64 bit servers through one instance? Essentially allowing you to use both 32 bit and 64 bit plugs in one instance of ensemble pro?
-
Same here, I have had VE Pro for only 2-3 months, and in that short time I can't imagine how I got along without it. Now it seems its going to address the few details that stopped it short of being the perfect solution, which for me was being able to automate plug-ins hosted in VE. However if they somehow manage to really bridge the gap between 32 bit and 64 bit, that would be phenomenal. Imagine using 32-bit plugs side-by-side 64-bit on one instance...like loading a 32 bit waves plug in the fx rack of a 64 bit kontakt for example. Not sure if this is even technically achievable though, but .
-
@Edward_Martin-Goodman said:
Hi all, new to the forums. I have a question, which may or may not have been asked before. Will VE Pro 5 allow for connectivity of both the 32 bit and 64 bit servers through one instance? Essentially allowing you to use both 32 bit and 64 bit plugs in one instance of ensemble pro?Hi and welcome [:D]
VEPro 5 will behave like VEPro 4 regarding separating of 32- and 64-bit servers. Bitbridge type of solutions come connected with certain problems that degrade performance, so we have decided to stick to our guns here.
-
@V_ad_im said:
It means, that now it's possible to connect vepro standalone to sequencer directly, as vst3 instrument, without iac-driver(OSX)?This is not possible. Server and standalone applications are separate because of synchronization issues. If you are using standalone, the only way to get MIDI into it, is by using a system MIDI driver.
-
I use Logic as my host and mainly run PC Servers. I'm guessing in VEP 5 the new FX version will be similar to the instrument version of the plugin but will be instantiated as an effect instead of an instrument on the host DAW. If that is the case, will the new FX rack version have a sidechain input so we can route the mac audio to the sidechain of PC FX's? Also will there be an AU midi controlled effect version so we be able to run PC based midi controlled FX's like vocoders on our Macs?
-
understandable. But, I so hoped for integration of the standalone app in the plugin in a way to have ONE session across all, marked as standalone session, with the server then starting the standalone app and sending the vepro project data from the daw, and vice versa. I use two pcs with a 52ch soundcard and am searching for a solution to have ONE project in my main DAW, setting up the slave machine with its hardware as well, instead of launching apps on each pc and loading two different projects into these, for one "logical" project... bummer.
-
The VEP5 audio plugin is instantiated in any channel, and connects to an instrument plugin. The instrument plugin is then responsible for sending and receiving the audio data to/from the slave.
The audio plugin does not offer MIDI input. VEPro for now also does not offer sidechain for fx hosting.
-
@TabSel said:
understandable. But, I so hoped for integration of the standalone app in the plugin in a way to have ONE session across all, marked as standalone session, with the server then starting the standalone app and sending the vepro project data from the daw, and vice versa. I use two pcs with a 52ch soundcard and am searching for a solution to have ONE project in my main DAW, setting up the slave machine with its hardware as well, instead of launching apps on each pc and loading two different projects into these, for one "logical" project... bummer.If you want to use a standalone version with audio hardware output, you are forced to keep your communication in MIDI, saving and restoring VIFrame/Metaframe files.
-
>>If you want to use a standalone version with audio hardware output, you are forced to keep your communication in MIDI, saving and restoring VIFrame/Metaframe files< i understood, already, but i had hoped that the standalone app launching/killing and viframe/metaframe loading/saving would have become manageable by the client/server plugin. may i ask other questions? 1) regarding automation how am i supposed to choose the automation parameter for a plug running in vepro server from the plugin within the daw? is there a "dropdown" list/tree? does the plugin pass all automation parameters of the servers plugins to the daw? i ask because i think there is a limit on the number of automation parameters... 2) what about a specialized integrated client/server vnc solution, to have the plugin guis of plugs running on the slave available on the server (via vnc for example) with mouse/keyboard actions sent to slave again... well, a way to have one desktop workspace but multiple cpus calculating... will there be ve pro 5 demo? will it run, when i demoed v4 already with the demo time expired... i="" understood,="" already,="" but="" i="" had="" hoped="" that="" the="" standalone="" app="" launching/killing="" and="" viframe/metaframe="" loading/saving="" would="" have="" become="" manageable="" by="" the="" client/server="" plugin.="" may="" i="" ask="" other="" questions?="" 1)="" regarding="" automation="" how="" am="" i="" supposed="" to="" choose="" the="" automation="" parameter="" for="" a="" plug="" running="" in="" vepro="" server="" from="" the="" plugin="" within="" the="" daw?="" is="" there="" a="" "dropdown"="" list/tree?="" does="" the="" plugin="" pass="" all="" automation="" parameters="" of="" the="" servers="" plugins="" to="" the="" daw?="" i="" ask="" because="" i="" think="" there="" is="" a="" limit="" on="" the="" number="" of="" automation="" parameters...="" 2)="" what="" about="" a="" specialized="" integrated="" client/server="" vnc="" solution,="" to="" have="" the="" plugin="" guis="" of="" plugs="" running="" on="" the="" slave="" available="" on="" the="" server="" (via="" vnc="" for="" example)="" with="" mouse/keyboard="" actions="" sent="" to="" slave="" again...="" well,="" a="" way="" to="" have="" one="" desktop="" workspace="" but="" multiple="" cpus="" calculating...="" will="" there="" be="" ve="" pro="" 5="" demo?="" will="" it="" run,="" when="" i="" demoed="" v4="" already="" with="" the="" demo="" time="" expired...="">
-
@V_ad_im said:
It means, that now it's possible to connect vepro standalone to sequencer directly, as vst3 instrument, without iac-driver(OSX)?This is not possible. Server and standalone applications are separate because of synchronization issues. If you are using standalone, the only way to get MIDI into it, is by using a system MIDI driver.
[url=http://www.servimg.com/image_preview.php?i=5&u=16988770][img]http://i48.servimg.com/u/f48/16/98/87/70/th/idea10.jpg[/img][/url] Hmm... What kind of synchronization issues? If it possible to send midi through network to VEPRO Server, it must be also possible to send midi through network to standalone, as I think... For UNIFORM, UNIFIED routing from host to any version of Vepro, standalone or server. Because it take many time, to change midi outs of 200-300 tracks from server to standalone and vise versa!
-
@V_ad_im said:
Hmm... What kind of synchronization issues? If it possible to send midi through network to VEPRO Server, it must be also possible to send midi through network to standalone, as I think... For UNIFORM, UNIFIED routing from host to any version of Vepro, standalone or server. Because it take many time, to change midi outs of 200-300 tracks from server to standalone and vise versa!As I wrote in an earlier post, it has to do with synchronization issues. In a standalone server, VEPro is synchronized to the soundcard clock. In server mode, it is synchronized to the master computer's sequencer. These live in separate worlds. If you want MIDI into your standalone VEPro over network, you have to use a netowork MIDI driver such as MidiOverLan or ipMidi.
-
I am understanding it. Let it be! But, may be it is possible to make "network recieve mode" in standalone Vepro, for recieving signals from vepro server interface without 3rd party midi drivers? May be, for this purpose need special, "midiout-only" version of server interface? For what all it needs: In standalone mode latency is more lower, than in server(especially, if connection through network). It need in one project (with many tracks) switch to standalone, for playing and record notes, and switch back to server, for mixing and bouncing. For now, using a network midi driver is not problem - all works fine. Problem is wearisome rerouting: it must to change track midiout from iac driver 5 (for example) to Vepro server instrument 7, from iac driver 8 to Vepro 12, and vise versa, for each track! But it may be by only one click for all track at once, big time economy..@MS said:
These live in separate worlds.
-
Martin, I understand it perfectly. BUT: wouldn't it be possible to at least "integrate" the standalone app launch/kill and MetaFrame load/save into the client/server infrrastructure in a way that you instantiate the plugin in a daw project, and in the plugin interface you'd be able to launch one standalone app on each slave pc and have the MetaFrame loaded into it from the DAW project or serialized from the standalone app to the DAW? In order to have the standalone apps launch state and their MetaFrames included in ONE host project, instead of managing multiple apps and their project files on multiple pcs for ONE logical project.
-
@V_ad_im said:
I am understanding it. Let it be! But, may be it is possible to make "network recieve mode" in standalone Vepro, for recieving signals from vepro server interface without 3rd party midi drivers? May be, for this purpose need special, "midiout-only" version of server interface? For what all it needs: In standalone mode latency is more lower, than in server(especially, if connection through network). It need in one project (with many tracks) switch to standalone, for playing and record notes, and switch back to server, for mixing and bouncing. For now, using a network midi driver is not problem - all works fine. Problem is wearisome rerouting: it must to change track midiout from iac driver 5 (for example) to Vepro server instrument 7, from iac driver 8 to Vepro 12, and vise versa, for each track! But it may be by only one click for all track at once, big time economy..From your post, I can clearly see that you don't understand it. Server and Master live in two different synchronization worlds. In server mode, VEPro only processes blocks sent from the master, at any point in time where master decides to send it blocks, which could be of varying size (especially in case of Logic).
