Software Version: 4.3.1274
NX Console Type or PC OS Version:
nx1
pc and nxwing
when we trigger a go for a cuelist via midimacro
onyx execute the go, but also set cuelist to 100% does not matter what the fader is set too on which the culist is recorded. also the fader does not set the cuelist intensity anymore. the list stays at 100%.
is this a bug?
it stays at 100% till release. and behave normal till a go is sent by midi.
thx.
can someone help, please.
Hello there,
I checked the issue and indeed the MIDI GO command seems to flash (and latch it) the cuelist as well which is probably unintended.
As a workaround (I still need to investigate this further) you can add another macro with the same midi parameters that executes a FLASHUP command.
thank you for that answer. so we have to go by osc, till a fix in a future build!?
thx.
…your workaround, after 3-5 go trigger the cuelist % jumps to 100 for a part of a second.
crazy, but so it is not a option.
thx.
if we do the go trigger with more than 3 secondes inbetween, then the workaround idea seems to work for a while. crazy.
thx.
Sorry to hear you have encountered this issue. This is an issue we are aware of, which is logged on our system as reference number ONYX-1104. Our software team are currently investigating this.
Please let us know if you have any questions.
hello, is there any progress in reference number ONYX 1104? THX
Hi @deflost
ONYX-1104 is scheduled to be fixed in ONYX 4.32 software. These fixes are not yet included in the latest ONYX 4.31 beta version.
Please let me know if you have any questions.
Edward
Might not be useful for you but I set the intensity inside the cuelist to whatever I would have the fader at and just run it at 100%.
Hi Edward,
I’m using the latest version of 4.32, and I am encountering the same issue. I have even tried using the “GO-NO-FADER” midi command, however my fader values still flash and latch to 100% when executed. The only way I’ve found to release the fader from 100% is to set a physical flash key on the fader, after pressing the fader value returns to where the fader is set.
Can you confirm if this bug is still present, or is there something that I am missing?
Hi @fortune
Welcome to the forum.
The GO-NO-FADER MIDI Macro will not affect a cuelist’s fader level. However, other MIDI Macros will.
For example, let’s say you have sent a MIDI Note to trigger the GO-NO-FADER MIDI Macro. This will trigger the cuelist, and will not change its level. Let’s say you then send a MIDI Note to trigger a RELEASE MIDI Macro. This macro will release the cuelist, and simultaneously force the cuelist’s level to full. The next time you trigger the GO-NO-FADER MIDI Macro, the cuelist will still be at full from the RELEASE MIDI Macro command.
Please let me know if you have any questions.
Edward
Thanks for the clarification. Is this a bug? It seems like unintended behavior.
Upon further testing I noticed more interesting behavior. When I send a RELEASE macro, the target cuelist will sometimes briefly flash to 100%, but then it will return to whatever level the fader is set to, and will update with the fader as expected while the cuelist is released. It is not until the next GO command that the fader will lock to 100%. This behavior is the same regardless of whether a GO or GO-NO-FADER macro is used, or even if the GO command comes from the console itself. The fader only unlocks after I flash it.
Currently, the best workaround that I have found is to also send a FLASH and FLASHUP macro along with the RELEASE macro. This will work fine for me for now, but for a larger show I imagine this would amount to a lot of extra programming time. Thanks for your help.
Hi @fortune
Our software team are investigating this further.
This is because currently, the RELEASE MIDI macro is forcing the cuelist’s virtual MIDI fader to full.
Another option would be to trigger a GO-NO-FADER MIDI macro that triggers a cue, which includes a Release macro.
Edward