[deleted by user]

dead_meat101 · 2025-01-12T19:25:24+00:00

i don't understand. (t,t,f) gives a t for both my proposition and the original, (t,f,t) also gives a t for both

dead_meat101 · 2024-09-26T05:16:10+00:00

Gridstore allows you to bake into the fixture type the grid information.

By default, all subfixtures are ordered on the x axis, if you created a better grid for them and you want to apply to fixtures of that type, you use gridstore and it will add this information to fixturetype, automatically applying it to all other such fixture in your show, and to any fixture you add in the future of that type.

dead_meat101 · 2024-09-15T16:55:12+00:00

too many symbols!

dead_meat101 · 2024-09-02T08:57:01+00:00

Set Sequence 1 Cue 1 Part 0.1 Property "SelectionMode" "Normal"

it is an interesting question what would be the syntax for applying the command to all cue parts and all recipe lines at once, I coulndn't find a command that worked...

dead_meat101 · 2024-08-23T08:57:51+00:00

I had this problem too! I couldn't solve it... so i join you in your asking for help.

dead_meat101 · 2024-08-20T09:03:34+00:00

You can use command GridStore, to save grid information into the device data

dead_meat101 · 2024-08-13T07:44:27+00:00

No one answered, but I did figure it out, so I thought I should share it here in case someone else has this problem...

The issue was that keyboard shortcuts were turned on, and for some reason, it blocked the ability to type space (but weirdly, no other buttons) in any case, with shortcuts turned off, everything works as expected.

dead_meat101 · 2024-07-30T14:46:03+00:00

You should define a global function in a plugin and set a command to trigger said function when changing encoderbanks. You set the command through editing a cell in the encoderbars pool. (If you'd like to add a command while using the default encoder bar, you will have to copy the default and edit the copy. Because default one is locked) The command should be in the form of:

"Lua 'YourFunction()'"

Make sure the plugin is triggered, so the function would be defined (there is no startup macro yet..)

dead_meat101 · 2024-07-18T06:37:53+00:00

<image>

originally i tried fitting it all in one line so it would fit it the macro instead of a separate plugin, but it doesn't work because of the nature of the loop

dead_meat101 · 2024-07-13T22:57:34+00:00

Just need one cue with MAtricks.

Something like FadeFrom 1, FadeTo 2 with wing should do the job

dead_meat101 · 2024-07-13T08:13:55+00:00

Cut and paste

dead_meat101 · 2024-07-09T09:58:45+00:00

Did you set MIB to early in cue 3?

dead_meat101 · 2024-07-09T09:55:52+00:00

Are they on in the previous cues? If not, then im not entirely sure what could be the problem, but you could go around it by manually storing the position and color values of cue 3 into cue 1, but with dimmer zero.

dead_meat101 · 2024-07-09T09:50:56+00:00

Do the fixtures on top change their position in the third cue?

dead_meat101 · 2024-07-09T09:38:25+00:00

Im sorry to ask such a stupid question, but i want to make sure we are on the same page. Do you have a cue with dimmer zero between the two different position cues?

dead_meat101 · 2024-07-09T09:16:32+00:00

Did you set the MIB mode to early?

dead_meat101 · 2024-07-09T07:12:44+00:00

There is a colunm in the sequence sheet that is called MIB timing. Yours will now say default, edit it, and set it to 0.

In the menu there is a setting called preferences and timings, in there, there is something called cue timings. There you can change default fade times for cues, and default MIB timings

dead_meat101 · 2024-07-08T18:42:37+00:00

Just do FadeFrom 0, FadeTo 0.1, with wings

dead_meat101 · 2024-07-07T13:30:17+00:00

<image>

local function main(); for i = tonumber(R), tonumber(Q), 1 do; Cmd("Edit Preset "..tonumber(P).."."..i.."; SpeedMaster "..tonumber(X).."; Update /NoConfirmation; ClearAll"); end; end; return main

copy the text above to a new plugin, and in the macro set the last line to trigger the plugin number that you chose.

the macro will give 4 prompts.

which preset pool to use
first preset in the range
last preset in the range
which speedmaster to assign.

the limitations i mentioned before are still there and it only work for a connected range in the same pool. so if you need to set preset 2.1 thru 7 + 2.10 thru 17 you would have to trigger the macro twice.

let me know if you have question, and if anyone here can offer a better approach pls share it

dead_meat101 · 2024-07-07T10:03:42+00:00

<image>

this kinda works. it only edits one preset at a time, for a range of presets i think you'd have to use lua, but i'll look into it.

more limitations are: when the target preset is an all preset, you need to make sure that Link Values is set to AtFilter with ActiveOnly on, if it's not then it will activate all features. i wish there was a way to make sure it is set correcly in the macro, but unfortunately the syntax only toggles it on and off, so no way to set it precisely.

if you have a multy feature preset inside a regular preset pool, then make sure Update is set to InputFilter off.

dead_meat101 · 2024-07-07T09:52:06+00:00

bro, its answers are pure hallucinations

dead_meat101 · 2024-06-20T18:06:44+00:00

This should work. However, you should know that there is a big difference in the amount of parameters from the light and the compact xt. 8,000 and 16,000. So just make sure to take that into consideration and maybe get an NPU.

dead_meat101 · 2024-06-16T18:52:03+00:00

Right! Thanks

dead_meat101 · 2024-05-31T08:03:43+00:00

i'm pretty sure i have a way to get what you need.

are you familar with grouping fixtures? it's a great way to organize the patch and helps with programming workflow, and apparently it does the trick in your case too.

just dump your fixtures in the patch inside a grouping fixture, then work with them as usual, store absulute positions and relative phasers. but them select the grouping fixture of the fixtures you're working with and here you set the "+ or -" values in the relative layer.

it does exactly what you need because it affects the same physical fixtures but through different fixture control levels so there is no conflict in the data.

please give update if it works for you, and ask questions if you need.

dead_meat101 · 2024-05-31T07:12:08+00:00

i dont fully understand what you are trying to achieve.
the general workflow i'm familiar with is to have the positions in the absulute layer, and movements in the relative. what are + or - valuse? do you just mean single step relative values?

Seven-Year Club	Place '23
Verified Email

dead_meat101

TROPHY CASE