I am running 3.10.12 advanced with Lor and it is lagging badly, ya I know I should have been using xlights to run my show the message I get is cannot allocate memory for event table, the DMX listener closes and then reopens it says DMX listener error 3 comm winsock error 10053, connections aborted due to time out or other failure, if this keeps up I could win most tackiest display this year.
I was having similar issues. Invest in a Falcon Pi Player. Converted my LOR sequences through xLights into F.seq Loaded up the pi player and now no lagging at all. The Pi is about $35 for a basic one. http://falconchristmas.com/forum/index.php/board,8.0.html
Don Gillespie wrote:I am running 3.10.12 advanced with Lor and it is lagging badly, ya I know I should have been using xlights to run my show the message I get is cannot allocate memory for event table, the DMX listener closes and then reopens it says DMX listener error 3 comm winsock error 10053, connections aborted due to time out or other failure, if this keeps up I could win most tackiest display this year.
Not sure if it'll help, Don, but have you tried to patch the show player and comm listener with the 4gb patch utility? I did this with all the LOR executables and haven't had a problem yet.
What is the 4gb patch first I have heard about it
Robo wrote:I was having similar issues. Invest in a Falcon Pi Player. Converted my LOR sequences through xLights into F.seq Loaded up the pi player and now no lagging at all. The Pi is about $35 for a basic one. http://falconchristmas.com/forum/index.php/board,8.0.html
Thanks I will look into anything at this point
Here's a link to a small application which will take a 32-bit application (which all the LOR apps are) and patch it to allow it to access 4GB of RAM instead of just the 2GB that it could normally access. I've run this on all the primary LOR applications (Sequence Editor, Show Player, Comm Listener, Visualizer, Control Panel). The first thing it does is to save a backup file of the original executable, in case it doesn't work. Then, it makes the patch and saves the executable with the same name as before so the rest of your system will be none the wiser.
http://ntcore.com/files/4gb_patch.zip
Knock on wood, I haven't had any trouble with it. And LOR actually runs very well. I have over 12,000 channels in my sequences and haven't had a crash of the sequencer or show player yet. I restart my PC (automatically) every morning (3:00am) to make sure RAM is clear. No hiccups yet.
That said, if things remain unchanged at LOR, I'll likely be using something else next year. Now that the show is up and running I'm gonna start learning HLS and get a Raspberry Pi so I can tinker with the Falcon Pi Player as well.
aaron1 wrote:Here's a link to a small application which will take a 32-bit application (which all the LOR apps are) and patch it to allow it to access 4GB of RAM instead of just the 2GB that it could normally access. I've run this on all the primary LOR applications (Sequence Editor, Show Player, Comm Listener, Visualizer, Control Panel). The first thing it does is to save a backup file of the original executable, in case it doesn't work. Then, it makes the patch and saves the executable with the same name as before so the rest of your system will be none the wiser.http://ntcore.com/files/4gb_patch.zip
Knock on wood, I haven't had any trouble with it. And LOR actually runs very well. I have over 12,000 channels in my sequences and haven't had a crash of the sequencer or show player yet. I restart my PC (automatically) every morning (3:00am) to make sure RAM is clear. No hiccups yet.
That said, if things remain unchanged at LOR, I'll likely be using something else next year. Now that the show is up and running I'm gonna start learning HLS and get a Raspberry Pi so I can tinker with the Falcon Pi Player as well.
This is worth a shot, I have thought about changing my dmx channels which are currently an lms file and see if I can export an clip board through xlights I think the clip board is a smaller file. I am going to download the 4 FB today another question Aarron does the down load ask you where you want to put it, and how long between sequences are you allowing when the show is running, currently I am using. 2 seconds thanks
Are you noticing the lag through the sequence player or from the show player? I am running 3.10.6 and gave up on playing them through the sequence editor due to lag due to large pixel counts. I play them back through the show editor and they work perfectly, and load only in a few seconds after I checked the box "Use Compressed Sequences".
Don Gillespie wrote:This is worth a shot, I have thought about changing my dmx channels which are currently an lms file and see if I can export an clip board through xlights I think the clip board is a smaller file. I am going to download the 4 FB today another question Aarron does the down load ask you where you want to put it, and how long between sequences are you allowing when the show is running, currently I am using. 2 seconds thanks
If I recall, Windows will ask you where you want to put the download. It doesn't have an actual installer, though. So, once it's downloaded, you'll just need to open the zip file and run the 4gb patch application from wherever you download it. When you run it, it will open up a window so you can tell it which application you want to patch. You'll go to the location where all the LOR executables are located (usually something like c:\Program Files (x86)\Light-O-Rama\). You'll choose a file to patch. It'll save a backup copy and then apply the patch to the original file.
I don't have any time between my sequences when running the show. I load one file immediately after the previous one is finished. Also, i have it set up to actually load all the files before theshow starts instead of as they're needed. I'm using compressed files, most of which are in the 100MB - 200MB size range, if you're looking for some comparison.
Hope this works out for you. Not sure whether it'll fix the lag or not, but more memory never hurts.
Thanks Aaron looks like this has it fixed ran it for a couple hours and so far no issues tonight will tell the tale
