Progress bar

[Greg McKaskle]

How long does it take? Unless you are parsing the data or are doing unnecessary variable thrashing, I wouldn't expect it to take long.

If you can correlate the file size to the time, that will give you a message to put in the UI, and then animate it by counting down.

Personally, I'd focus on fixing it to be fast if possible.

Greg McKaskle

[siggy2xc]

I've already done a lot to make it efficient but it can take a good 5sec to load a 15sec file once you have a large number of user inputs that change often. I don't want to limit myself to 15sec though. If the progress bar is going to be a good size amount of work or slow down my code I don't think I will implement it. I was thinking maybe check to see if the array size changes while being written but I'm a little busy with preparing for the ACT testing I have in about an hour

[Greg McKaskle]

Good luck with the ACT.

When you are recovered from that, post your latest code, I can help see what is slowing it down.

Greg McKaskle

[siggy2xc]

Not 100% up to date, but this is pretty close to my current code. My current one is a little messy at the moment
http://code.google.com/p/autoflex-team1736/

ACT was a piece of cake

[Greg McKaskle]

I downloaded the 1.1 zip and it sounds like the Playback code is what you were talking about.

The thing to realize is that variable nodes are one of the most expensive memory hogs in LV. Wires are always better.

If it isn't guaranteed that the local used to give the datatype to the file read is empty, don't use it. Right click on it and create a constant. Empty the constant and wire that instead. Next delete the variable used to get the array size. Instead get the array size of the data coming from the file read. Similarly, the next sequence frame reads it again. Delete the variable and use the wire to index. Variables without much data in them aren't a big deal, but with a big array, each one matters.

Greg McKaskle