Does anyone know, how I can solve this:

My current set up.

DP on one mac, generates all midi through MidiOverLan CP3.

ProTools 11.3.2 on second mac running VePro 6 server AAX plugins.

Audio feeds directly into ProTools. No network or ethernet transfers. All Internal on the Pro Tools mac.

MIDI is triggered via external midi in VePro via external midi.

Is there any way to split midi and audio for an instance of a VePro Plug in.

MidiOverLan has been out of business, and the software is hanging on even in Catalina. I was able to get it work for a while, but then changed a the drive to a different mac, and then it stopped working. In 10.14.6 MidiOverLan still works.

Current system, NO audio glitches.

Currently I have something like 400 midi tracks in DP, 48 tracks of similtaneous record in ProTools while running 8 instances of VePro with about 36x16 patches, 30 instances of the Lexicon PCM. All with no issues.

Trying to run everything through DP, using VePro in DP and feeding DP all audio and midi from VePro, chokes the system with a twelve core Mac Pro. Splitting between the two computers is more efficient IF I can get midi from the DP computer to the ProTools computer.

And no, CopperLan, RPTMidi, and ipMidi do not work. They don't have enough midi ports (I currently use 41) and they are tapping off of Apple's midi system which is a high level driver and starts choking after about 8 ports. MidiOverLan uses a kext which made it work so well they came out with a 128 port version right before going out dropping development of it.

Any thoughts appreciated.

Thanks

Anyone? Inquiring minds want to know.

Does VePro benifit from the faster 10Gbit ethernet networking speeds and if no, are there any plans to tap into that?

Not me, but know people buying new macs and want to know if it's worth the extra 100 dollars for the faster network option.

"I currently run about 40 midi ports (16 channels each) with MidiOverLan, and use External Midi to trigger my instruments in VePro running as AAX plugins in Pro Tools. As MidiOverLan is no longer sold by MusicLab, and Copper Midi doesn't have enough instruments, (and was too slow) a replacement is needed."

Yes I am running it as server. I need a replacement for MidiOverLan. I thought AU3 was that.

Hi

I'm not running VePro in DP or the MAS version of it. VePro is on a different computer, giong straight into protools, and I need to trigger midi only from the DP computer. The audio From VePro is going into protools on the different computer.

Essentially I need the midi and audio of VePro split, and I thought the AU3 program was something new that did that.

Midi IP, copper midi, and other external midi programs all use Apple's midi code and are either too slow and unreliable, or don't provide enough midi channels for many people. MOL CP used a kext to give it the speeds it had.

I understand Vienna's viewpoint, but there are many people that need the external midi function to transmit midi between two machines, and it would be cool if Vienna had a program that did that.

I have DP on one computer, and Pro Tools on another mix computer, with VePro running in tadem on the mix computer. The audio from VePro feeds into Pro Tools, and I trigger the midi going out of the DP computer using MidiOverLan, going into the external midi of VePro on the mix computer.

Does the AU 3 Beta work with other platforms like DP, and will it do what I would like it to do. I am guessing, no.

Thanks

Alan

Forgive my lack of knowledge, but I just saw the features of vePro 7 and it talks about the AU3 beta included.

What is this? And what does it do?

And more importantly, to me, is it a replacement for MidiOverLan?

I currently run about 40 midi ports (16 channels each) with MidiOverLan, and use External Midi to trigger my instruments in VePro running as AAX plugins in Pro Tools. As MidiOverLan is no longer sold by MusicLab, and Copper Midi doesn't have enough instruments, (and was too slow) a replacement is needed.

Please explain, as I can't seem to find any thing that explains exactly what it does.

Thanks

Also, if I am not mistaken, the Is the AU, VST and the MAS version of the plug in. While you are limited to only one set of 16 midi channels, in the AU version, it does work yes? Could be a work around.

Lol. I was addressing the guy and others that upgraded from a previously working OS and versions of DP and VePro. Where is your previous computer? Same principle applies. You use the old hardware system until you’re sure the new one has all the bugs worked out. Now if this is your first system ever, well then, what can I say, you’re screwed. And until this bug is worked out, you have a very shiny mac paper weight. Sorry.

