I noticed when Onyx on PC was my primary and NX1 was my secondary during A joined show, that when I had BPM displayed on the top of both, the nx1 had a different BPM than Onyx on PC. Is that normal? It was when running DYLOS. What would cause that? Also adjusting parameters in onyx in the NX1 caused it to crash and it disconnected from primary and ran in stand alone. I turned it off and turned it back on. I’m basically just playing around with Onyx on PC/NX1 as a secondary and Reaper on the same PC to practice with DYLOS. I gave up after I found out that I cannot both listen to through speakers and output to Onyx with reaper and the PC. I wish they made something that could do both maybe hardware that anyone knows about besides buying a dedicated PC for just audio because I’m a LD I don’t usually mess with audio but I’m training on Onyx rn.
Currently BPM information is not transferred over X-NET, so what you are seeing is expected.
Sorry to hear this. What software version were you running on NX1 and Onyx PC?
In what way did it crash? Did it freeze and then recover, or did it freeze completely? Were any error messages displayed?
Edward
I’m running the latest bios and Onyx on NX1 and Onyx on PC. It freezes and then disconnects from x net turning them both into standalone. Happens frequently, there’s no error that shows up they just immediately disconnect from x-net. I’ve seen a few people say it disconnects in the middle of live shows when they are working. I have to re join shows. I also notice that if I’m doing something in the primary it doesn’t show in the secondary and vice versa. Like programmer shows one thing in one and nothing or something else in the other. If I’m doing anything with DYLOS it’s guaranteed to disconnect from X-Net at least once sometimes more than once. Timecode only displays correctly in the primary the secondary shows no timecode so I’m having to run double time code to get both to display the same information, this should be shown through x-net but it’s not.
Thank you for reporting this issue. I have logged this on our system as reference number ONYX-1038, to allow us to resolve this in a future software update.
Please let us know if you have any questions.
Currently with the NX1 running secondary and my PC as primary, I lose time code on the NX1 and the only way to get it back is to turn the nx1 off and then back on. I also notice that I cannot use the NX1 on my primary, like I was trying to adjust parameter with the encoder on the NX1 and it doesn’t do anything on the primary. The windows never match up if I’m in a workspace eon my primary, the secondary is in a different window. Also windows that I create on the primary don’t carry over to the secondary when shows are joined. I also notice if I’m editing in DYLOS on the main the secondary doesn’t have the same parameters it even colors or anything on DYLOS on the secondary. It’s confusing it’s like having two different shows going on.
cue
Just trying to record one cue with DYLOS and this setup(a NX1 and a premier license on PC) just doesn’t want to work. The MIDI stops randomly, the console goes into stand alone constantly, anything with DYLOS causes disconnects from X-Net, frozen MIDI timecode and the NX1 started putting random UI element images as the DYLOS source. I did after three hours get a cue recorded but it’s the wrong color so I hit load load on that cue fix the color and DYLOS turns it to bright white instead of the pink I selected. I’ll try again later.
Thank you for the additional information.
If you would like to use X-Net reliably, for now please avoid using DyLOS. Or, if you wish to use DyLOS, please avoid using X-Net, whilst our software team investigate ONYX-1038.
Apologies for the inconvenience this may cause. Please let me know if you have any questions.
Thanks Edward, I have noticed alot of people are having issues with X-Net and their NX1’s so it’s not isolated. I still haven’t figured out the problem, there shouldnt be a problem as X-Net has its own dedicated network and switch. The only traffic I’m allowing is x-net and the cable is 6’ it’s just to connect the nx1 and Onyx on PC together. Definetly a head scratcher but judging by DYLOS displaying UI elements torn onto the graphics and the freezing and disconnecting I’m confident it’s software related. I’ve ruled out hardware as everything’s brand new.
If it helps any I’m using DOREMIDI USB MIDI and LTC box it’s a timecode generator, converter and reader. It plugs into a USB port and is recognized by the NX1. It also has a OLED screen on the DOREMIDI and it always keeps timecode but the NX1 stops timecode after a little bit and will not work again unless the console is shut off. Hope that helps for the timecode part still not sure about x-net I checked the network resources and it never output a super high amount so the network isn’t congested.
@TheatricallyJerry - as a fellow user, thanks for the description(s) and accuracy in describing the problems you are encountering. While they are not ideal, the more information you provide, hopefully the quicker and better a solution can be found.
One suggestion to help aid in that. If you can take pictures of the UI tearing and describe if it’s appears to be coming from a certain workflow order. (IE. Fixture groups window to DyLOS Zone Parameters always show tear) this will help them recreate the problem faster. Also listing the exact version you are working with. Latest or Current version aren’t helpful.
Please keep reporting bugs or issues you have, it only makes the platform stronger. And good job learning the system. I know you are newer to it based on some other post.
Watson
Jerry reported on the facebook group he solved it by disconnecting one of the timecode to midi adapters from the NX1.
Correct, it has been resolved by removing the USB MIDI device from the NX1 and moving it to the PC. I will admit that it did corrupt Onyx on the NX1 when it was plugged in. It was using windows MIDI drivers so not sure why but it did wreak havoc on the NX1. Once moved to the PC it was fine. I ended up putting a USB to MIDI cable out from the Nx1 and into the MIDI box attached to the PC to solve the problem.