by CopperPhil » 15 Nov 2015, 11:41
Hi,
I can explain what is occurring, but not why...
You know that the VNM is the CopperLan engine, managing routing and network background tasks. Historically, a CopperLan application searches for a VNM located on the same (or on an attached) hardware machine at startup.
In order to ease integration of mobile CopperLan apps (iOS, Android) with hardware devices (only Archwave and Cymatic Audio products at the moment), we made a change in the version 1.4. Now, any CopperLan application tries first to get connected to a local VNM (same machine), and if it does not succeed, then the app searches for alternate VNMs located on the network and select the most efficient one (scoring based on CPU, memory, speed, ...). For example, thanks to this new method, an iOS or Android version of Cymatic uRemote app is able to control a uTrack24, a uTrack-X32, or any Archwave AES-67 board without need of any computer on the network (a computer was necessary before version 1.4 to host mobile CopperLan apps relying on an external VNM).
So in your case, due to some unknown reason, the CPManager running on your Windows 7 pc is not able to get connected to the cpvnm.exe service located on the same machine. Then it falls back on another VNM located on the other PC.
My question: do you see the VMIDI ports related to your Windows 7 computer on the network? These ports are managed by the Win7 computer's VNM, so not seeing them is an indication that the Win7 VNM is frozen or stopped. If the Win7 VNM is stopped, just try to restart it and check then if it is still stopped or running. It can be stopped again in case of exception, in this case please check the windows event logs and tell me if you find any log related to a VNM crash.
Please not that you have to quit and restart the CPManager to make it trying again to get attached to the local VNM.
If the VNM is frozen (running, but process load at 0%), just try to restart it.
If it is still frozen, please disconnect any MIDI device attached to the Win7 computer. Then if the VNM is working fine, attach MIDI devices one by one, restarting the VNM at each step until it gets frozen => you know which MIDI device causes the problem => report it here.
Sorry for this pretty difficult workflow but I have no better solution on hand at the moment...