Author Topic: xSchedule '64 Excessive delay on Renard data vs E1.31 on Falcon F16v3 - "Help"  (Read 620 times)

Offline Tory Street Lights

  • Full Member
  • ***
  • Posts: 134
    • View Profile
Running a test show using xSchedule 2019-64 I am seeing massive lagging data on my Renard AC data (700 Channels) fed via serial ports, vs the Pixel data handled on E1.31 by a Falcon F16v3.  The same sequences run using the sequencer it'self to playout to the lights is perfect, no issues at all.

The Renard controlled lights look as though they are being throttled down in speed, it is the most weird effect I have witnessed in 11yrs of light shows. My guess is after about 3 mins of show the Renard data is about 1 min behind!!!,  and the official show start time is 18 hrs away!!

The machine running the show is a 2.5 Gig Quadcore HP workstation with 8 Gig's of ram onboard, and Windows task manager suggests that it is only running at about 20% processor activity and using 1.8 Gig's of Ram.

The same machine ran last years show with an almost identical setup apart from the E1.31.data being handled by 23 or so ESP8266 Pixelsticks, which gave me intermittent lagging of the E1.31 data we suspect was due to  local WiFi interference!  This was using 2018-40 version, maybe a return to that version may help  ??

Any helpful comments extremely welcome!!!

Terry
« Last Edit: November 30, 2019, 05:13:11 AM by Tory Street Lights »

Offline keithsw1111

  • Administrator
  • Hero Member
  • *****
  • Posts: 2733
    • View Profile
    • Kellyville Christmas Lights
Yeah not sure. Does it play from xlights. Logs?  We could turn on frame logs for more details. 700 is a lot of Renard channels.

Offline Tory Street Lights

  • Full Member
  • ***
  • Posts: 134
    • View Profile
Thanks Keith, Yes it plays perfectly when played out from the sequencer, 700 active channels of Renard but handling more like 900 with some unused.  I have never seen anything like it when run from the scheduler!

Attached are the logs from last night.

I know there are some issues with file locations, as the data was copied from my sequencing machine to the show machine and for some reason, even though I have told the playout machine installation what the show folder is it is on both the sequencer and the scheduler, it is still looking in the incorrect folder on a non existant drive for the audio tracks on occasions!!

I am afraid I am more than stumped!!!

Terry

Offline Tory Street Lights

  • Full Member
  • ***
  • Posts: 134
    • View Profile
Sorry Guy's after a long zoom session with Keith, the delay is still the same after removing the Ledtrix driver utility.  Where to now!!

Terry

Update - test run and all is well, running nicely under manual control, not sure if anything has changed, only difference being Xlights sequencer is sitting idle in the background!

Terry
« Last Edit: December 01, 2019, 12:35:19 AM by Tory Street Lights »

Offline Tory Street Lights

  • Full Member
  • ***
  • Posts: 134
    • View Profile
Further update on the Excessive serial data delay seen as above.  Many, many thanks to Keith doing the hard yards attempting to sort out this issue for me.

At this stage, after running all evening as a public show, without the utility running my Ledtrix Panel everything ran perfectly, log file attached.  I then ran the schedule manually, with the Ledtrix utility running the panel, and that was fine, Log file attached, as well, plus a screen shot of Taskmanager and the command line utility running while operating.

The biggest change visible in Taskmanager was the processor activity, we watched it running at around 20% - 25% when "bug fighting" it now sits between 1% - 5% and only jumps to 10% when loading the next sequence in the schedule, and the "Turtle" only appears for about 3 sec's.

The only change I can remember making since the delay last appeared was moving some log reported missing files to where xschedule was looking for them.  If that was the cure, it seems the problem may have been created by ubiquitous finger trouble by the operator when moving all the data involved from the sequencing machine to the show machine  :-(   Mainly drive related I suspect, xLights is on "E" drive on the sequencing machine, while the show machine is using "C" drive, serious food for thought!!!

I be able to relax once the show has run a few times without issue, although at this stage it certainly looks hopeful, and positive.  Being of a "Certain Age", hardware trained and isolated here in NZ, I cannot speak highly enough of the software writers/designers making themselves available to dig us mere mortals out of deep holes when they are busy with their own displays, and work, heaps of thanks to all involved :-)

Cheers,

Terry
« Last Edit: December 01, 2019, 05:27:24 AM by Tory Street Lights »