200,852 users have contributed to 43,214 threads and 259,138 posts.
In the past 24 hours, we have 2 new thread(s), 6 new post(s) and 60 new user(s).
Sorry, I've totally lost what you're asking now.
AFAIK:
Am I missing something?
BTW what sample player are you using with VEP?
DG
you should be able to achieve a very excellent result using VE Pro on a slave using the server, instead of MOL at all. I doubt MOL gets midi over the network better, or VE Pro would not be very viable in the marketplace.@composermark said:
Should I have been able to achieve as good a result using VEP Server?
I don't get what you're after with all these workarounds behind the premise 'VEP doesn't work', 'audio over LAN doesn't work'. I assure you it works very well with lower latency than I've ever had with virtual instruments.
Yes - well I have gigabit Lan connection between two computers. I'm not using a switch at the moment - I've bridged two connections on one computer, allowing connection to a router. But the computers are directly linked by ethernet cable. I've also tried it as a simple crossover cable arrangement.
For a time, I thought I had cracked the situation. One of my cards wasn't actually running at 1000 mbps. But once I forced it to, I got a very usable result.
Today though, it was back to an unusable latency. That is I'm talking about playing a note, and the sound coming late. It's not as bad as it was when I first opened this thread (because I was obviously at 100 mbps then) - but it isn't good enough. Not a patch on the results I'm used to getting from simple Midi Over Lan - but using an audio interface in each slave computer.
This was my big issue with FX Teleport. I spent all the money on a gigabit switch and gigabit NICs and MOBOs with built in gigabit LAN but found the thing unreliable.
I'm seeing the same unreliability here. And what are we supposed to do, bounce around for days on a forum, debating whether it is this setting or that hardware that is the problem? Spend money on something else - does it fix it - maybe / maybe not.
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.
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
Dave
Yes 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.
