Hi all,
Recently I was doing a show with the avo 04. And a persone came to me and he saw me screwing around with the palettes. He did some changes in the user settings. And suddenly things got way easyer then they were.
Normaly when you recal pallets you can set you atributes to dimmer, or select a specified atribute. Then the palette has effect on the selected fixtures. (that was before he changed some thing)
AFTER:
I don't have to select my fixtures, he automaticly set the palattes back to my selected fixtures as I programmed them.
Does anyone know how he did that? I wipe my tabel and al my settings went back to default so I don't what he did.
Options for palattes
Moderator: Moderators
Most likely he enabled 'quick palettes' in user settings. If no fixtures are selected then everything in that palette recalls (subject to attribute mask).
This makes it quicker since you don't need to select fixtures. If you deliberately program palettes to only contain exactly the information you want to recall (ie. individual palettes for each fixture/attribute type) you can leave attribute mask on dimmer (all) and recall palettes with only one button press or two if you want a fade. You can even set up a master fade time which would always apply unless a different time is entered.
I recommend this way of working. It is fast and eliminates possibility of making a mistake. This does potentially come with the cost of requiring more palettes but if you also enable 'palette paging' you can have four pages which switch with the fixture pages.
It is still possible to select individual fixtures to apply palettes if you need.
This makes it quicker since you don't need to select fixtures. If you deliberately program palettes to only contain exactly the information you want to recall (ie. individual palettes for each fixture/attribute type) you can leave attribute mask on dimmer (all) and recall palettes with only one button press or two if you want a fade. You can even set up a master fade time which would always apply unless a different time is entered.
I recommend this way of working. It is fast and eliminates possibility of making a mistake. This does potentially come with the cost of requiring more palettes but if you also enable 'palette paging' you can have four pages which switch with the fixture pages.
It is still possible to select individual fixtures to apply palettes if you need.
I already tried Q-palette. But then I had another problem. I think it is an programming issue. When make a palette for my spot MH's and another for my wash MH's the override eachother... both palette's have effect. When I press position 1 (SPOT MH's) the spot and wash MH's move to that position and visa versa...
What can couse this problem?
What can couse this problem?
This is because you have stored information for both fixture types in both palettes.
It is important to be accurate. When recording palettes anything in the programmer will be stored filtered by attribute mask.
Personally I think it is best practice to always press Clear (to remove all values from programmer), bring required values into programmer by preferred method (for example nudge wheel), select dimmer attribute and store palette.
To remove mistakes you can use OFF.
In this example select fixtures that should not be in palette. Press OFF. [turn off selected fixtures], select dimmer and then store palette on top of existing. This will merge OFF values for all attributes of the selected fixtures, thus removing them completely from the palette. You can also use the OFF function to remove specific attributes - for example if you accidentally stored dimmer values.
It is important to be accurate. When recording palettes anything in the programmer will be stored filtered by attribute mask.
Personally I think it is best practice to always press Clear (to remove all values from programmer), bring required values into programmer by preferred method (for example nudge wheel), select dimmer attribute and store palette.
To remove mistakes you can use OFF.
In this example select fixtures that should not be in palette. Press OFF. [turn off selected fixtures], select dimmer and then store palette on top of existing. This will merge OFF values for all attributes of the selected fixtures, thus removing them completely from the palette. You can also use the OFF function to remove specific attributes - for example if you accidentally stored dimmer values.
Uhu, I understand.
But a few weeks ago, I worked on a pearl expert. And I did like I explained above. I made 2 different palattes. One for my washes and one voor my spots. And it went wrong... And I don't know how. I'm sure I only selected my spots for the spot position. Same for the wash position.
My set my avo always to record by channel, when I begin. But do I have to set 'Q-palette' for the beginning? Or makes this no diference?
But a few weeks ago, I worked on a pearl expert. And I did like I explained above. I made 2 different palattes. One for my washes and one voor my spots. And it went wrong... And I don't know how. I'm sure I only selected my spots for the spot position. Same for the wash position.
My set my avo always to record by channel, when I begin. But do I have to set 'Q-palette' for the beginning? Or makes this no diference?
If Expert was running Classic then there is no difference and it records only what is in the programmer filtered by attribute mask.
If it was running Titan then there are different record modes selectable before storing.
It is more than likely you did not press clear between editing the different fixture types.
Quick palette only affects recall. In Titan it is always enabled.
If it was running Titan then there are different record modes selectable before storing.
It is more than likely you did not press clear between editing the different fixture types.
Quick palette only affects recall. In Titan it is always enabled.
Presumably by simulator you mean Visualiser?
Most likely you are using the wrong .vis file. The correct one is SHLEDOCT. Tested and works fine here. If you don't have it you can download from the website. Place the file in the vis/extensions directory and it will then be available under moving heads in Vis.
Also note that (at least as far as the vis definition is concerned) you need shutter at 100% for normal open operation. Shapes that work will be rainbow, RGB and red/green/blue types.
Most likely you are using the wrong .vis file. The correct one is SHLEDOCT. Tested and works fine here. If you don't have it you can download from the website. Place the file in the vis/extensions directory and it will then be available under moving heads in Vis.
Also note that (at least as far as the vis definition is concerned) you need shutter at 100% for normal open operation. Shapes that work will be rainbow, RGB and red/green/blue types.
Thx now it work...
Sorry for all my questioning... but I have another question.
Above you explained how to install the palette recal like I described.
But if I use Q-palette, can I still use the normal mode for programming a color chase for example. I mean on different fixtures (odd = red / eve = blue)
Sorry for all my questioning... but I have another question.
Above you explained how to install the palette recal like I described.
But if I use Q-palette, can I still use the normal mode for programming a color chase for example. I mean on different fixtures (odd = red / eve = blue)
Quick palettes just means you can recall a palette without selecting any fixtures.
Otherwise everything works the same. It has nothing to do with programming.
Perhaps the only thing you need to remember is that, since you haven't selected any fixtures, QP recall does not place the information in the programmer and therefore won't override values from playbacks (ie. chases).
Sometimes this is what you want, sometimes it isn't. If you specifically need a palette to take precedence over playbacks then you must select fixtures first.
This is another area that has been improved in Titan. Here quick palettes do take control over playbacks even without selecting fixtures. This includes values coming from chases. Firing the same chase again or another playback using these fixtures/attributes will restore priority to the playback. This is very useful.
Otherwise everything works the same. It has nothing to do with programming.
Perhaps the only thing you need to remember is that, since you haven't selected any fixtures, QP recall does not place the information in the programmer and therefore won't override values from playbacks (ie. chases).
Sometimes this is what you want, sometimes it isn't. If you specifically need a palette to take precedence over playbacks then you must select fixtures first.
This is another area that has been improved in Titan. Here quick palettes do take control over playbacks even without selecting fixtures. This includes values coming from chases. Firing the same chase again or another playback using these fixtures/attributes will restore priority to the playback. This is very useful.
Who is online
Users browsing this forum: No registered users and 28 guests