Forum

Hi Colin,

I'm pasting my reply from the Blue Room here:

Windows Vista with grandMA onPC 2.3.1.1, IP 192.168.1.43
Windows 7 with Capture Polar, IP 192.168.1.31

In grandMA onPC I went to 'Setup' and 'Network master', 'MA Network Control'. There I changed the 'Station IP' to 192.168.1.43 and restarted MA onPC. I went back in there and input a 'Session name' ("Lars") and clicked on 'Start/Join Session'.

In Capture, I opened the MA-Net settings, changed to "MA-Net2" and clicked on 'Start'. Capture connected and then listed all universes.

At this point, unsure of how to operate an MA, I patched a VL fixtures to channel 1, and then gave it 100%, which was reflected in Capture's universe view.

Hi Lars,

I too will add my reply to the Blue Room. I have finally got this working. Your advice did lead me to solving this so thankyou very much.

Your example was for MA2 onPC and not MA onPC. However, the principals of networking are very similar and it showed me that the way I had been trying to configure MA onPC was correct. However, I could still not create a connection with Capture.

Next I wondered if a connection issue existed with MA onPC (not MA2) and so I downloaded the MA2 onPC software. This too would not connect to Capture on my Windows 7 setup!

I have discovered the problem lies with the presence of the Wholehog 3 Visualisation Connectivity application which I have installed on the Capture machine.

In my original post I said "When leaving Capture to detect the IP address "automatically" I cannot get it to work. So I tried to tell it to use the specific IP address of my LAN. Capture said for the change to take place I need to restart. When I close Capture it will not reopen unless I reboot the machine - the change does not hold."

I discovered that firstly it IS necessary to tell Capture to use the IP of the XP machine, as the sight of various other networks (Bluetooth, WiFi etc) were blocking automatic connection. Secondly, when closing down Capture, the Hog 3 VC app does not close with it, and this was blocking Capture from restarting unless I rebooted the machine. After the reboot, the IP changes were not held as the software "restart" had never taken place. Wondering if the Hog 3 VC app was the issue, I uninstalled it and tried to make this network setting change again and Capture restarted as it should and I was immediately able to connect with both MA and MA2 onPC.

To summarise, the single reason for the problem was that the network changes in Capture could not be made because the Hog 3 VC did not close along with Capture. Had I just closed it from the Task Manager, Capture would have restarted fine and I would not have had so much trouble.

I can confirm that now the network change for MA Net in Capture has been set, having Hog 3 VC running presents no connectivity issues at all with Capture and MA onPC. It has been reinstalled!! :-)

I wonder if in the next release of Capture you could make it possible for Capture to automatically close the Hog 3 VC app when Capture itself closes???

Sorry for the long post, but I hope this information is helpful to yourself and also other users.

Now I can learn MA! :-( (Can you tell i'm a Hog boy?)

Thankyou for your help.

Cheers

Colin

Hi Colin,

I'm relieved to hear that you have gotton around the problem!

Capture does attempt to close the Hog 3 connectivity app, but unfortunately it sometimes misbehaves and prevents Capture from closing. As Capture saves the settings as it closes, it also means that you network settings were never saved! I'm taking a not of this and we'll change Capture so that the settings are always saved immediately.

Being kinda new her; but where are the MA2-settings in Capture?

Hello Kurtos,

Please navigate to our Universes Tab in the Project Window, and right click inside the external universes. In the pop up window you can then select MA-Net and join the session.
In case you need to set a specific IP address for the MA-Net you can do that from Tools>Options>Connectivity.

I must be overlooking something, as I can't find any reference to MA-Net in the connectivity options window. I'm using version 2.10.18 under OSX. Screenshot: http://imgur.com/f6N1e27 Thanks!

Never mind, the manual tells me that it's not supported under OSX.