tdms performance

[National_Burritos]

Hi,

I would check out this white paper on AVI2 for more understanding of what is going on: http://www.ni.com/white-paper/14466/en/. Some more food for thought.

Keep us updated on progress!

[National_Burritos]

Hi,

I would check out this white paper on AVI2 for more understanding of what is going on: http://www.ni.com/white-paper/14466/en/. Some more food for thought.

Keep us updated on progress!

[xl600]

Thanks for the link.  I had actually read that through to understand where the older AVI vis had gotten off to.  It seems the AVI2 VIs have lost the ability to write the extra data (string) along with each frame?  That's a shame since that would have helpped my application.  I am starting to think in terms of:

• Stream frames to AVI2 Y800 (This is easily the fastest of the CODECs available to LabView RT)
• Post process frames and store the frame meta data into a TDMS file
• Use the TDMS file to index the video frames rather than store the frames

I'm currently working with NI on options for SSDs and more memory for my 8135RT so hopefully the combination will lead to the necessary performance.  Otherwise, I'll be stuck with only a few seconds of in-memory buffering

[National_Burritos]

I see you are working directly with one of our Applications Engineers now. Feel free to post updates for the community if you so desire, but all the best with troubleshooting through that avenue!