BTW what sample player are you using with VEP?I'm using Play 3.
-
-
I get latency with goodly sized projects in a full mixing scenario of around 10 milliseconds combined. For most things it's negligible. If I needed bigger projects than I do, and saw the need to add more latency, I would farm out to an additional slave and be pretty confident of the same level of performance with the latency I enjoy now. I know from working day in day out with VE Pro, that it works. I do not have problems with it. It is completely stable and I just make music with it. The software is reliable, all the time. NB: I'm just an end user, I have no vested interest.@composermark said:
I simply can't see how LAN technology (which requires every bit of information to be put into a packet, received, acknowledged etc.) no matter how theoretically fast it is, can be a substitute for sending a digital signal or analog for that matter over an audio or digital cable. The only conversion there is Digital to Analog - and if your sound card is good, you get very little latency.You have an idea that it doesn't work. I don't know why you get the unsatisfactory results you do specifically, you have complications I have no knowledge of [I've bridged two connections on one computer, allowing connection to a router/ crossover cable arrangement.'] but you seem to have made conclusions about how well it works or doesn't following your idea it must be problematic.
How does it work just connecting with a single cable? BTW, it must be a CAT6. It can't be a CAT5 and expect it to work right.
-
How does it work just connecting with a single cable? BTW, it must be a CAT6. It can't be a CAT5 and expect it to work right.
Well I managed to get a much better result now. There were a few other issues that were fouling up the works, like Cubase choosing the default ASIO driver - which of course has appalling latency.
I will definitely want to try CAT6 though. I don't think the cables I had lying around here in the UK are. I have CAT6 cables back in LA. Maybe this will sort out one remaining issue I've experienced, which is that changing the tempo in a project causes the instruments on the Slave to glitch (audio pop).
-
@ddk said:
I thought I was the only one who wants to use VE-pro in server mode
but run audio over ADAT.
I also thought I was the only one who can't deal with the latency of VEPRO over ethernet.
Please VE-PRO can we have this added to furture updates??
thanks
DaveYes that would be ideal I think. At least if VEP in server could offer that alternative. Then it would still respond to all the extra sync data you need with your project plus MIDI, but that your audio has its own separate channel.
One thing I'd like to be able to do though, is route the separate Mic positions in the Play libraries to different outputs in VEP. I can't find a way to do that yet. I can only change the overall output of the VST instance.
-
@ddk said:
I thought I was the only one who wants to use VE-pro in server mode
but run audio over ADAT.
I also thought I was the only one who can't deal with the latency of VEPRO over ethernet.
Please VE-PRO can we have this added to furture updates??
Not possible, for synchronization reasons. In server mode, the host software (Cubase,Logic etc) is the sync source - it sends VEPro a chunk of data, which VEPro processes and sends back. VEPro is then not caring about timing. In standalone mode, the sound card is the sync source - it continually asks for blocks of processed data in realtime. Combining the two is not possible, without additional buffering and latency.
So, if you want to use your soundcard outs - use VePro standalone and MoL or ipMIDI. If you want to run midi/audio over network - use VEPro Server.
-
@composermark said:
One thing I'd like to be able to do though, is route the separate Mic positions in the Play libraries to different outputs in VEP. I can't find a way to do that yet. I can only change the overall output of the VST instance.VePro supports auxiliary outputs from VST/AU instruments. If your instrument (Play) offers the feature to send different mic pairs to different outputs, you can create tracks in VePro to handle them. This is explained in the VEPro manual.
-
@MS said:
VePro supports auxiliary outputs from VST/AU instruments. If your instrument (Play) offers the feature to send different mic pairs to different outputs, you can create tracks in VePro to handle them. This is explained in the VEPro manual.
I think I found this now - on page 23. You have to create Input channels within the VEP mixer - and then you can see the different outputs of the VSTi as possible Inputs for that channel.
-
Indeed I'm sure you are right. However the fact remains I'm still on this forum trying to solve and track down mystery pops in slave VSTis when I change tempo too quickly in my sequencer - a problem I never had with hardware audio.
Is it the VSTi? Is it the sequencer? Is it VEPro? Is it the quality of onboard Gigabit Lan interfaces of ones motherboard? Or how the motherboard handles the data stream? Is it the network cables?
Maybe it's the janitor?
My point being that Pro Audio card does what it says on the tin. It may have its limitations and you can always get driver issues with your choice of OS and software, but the Pro card manufacturers tend to work hard at ironing those things out. I've never really had an audio card problem with multiple different manufacturers over many years.
-
I understand that this is not possible, for synchronisation issues... however, would the following be possible: I want to work on a [cubase|sonar|...] project on the master pc. I instantiate the VEPro plugin. In the VEPro gui, I tell a server to launch the VEPro standalone on the pc the server is running. On saving the project, the Server requests the VEPro standalone state, sends it to the client/Plugin, which sends it to the host, so that the Standalone VEPro state on the slave gets saved with the host project on the master. (It would be like saving the standalone VEPro project to a file and sending this file to the client) On opening the master project, the Plugin requests the server to launch VEPro standalone and sends it the saved VEPro standalone state. (It's like sending the VEPro standalone project file over to the slave and launching the Standalone VEPro with this project file) It is just necessary to have the Standalone VEPro launched on the slave and have it loaded a VEPro project file automatically whenever a DAW project on the master is opened that relies on the VEPro standalone on the slave. No need for transfering audio over LAN to a standalone VEPro. Audio will be transfered with two synced audio cards.
-
oh bummer... I once checked the demo as I already use two PCs, both equipped and linked with a RME HDSP Digiface by 24 x ADAT. It was the first thing I encountered: No Audio Hardware with the VEPro client. No standalone instantiation with a DAW project. I always have to manually load a "slave project" on the slave PC, on my slave DAW app, when I load a master project on my master PC within my master DAW app, with the slave project corresponding individually to a master project... quite a hassle... bummer However, are there any details available how automation in VEPro 5 is presented to the user? Are automation parameters of plugins instantiated in a VEPro client available via automation parameters of the VEPro plugin? Any details how automation is presented to the user? (I come to think about the limitation of the number of automation paramaters per plugin ~ 1000) I think about opening a plugin GUI via the VEPro plugin on the master, without audio processing, but sending automation data of that plugin via the VEPro plugin to the plugin instance on the slave. (So you see the plugin GUI on the master, but have audio processed on the slave) like Cockos ReaMote does? I already have the demo license for VEPro 4 on my USB key used. Will there be a new demo license for VEPro 5? Thanks!