Improvements with the fixture schedule. Also some issues with the archive...

Joe BleasdaleJoe Bleasdale Registered User
I think the ability to see the DMX protocol or at least the channel amount of a fixture in the fixture schedule window would be good.

My reasoning about this...I have been working with Light Converse recently (LC). I had a show patched up on H3PC. Now fixtures in LC didn’t match with fixtures in Hog for example. I was using an iPC in Hog 3 mode at Lite Alternative, UK. They where nice enough to let me come in for a day to play around with it all. I basically wasted the day. LC wouldn’t communicate well with the visualiser driver. The driver was on 3.04. iPC was on 3.0.0. I was assuming that was the issue. So I went to download version 3.0.0 of the driver from the archive... Not there. So I settled for 3.0.1. When I installed it, it told me it was 2.25. in the bottom right corner of the DP. I thought I had downloaded the wrong file by accident... so downloaded again. Same result. The file was labelled up as 3.0.1 (2425)... but that wasn’t the version displayed in the Wholehog DP.

So I took the driver out of the equation. We used DMX over Art-Net and threw that into LC. It worked partly. It kept dropping out and strange happenings with the DMX signal. Some info was getting through as the fixtures would move when I moved the trackball. Now the problem was that the fixtures in LC didn’t match the ones in Hog. I gave up patching and re-patching type by type to see which ones matched. Sometimes it was fairly obvious that they didn’t match. For example 200 channels used in universe 1 of Hog, but 230 using in LC.

If there was the ability to see how many channels a fixture had just by looking at the schedule, rather than re-patching. I would have been a lot better off. The visualiser driver may have been the cause of all these issues, but I think there where problems both sides.

I have also suggested to LC developers to put in a "user mode" on the start up of the software. The way this would work:

1) you select which console you use, E.G. Hog.
2) software loads as normal.
3) when it has started in DMX only mode, it will have an identical library to that which is in Hog.

That way the naming, selection etc is the same.

This is all constructive criticism. I am happy with the Hog consoles and will continue to use them. But the issues I was having with both LC and Hog is being expressed to the appropriate parties to make sure this doesn’t happen again.

I hope this all makes sense. Please do feel free to ask questions if I have been vague or I am not making sense!


  • z6p6tist6z6p6tist6 Registered User
    edited May 2009
    I would second the request for channel counts in the fixture selection dialog box. This would also be especially helpful when trying to figure out what fixture mode HES/FPS used when making the profile.

    This could be as little as putting the channel count in parentheses at the end of the fixture name.


  • cmuenchowcmuenchow Registered User, Administrator, HES Staff
    edited June 2009

    The issue of fixtures in LC not matching with fixtures in the Wholehog is a known issue that primarily effects slotted parameters and multi-funtion/multi-channel parameters. The guys at Light Converse are working on this and working hard to adjust their library model to be compatable with ours.

    As far as connectivity goes there are a number of tips I should mention here to make connectivity less of a headache:
    1) Run the latest version of both the Wholehog software and the connectivity driver. There might be compatability issues when mixing older software with newer software so it is best practice to always use the latest
    2) Disable all network adapter in the Windows except for the one you will be using for the connection to your console. There currently is no UI in the connectivity application to select the network adapter you want to use. We hope to implement a network adapter selection option in the future.
    3) The version number posted on the bottom left hand corner of the connectivity dialogue box is the connectivity version number. This number didn't start matching software version numbering until v3.0.3.
    4) The version number at the top of the connectivity dialogue box is the software version of the Wholehog console that is connected on the network.
    5) One final tip is to install Hog3PC on the visualizer computer when you are troubleshooting visualizer connectivity. If you can't connect Hog3PC as a client then you won't be able to connect the visualizer.
  • Joe BleasdaleJoe Bleasdale Registered User
    edited June 2009
    Thanks Chris. I could connect to LC via H3PC. We ended up going in by Art-Net "over the network". This worked but we still had the fixture issues. I am also talking deeply with the appropriate members of LC.

Sign In or Register to comment.