Vegas 12--External preview to firewire not working

Maestro wrote on 11/11/2012, 1:02 PM

I'm hoping someone can help with this. The short story is that previewing to an external monitor via Firewire doesn't work in Vegas 12. Here's what I know:

Preview Device in Vegas 12 *does* show the OHCI compliant device. It says it's hot pluggable and the device IS connected. The device is a Canopus ADVC-100.

When I switch over to the external monitor, all I get is black, not even the tell-tale "blip" in the video when the monitor starts getting a signal. Basically, nothing happens. No error, nothing.

I *can* do a Print To Tape within Vegas 12. Everything works. I can see the video just fine on the external monitor.

Previewing to an external monitor in Vegas 11 64-bit works just fine--even along side Vegas 12.

This has also been tested with Vegas 11 not installed.

Someone please tell me this is a known issue. I never thought I'd see the day when Vegas 11 works better than Vegas 12. But there you go.

Cheers,

-Brent

Comments

set wrote on 11/11/2012, 8:23 PM

Brent,

May I know what is your project settings?
also, what media do you use ? is it DV 4:3 or 16:9 ? also, is it similar aspect ratio with your ext. monitor display ?

Try add Video-Output Level (or any FX). If the picture appear on monitor, then we found the same bug.

I caught similar issue with yours before.

Maestro wrote on 11/11/2012, 11:17 PM

NTSC DV 4:3 using Sony DV codec. The aspect ratio of the reference monitor matches the project settings.

Well, you nailed it. I add any video FX and it will show up in external preview, albeit with the frames recompressed. I guess I'll open a ticket for what it's worth. Maybe in two months someone at Sony will get around to reading it and reply back with a "please reinstall Vegas" form mail.

Pardon me if I sound cynical. I've been down the support road with Sony many times now.

set wrote on 11/12/2012, 12:10 AM

Nothing to worry about Brent.

Glad you found it too, so thanks!
I have just sent the ticket regarding this issue too.
'Small' problem which can lead to huge confusion...
My question on that thread now is answered too.

Just hope so - as there are so many serious bug in VP12 that still need to be addressed.