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
  • Color and Beam palettes are record as global as a standard. So for example you create them with one fixture(type), then they are available for all other fixture(types).
    As soon as you edit or merge some fixtures they will get more complex, you can see this when you open the palette.
    So your way/idea of adding in per type/fixture is correct.
    Please remember: If you store a palette only for color mixing and store later also some color wheel-infos into this palette they won´t be back-referenced in existing cues. (Andy this is your issue, I know)
    About HS vx. CMY, i prefer HS, because it is more accurate and efx are easier to create. Also when talking to other departments like print or graphics, HS is a "global" language.
    When dealing with LED with amber or white, I also stay in HS and create some more palettes including white/amber values and have white/amber always be part of my HS-Preset even if they are at 0%.
    Maybe we get back the calibrated colors ony day or an option to calibrate fixtures ourself. Then the whole process would be easier, because the console knows the available colorrange of the fixtures and we would only need to change type and repatch
Reply
  • Color and Beam palettes are record as global as a standard. So for example you create them with one fixture(type), then they are available for all other fixture(types).
    As soon as you edit or merge some fixtures they will get more complex, you can see this when you open the palette.
    So your way/idea of adding in per type/fixture is correct.
    Please remember: If you store a palette only for color mixing and store later also some color wheel-infos into this palette they won´t be back-referenced in existing cues. (Andy this is your issue, I know)
    About HS vx. CMY, i prefer HS, because it is more accurate and efx are easier to create. Also when talking to other departments like print or graphics, HS is a "global" language.
    When dealing with LED with amber or white, I also stay in HS and create some more palettes including white/amber values and have white/amber always be part of my HS-Preset even if they are at 0%.
    Maybe we get back the calibrated colors ony day or an option to calibrate fixtures ourself. Then the whole process would be easier, because the console knows the available colorrange of the fixtures and we would only need to change type and repatch
Children
No Data