Latest update has DESTORYED NDI on Onyx. Everything works fine with NDIs software but with the latest Onyx I can no longer access anything including VST plug in for reaper. If I use studio monitor on NDI tools I can access the VST audio just fine. When I go into onyx I cannot see my own PC or the laptop as sources.
it says offline and the VST says offline with a yellow thing in the corner. If I try on my laptop with latest onyx it also doesn’t show VST plug in but does show the laptop and the desktop.
I can furnish you a video of how Onyx is reacting because right now it’s not good. I believe again this has to do with Windows 11 24H2 and specifically onyx since NDI tools and Reaper are all the latest builds and work as expected.
The source is on my desktop and my desktop cannot see my laptop or desktop source or VST. The desktop is brand new it was bought last week. I had the same problem on my old desktop as well. It has to do with Windows 11 24H2 and Onyx. I can send you a video if you would like. It’s not the settings as I’ve stated NDI tools works fine in the laptop and Desktop. The NDI setting in Onyx is enabled. Here’s some screen shots:
I can confirm it’s not a network problem as my NX1 is on the same network as the laptop and Desktop and it can see the NDI nodes as well as the VST plug in and it can use it. I tested the WAV form on the NX1 and the stuttering of the waveform seems to be fixed so that’s good. It just broke everything else…
I figured out that Onyx doesn’t allow two NICS at the same time which is odd because I’d like to isolate my ARTNET to a NIC and NDI/X-Net to a nic. If I disabled my Artnet NIC and then disable my X-Net nic and then re enable my X-NET NDI works and the local node shows as well as any test patterns and video feeds. As soon as I re enable my Artnet NIC the NDI node goes offline. I have the Artnet nic set as refereed NIC in NDI tools. The Artnet is on its own universe in the 2.xx.x with a subnet of 255.0.0.0 and the xnet NIC is on 192.168.0.10 with a subnet of 255.255.255.0 and is fed to a managed switch which is connected to a wireless router with no internet.
I have tested CITP fixture discovery and fixture import in ONYX 4.31.1296, and this appears to be working correctly.
If you have a Capture project where this is not working, please could you send me the zipped Capture Presentation export from your Capture Project? I will then be able to investigate further.
I recorded a cuelist with the “release” value in the intensity parameter.
If i do that in the second cue, it releases the hole cuelist, but it works as it should in other cues.
I can not fade the weight parameter with a fader, not as an override or cuelist.
It fades if I go the cue with a fadetime, but why cant i yust fade it with an override?
If your cuelist just contains a single intensity parameter, and that intensity parameter is released in a cue, this will then release the whole cue list, as all parameters in that cue list have released.
Please select the fixture you have recorded into your “Weight” override cue list. Then, enable Weight mode in the CV, and view the parameter you have recorded. Then, raise your Weight override fader - you should see the Weight value changing with the fader.
If you don’t see the value changing, please open the Cue list values window, and select your weight override cue list. In here, make sure that a Weight value has been recorded for the required parameters in this cue.
I think I just stumbled across a bug (or need clarification on proper use). If I have a cuelist on a playback fader and active, it will show in the Active Cuelist window. If I delete it from the fader it will remain in the cuelist directory. However, if I accidently delete it from the Active Cuelist window (instead of pressing release) it will delete it from the playback fader and the cuelist directory. I stumbled across this when I had a cuelist that was set to auto start / run at console start up and it got deleted instead of released. I went to re-fire it and it was not in the cuelist directory. Is this a bug or intended operation from that window. NX4 on 4.31.1296 (RC2).
Yes - this is the correct behaviour. The Active Cuelists window is essentially the same as the Cuelist Directory window, but filtered to just show active cuelists.
If you ever see “CUELIST VIRTUAL CUELIST” on the command line, this is referring to the cuelist itself. You will see this command populate when deleting from the Cuelist Directory or Active Cuelist windows. When working with cuelist assignments on playback faders, you will instead see “CUELIST PLAYBACK Fader”. These commands will not affect the cuelist itself, just which playback it resides on.
I hope this helps. Please let us know if you have any questions.
We recommend testing in a controlled environment with enough time to roll back to a non-beta version if needed.
Preview Documentation: Onyx Beta Preview Manual
