Sony Vegas 10 Crashes on .TS / .mpeg/.mov

[Mike Fego]

When I tried SV 9 (64 bit) and tried to load the .mov footage, I get this:

Extra Information
File: C:\Users\Media Center II\AppData\Local\Sony\Vegas Pro\9.0\dx_video_grovel_x64.log
File: C:\Users\Media Center II\AppData\Local\Sony\Vegas Pro\9.0\dx_grovel_x64.log
File: C:\Users\Media Center II\AppData\Local\Sony\Vegas Pro\9.0\vst_grovel.log

Problem Description
Application Name: Vegas Pro
Application Version: Version 9.0e (Build 1146) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Program Files\Sony\Vegas Pro 9.0\x86\FileIOSurrogate.exe
Fault Address: 0x0000000024A050F0
Fault Offset: 0x0000000024A050F0

Fault Process Details
Process Path: C:\Program Files\Sony\Vegas Pro 9.0\x86\FileIOSurrogate.exe
Process Version: Version 1.0 (Build 8)
Process Description: File I/O surrogate (not visible)
Process Image Date: 2010-05-12 (Wed May 12) 16:56:48

So both 9 & 10 are having errors now

[Rob Franks]

What version of quicktime are you running?

[John Rofrano]

[Mike Fego] “Does anyone know a m2ts converter, because that seems to be the only thing that works on my system”

The workflow that most people use with the Canon 7D is to convert the files to CineForm with NeoScene ($99 USD). CineForm will retain all of the quality of your original footage. Rendering to another lossy highly compressed format like .m2ts is not a good solution.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Mike Fego]

It says 7.6.9.

Now its doing that low memory crash when I try to render( I have seen lots of other users with that issue but not me–till now)

This Vegas 10 is really getting frustrating might just go back to 9 and see if that works better…IDK

[Mike Fego]

Thanks John. I might look into getting that next month, because these errors are putting me waay behind and I’m getting backed up with paid projects due to the constant shutdowns.

[Rob Franks]

People are complaining that when they place a lot of mov files (from the 7d… T2i… etc) on the time line you will get a crash. I developed a small hack that will extend memory on some of the modules causing the problem. You can follow in this thread:

https://www.hv20.com/showthread.php?40962-Trouble-with-Importing-too-Many-T2i-Files-into-Vegas

(You can also adjust the memory flags on the mpeg and wmv I/O plugs if you’re having problems there too).

[John Rofrano]

[Mike Fego] ” I might look into getting that next month, because these errors are putting me waay behind and I’m getting backed up with paid projects due to the constant shutdowns.”

If you buy it now and it stops the crashes, wouldn’t that help you get this months work completed?

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Dave Haynie]

The real fix is to use 64-bit, when you can.

The hack here is potentially a problem, depending on the code. Windows user space in 32-bit mode is limited to 2G normally. The reason for this is simple: some bad programming techniques sometimes treat memory pointers as integers. If those are not expressly written as unsigned integers, then manipulation of pointers over 2GB works in signed math, and produces incorrect results.

Setting this flag allows Windows to devote up to 3GB in a 32-bit OS, or 4GB in a 64-bit OS running the things in 2GB mode. It’s not an issue on 64-bit resources in a 64-bit OS. But if they’re not “4GB clean”, changing these flags will bring on errors.

-Dave

[Rob Franks]

“But if they’re not “4GB clean”, changing these flags will bring on errors.”
======================================

Hasn’t happened yet.

Interestingly enough, this is actually a slight modification from a memory flag hack I developed some time ago to solve a crashing avchd problem. It was either with vegas 8 or 9…. I can’t remember which… but it’s been used hundreds of times with no issues at all. In fact from what I understand, Sony support actually started offering it as a work around for others.

Never hurts to try… you can always switch the flags back again if not satisfied.