v7.3.1cs2 - Two (2) Video Related Issues

[Chief Technician]

My system: Quad 2.5GHz G5, 4.5GB RAM, OS X v10.4.8, HD|2 Accel, 192 I/O, SYNC I/O, Keyspan USA-28x, SIIG FireWire card (the qualified one), Mojo SDI

Issue 1 - After loading in 1.75 hours of audio and video, I got an error and couldn't revive the lost video clip (which has happened before), which resided on it's proper drive (a drive other than the audio drive or Macintosh HD) taking up 16.5 gig. Another similarly configured system experienced a similar glitch, but WAS able to drag the file back into Pro Tools and use it. Unfortunately, the video file was somehow corrupted... so I had to start all over again for another 1.75 hours.

Issue 2 - Dragging a DV stream into Pro Tools and dropping on the video track resulted in the WRONG CLIP ending up on the time line. The session continued to reference the same file on a different disk attached to the system. Even though we were dragging the correct file to PT- the video track wouldn't stop thinking it was the same file from its previous location. This caused massive confusion for all during the session. The solution seems to be to bring in video via the "import" command rather than dragging and dropping.

Has anyone else had this happen to them? Any information on these issues would be appreciated.

Thanks for reading!

[DigiTechSupt]

1. What is the error message that you got?

2. Yes, this is a known issue and is logged for a fix.

[jeremiahmoore]

Yes - I've seen the wrong clip thing nearly daily...

Workaround is to use "Import / Video" in File menu. Cmd-Opt-Shift-I

-jeremiah

[Chief Technician]

1. What is the error message that you got?

I wasn't operating the system at the time, so my information is sparse. Error messages included phrases such as "picture playback error" or "bus error". When the engineer tried to import the video file that was recorded but not placed upon the timeline when stopping, the error message essentially said "sorry, there are no video frames in this file".

2. Yes, this is a known issue and is logged for a fix.

We are anxiously awaiting v7.3.1cs3! Thank you for the information.