create a phaser with step 1: dim=0 thru 100, step 2: dim=100 thru 0, phase=0 and see what happens...
Posts by zangetsu
BECOME PART OF THE COMMUNITY - Sign up here
if you just start to program your show, you can use dmx invert instead of encoder invert. then your problem will be solved. but if you already have stored values, it'll mess everything up.
hey folks, is it normal that store /look breaks up preset values when storing them into a sequence or am i doing something wrong?! i activate all my programmer values and then store /look /allforselected into a sequence...
you can make sequence with all your haze/fog outputs at zero. then you give it a high priority and make it a temp fader. so now it does not matter if its a dimmer/control/etc attribute. you can limit your haze/fog outputs by moving the fader upwards.
Andreas i have no distributor. but i'll try it tomorrow with the "simple show" showfile.
Andreas that is my workaround now. using 1 recipe with half groups and circle/inverted circle lines as a template similar to ma2 effect lines... i adjust the values and save this as a new preset which i use in my cues. when i now edit this new preset's size and update it, the absolute preset in the tracking does not get broken up. but that is a pretty annoying way to do such a simple thing...
Andreas i tried that now. same thing happens. but i noticed something...at first i stored my static absolute preset into my cue. then i ran my cue. next i called my relative circle preset into the programmer which is now a recipe as you suggested. and here i could see (as in the screenshot), the absolute layer of the fixtures gets activated and the wall preset reference in the encoder bar gets broken up immediately...so i switched off the absolute layer, stored my relative values into my cue, and now the wall preset reference got broken up there again...it's witches brew somehow haha
Andreas i was wondering as well why every 2nd fixture has lost it's preset reference on pan...i mentioned that in another thread once...
i used to use recipes for my symmetrical circles by splitting my linear selection into 2 groups for example 101 thru 110 in 101 thru 105 and 110 thru 106 and use one circle running direction 1 and the other circle running the same but with "mirror time on x-axis", problem was you had to assign every phase etc in 2 recipe lines then and all those inverted half groups where useless for symmetrical dimmer effects, so i was glad that the "Transform: Mirror" option came up.
thank you for that workaround, i'll try that tomorrow!
Andreas hey i played around a little bit today and what i found out is: everything works fine, BUT the problem comes if you use the new MAtricksoption "Transform: Mirror"...
so i programmed a static position preset and a relative circle moving around it, works fine. also editing the circle size afterwards and update the preset works fine.
then i programmed a relative symmetrical circle moving around it using the "Transform: Mirror" option. i saved that into a cue and there was the first problem. you have to toggle the sequence again or else the relative circle is not running. and if you change the relative circle preset's (containing MAtricks and within that "Transform: Mirror") SIZE and update that preset it breaks up the static preset in the tracking sheet..
that is a bug
Andreas the second step in the absolute preset before was empty. so here i used single step. same result.
its also strange that if you have no sequence running and you call the pure relative circle preset in the programmer, the absolute layer gets activated...on the other hand if you have a sequence runnig, and call a pure absolute single step preset into the programmer some purple phaser layer gets activated altough it doesnt exist...i took those screenshots while the sequence was not running...
Andreas as soon as your sequence runs and contains relative phaser values and you call the absolute wall preset into the programmer it shows the purple phaser layer, regardless if it contains any values in it.
Andreas it doesn't make any difference if my absolute wall layer has 1 or 2 steps. i tried that, same result...sry that i forgot to write that i forgot to delete the 2nd step. but i played around for hours until i got pretty upset, took the screenshots and posted here...
here is the content of the presets in the programmer sheet. nothing wrong with it...
i just found a really annoying bug. i have a 1 step absolute preset which is called wall. i have a 2 step relative circle preset which is called circle. i store this into 1 cue into a sequence and the look is as it's supposed to be, tracking is clean as you can see in the screenshot. both presets show up in the tracking sheet.
but when i edit the the relative circle preset, change it's size and update it (does not matter if i do it using the update menu or just store merge it) the new look with the enlarged circle size does not convert to the sequence where the preset is used, instead it completely f**** up the look. only when i call the now enlarged circle preset again and store merge it into the sequence, the look is as it's supposed to be, but therefore the absolute preset wall, gets broken up into some hard values in the tracking sheet!
and if i now call the absolute preset wall into the programmer again and merge it into the cue, the look gets f****ed up again...
i also tried to edit the absolute wall preset and and update the preset. and if i do that it converts over into the sequence, but it messes up the phase in my relative circle preset. it changes from 0 thru 360 to 0. after calling the absolute wall preset into the programme and store merge it into the sequence it works...
if you create a relative position preset in the phaser editor from scratch in a empty programmer, without having any sequence or whatever running, as soon as you place your 1st step it activates the absolute layer for no reason. so i am pretty sure grandma3 still has problems with relations of absolute and relative presets and updating things. i've tried it many times now and i am almost sure i did nothing wrong...
Andreas thanks for explaining. that feature drove me crazy...
and the story doesn't end here. when i double click on the wall preset and single click on the circle preset directly afterwards, the values get stored into my cue as expected.
but when i double click on the wall preset and double click on the cirlce preset directly afterwards, the values get stored into my cue, but not the pan/tilt value from the absolute wall preset. the relative values from the circle preset seem to equalize it...
that is so strange!
hey folks, i am pretty desperate. i am using grandma3 on PC 126.96.36.199. both presets were built from scratch no sequence runnig, just pure values in the programmer. i built 1 absolute preset pointing towards the wall, stored it, everything ok. cleared programmer...then i built a 2nd preset. same fixtures, a relative circle. and here came the frist problem. as soon as i added my first relative point in the phaser editor, on tilt axis, the absolute layer got activated(for no reason at all). a can live with that an switched off the absolute layer and stored that relative circle preset.
so now i have 2 presets. a "wall" preset and a "circle" preset. both consisting of either pure absolute or pure relative values.
and what happenes now is a miracle. when i double click on my wall preset, my 10 fixtures get selected and point towards the wall, when i now once click onto the circle preset i create a look.
now i clear out the programmer and i double click onto my wall preset and then double click on my circle preset and the look is different...that shouldn't be.
so what i realize when i look into my programmer window and check out my relative values of the circle preset: every fixture which got it's values from the 'tranfsform mirror" option in MAtricks has got a zero value on the pan attribute instead of the preset name written in the fixture sheet...i added some screenshots:
1Hz=1/T -> T=1s which means the length of 1 period = 1 second at a speed of 1Hz(60bpm)
2Hz=1/T -> T=0.5s at 120 bpm and so on
so you could just create a cue, with a follow cue, that stomps the phaser after a delay of T...
then it's a single shot!
Andreas omg, that is really emberassing, that i did not see that sorry for stealing your time...i just opened the .xml file and saw it right there :O
but it is strange that MA3 does note state: object does not exist, when it tries to execute Macro: "clean cue " which basically does not exist...
these are the macros: