VegasPro (VP) won'topen.avi files created by VP

strz_grant wrote on 9/15/2014, 12:49 PM

I have the latest version, 13.0 (373). I have checked all Windows, virus, and registration, and system checkers. Everything is current. BUT, Vegas Pro will NOT open .avi or .mp2 files it created!

Is anyone else having this problem? What is the solution?

I save my work in pieces so that I don't loose anything. Then put all the pieces together for a final cut. On the re-assembly, Vegas Pro would NOT open the files it created. However, they open and play in Windows Media Player. And, when I placed the segments in to another video program I have, it worked perfectly.

What is going on!?

Comments

videoITguy wrote on 9/15/2014, 12:53 PM

This is possible, because what you must be sure of is that you are rendering to file types that Vegas understands. Note that just rendering to something willy-nilly is not smart. If as you suggest you are creating digital intermediates, then you must choose the appropriate codec to do that part of your workflow - Cineform would be an excellent choice.

strz_grant wrote on 9/15/2014, 1:23 PM

I try to use the default settings from render. I do understand that just randomly changing settings is "bad." So, I try to stick with what is set by the experts, the default. I wanted high resolution, so went with .avi. It wouldn't load back in. Then tried the same thing with .mp2. That wouldn't load either. But, I could load and assemble in a less robust Corel X6! I don't like that software as much because I don't have the editing control I like with VP. BUT, if I can't get to a final product ....

rmack350 wrote on 9/15/2014, 2:05 PM

All sorts of things can be encoded into an AVI file. If you can be specific about the settings maybe someone can try to reproduce it. Saying "It's and AVI file" isn't enough information.

Rob

videoITguy wrote on 9/15/2014, 2:09 PM

an .avi is a container - it can contain all kinds of codecs, audio combinations, and a myriad of settings that will make it impossible to load in different programs. An uncompressed .avi container can be useful as an intermediate - but Cineform which can be an .avi container is much better.
i don't know what an .mp2 was supposed to be or what you created to make it.

strz_grant wrote on 9/15/2014, 2:25 PM

Everything was rendered from Vegas Pro 13.

At this point I will start over from my timeline and see what happens if I render with different settings.

Is there a way to reset to the software default?

Stringer wrote on 9/15/2014, 2:35 PM

Why are you rendering from Vegas and then bringing ( trying to ) the rendered files back into Vegas?

Perhaps you could describe briefly what you are trying to accomplish, then someone could suggest the best workflow..

rmack350 wrote on 9/15/2014, 2:42 PM

Everything was rendered from Vegas Pro 13.

There are many types of AVI that Vegas could encode. I can't think of any that it can't also read but maybe you're doing something ingenious.

One thing you could probably do is download MediaInfo and find out what's actually IN your AVI file, then share that info here.

Rob

diverG wrote on 9/15/2014, 3:08 PM

You have not stated what your original files are.(may not be important)

Starting from a HDV project 1440x1080 50i on a matching timeline it is possible to render .avi's in both cineform (gopro) and canapus HQ. These were the only avi types available to me that I recognized on my pc.
Vegas rendered two files both of which could be brought back on the source timeline.

johnmeyer wrote on 9/15/2014, 3:13 PM

The Mediainfo suggestion is a good one. Another alternative is to put a region around 2-3 seconds of video, render that to a file, and then upload it so we can take a look. I'm sure we'll figure out the problem very quickly once we see that.