Scheduler crashes
Printed From: Aurora
Category: Aurora Sequencer Software
Forum Name: Bug Reports
Forum Discription: This is the place to report bugs
URL: http://www.aurorashow.com/forum/forum_posts.asp?TID=1090
Printed Date: 24 May 2024 at 10:41pm Software Version: Web Wiz Forums 9.06 - http://www.webwizforums.com
Topic: Scheduler crashes
Posted By: dynawg
Subject: Scheduler crashes
Date Posted: 06 Dec 2010 at 10:35pm
This year (for the first time) I've had unexpected scheduler shut downs.
Always at different times during the show, and always different songs.
Here is the latest from the log file.
Aurora Error Encountered at 9/20/2010 8:12:33 PM Debugging Information: 339: Component '' or one of its dependencies not correctly registered: a file is missing or invalid Refresh Grid AuroraSequencer
Aurora Error Encountered at 9/20/2010 8:12:36 PM Debugging Information: 339: Component '' or one of its dependencies not correctly registered: a file is missing or invalid frmMain Loaded AuroraSequencer
System is WinXP - version is 69.. (or the scheduler shows 68)
D-lights hardware (ac16 & fireflies)
Still running 1.17 and 2.0 firmware. (Hard to think it's a firmware issue though.)
Any ideas where I should start looking? Is another piece of software running in the background starting up and interfering?
Many Thanks! Bob P.
|
Replies:
Posted By: Slinkard
Date Posted: 07 Dec 2010 at 2:01pm
I think I had that in the past.
Are all your songs in .wav format?
I think when I changed them to .wavs that fixed it for me. something with the conversion if I recall correctly.
------------- http://www.aurorashow.com/">
Coming soon www.computerizedlights.com
|
Posted By: dynawg
Date Posted: 07 Dec 2010 at 3:31pm
I just double checked, and yes, all are .wav files.
Last night the crash occurred towards the end of the third loop of the show. Aren't all conversions done and cached before the scheduler starts?
If it happens again, I'll try to get the error message that displays on the screen. (I haven't caught it before because I'm having to do the ctl-alt-del method to close the program as well.)
Thanks for the advice! Bob
|
Posted By: Slinkard
Date Posted: 07 Dec 2010 at 3:54pm
is you screen completely blacked out during the time that your scheduled show is actively running?
------------- http://www.aurorashow.com/">
Coming soon www.computerizedlights.com
|
Posted By: dynawg
Date Posted: 07 Dec 2010 at 4:07pm
Yes.
I did see another post today that mentions double clicking the window. I'll try that tonight.
|
Posted By: Jonathan
Date Posted: 07 Dec 2010 at 6:39pm
Delete Borealis.dat. It's in the Show folder. (The file will be regenerated.)
------------- ~Jonathan
|
Posted By: dynawg
Date Posted: 07 Dec 2010 at 10:43pm
Well, the double click does minimize the video screen, giving access to the scheduler screen, allowing a 'proper' shutdown.
And.... The show ran perfectly tonight. (of course it has for several nights in a row in the past week as well.)
I did make one 'shift' in the system tonight, and we'll see what happens in the following nights.
And I'll say again, thank you all for your help!
Cheers! Bob P
|
Posted By: dylanwalker
Date Posted: 19 Dec 2011 at 11:43pm
I am getting the same scheduler crashes (on win7 x64) and error messages that dynawg was getting in the log file about a missing component. I upgraded to 1.0.90 from 1.0.69 (using the full uninstall/reboot/new version install/reboot method) to avoid late night lights going on after all schedules had been completed. Was anyone experiencing this issue able to resolve it? I've tried re-booting and running the scheduler clean after deleting the borealis.dat file in the /show/ directory, but it doesn't seem to help. I'm using .wav files for my sound. I don't have any video and I don't get the old blanked screen (so there's nothing to double click), but I've tried running it with the scheduler window active or minimized and it doesn't make a difference. I've also tried running a "repair install" from the aurora installer and rebooting. Is pre-1.0.69 the only stable and dependable scheduler that doesn't lead to phantom lights turning on?
I'm all for exploring dmx in the future, but right now, I can't even get a scheduled light show on a single controller to run with any regularity without strange issues. I can't see investing more money into future versions of aurora if I can't depend on it to run my show.
|
Posted By: LightsOnLogan
Date Posted: 20 Dec 2011 at 7:38am
Error 339 is almost always a bad installation. Those experiencing error 339 about component registration should do a complete reinstall of Aurora. Follow this procedure exactly:
0) Backup all sequences
1) From the Control Panel Add/Remove Programs (not from the Aurora uninstaller), remove every copy of Aurora that shows up there.
2) Reboot
3) Install the latest version of Aurora
4) Reboot again
The two reboot steps are necessary to prevent the Windows MSI installer cache from "protecting" old files that it incorrectly thinks should still be present. Failure to follow these steps results in Aurora functioning with a crazy mix of components from its various versions. Even when it works the behavior can be unpredictable. Error 339 can happen when Aurora needs something that a newer version of the component provides, but the installer pulled a "protection" switch and forced the old version to persist.
The only other condition of error 339 is when another software product has switched out an Aurora third party dependency with an older version (such as videoedit.ocx, etc.).
The good news is that error 339 will be a thing of the past once we roll out the next version. The MSI installer is going away in favor of a registration free installation (completely portable, can even run from a USB drive without installation). Before public release we will be fixing the errors surrounding file format conversions that have been the big issue this season.
As for the midnight show start bug, even if you roll back to a pre-69 version that used to not do this, you will find that it does now. This bug began when a Windows Update altered a Windows API in a way that broke Aurora. I highly do not recommend running older versions of Aurora as not only do they not contain this bug fix, they also are not stable with modern firmware releases and do not contain fixes for bugs which led to data corruption.
Michael
------------- http://www.aurorashow.com/">
|
Posted By: dylanwalker
Date Posted: 20 Dec 2011 at 10:43pm
LightsOnLogan,
I followed your advice and did a complete uninstall through the control panel, reboot, complete reinstall, reboot. I still get scheduler crashes, regardless of whether I select VCP engine or D2XX. (With D2XX, though my fade-ons are not working correctly and instead appear as full ons). I also don't see the ordinary log file anymore after crashes (only a log file that relates to D2XX). There doesn't seem to be any information relating to the log file.
I tested running my sequence on loop directly from aurora sequencer and it runs indefinitely without any problems. How can I track down why the scheduler is crashing and resolve it?
By the way, in case this is relevant, I am not using the most recent 1.20beta d-light firmware, as this resulted in funny behavior for channels being ignored or stuck on even if I set the register 40 value to 1 as recommended by d-light.
thanks,
Dylan
|
Posted By: LightsOnLogan
Date Posted: 21 Dec 2011 at 10:24am
In build 90, are you using the "seamless" mode (the check box near the bottom of the edit show properties form)? Does enabling/disabling this setting improve the situation?
Michael
------------- http://www.aurorashow.com/">
|
Posted By: dylanwalker
Date Posted: 21 Dec 2011 at 11:41am
Michael,
Good idea, I will try out the "seamless" mode tonight.
I realize that I might have spoken too soon, however, about Aurora Sequence running the loop long term without a hitch-- Even the Sequencer eventually crashed after looping for an hour or so. Is there a way to enable verbose logging for the sequencer/scheduler, because I don't see any log files generated.
I am also wondering for those using aurora/d-light (non-DMX) what the most stable aurora version / d-light firmware combination is?
I had channels stuck on and missed pieces of sequences with aurora 1.0.69 and d-light 1.20beta1 firmware (with the 40 bit changed to 1), but I don't think I've tested the latest d-light firmware with aurora 1.0.90. Could these crashes be related to that at all?
thanks,
Dylan
|
Posted By: bc_34sa
Date Posted: 23 Dec 2012 at 6:48pm
did you fix this if so how? I am now babysitting my computer as it is doing the same thing shuts down randomly.
|
Posted By: Jonathan
Date Posted: 24 Dec 2012 at 9:01am
Sticky channels are from the firmware, and those aren't the only firmware related issues. Even the most recent firmware (as of this writing it's v1.20 with the EEPROM hack) has it's own issues, hence the "Change all ID's to 50+" recommendation. It is because of issues like these that Aurora 2 will be DMX only. Why? DMX is VERY stable once it is set up. I currently run a mix of v1.17 and v1.20. Both work fine for me except when they would lose their ID's (which stopped when I changed the ID to 50+).
Now, if a show won't complete a loop, I'd start by swapping out the audio on your sequences. If you are not using all .wav's (or .avi's), then that's the first thing to change. I have one sequence whose .wmv movie plays but then never progresses to the next song, effectively shutting down the show. Meanwhile, another .wmv movie plays fine. If you are already using .wav files, then move them and reassociate the sequences with them (or move the audiocache.dat file, either method accomplishes the same thing). It may help.
I also agree about using seamless mode (available in v1.0.90). You may want to create a blank 2 second sequence or other announcement to place in between your other sequences as the time in between sequences is near instantenous.
------------- ~Jonathan
|
Posted By: BigDPS
Date Posted: 26 Nov 2013 at 2:23pm
Hi guys. I would like to know what these errors are caused by? This is in Borealis:
Aurora Error Encountered at 11/26/13 4:18:02 PM Debugging Information: 3709: The connection cannot be used to perform this operation. It is either closed or invalid in this context. Aurora.Scheduler.RefreshTick.0 Aurora.Scheduler.ScheduleItem.AddSequence.0
Aurora Error Encountered at 11/26/13 4:18:18 PM Debugging Information: 457: This key is already associated with an element of this collection Aurora.Scheduler.Initialize.0 Aurora.Scheduler.Initialize.1
------------- http://www.aurorashow.com/">
|
Posted By: Jonathan
Date Posted: 26 Nov 2013 at 2:38pm
Ah, the "I'm never going to open again" error. The way to clear it is to delete Borealis.dat in the Shows folder. I think you may need also need to delete audiocache.dat as well (and reassociate it), but I'm not sure on that last one anymore, so start with Boreais.dat and go from there.
------------- ~Jonathan
|
Posted By: BigDPS
Date Posted: 26 Nov 2013 at 5:42pm
The 3709 happens when I try to load a sequence that has an avi in it. It worked all right last week but since last night, it isn't cooperating with me at all. I am so desperate that tomorrow afternoon, I will be wiping my whole hard drive and re install everything from scratch.
------------- http://www.aurorashow.com/">
|
Posted By: Jonathan
Date Posted: 26 Nov 2013 at 6:00pm
Are you running D-Light for the season or DMX? If you do decide to take such a drastic step, my suggestion is to NOT let Windows update itself. Windows updates have a history of breaking the environment Aurora runs in. The 2009 mid season update and subsequent scramble to develop new firmware comes to mind...
------------- ~Jonathan
|
Posted By: Jonathan
Date Posted: 26 Nov 2013 at 6:02pm
You can also try a WMV file. I had an AVI file that just refused to work no matter how many times I created it. Switched to a WMV and then it worked fine. Format Factory is a free conversion application and will convert files easily.
------------- ~Jonathan
|
Posted By: BigDPS
Date Posted: 27 Nov 2013 at 12:08pm
No I am running full DMX (which I was dead against it with fear at first) and have decided to give the 1.999 version a go to run the display. It can't be worst that the 1.185 can it?
------------- http://www.aurorashow.com/">
|
Posted By: Jonathan
Date Posted: 27 Nov 2013 at 1:21pm
In my opinion, and that is just me, if you are running DMX then the 2.0 Beta is far better than all the v1.X series with its various DMX hacks.
Yes, there are still a few bugs, but I have found that the 2.0 Beta is still more stable than the 1.X series ever was.
------------- ~Jonathan
|
Posted By: MarkDXB
Date Posted: 03 Dec 2013 at 1:42pm
hi, Just having an intial play with the new release.
Imported the sequences. I check the drawing and all the channels are there. When i play with preview i dont see any lights. IE they are not there.
did i miss something?
thanks
|
Posted By: LightsOnLogan
Date Posted: 03 Dec 2013 at 2:00pm
Try selecting "restart universes" from the universes menu. This is probably related to a known bug we are working on fixing.
Michael
------------- http://www.aurorashow.com/">
|
|