Thread: Strange VSA Behavior

Tweet

I'm working on another VSA routine for my three-axis skulls and am seeing some strange behavior:

My wife and kids spent all day creating open and close events for the jaws of all four skulls in synch with the song "This is Halloween."

When played from beginning to end....the first half looks fine...then the jaw movements start getting ahead of the soundtrack.

So I moved the start and stop markers to the spot where I first noticed it was out of synch, played between the markers, and the jaw movement lines up fine with the soundtrack.

Looking at the open and close events on the screen, though, it seems that they are opening and closing early (as the jaws appear to do when played from beginning to end.)

So....why would there be a timing difference in how the actual servos react to events when played all the way through versus when played between markers?


(I hope I was able to describe the behavior clearly enough....I'm not so sure.)

Couple of things to check, firstly goto the timing settings on the settings control and see if you have key frame checked.

Next under tools do a bandwidth check.

The problem could be that you are using a serial board, you have 4 skulls there with 4 axes each updating at 30 times per second thats 4800 commands per second, with each command taking maybe 6 bytes or more that 28,800 bytes per second.

Serial is SLOW, very slow, this is one of the reasons why DMX is so much better.

those would be the two problems... either your event stream is out of frame and the cumulative doesn't show up for a while, or you computer is lagging behind the audio track. few years back i might have thought it was a slow or low memory computer - but anything off the shelf in the last four years should run this easily enough... can you run the event line for just one skull? might help you lock the problem down.

Thanks guys. I will check these things out.