QuickTime 7.6.2 discovered something frustrating

cal79 wrote on 9/11/2014, 4:57 PM

Can anyone help, i've got QT 7.6.2 installed on my system.. i've discovered something.. I can't get VP13 to successfully render out a quicktime file to any hard drives on my system other than my C drive (OS drive).. whats going on there?

I render to external drives all the time using all other formats and codecs.

Thanks,
Cal.

Comments

fldave wrote on 9/11/2014, 5:44 PM

Does V13 still require that old QT? I thought it was ok to use the latest since v11 or v12?

videoITguy wrote on 9/11/2014, 6:38 PM

Win 7 or greater? Using user account control? Are you the sole admin and owner of the file system? Did you install Quicktime after or before VegasPro? Did you install both applications as the admin? What codecs if any are you working with BlackMagic install?

NormanPCN wrote on 9/11/2014, 7:04 PM

I have QT 7.7.4 installed. Vegas Pro 13 b373 and I can render Quicktime DNxHD and PNG codecs to my D:\Renders\ folder.

FWIW, My QT 7.7.4 was installed long before VP13 was installed.

wwjd wrote on 9/11/2014, 8:50 PM

I think you can only render MOV to disk drives with no SPACES in their names.

Yes, DVMBEST THING EVER, but I had that problem.

Former user wrote on 9/11/2014, 8:58 PM

Saw on Creative Cow that they are suggesting going back a version. Something wrong with that version of QT.

NickHope wrote on 9/12/2014, 2:18 AM

I found a limit on the length of Quicktime filenames in Windows. Could that be related?

cal79 wrote on 9/12/2014, 3:31 AM

I am the sole admin guys I don't have any user accounts, Quicktime was installed after Vegas.. drive names are default no spaces.. this is really weird?

I can try a shorter file name regarding that 'limit on length of QT file name issue' but I don't think thats related.. This really is bizarre. Anyone running QT 7.6.2 on VP13?

Can you share what QT version you are all running?

Thanks,
Cal

musicvid10 wrote on 9/12/2014, 6:48 AM

Try disabling all antivirus and reboot also.
You have a new version of Vegas. Therefore, you shouldn't "need" 7.6.2
7.7.1 is fairly reliable, according to some.

Tom Pauncz wrote on 9/12/2014, 8:13 AM

I have 7.7.5 and have no issues on VP13, VP12, VP11....
Tom

videoITguy wrote on 9/12/2014, 7:51 PM

cal79 - I asked if you are running user account control service - which likely you are - it is the default. Perhaps you misunderstood the question and further the implication.
Quicktime installed after VegasPro is a no-no and you have to start over with the correct installation sequence.

larry-peter wrote on 9/12/2014, 9:16 PM

wwjd is right. I had the same thing happen. The OP said the volume names were "default." If your volume is named "Local Drive," or "Local Disk," which is what new drives defaulted to on my system, QT won't render to it. Try renaming your volume. Seriously.

dxdy wrote on 9/13/2014, 7:29 AM

Right, neither the file name or the subdirectory name can have any spaces.

cold ones wrote on 9/14/2014, 8:33 PM

A shot in the dark, but I've had this problem with Quicktime renders in the past:

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=802144

cal79 wrote on 9/15/2014, 5:02 PM

Thanks to all you fine folk for your help and support.. that's the problem fixed now.

My Drives are labeled as 'New Volume' by default, and like a few of you already mentioned.. because of the spacing in the drive name.. it wouldn't let me render a QuickTime file.. Seriously like how ridiculous is that? is this a Vegas or QuickTime bug? I have no idea how someone discovered it was related to name spacing but i'm very grateful for the fix. Thanks again for your help guys, all systems go again!

Also upgraded to Quicktime v7.7.5, running fine on VP13

Cal