-
Larry Brewer
August 26, 2010 at 1:10 amBingo! Yesterday’s Quicktime upgrade messed up my Sony quicktime rendering. Now everything is back to normal with 7.6.5.
BTW… Earlier today posted a question regarding ProRes 422 codec and how I might render those files from Vegas. I guess it can’t be done. Is that your understanding?
And thanks for the quicktime suggestions.
-
Sam Caino
August 26, 2010 at 1:18 amWow, I’m surprised that bug exists in version E. They fixed the .mov rendering black one in C, I believe. I guess I shouldn’t be surprised, every bug fix released has a new set of bugs the previous release didn’t. That’s why my department is stuck on 9b.
As for ProRes 422, I have no experience with the ProRes codec so I won’t be of any help to you. I seem to remember people on the boards saying ProRes is the preferred codec for interchanging between Final Cut and Vegas though.
-
Larry Brewer
August 26, 2010 at 1:38 amGuess what? The problem is back.
It goes like this… I have a 5 min animation, delivered to me 1348 x 768 avi. And everytime I try to render it to quicktime, it screws up my quicktime / Vegas relationship. The render ends even before it begins. Render window says 100% complete, but no file.
I can reopen Vegas, put up up another video clip, any resolution, and attempt to render quicktime… nothing.
As crazy as it sounds, the 1348 x 768 avi file is having an effect on the Vegas setup, or the quicktime setup, or both.
I have never been this puzzeled before.
I’m going to reinstall quicktime.
-
Sam Caino
August 26, 2010 at 1:44 amThat’s wild. If this .avi is the cause of the problem, my approach would be to convert it to something else in a program like handbrake before importing it into vegas.
-
Larry Brewer
August 26, 2010 at 1:59 amDidn’t work. Gotta rethink this
I’m going home. Tackle this tomorrow.
Thanks for the help.
-
Larry Brewer
August 28, 2010 at 8:55 pmThe issue has been resolved. A complete and clean uninstall and reinstall of Sony Vegas, DVD Arch, and Quicktime.
This clean uninstall involved using regedit and deleting everything including the folders.
. -
Sam Caino
August 29, 2010 at 4:47 pmGood to know. I’ve done that full uninstall before. It’s not fun.
-
Mike Tobias
August 30, 2010 at 3:09 pmI’ve had difficulties render QT files to a network drive. Any time I’ve had the problem, changing the target to a local drive has fixed it for me. I have the same problem if trying to rendering within the QT Pro program.
-
Tyson Onaga
September 8, 2010 at 11:01 pmI ran into this same issue and think I’ve found out what my issue was … wrong HD format.
HD #1 NTFS, Quick Time 7.5.x
a. Render As, Quick Time 7, Video Format = PNG, Compressed Depth = 32 bpp
works fineHD #2 FAT32, Quick Time 7.5.x
b. Render As, Quick Time 7, Video Format = PNG, Compressed Depth = 32 bpp
fail … Render As goes to 100% and no .mov file is createdHD #2 FAT32, Quick Time 7.6.7
c. Render As, Quick Time 7, Video Format = PNG, Compressed Depth = 32 bpp
fail … Render As goes to 100% and no .mov file is createdHD #1 NTFS, Quick Time 7.6.7
d. Render As, Quick Time 7, Video Format = PNG, Compressed Depth = 32 bpp
works fineI made multiple attempts and here’s what I found:
.veg file HD, rendered file HD, result
NTFS, NTFS, success
NTFS, FAT32, success
FAT32, NTFS, success
FAT32, FAT32, failI tried uninstalling/installing various versions of QT and always ran into a Render As failure. The common denominator was the old FAT32 secondary HD. Solution is to only use NTFS. QT must not like FAT32. I did not at any point uninstall/reinstall Vegas.
Kinda weird … can anybody verify?
Thanks,
– Tyson
Reply to this Discussion! Login or Sign Up