My post is meant as advice, not an admonishment. I started with DP using a Mac plus, so I do have some experience in these matters. And I have three studios that I work out of, so I am very much sensitive to any upgrade issues. Changing one thing in one means I have to change in the other two. Bottom line, if it ain’t broke, don’t fix it. The only time I upgrade is when a sound library requires it.

For those of you that feel frozen by this, let me offer some advice: first just because a software update is offered doesn’t mean you need to use it. If the version you are using works, leave it alone. Usually updates are offered for various bug fixes. If you don’t have that issue, don’t upgrade.

Concerning updating to high seirra, someone mentioned that sooner or later he’ll HAVE to update. We actually, the only reason to update is for safari compatibility, and security issues related to that app. Otherwise, think of this like a hardware synth. The version you buy is the version you get.

The other thing is if you are doing this professionally, then you need to have one or two other cloned drives a available in case your drive fails. If you do an update of anything, especially the OS, do it on your cloned drive. That way you don’t lock yourself out from work. Then when bugs like this get fixed, you can test it and then convert to the new OS.

On that note, I use DP 9.0.1 still, as the later versions don’t allow for generating plug ins in real time, and pregen hasnever worked for me. On my protools computer I was using systen 10.9 until recent. Why? Because it worked. It was only becuase of some library that I decided to update. So yeah. Eventually you will have to update. But that day is a long way away.

I have dealt with this as well. 9.5.1 is supposed to be the fix for the MAS plug in in High Sierra, but it ain't.

I deleted the MAS pref "Audio Unit Info Cache 64-bit" from the User-Library-Preferences-com.motu.MotuAudioSystem folder

And

"MOTU Audio System Prefs" from the User-Library-Preferences-com.motu.DigitalPerformer folder

 

This forced DP to reexamine all the AU units as well as the MAS plugins, and the VePro MAS worked.

 

But then I closed and reopened the file and it reported the plugin missing. It still showed the plugin in the add instrument menu, but then reported a MAS error when opening.

 

SO

 

It ain't fixed.

Hi, that would work. Is there any equivalent Audio unit plugin for Mac OSX?

I have a question concerning panning I can't figure out.

I want to hear only the left side of a stereo channel, and pan it to the center. I can't see to be able to do that. Is it possible with the VE Pro 4?

Again to be clear, I only want to hear one side of a stereo signal, but want that one side panned center, so I'm hearing only the left side and none of the right

Thanks

Alan

Trying to get VEPro going with Windows XP x64 computer. Asus P5k-VM intel q6600. eLicenser doesn't see my vienna key, (which I know is good, since I pulled it from another windows xp 32 bit machine to test this computer) and as a result vienna gives me the error message about no key. I can't find anything on the elicenser site.... Any thoughts?

Alan

Update...

Never mind.... thought the stupid new iLok was the vienna key.... I hate this crap!

Hi

My setup is currently configured like a pro-tools system, except I'm using MOTU hardware and cuemix software. I have a Mac sequencing computer with DP running my PCs through Midioverlan, and audio from various audio interfaces (echo audio boxes mostly) routed into my mix computer with the MOTU hardware and using Cuemix as the mixing software.

I was pleasantly surprised to discover that I could use VEP in stand alone mode as mixing software for the MOTU hardware. Everything works great!

What I would like to do is be able to incorporate Network audio from into my mixing setup. In other words, run VEP on another PC to run kontakt or some other VST plugin, use the VEP server software to connect it to the VEP server software on the mix computer running VEP in standalone mode, and have the VEP in standalone mode on the mix computer see the network audio connects as well.

As far as I can tell, the only way to do this is when VEP is running as a plug in, not as standalone. I can get VEP to send audio via the server software as a plug in, but that doesn't help me in this situation. I need VEP to run in standalone mode, having the VEP server application run as well, and have the standalone see both the physical inputs from the audio hardware, and the network inputs from the VEP server application, and be able to mix them all at the same time. From what I can tell now, the program either sees one or the other.

Perhaps there is a way to do this that I don't know yet.

Thanks

Alan

Yet another update...

