Audio Over Ethernet

An area for people to discuss Scope related problems, issues, etc.

Moderators: valis, garyb

Ripper
Posts: 230
Joined: Tue Jan 08, 2013 5:33 am

Re: Audio Over Ethernet

Post by Ripper »

djmicron wrote:
Ripper wrote:
djmicron wrote:when copperlan is set to auto startup, then it starts before scope, so it doesn't find the scope midi ports and you have to reload the virtual routing configuration each time.

A solution is to disable cpvnm from windows services, and run it after scope has been started.

It can be started also from its location such as "C:\Program Files\CopperLan\CPVNM\CPVNM.exe" or by entering command line and typing "net start cpvnm" .
Exactly what I do.
It's always a good thing to share information for the community, this is why i wrote it down, not for you, but for the others.

:wink:
mausmuso
Posts: 531
Joined: Wed Apr 25, 2001 4:00 pm

Re: Audio Over Ethernet

Post by mausmuso »

I have uninstalled Copperlan and gone back to hard wired connections.
This gave me back a number of physical Midi ports that had stopped working when Copperlan was presiding over the system.
- I have a 4 Port Midi Box that now works again.
- I use a EMU 1212 card (only for its Optical I/O on the second machine) and its Midi In port now works again
- Scope is still playing up somewhat (mainly with Samplitude) with occasional communication error messages, but it does recover itself, which is better than before (Close down everything and reload Scope and Sequencer).
I am currently keeping the Scope Midi setup really simple (one Sequencer Dest Module only) until I can figure out what is going on.
BTW it is the Midi Sequencer Dest Module that seems to get affected.
Hopefully Copperlan will fix the small bug related to physical ports soon and then I might retry the virtual Midi approach.
Post Reply