High Fade Engine Avg and Peak times

Please either add those logs as well as a showfile here, or send them to me at eos(dot)moderator(at)etcconnect(dot)com referencing this post.

Thank you.

Hello stevelx , we have taken an initial look at the Ion Classic (Win7) logs you provided.  It looks like the lags started happening on 2025-01-21 around 12:45pm, and are not evident after 2025-01-23 18:11, even though there are two additional days of logging.

stevelx said:

In the event a cue is fired whilst the fade engine is experiencing a period of increased processing delays, will this affect and delay the sACN output?

 Yes.  The Fade Engine messages are recorded in milliseconds and represent the amount of time between "ticks" of the Fade Engine - how often it calculates all outputs to then send out via sACN.  If the system is running normally, the Fade Engine calculates outputs every 22ms (to match DMX and sACN specs) although sACN can be sent less-frequently over the network, per spec, if nothing is changing levels.

The lags seem to be happening near times when the Backup Gio console is coming online.  If you could provide logs from that Gio console as well, we may be able to make a stronger determination. 

At a minimum, I would ask if anything changed on those days (the 21st, when the issue started, and the 23rd, when it stopped).  This could be as simple as a glitchy / compromised network connection between the Ion and the Gio that went away by replacing a network cable.

Hi Matt Pumplin , I have sent through the Gio logs as requested. FYI, the Gio console is used at the production desk for programming and is struck before performances.

Whilst the period of high latency reduces after the 2025-01-23, the issue with the delayed sACN output continued in the performances on 2025-01-25. There were delays in the evening performance (between log time of 19:25 to 21:35), with especially noticeable delays when playing back the following cues: 1/33, 1/40.5 and 1/41.

As a result of the issue, the network switch and interlinking cables that were connected to NIC 2 of the Ion (for OSC) were replaced on 2025-01-24. Since the equipment replacement and as previously mentioned the fault then occurred on 2025-01-25. As a result, on 2025-01-26 the NIC 2 link was removed and there have been no further reports of issues.