Anyway, it looks like we have the subscript errors and crashes from 0.5 taken care of and behind us.  Right now we are working on fixing the importers.  When complete a 0.6 release will appear to replace 0.5.

 

ETA: Wednesday or Thursday.

 

I have a short leaping arch in my living room that is connected to an acx16 channels 1-8.

The controller is using the 1.14 version of the acx16 firmware.

 

The reason I was trying to copy and paste a w2e channel was to set all the channels it the arch to follow the music. I can have the program generate all the channels, but I thought a copy and paste would be faster.

 

Sorry if the .1 second timing caused you some concern, but I did assume that the controller will not accept the commands accurately when placed under stress.

 

My WAG is the firmware needs updating.

 

Were both of these channels within the same 8 channel bank (e.g. 1-8, 9-16) or were they in different banks?  What firmware version?  "In the lab" I can maintain 2 channels to an ACx16 v1.13 at 25FPS.

 

Re: copying... It is best not to attempt to copy/past a W2E section as (at the moment anyway) Aurora will want to put down a timeline marker for every intensity change.  Instead, just use the W2E tool on the other channel as well.

 

My instructions for copying off screen are valid for all other tools though.

 

Update: Beta testers have not broken 0.5.1 it yet... I'm going to fix the importers over the weekend.  We should have a fix for the major issues early next week.

 

For those who want to downgrade, you will need to do an uninstall from add/remove programs before reinstalling 0.4.  Your sequences will remain intact, but you may have problems viewing any of the circle based drawing elements made in 0.5.  0.4 does not recognize the new data fields (such as radius, aspect, arcstart, arcend) added for support of these objects in 0.5.  The results may be truly bizarre so it is recommended that (if 0.5 will let you without crashing) you remove these objects from your sequence before downgrading to 0.4. 

 

For those with demo discs from TCL who do not have access to 0.4, please be patient... we will be publishing a 0.6 release very soon (within the next week).

 

For the technical types: What we have going on are some bad memory pointers in the code which are allowing data to overrun one data table and into another whenever the data being written happens to reside on a data page boundary.  Most of the time this results in simple data corruption when one table overruns into another but occasionally the page boundary is adjacent to another thread which results in an instant crash of the application (in the old days these were common causes of the General Protection Fault messages).

 

Unfortunately, due to the nature of this problem, 0.5 looked good when I gave it to the beta testers and didn't start acting up until after the release emails went out.