I found the VE Pro PC server program, in the start menu... not the most obvious place.... but was able to get the mac to see the PC as a slave...

Overall... very cool...

Alan

Another Update


I also have been able to get the VE Pro to network between the mac and PC.... however I can only get the mac as a slave and the PC as a master, not the reverse, which is what I would like. In the manual it says to start the VE Pro server software on both computers first, but I don't see where I can do that on the PC side. If I start the standalone on the PC, I don't see any button or menu option to do that. Is there a separate installer I missed, or is there a menu item I'm not seeing in the software?


If I start a host application, the VE Pro vst server window comes up and works correctly, but as I said, I'm trying to get the Mac to be the master....


Thanks in advance


Alan

Update

I got the program to not crash. When I uninstalled the previous version, the uninstall program doesn't remove the vsl preferences from the Library preference folder or the user library preference folder. I uninstalled the program, removed all the preferences, reinstalled version 4.1.7553 and it stopped crashing....

Thanks DG

That link you provided was helpful. I've done everything you've said. Downloaded the latest version 4.1.7553.

The Mac versions, both 32 and 64 bit start, then quit after 2 seconds. Every time. The server app doesn't quit, but still doesn't see the PC.

Tried previous version 4.1.6853, and that quits too after 2 seconds.

Went back to the version on the disk 4.1.5436 and that is stable again, but still doesn't see the PC.

Again, pinging the pc from the mac or pinging the mac from the pc works. They both see each other. It's just VEP that doesn't see each other

Not feeling hopeful...

Yes... did all of that: no firewall (turned off on both PC and Mac) fixed Ip addresses. Did not install the vienna epic library, but loaded up a Kontakt library when testing...

Install was from the Disk, including the elicenser. Does the included software have known issues?

Also, pinged from the mac to the pc, that works, and pinged from the pc to the mac, that works.

Also, in my final set up, more than one ethernet port MUST be enabled. For now, only one is enabled. Is this going to be a problem? lol

It's not a problem with MOLv3.

If it is a problem, it's going back to the dealer.....

I have tried various things to get this to work. I have looked up posts both here and other places on the internet.


What I want to do is route one of my samplers (which has something like 12 eastwest, zero g libraries, etc) back into my mix computer (mac with 4 motu interfaces) I set up a test mix computer, dual core running 10.6.4 and installed VEP. Set up a test pc running win xp pro (32 bit) P4P800-VM 3.2 gig P4 cpu and 2 gigs of ram, and installed VEP. Both work with standalone fine. Trying to get them to communicate with each other however, is not working


I have:


Tried letting the computers set their own IP addresses.


Tried different IP address, including pairing them, for example 192.168.1.120 and 192.168.1.121, or completely different addresses as in the manual (useless by the way for this part of the software. Anyone releasing software that uses an ethernet connection needs to give extensive and detailed instructions as to IP address, settings, etc.)


Tried connecting the two computers directly with a crossover cable, and with a regular cable. Tried with a gigabit switch.


Tried different cables, all CAT 6


Tried changing the settings as suggested by another post here by Chris White.


Unplugged and plugged in the gigabit switch (which I used with Midioverlan for a couple of years and have been using since then, no problem.


Tried uninstalling midioverlan on the pc thinking perhaps it was screwing up VEP


Tried starting the slave first then the master, or the master and then the slave, or the gigabit switch, then the master then the slave, or the slave then the master then the switch, or the switch, the master and the slave, or the master, the slave and the three legged rooster.


Tried installing a third party pci gigabit ethernet card in both computers.


Nothing Worked. I've used up 3 hours of the demo time.


Simply put, the program needs to be more robust when it comes to this aspect of it. The audio over lan is THE sole reason why I purchased the program. I have other VST shells that work well, but.... in this particular case, the functionality of being able to route the audio to the mix computer in separate channels would help me when printing stems for delivery.


Of course, I have not registered the keys yet. Now, if you tell me the audio over lan doesn't function until I register, I'm going to be pissed. (right now I'm just uncomfortably unnerved)


Having said all that, the program does look great, and I know people have gotten the audio over lan to work..... I just haven't..... lol


email or post...


Thanks in advance.


Alan