Author Topic: xLights 2018.55 and 2018.56 "Not Responding"  (Read 1182 times)

Offline Sourdough

  • Newbie
  • *
  • Posts: 5
    • View Profile
xLights 2018.55 and 2018.56 "Not Responding"
« on: December 18, 2018, 10:17:08 AM »
I go through frequent times with xLights "Not Responding" when working with two sequences converted from LOR via the Import Effects and an xmap I created. I really can't do much of anything without going through another Not Responding period. Those periods have been as long as 15 and 30 minutes EACH. It makes it pretty hard to get anything done. Even just loading FPP Connect takes more than 10 minutes.

I've checked my computer resources and all are under 70% or so. But when Not Responding the CPU is still using about 10% and the memory has about a gig (I have 8 gig RAM). I am using a laptop with an Intel I7 processor (I think 7th gen), 8 GB RAM and have 40% or so of my disk space left.

I have deleted and reloaded xLights. I'm using the current 2018.56 (previous versions had the same issue). I've tried it on a different computer,a 9 month old Dell with an I5 and 8 GB; it had the same issues. I've even recreated the sequences from scratch with the same results.

My first thought is always Operator Error. But I've tried the things that I know to resolve it.

HELP!

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: xLights 2018.55 and 2018.56 "Not Responding"
« Reply #1 on: December 18, 2018, 10:20:58 AM »
And what is your experience with sequences created in xLights only?

Offline Sourdough

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: xLights 2018.55 and 2018.56 "Not Responding"
« Reply #2 on: December 18, 2018, 10:40:29 AM »
They seem to be OK. But FPP Connect is still an issue with xLights sequences.

Offline Sourdough

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: xLights 2018.55 and 2018.56 "Not Responding"
« Reply #3 on: December 18, 2018, 10:43:33 AM »
By the way, this is a really basic display. One MegaTree (16x50), three snowflakes (Boscoyo) and 4 mini trees.

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: xLights 2018.55 and 2018.56 "Not Responding"
« Reply #4 on: December 18, 2018, 10:55:17 AM »
When you do an import of LMS files it creates thousands of tiny node level effects.  It doesn't create the best representation of our program.  Those times you mention are crazy long.  Have you inspected the log file to look for indications of a problem?  I don't use FPP connect so not sure how that works but it should be quite fast.  I'd have to believe you still have a rendering operation occurring if its taking that long.

Offline Sourdough

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: xLights 2018.55 and 2018.56 "Not Responding"
« Reply #5 on: December 18, 2018, 08:25:43 PM »
Thanks for your reply. I had to leave and run some "errands" so this reply is tardy.

I want to make sure you understand that I REALLY appreciate what you do and the product that is xLights.

I also am not surprised that conversion from LOR is not the strength of xLights. I had suspected as much. I have forced the issue this year (taken long breaks, gotten coffee, etc) while working with the LOR converted sequences. I suspect that I will move on to new sequences over the next year.

As for FPP Connect taking a long time just to load (I timed it at 3 minutes today when the computer was otherwise idle), I also suspect that somehow just having the LOR converted sequences has slowed EVERYTHING down. I actually had to uninstall it on my second computer because other unrelated things were locking up. Uninstalling xLights solved the response problems on that computer.

Again, thanks for all you do. I'll simply turn the page and move on next year.

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: xLights 2018.55 and 2018.56 "Not Responding"
« Reply #6 on: December 19, 2018, 06:02:26 AM »
Well we have hundreds of users that aren't having those problems.  It's usually fixed by a better PC.