Value Historian

This update fixes playback, which previously gave slightly erroneous output for a given input time.

Also applied a few other small optimizations, so it should be a bit snappier (probably not noticeable though).

This update to ValueHistorian adds named input support, and fixes a few bugs when partially re-recording.

This is hopefully the last beta before public release, so please hammer on it, and discuss any last-minute features/bugs so they can be discussed and addressed.

http://kineme.net/Discussion/ForumDiscussion/ValueHistorianPatch20090105...

This update to the Value Historian beta improves performance while recording, and adds Samples/Duration outputs.

When recording over a previously recorded time span, only samples after the initial re-record time are discarded (previously, all samples were discarded). This means that if you have a 0-10 second recording, and you start recording at 7 seconds, only data from 7-10 is discarded.

Please continue discussing at http://kineme.net/Discussion/ForumDiscussion/ValueHistorianPatch20090105betadiscussion

This is the initial beta release of the Value Historian patch. Please read the following description/instructions.

The Value Historian patch records values for later playback, similar to the queue patch.

Notable differences:

• The patch saves its contents with the composition, so the same values will be present when you re-open the composition at a later date.
• There are a variable number of inputs, controllable through the inspector panel.
• You can import/export its current state to plist files.

Notable Limitations:

• If you record Colors, Images, or any custom fancy type (QCStructures, Textures, Kineme3D objects, etc), it will function, but saving the composition will fail (and exporting the patch's state will fail). This is a limitation of property lists (Strings, Numbers, and bools work well). QCStructure support will probably be added in a future beta, before release.
• If you record data at a time earlier than the latest recorded data, it will remove all currently recorded data. (So, if you recorded stuff from t=0 to t=10, then recorded at t=13, you're ok. If you recorded at t=9, it would erase everything). This needs to be discussed some (the purpose of this beta release), and then refined.
• Recording isn't particularly memory-space efficient, so recording for very long periods of time will harm performance, and eventually crash QC. The length of "very long periods of time" depends on the number of items recorded, the type of data recorded, the framerate of the composition, and lots of other factors -- be careful before using this in a live performance setting.

Discuss here: http://kineme.net/Discussion/ForumDiscussion/ValueHistorianPatch20090105betadiscussion