Quick Time woes...

SWS wrote on 7/30/2014, 4:13 PM

I know Quick Time can be problematic in Vegas but I've never had this.
I'm working with Vegas Pro 13 (and Vegas 12 & 11 as well) and Windows 7 Pro...

I have the newest version of QT (maybe not a good thing 7.7.5 (1680.95.13 )

I've selected a file for rendering in the Vegas timeline (happens to be a simple rendered MXF clip or any clip for that matter)

I select a QT template ( I tried pretty much all QT templates with the same result)

Hit render and the render box pops up and instantly says it's rendered 100%. (Of course it hasn't really done anything)

This is only with QT. All other flavors other than QT seem to render just fine.

I've re-booted the system, and "reset" Vegas to no avail. I've un-installed QT and re-installed. QT does play clips just fine on the desktop and in Vegas so it seems that QT is working to some degree.

Also in the spirit of full-disclosure I cannot get Adobe CS6 Premier to render in Quick Times either. I get the message.."Error compiling movie. Unable to create or open output file."

I would skip it and render to something else but the client prefers a QT.

I also went back to QT version 7.62 with no joy either.

Is anybody else having a problem like this with QT. Any ideas?

Comments

JohnnyRoy wrote on 7/30/2014, 4:50 PM

You didn't say what codec you are using. QuickTime is just a container.

I have no problems here. I'm using QuickTime 7.7.5 with Vegas Pro 13.0 Build 373 and just rendered an Avid DNxHD 1080-60i MOV file and it works great.

~jr

John_Cline wrote on 7/30/2014, 5:13 PM

Well, one thing... Quicktime doesn't like unusually long file names.

SWS wrote on 7/30/2014, 6:14 PM

Thanks for the response.
Name was three letters, pretty short in my book. Also I've tried everything under QT's video format..Sorenson, H.263, MPEG-4 Video...etc. etc. Just plain weird...but that's just me I guess!

NormanPCN wrote on 7/30/2014, 7:03 PM

I have VP13 b373 and QT 7.7.4. I have only ever rendered third party DNxHD and Cineform codecs and I've not had any problems with those two.

Tom Pauncz wrote on 7/30/2014, 7:17 PM

I am on VP13 Build 373 and QT 7.7.5 and same as NormanPCN - no problems whatever.
Tom

musicvid10 wrote on 7/30/2014, 7:25 PM

In your render properties:

Set for square pixels only = 1.0 PAR
Set render resolution in exact multiples of four for each dimension.
Try again (with a new filename) and see if that makes a difference. It used to . . ..

SWS wrote on 7/30/2014, 8:29 PM

Once again..Thanks all for your tips.

pixel was set to 1.0
It's a 1920 x1080 file to a 1920x 1080 file
and different file names have were used..

all with no change in result.

musicvid10 wrote on 7/30/2014, 8:41 PM

Well, at least now we know what it isn't . . .
Tried GPU turned off, I assume (not that it should make a difference)?
Tried renaming fileIOSurrogate.dll and reinstalling Vegas?

SWS wrote on 7/31/2014, 10:06 AM

Once again thanks for all the thoughts.

Turning off GPU didn't help.

Now you mentioned renaming "fileIOSurrogate.dll" I guess that's the last thing to try. But would/should that effect Adobe Premier as well?

Tom Pauncz wrote on 7/31/2014, 10:35 AM

Don't think so. It's a Vegas .dll, I believe.
Tom

musicvid10 wrote on 7/31/2014, 12:17 PM

Good point. It shouldn't affect Premiere.

SWS wrote on 8/1/2014, 7:51 AM

Think I'll start playing with "Restore Points" to see if I can get things back like they were cause it seems nothing is working in this regard.

Thanks everyone for trying!

winrockpost wrote on 8/1/2014, 7:51 AM

...........Hit render and the render box pops up and instantly says it's rendered 100%d

I have also had that happen with QT, usually if I had already rendered the project ,made some change and tried to render again. Make sure there are no prerenders in the project, and maybe try changing the project name.
Good luck

SWS wrote on 8/1/2014, 8:39 AM

Good point.
But I have gotten to the place where I just open a new project .veg drop one clip on the timeline (short name) and try to render to QT, any flavor of QT, and no joy!

As I said guess I'll start looking at system "Restore Points"...