Jump to content

Firewood1

Regular Members
  • Posts

    52
  • Joined

  • Last visited

Previous Fields

  • Member Status
    Working in the industry
  • Current Employment or place of study
    Freelance Lighting Designer and Production Electrician
  • Professional organisation membership
    ALD (Professional Designer)
  • Full Name
    Colin Wood

Contact Methods

  • Website URL
    http://ald.org.uk/ColinWood/bio.php
  • ICQ
    0

Profile Information

  • Location
    Birmingham, UK

Firewood1's Achievements

Full-timer

Full-timer (6/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

  1. Hi Lars, 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, and to everyone who also contributed to this thread. Cheers Colin
  2. My word, I disappear for a couple of days to try and work on this problem and come back to find my topic well and truly trashed!! ;-) Back to the subject of connecting MA onPC to Capture, I have just posted the below message on the Capture forum. Hopefully Lars will post his reply in both places so that if anyone else has this issue it will help them. Hi Lars, Thankyou for you advice on the Blue Room forum. However, 2 days later and after a lot of messing about with my system, I have yet to make a connection. Here's where I am now. My Macbook is running Capture in Windows 7 Ultimate using Bootcamp. My PC is running MA onPC in Windows XP Professional. I have managed to get Hog 3 to connect with this setup, which gives me hope. 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. On the MA onPC side of things, I am not totally certain what I need to be doing to create the connection. I have found the MA Network Configuration and set this to the IP address of the LAN. I must stress my network does work and I can ping the Mac. I am then unsure what I need to do. I tried starting a session, which I figured would be the way to go. Back to the Macbook and Capture. Ignoring the fact the network setting wont change from automatic, when I try and start the MA NET, I click start and it "thinks" for a few seconds but then does nothing. Basically I'm totally lost with this and getting very frustrated about the time I am losing. Please help! I will also post this on Blue Room so Joe can see. Cheers Colin Any help with the above issue - particularly from the MA side wuld be gratefully received. I am sure Lars will deal with the Capture side. Colin
  3. Thanks Lars and Joe, I have to confess I didn't look at the manual because in the past with the likes of Hog 3 and Magic Q it has always been so simple, so I figured the universes would just pop into view with MA in the same way. When they did not, I thought I'd turn to the forum here rather than bother you guys once again for something that was probably a quick fix! As is also the case with Hog 3 (it was me who posted on the Capture forum about this the other day)it is a great shame that this does not work with the Mac version of Capture (I fully appreciate this is a Hog 3 issue and not under your control). I was running my Mac version....hence my trouble! I hope very much that by using Windows XP running in Bootcamp on my Mac that this will once again open the door to me using Capture with a decent console OS! I will report back if this does not clear things up but in the meantime, thankyou very much for your help. I hate to admit it but life was a little simpler before I changed one of my systems to a Mac...I hope MA support for Capture on Mac will be in the pipeline!! Cheers guys Colin
  4. Hi Joe, Can you confirm that Capture will connect with MA onPC, rather than simply (albeit expensively!) connecting to an actual console? Can this be done with a network switch and a couple of lengths of Cat5? ie - without any nodes? If you have done this, are you able to go into any more detail? What part of the MA onPC setup needs configuring as there are many output possibilities. Do I even need to configure DMX outputs, or should simply creating a network be enough for Capture to see the MA universes? Cheers Colin
  5. Capture say it is possible, but also say follow the instructions in the manual....of which there are none!
  6. Problems once again connecting software! It seems only Hog and Magic Q can do this easily!! I'm trying to connect MA onPC (MA1) which is running on Windows XP, to Capture Polar which is running on a Mac. I have tested my network and the two computers can "talk." I am not familiar with Grand MA, and the purpose of connecting to Capture is so I can learn the console prior to a forthcoming job. The manual references only to connecting to WYSIWYG. Currently I have configured the network within MA onPC and attempted to output DMX via ethernet using Artnet, but I'm really not sure if this the correct way to interact with Capture as I doubt MA onPC is enabled to output DMX. Any assistance from those in the know would be gratefully received. With Magic Q and Hog the universes just pop up as soon as you set the IP address....why is it not that simple?!! Cheers
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.