Aurora Support Forum: Known Issues with 0.2.0

Well, I bit the bullet and started over... I really should learn to save more often! I would still like to know what the possibility is of recovering lost work.

Carey

Being a pre-release version not all of the features are completed and/or some things are broken. Below is a list of things we know about and how to avoid them:

The sequencer's lightbulb (playback to lights) tool will throw an error if no adapter is connected and/or the COM port settings in Settings/Network are incorrect.
The playback button in the sequencer will occasionally stop functioning. To resolve this File/Save your current work, close Aurora, re-open Aurora, and then re-open your sequence. This unavoidable annoyance is a known issue that will be resolved in future releases.
Minimize button in scheduler does not work and results in a nasty set of errors that eventually require a complete restart of Aurora. To avoid this simply do not attempt to minimize the scheduler
Attempting a paste that extends beyond the end of the song results in erased/wrapped events. To avoid this make sure there is room available for your paste before performing the paste operation.
Vista users: It is recommended that you change the playback engine in Settings/Playback Config from MSDXM to DirectShow.
All users: If playback to the lights appears to be ahead of the music compared to how it appears in the preview visualizer, it is recommended that you adjust the frame offset in Settings/Playback Config from the default of 5 to a lower value such as 2 or 3.
There is a momentary "heartbeat loss" between songs during show playback. This will conflict with a bug in older D-Light firmware versions (around 1.6 to 1.9) where the controllers occasionally stop responding and require a power cycle. To avoid this it is recommended that the newest firmware version be used on D-Light brand controllers. A workaround for older firmware version support is being tested by the beta group.
Attempting to edit a schedule in the scheduler while the scheduler is in the started/running state will result in a BOF error at the end of the show. To avoid this make sure the scheduler is stopped (red button) before editing the schedule.
The right click option for "Channel Properties" does not do anything. Use the left click on a channel name method instead.
If you delete the contents of the /Cache directory the app may fail to rebuild the cache properly if there are any short (< 30 second) audio files.
Ramp durations between 1.9000 and 1.9999 seconds will not output to the lights properly. The workaround is to use a slightly shorter (1/10 second) ramp duration.
If your display properties have been set to Large/Extra Large fonts instead of normal fonts, Aurora Scheduler may fail with Error 5. The workaround until this is fixed is to use Normal fonts instead.

Edited by LightsOnLogan - 31 Dec 2007 at 6:47pm