An odd quirk under Windows 7 64-bit & Vegas 11 (Build 511 & etc)
I hope most of you will never experience this, but I'm going to document this workaround for the one person who might share my misfortune. Recently, all my Quicktime renders (on two different systems) failed immediately. No one else was experiencing this problem, it seemed, but me. Now I think I know why.
For years, I've rendered all my movies to a folder on my X drive. Also residing on X drive is another folder that I share, and for simplicity I've mapped this folder to our network as T drive.
All Quicktime renders in Vegas 11 fail when trying to render to X drive. Even stranger, only Quicktime fails: all other codecs render with no problem. The fix is to disconnect the mapping for T drive, and then Quicktime renders as per usual.
Moral of the story: Quicktime won't render to drives that are mapped twice like this. (The devil is in the details: Quicktime WILL render to this drive, but only to the LOWEST drive letter of a drive that's mapped like this.)
And how was your day?
I hope most of you will never experience this, but I'm going to document this workaround for the one person who might share my misfortune. Recently, all my Quicktime renders (on two different systems) failed immediately. No one else was experiencing this problem, it seemed, but me. Now I think I know why.
For years, I've rendered all my movies to a folder on my X drive. Also residing on X drive is another folder that I share, and for simplicity I've mapped this folder to our network as T drive.
All Quicktime renders in Vegas 11 fail when trying to render to X drive. Even stranger, only Quicktime fails: all other codecs render with no problem. The fix is to disconnect the mapping for T drive, and then Quicktime renders as per usual.
Moral of the story: Quicktime won't render to drives that are mapped twice like this. (The devil is in the details: Quicktime WILL render to this drive, but only to the LOWEST drive letter of a drive that's mapped like this.)
And how was your day?