Posts by Clintos

This problem will be fixed.

What’s the sCrash flag?

Scale of fixtures is determined by the fixture type.

You can change the scale of environmental objects.

Agree

I would like to see an option to populate recipe lines with the group, preset and ma tricks selection of the current active values in presets or cues.

The new ‘make recipe’ function is nice but creating a ‘traditional’ recipe from the current programmer is the dream.

Should this work across fixture types or are magic presets still only working for the fixture type they were stored with?

You are correct, doesn't seem to work with dimmer, I would report this to your distributor.

In the meantime put "Faderspeed seq xx 0" in cue 1 cmd

and put "Faderspeed seq xx 12.5 fade 20" in cue 2 cmd

As we know that 240bpm is the 100% value of the Seq speed master it is easy to divide 30/240 to get the 12.5% value to set the speedmaster to for your desired 30bpm.

Quote from Rikurama

You could do this by changing your chase speed to 60 bpm and then use div2 in speedmaster seq settings and then just say FaderM (executor where the speedmaster is) at 50 fade 20

example: FaderM 201 at 50 fade 20

if the fader is at page 1

EDIT: Seems that you cannot fade the speedmaster with time. So this does not work.

Also FaderSpeed does not fade

Display More

You can fade the speed with time… it does work

Target the sequence not the executor. Playback is always at the sequence level in MA3

I literally programmed lights on in a circle at 1bpm in cue 1

Copied cue 1 at 2

Edited cue 2 and made speed 30bpm.

Fade time of 10

Lights slowly speed up over 10 seconds…

Dont know what to tell you

I just tried storing the same values in 2 consecutive cues, 1 with 0bpm and the next with 30bpm and the light just faded up to speed slowly.

In v1.7.2

Yeah for it to reset as “single step” does makes a certain amount of sense.

Set the seq masterspeed to 0 in the first cue.

In the second cue set a cmd to bring it up to 30 with a 20second fadetime.

Ie

FaderSpeed Seq xxxx 30 fade 20

So I think we know about this issue where on some sequences created in v1.6 a Phasers that tracks through multiple cues seems to 'jump' with each cue change rather than continue to run smoothly through the transition.

This doesn't occur on Phaser cues created within v1.7.

Has anyone had success in determining what is making it jump and thus 'fixing' these v1.6 cues yet?

Deleting the cue data and storying again those attributes did not seem to fix it.

Cheers!

Yes of course it does, wrote that after a long day and don’t know what I was thinking of. Thanks for the correction.

Hmmm

Not really, you get a bit of a soft ‘wave’ like fade.

But what if you only wanted one fixture out of your selection on at a time and this to bounce back and forth?

It will show Preset names if an attribute is in a preset. But not the channelset names.

This is the same as MA2

I believe ‘results have varied’ with bringing shows already existing up to v1.7.

This my indeed be your issue.

Ah good to know!

Thanks

This is the interesting thing though, it was only values that were orange and there were no conflicts shown.

This makes sense though what Ryan is saying and why it only happens on MA2 libraries brought in.

Thanks

The viz key should be connected to capture.

OnPC shouldn’t be running on that machine…

Do you have multiple network interfaces sharing the same ip range?

Have noticed something new that I can't find documented (which certainly doesn't mean it isn't!).

When bringing in some MA2 fixture types, the DMXModes tab shows some values in Orange (see pic).

Can't work out what this means, if I simply type the same number into the field it changes to white as expected...