@ExactImage: I think 20 seconds would be plenty - enough to evaluate the playback without being fooled by frame caching.
@Roberio: I don't speak for product management, but in my opinion, probably not. Reason being, our 422 MXF support in CS 5.x was not directly implemented by us, it goes through Main Concept components. Consequently, to get a fix, we'd need to take a new drop of the Main Concept SDK. This impacts not just 422 MXF support, but all MPEG support in the product, so it's a more risky proposition, one that generally doesn't happen in a dot release. Evaluating a new SDK drop is something that normally happens during a regular product cycle.
I can vouch that the audio looping bug is gone in CS6, as I was asked to test a file with this problem against my implementation. Going forward, our 422 support will be easier to maintain, as we do all the file handling/container navigation, and only rely on using the Main Concept SDK for the actual essence decoding, so we'll have more control for fixing issues such as the looping audio bug.
