Follow up to the Presonus NSB latency issue from a late Dec. 2023 event.
Vložit
- čas přidán 23. 08. 2024
- Talking about using the Presonus NSB 32.16 with the Presonus 32SC console. I check on a potential latency issue by setting up the console to force the audio to pause.
Hi, I’ve had this issue with complete periodic drop outs. Found it was an Ethercon cable connector issue. All starts up and connects fine when you check clock etc. But if you pull the cable a bit, or someone kicks it, and the RJ45 connection is worn, it can still have connection but you loose the clock signal. The signal starts to cut out periodically. Give away is the green flashing LED stops flashing on the Etheron socket in the desk/stage box. Yellow light stays on. Test by connecting it all together and then gently pull/push the connector in different directions and watch the lights. Might just be a new RJ45 needed. Sorted mine out, hope you find it. Cheers.
Good idea. I have that issue with one of the jumpers (which has been removed from the inventory). Will test the connectivity on the main Ethercon.
Was the audio dropout complete, or just on some tracks? If complete, I would suspect the CAT 5 cable either for rated transmission distance or EMI interference or both. CAT6 (all variants) have much higher and longer transmission ratings. Also check that the cables have an actual STP (Shielded Twisted Pair) rating to reduce EMI and preferably a ground drain conductor as well.
Good suggestions. The Ethercon cable used was a Cat-5e (100Mhz). The testing in the video used the same cable (100ft). However, we have Cat-6a cables, which I will deploy the next time. As I'm writing this, I think the Cat-5e is an STP (foil) cable. The Cat-6a cables we have are all FSTP. More to follow...
@@stageleftaudio Keep us posted on your progress!
Posted a recent video covering the cause of the issue. Check out Feb. 17, 2024 for the video.
Did the audio like "stop" or was there a noticeable 1 second delay between the board and the PA? Such huge delays could are likely unpossible (if it wasn't a user-error). There's no built in buffer that could handle such long delays. I can only imagine that an output delay was engaged on a bus or any other outs.
If there were pauses / cracks / pops that could mean that the synchronisation messed up, which can sometimes be due to voltage or bad network cables.
Thanks for the reply. From my understanding at FOH, it was probably more of a "stop" at FOH, than a delay/latency. When it occurred, I was at the stage; I can't speak to what all exactly took place at FOH. You are right, there is no buffer to handle long delays. As well, FOH did not report hearing any cracks / pops. I'm confident the synchronizing was good... which led me to believe there may have been a "pause" in the console. Since putting this video together, I've conducted other tests with the console, the NSB, using other cables (Cat-6a vs Cat-5e)... no drops, no pauses, no issues...
Do you remember if the wedges also cut out at that moment? @@stageleftaudio
I have no idea if they did. The stage was at a good volume; the monitors were not loud. If the monitors did cut out, the ambient noise floor from the instruments and vocals could have covered up a quick moment of silence.
I've had and seen issues with 100' + ethernet cables from 40°F and under. It doesn't matter if its Midas, Presonus, A&H.... popping, sudden loss of signal for a sec.
So anytime I'm doing a show under those conditions I always run an analog snake
Good point!
Or maybe use a Shielded Twisted Pair Ethernet Cable, More expensive but blocks noise intrusion better. Having said that, I agree, go analog if 100' or more.
Check output delays, console shouldn’t be time aligned with stage boxes and total processing should take maybe a few ms
Good idea. No output delays or time-alignment setups for this event. Will be setting up the gear again to test for physical connection issues.
Meant to say stage boxes should be time aligned. I’ve mixed inputs between x32 and s16 or sd16 and haven’t had any anomalies.
Was the latency in both monitors and FOH? It's not likely the venue power contributed to a clocking issue with the way digital equipment PSUs are these days and everything being rectified to DC and well regulated. Did you have a system processor/driverack in use at the event? If so perhaps there was an output delay set there? Or maybe he was just standing 1000 ft from the stage?? :D
Good points! No processor/driverack used for this event. I'm not sure if the latency/audio-drop was in the monitors. I was managing the stage, but was not on the stage when it happened. None of the performers mentioned anything about audio being dropped. Right... maybe 1000ft away!!
👍✅
WHy don't you just use a couple of small multipin sub snakes to the stage box. Then all you need to so is hook up the multipin to the fans which stay connected to the stage box. I would never go back to running a full snake to FOH at this point.
The type of setup you are referencing usually consists of a socapex type of connector (which would work better), but most of those are for connecting a FOH console into an analog snake. The stage box in the video is a digital stage box; the snake between FOH and the stage-box is a Cat-6a cable.
@@stageleftaudio no I mean small sub snakes with mulitpin connectors on the fan. I use them myself. The fan stays in the stage box and you use cat cable to get to the console. Multi pin is also used on small boxes not just big runs to the console.
I see what you mean. Yes, that would work.
Greetings, can you tell me which ups converter you use..
The UPS: Tripp Lite Smartpro rackmount 500VA
It has enough power to temporarily run a Presonus SL32 console, the NSB 32.16 stage-box and (if needed) the 5-port switch, for about 10 minutes. The UPS protects the gear from an unintended power outage. It will give us enough time to shut everything down gracefully if needed to.
@@stageleftaudio Thanks
possibly operator error? :D
Highly doubtful!!
Nice voice
Firmware losing.
Firmware was all current at that time (and is still current as of this update).
I had 32sx with 16R, they were recognized together despite same firmware update. After i chosed another firmware, it was ok.
I was hoping for a firmware issue...
Dear Bob, in resume: problem comes from connector and CAT 5a cable? Or it was something unexpected?
I'm not sure yet. Since the making of the video, I tested the cable used at the event and tested other cables; no issues. I will post something later on my findings.