Best, easiest file to work with in Vegas? .AVI?

i c e wrote on 5/23/2010, 5:36 PM
Hello all yet again,
I am about to begin a very large product and don't want a major change halfway through. I have all my original files in AVCHD. I can't work with these files because my laptop just won't handle it.

I am going to use peachrocks multi render to convert the files. What would be the best file to render to. Of course I want quality but I am not thinking I can handle HD (but i really don't know). I typically use .avi. but I just thought I would ask in case I am missing something. works good and the quality is pretty decent.

Thanks all..

peace


Comments

TheHappyFriar wrote on 5/23/2010, 5:53 PM
DV AVI or HDV never seems to fail for me. On 32-bit vegas HDV can run out of memory so I normally render in segments (batch render script) & put together in a master project.
Mikey QACTV7 wrote on 5/23/2010, 7:27 PM
Other things to think about is the compression of your files when you convert.
ushere wrote on 5/23/2010, 9:30 PM
i always use .mxf - so far very successfully..
Grazie wrote on 5/23/2010, 11:01 PM
I've been doing mixed work MJPEG and MP4. All I can tell is that from the cameras I got them from, these are really delivery formats and I have had to transcode to something else. Using VASST ULiSPro4 I was helpfully lead through the process of transcoding from MP4>AVI(WS-DV) - which I've been succesfully editing in - the process was straightforward enough. The MJPEG I've used off-the-bat but have had to transcode to NTSC away from PAL to do the 30-PAL render to DVD - go figure . . . .

As I haven't transcoded or transmuted myself to HD, yet, and still working on projects in SD, BUT have a personal research-arm of Grazie-Global, I have had the option to work with both MXF and AVCHD, pretty much MXF has the flow-jo i need on the monitor.

I stress I haven't done anything in real anger with HD yet, but this year it WILL change! - Oh yes . . . .

I think the whole Encode<>Capture<>Workability schema generally is in a real mess. At the Prosumer and consumer end it's like the WildWest out there. And plaheese . . . don't get me started on AVCHD!

Grazie

K-Decisive wrote on 5/28/2010, 9:07 AM
I second MXF, I'll be using that going forward when I go the proxy route. I also have batch rendered out to DVCPRO using the matrox stuff that works well too. Here's a couple of tricks: You can rename and .AVI file to .MOV and Vegas will still understand it, just drag and drop, it also works in reverse. So I have two directories, one with the original H264 files (from a 7D) and one with DVCPRO files renamed to .MOV. Same exact file names. Once I'm done editing with the DVCpro files. I close, swap the folder names, and reopen...no problem. ( I wrote a simple VB app to rename the files ).

You should also be able to just export an EDL, do a search and replace on the directory paths, then re-import the EDL to a new project without changing the extensions. But I haven't tried that yet.