Clips from 2 HDR-AS15 cameras no longer 3D pair

DDDyson wrote on 7/25/2013, 2:44 AM
I have two Sony HDR-AS15 action cameras I have used for stereoscopic filming. I have previously successfully paired several clips from them into stereoscopic subclip, and it has worked just fine.

Yesterday, Vegas suddenly refused to pair two new clips. Just as before, I placed the two clips on two tracks in the timeline, right click -> Pair as a Stereoscopic 3D Subclip -> nothing happens - the clips remain unpaired. (but strangely, the Use Count of the clips increases in the media pool view)

All new test clip pairs I have recorded after yesterday afternoon, have refused to pair since.

All the clips I have recorded before yesterday afternoon, can still be paired just as before. Here's the proof Ive already done it before:
http://archive.org/details/JulianLaynPianoStockholm20130713

- The settings between the cameras are identical. All videos are 1080p, 60 fps from both cameras. These specs look the same in Vegas media pool as well
- Both cameras have the same firmware version
- The video files can be viewed on any player, and display normally in Vegas Movie Studio
- ..... the only thing is, that the clips recorded after yesterday afternoon refuse to pair as a stereo 3D subclip. (?!)

I'm dumbfounded. What could possibly have changed, or gone wrong?

I have already attempted to reset the cameras, and format the memory cards. The video files don't appear broken in any way, but I may need some video analyzer software to see if something is still broken somewhere.

I have tried the pairing both in Vegas 11 and a trial version of Vegas12 (x64). Same problem on both.

I can provide a pair of clips that can be paired, and ones that cannot be paired, if you Vegas developers want to take a look at them.

Comments

DDDyson wrote on 7/25/2013, 2:56 AM
Just tried it with 30 fps clips instead of 60 fps. The problem persists.
DDDyson wrote on 7/25/2013, 3:27 AM
After later test, VMS 11 now crashes when I attempt to pair newer test clips.

I guess that's progress... but unfortunately it does not produce a bug report I could send over. I can get one from the Event Viewer if needed, however.

I have already earlier tried un- and reinstalling Movie Studio. Is there a way to do a complete 'purge' to delete all residual files before reinstalling it?

I'm about to begin production and I would very much prefer not to be held back by this software failure. :(
DDDyson wrote on 7/25/2013, 4:05 AM
FYI: I tried installing VMS 11 to my laptop (Win7 x64). Fresh install, hasn't been installed there before.

The new clips 3D pair normally.

This suggests that something is broken in my desktop Win7 x64 PC, which the Vegas 11 un/reinstall did not fix.

Possible difference: the K-Lite Codec Pack has been installed on my desktop PC. But this was already done several days ago. It does not explain why clips from before yesterday still pair, and all new clips refuse to pair.
DDDyson wrote on 8/11/2013, 1:55 AM
It wasn't the K-Lite Codec Pack. I installed it on my laptop as well, and it didn't break anything.

Vegas 11 now crashes if I attempt to 3D pair two new clips on my desktop PC, instead of "do nothing, add use count". Alas, it doesn't actually generate a crash report I could send over to the developers. :(

What's really odd is that I can still pair older clips, but newer clips refuse to pair. What's the difference?
DDDyson wrote on 8/26/2013, 2:44 PM
Thanks Markk655, I'll try that next!

The reason I bounce the topic now is that I just tried this:
- I took a pair of clips that was unpairable on my desktop PC, and tried paring them with Movie Studio on my laptop. They paired fine.
- I saved this as a Movie Studio .vf project file, and tried opening it on my desktop PC. It opened and played fine.
- Also, when I attempted to pair the clips in this project again on the desktop PC (creating another subclip of the same media), Movie Studio didn't crash, and they paired just fine.

This kind of suggests something goes wrong in the import phase, rather than the pairing phase.

But yeah, I'll try that full, clean un/reinstall a couple weeks from now, when I have a free weekend for the time window it requires. Thanks for the tip!