Options
Related

Load to all servers via CMA

It would save LOADS of time we could have the ability to load custom content files and folders to ALL units on the network instead of one at a time via CMA. Also we need the ability to autoset the DMX for the files and folders in this manner as well.

I have had mixed results with Cloning content.:( If there is a lot of custom content used this becomes impractical when adding just a few files or folders because the system wants to overwrite all the existing custom content while cloning This can take quite a long time with many fixtures on the network combined with a large ammount of custom content.:aiwebs_007:
Parents
  • 0
    Marty, can you elaborate a bit? The intent with cloning content was to copy all content from fixture A to fixture B. Files on fixture B which are named the same as files on fixture A will not be copied from fixture A to fixture B. The idea is that you can deploy some content to fixture A then clone content from fixture A to fixture B. Now fixture B should have the same content as fixture A. If you then add more content to fixture A then clone content from fixture A to fixture B only the files you added to fixture A will be cloned to fixture B. This is only true if you are adding content to fixture A if you move content around or rename it on fixture A it will be deleted from fixture B and copied to fixture B again. It sounds like you may have found a bug where content is unecessarily getting deleted from fixture B? I understand your frustration the cloning feature is far from fast.

    Cormac, can you elaborate a bit on your network setup as well? Are you using a router, or a switch, or a crossover cable? Do you have a DHCP server in your network or are you using Auto-IP? What is the network setup like on your laptop? Does it have wireless and a wired connection? Which version CMA/Axon are you using? Hopefully 1.3.1.1208 for both the stand alone CMA and the Axon. The CMA discovers fixtures not the other way around. In order for the CMA to discover fixtures the CMA must be on the same IP network as the fixtures. A good test is if you can ping the Axon from your laptop the CMA should be able to discover the Axon.
Reply
  • 0
    Marty, can you elaborate a bit? The intent with cloning content was to copy all content from fixture A to fixture B. Files on fixture B which are named the same as files on fixture A will not be copied from fixture A to fixture B. The idea is that you can deploy some content to fixture A then clone content from fixture A to fixture B. Now fixture B should have the same content as fixture A. If you then add more content to fixture A then clone content from fixture A to fixture B only the files you added to fixture A will be cloned to fixture B. This is only true if you are adding content to fixture A if you move content around or rename it on fixture A it will be deleted from fixture B and copied to fixture B again. It sounds like you may have found a bug where content is unecessarily getting deleted from fixture B? I understand your frustration the cloning feature is far from fast.

    Cormac, can you elaborate a bit on your network setup as well? Are you using a router, or a switch, or a crossover cable? Do you have a DHCP server in your network or are you using Auto-IP? What is the network setup like on your laptop? Does it have wireless and a wired connection? Which version CMA/Axon are you using? Hopefully 1.3.1.1208 for both the stand alone CMA and the Axon. The CMA discovers fixtures not the other way around. In order for the CMA to discover fixtures the CMA must be on the same IP network as the fixtures. A good test is if you can ping the Axon from your laptop the CMA should be able to discover the Axon.
Children
No Data

www.etcconnect.com