Creating and editing color palettes

I am a little embarrassed to have to ask this, but I need help developing a reasonable strategy for dealing with color palettes on the Hog 4 platform.

My goal is to get to a point where I always start with a custom generic show file so I am not constantly recreating color and beam plaettes, views, custom effects, etc. As a point of reference, in the Hog2 days it was simple enough to select a single fixture of each fixture type to create palettes that would be recognized by any number of those same fixtures. I realize that the GLOBAL, PER TYPE and PER FIXTURE options are far more powerful but somewhere along the line I get fouled up. This problem is exacerbated when I have to start editing those palettes which I have to do all the time.

My plan would be to start with one instance of as many different fixtures as possible to create my standard color palettes. I would assume all of these palettes would be recorded PER TYPE. Whenever I start a new event, I would then merge whatever new fixtures might be necessary to my standard show file before moving on to actual prgramming thereby increasing the number of fixtures in that generic file. I am again assuming I would merge these palettes using PER TYPE.

By the way, I am aware that the HOG OS more or less requires one to stay in a single color model per fixture type. I like the idea of the HS model as it certainly makes the effects engine and detailed programming far more powerful. I am not convinced, however, that HS is truly the best model choice. I am also not entirely sure if using white and/or amber LED's with the HS model constitutes mixing color models.

Since moving into Hog 3 and now Hog 4, I have constantly run into issues with colors that will not update or that just play back incorrectly. I am fairly certain that some problems may occur due to my potentially forgetting to choose PER TYPE when recording. There have been times that the only way I can "repair" a specific color might be to use the "PER FIXTURE" option.

As I mentioned in another thread, I would like to have more than one standard color palette so that I can switch back and forth between them based on current usage. I want to make certain, before I invest any time in the process of creating a standard show file, that I am doing things in a way that will work. To some extent I have the same problem with beam parameters. It does not seem like this should be that difficult but it has been driving me nuts. Any thoughts?
Parents
  • [QUOTE=inthe128;72314]Just a note on the rotating gobo thing:

    To my mind if the fixture has its rotating gobo on gobo 2 as an example, thats fine. The cue has a break up with slowly rotates. I update a gobo, say slot 2 on gobo wheel 2, then update the slow rotation palette. In this case I would expect the cue to replay both palettes, the rotation appears not to follow programming even if the original information was derived from a fixture where gobo 1 has the index/rotating gobos, I just think it should.

    Regarding less than good fixture files, I have sent a few in for checking, had one with 4 pan channels and no tilt channels, easy fix when you opened the file up, inverted zoom channels of a few Robe fixtures, also the Robe DLX had 0>255 when it should be 255>0 on colour. You might remember I had some mini-scans that really caused some *** with the split fade and strobe channel, in the end that was a badly written file and once I made an edit I got the best way to deal with split functions.

    Is there an official way to send in fixture problem requests. I would like a way to send comments and see that they have been received, confirmed as a problem and re written, anything I have sent in I have not had a reply to.

    You know all direct contacts you need ;-)
    You can also send me a list and I can pass it on
Reply
  • [QUOTE=inthe128;72314]Just a note on the rotating gobo thing:

    To my mind if the fixture has its rotating gobo on gobo 2 as an example, thats fine. The cue has a break up with slowly rotates. I update a gobo, say slot 2 on gobo wheel 2, then update the slow rotation palette. In this case I would expect the cue to replay both palettes, the rotation appears not to follow programming even if the original information was derived from a fixture where gobo 1 has the index/rotating gobos, I just think it should.

    Regarding less than good fixture files, I have sent a few in for checking, had one with 4 pan channels and no tilt channels, easy fix when you opened the file up, inverted zoom channels of a few Robe fixtures, also the Robe DLX had 0>255 when it should be 255>0 on colour. You might remember I had some mini-scans that really caused some *** with the split fade and strobe channel, in the end that was a badly written file and once I made an edit I got the best way to deal with split functions.

    Is there an official way to send in fixture problem requests. I would like a way to send comments and see that they have been received, confirmed as a problem and re written, anything I have sent in I have not had a reply to.

    You know all direct contacts you need ;-)
    You can also send me a list and I can pass it on
Children
No Data