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
  • I am no sure this is so black or white...excuse the pun.

    I have had auto coloured buttons changing colour completely, in the case of a fixture that had inverted RGB values, so my yellow palette went blue, the palette when selected gave yellow, but programming using yellow gave blue...... In that case making a copy of the fixture and fixing the values would have been a better choice of outcome, but I often wonder why programming using palettes, sometimes seems hit or miss.

    Also and certainly using fixtures that might have a white or amber channel, but also fixtures with colour correction channels can be awkward. Often I make an edit, looks good on stage and then only to find when I have updated, merged the colour goes back to what it was. All combinations of editing seem to not give back what i just re-recorded.

    I seem to have problems regarding Robe fixtures when using gobo rotation, as they seem to have fixed as gobo 1 and index/rotation as gobo 2, as I programmed with a fixture that has index/rotation on gobo one, I find even though I update gobo palettes and rotation palettes, the rotation never plays back although the programming is referencing the slow rotation palette.

    We talked about this Marc I know, but I was less than happy arriving at a gig and having a Mac 500 do pink and not amber in programming, but being able to select amber from the palette, output window shows amber, the eye see's pink.

    It seems to me and certainly when you have a show picking up whatever is at the gig that you need to do a CMY fixture, the a colour wheel fixture, then an RGB + W, + Amber, rather than doing programming with one type of fixture, which I have always managed on other console's.

    I feel not in control sometimes, in my mind i expect a any programming using palettes to reference what is in the palette on an edit without question, blue is blue whatever the fixture type. I feel somewhere along the line I am missing the point of the current system and thus it causes a lot of problems, although I am learning a lot about editing fixtures... :-)
Reply
  • I am no sure this is so black or white...excuse the pun.

    I have had auto coloured buttons changing colour completely, in the case of a fixture that had inverted RGB values, so my yellow palette went blue, the palette when selected gave yellow, but programming using yellow gave blue...... In that case making a copy of the fixture and fixing the values would have been a better choice of outcome, but I often wonder why programming using palettes, sometimes seems hit or miss.

    Also and certainly using fixtures that might have a white or amber channel, but also fixtures with colour correction channels can be awkward. Often I make an edit, looks good on stage and then only to find when I have updated, merged the colour goes back to what it was. All combinations of editing seem to not give back what i just re-recorded.

    I seem to have problems regarding Robe fixtures when using gobo rotation, as they seem to have fixed as gobo 1 and index/rotation as gobo 2, as I programmed with a fixture that has index/rotation on gobo one, I find even though I update gobo palettes and rotation palettes, the rotation never plays back although the programming is referencing the slow rotation palette.

    We talked about this Marc I know, but I was less than happy arriving at a gig and having a Mac 500 do pink and not amber in programming, but being able to select amber from the palette, output window shows amber, the eye see's pink.

    It seems to me and certainly when you have a show picking up whatever is at the gig that you need to do a CMY fixture, the a colour wheel fixture, then an RGB + W, + Amber, rather than doing programming with one type of fixture, which I have always managed on other console's.

    I feel not in control sometimes, in my mind i expect a any programming using palettes to reference what is in the palette on an edit without question, blue is blue whatever the fixture type. I feel somewhere along the line I am missing the point of the current system and thus it causes a lot of problems, although I am learning a lot about editing fixtures... :-)
Children
No Data