Goboshake Stops When Changing Gobo Rotation or Gobo Index

Shween · February 7, 2025 at 1:20 AM

I have come to almost complete this DDF.

However There are a few Clerical issues.

1st:
If you activate Gobo Shake, and then activate either Gobo Rotation or Gobo Index, The Gobo Shake Stops as DMXC resets the value to the normal GOBO DMX Address rather than keep it in the Gobo Shake Handler Range.

If you first activate Gobo Rotation, and then activate Gobo Shake, this does not occur...

2nd:
I am trying to figure out a more efficient way to adjust the Blades rather than using RAW channels.

Please see my original Thread: Blade Control Separate Topic. Control 2 channels with one parameter [DDF]

I have uploaded the current DDF profile and DMX Schedule.

What could I have done wrong? Or is there a setting in DMXC I need to change in order to stop the automatic change of the Gobo Channel to reset from the Shake Schedule?

Thank you much!

Shween · February 7, 2025 at 2:38 AM

Sorry about this Repost, as I originally posted in DDF Support.

But I have tested this with other DDF profiles, and it occurs across the board.... so I thought it might be appropriate to post here.

Here is a link to my original thread: Goboshake Stops When Changing Gobo Rotation or Gobo Index - DDFs V3 - DMXControl Projects e.V.

I have come to almost complete a DDF.

However, There are a few Clerical issues.

If you activate Gobo Shake, and then activate either Gobo Rotation or Gobo Index, The Gobo Shake Stops as DMXC resets the value to the normal GOBO DMX Address rather than keep it in the Gobo Shake Handler Range.

If you first activate Gobo Rotation, and then activate Gobo Shake, this does not occur...

This also occurs if you recall a cue, and can only be fixed if you add a delay to the Gobo Shake in the Cue Timing Editor.

I am now not sure if this is the way the DDF is written with handlers and support tags, or what now.....

Is this potentially a bug?

**LightningBrothers** · February 7, 2025 at 9:55 AM

Good morning,

to avoid, that there is a double made discussion about the same topic, I bring your two post back together to one thread. If this topic will stay in the DDFv3 forums or will move to the help and support section, can be managed later. All our club members have opportunity to moderate all postings and move them to other sections or also split a discussion into several individual threads.

So: don't worry about if you realise by time, that a thread was started in the wrong section. We will handle that.

Related to your topic: that's a point, I need to figure out by myself. The point is, that I didn't use the goboshake function not really in my projects - especially not in combination with rotating or indexing the gobo. But I have an idea, where I will / can check them, if it could be an potential bug or not.

Stefan

**LightningBrothers** · February 7, 2025 at 6:58 PM

So... as I said, I have to figure it out, I got now the solution for your "problem". The simple point is, that you have to add some informations to the definition for the goboshake. The example is the following:

XML

<gobowheel dmxchannel="0">
  <goborotation dmxchannel="1">
    <step type="stop" mindmx="0" maxdmx="0"/>
    <range type="cw" mindmx="225" maxdmx="239" minval="0.1" maxval="5"/>
    <range type="ccw" mindmx="241" maxdmx="255" minval="0.1" maxval="5"/>
  </goborotation>
  <goboindex dmxchannel="1">
    <range range="360" mindmx="0" maxdmx="191" minval="0" maxval="360"/>
  </goboindex>
  <goboshake/>
  <step type="open" mindmx="0" maxdmx="5" caption="Open"/>
  <step type="gobo" mindmx="6" maxdmx="11" val="Futurelight DMH-160 Gobo 1 (Rad 1).png" caption="Gobo 1">
    <range handler="goboshake" also="goborotation,goboindex" mindmx="98" maxdmx="115" minval="0.2" maxval="4"/>
  </step>
  ...
</gobowheel>

Display More

The focus is on the additional attribute also with the values goborotation,goboindex. With this addition you can define exactly, when the goboshake is "available" - that means when the device is possible to execute the goboshake function. When you addgoborotation,goboindex, then a goboshake can be execute also, when goborotation or goboindex is set. When you remove one of them (including the ,) and define just also="goboindex", then the goboshake will be turned off automatically when you set a value for the goborotation.

I hope, you can follow my explanations and my example. If everything runs also for you as expected, I can add this to our documentation.

Shween · February 7, 2025 at 11:40 PM

Thank you for looking into this. I will modify the code and test the sample hopefully within the next few days.

In the meantime, I still wonder about the blade features.

Is there any additional syntax to control 2 channels based off one parameter?

We proudly present: The release of DMXControl 3.3.3!