No Video out Firewire

[rgm]

hey everyone,

for two days now I have a really strange problem:

when I start a session from scratch with a video track (DV) everythings is working fine.
when I save and reopen the session the video won't play via firewire but only in the quicktimewindow. even deleting the videotrack and reimporting the video will not do.
I tried trashing all preferences / databases. I tried running the harddisk doctor program.

any ideas what the problem could be?

will I have to setup the whole system again?

thanks for your thoughts!

Raul

ProTools HD3 with PT 10.3.0. OSX 10.6.8.

[Chief Technician]

Originally Posted by rgm

when I save and reopen the session the video won't play via firewire but only in the quicktimewindow. even deleting the videotrack and reimporting the video will not do.

Is the Video Out FireWire selection under the Options menu checked off or selectable when this happens?

[rgm]

yes, the video out firewire option is selectable.
the screen will stay black.

[Chief Technician]

So then the software is configured properly and you just do not see any picture on your external monitor, correct?

[rgm]

yes, the software is installed properly.
I see the picture when I create a new session with a videotrack.
I can switch between quicktime window and firewire monitor without problems.
only after closing and reopening of the session the firewire monitor gets no picture. the quicktime window is still working. even deleting the video track and importing a new videotrack does not work.

[Rikk]

Are you sure the video is DV codec?

[rgm]

yes I am sure. I only work with DV files in PT.
I set up a complete clean installation today but I still have the same problem!

[Rikk]

Does the deck nor FireWire device work with different software? How about a different file?

[Chief Technician]

This sounds like an initialization problem. It might be something with the session document that once it is saved and closed, the FireWire output is not made active when the same session is reopened.

Have you logged this as a bug at protools.ideascale.com?