Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe After Effects Can’t render quicktime (.MOV) files to local hard drive?!

  • Can’t render quicktime (.MOV) files to local hard drive?!

    Posted by James Dinndorf on June 27, 2011 at 5:18 pm

    I’ve got one of the strangest problems that I can’t figure out.

    For some reason, After Effects and Sony Vegas both won’t let me render MOV/quicktime files to any of my local (internal) hard drives. However, I have no problems rendering them to my external USB drive. It’s only quicktime files that give me this issue. Up until now, I’ve just been rendering them to my external and then moving them onto my local drive(s), but it’d be nice to fix this problem.

    Thanks!

    -James

    P.S. I’ve been using AE cs4 & cs5, and Sony Vegas 9 & 10. The problem occurs on all versions.

    Oleg Burinsky replied 9 years, 11 months ago 9 Members · 12 Replies
  • 12 Replies
  • Anders Hattne

    June 27, 2011 at 7:36 pm

    All I can think of (on a Windows platform) is whether you HD is formated as FAT, as it compared to NTFS doesn’t allow you to copy or create files larger than 2gb or something. So once the file becomes that size, writing to it will be .. illegal and the render will fail.

    Could that be it?

    http://www.ardillamedia.com

  • James Dinndorf

    June 28, 2011 at 12:00 am

    I’m on windows 7 and all of my drives are NTFS formatted, including my external. When I click render, the file doesn’t even start to render, I just get an error.

  • Kevin Camp

    June 28, 2011 at 12:23 am

    can you create any new file on main drive? if you opened note pad and created a new text file, could you save that?

    Kevin Camp
    Senior Designer
    KCPQ, KMYQ & KRCW

  • James Dinndorf

    June 28, 2011 at 1:13 am

    Yes. I can render and save any other file on my drives. It’s ONLY quicktime (.mov) files that give me trouble.

  • Kevin Camp

    June 28, 2011 at 11:26 am

    is quicktime installed on the system?

    if so, is it the latest version?

    Kevin Camp
    Senior Designer
    KCPQ, KMYQ & KRCW

  • Kevin Camp

    June 28, 2011 at 11:59 am

    [Kevin Camp] “is quicktime installed on the system?

    if so, is it the latest version?”

    — sorry, that’s obviously not the problem… you can render quicktime, just not to the main drive (…to little sleep today)

    are you always trying the same codec for the mov files? maybe try another codec… lossless animation, photo-jpeg…

    i’ve really never heard of anything like this…

    i know win7 introduced a bunch of security measures to try and keep the average user from installing malware… the only thing i can think of is that win7 (or maybe some other anti-malware software) has somehow flagged quicktimes as risky files.

    maybe there is a way to change the security settings to be less restrictive, or get higher user permissions, like administrator.

    Kevin Camp
    Senior Designer
    KCPQ, KMYQ & KRCW

  • Madhanraj Dharmaraj

    February 7, 2012 at 5:46 am

    I am also Getting same error while render QT.

  • Samuel Were

    October 25, 2012 at 12:04 pm

    Strange! I just installed new disk in my computer and I also can’t render QT to it! I still can render QT to my all other disk. I am also can render to other kind of files (like JPEG sequence) and write them to my new disk.
    Help please!

  • Rob Maybury

    December 6, 2012 at 5:56 pm

    Its a strange one but try renaming your volumes. Changing the name of my drives from ‘Local Disk’ to something else worked for me.

    I’d been struggling with the exact same problem for over a year on an extrernal raid array via e-sata – I could render QT to all my local drives but not that one. Every other file type was fine.

    Just installed a new local raid drive and got the same problem – re-naming the array cleared it up.

    Think it’s a Quicktime bug – hope it works out. Be interested to see if it clears it up for you guys..

  • Yan Roomush

    January 14, 2013 at 4:37 pm

    I approve. Changing the Volume name to a different one fixes the problem.

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy