If I want to make Vegas crash immediately...

Laurence wrote on 2/9/2006, 8:57 PM
If I want to make Vegas crash immediately all I have to do is touch the cursor to any m2t file with autoplay on in the Vegas explorer window! I try to remember not to do this, to only try playing the proxies as I decide what to drag to the timeline, but every so often I forget...I'm just getting ready to reboot now (losing my last half hour or so of work).

Comments

Laurence wrote on 2/9/2006, 9:01 PM
Thankyou Sony for autosave! I only lost an edit or two! Now back to work. Remember Laurence, don't preview the m2t's in the Vegas Explorer window! Whatever you do, don't preview the m2t's!
DrLumen wrote on 2/9/2006, 11:16 PM
While this is not a fix, but can you move them to their own directory?

intel i-4790k / Asus Z97 Pro / 32GB Crucial RAM / Nvidia GTX 560Ti / 500GB Samsung SSD / 256 GB Samsung SSD / 2-WDC 4TB Black HDD's / 2-WDC 1TB HDD's / 2-HP 23" Monitors / Various MIDI gear, controllers and audio interfaces

Laurence wrote on 2/9/2006, 11:29 PM
You can't. Gearshift needs the proxies and originals to be in the same directory. I just did it again. AAhhh!
FrigidNDEditing wrote on 2/9/2006, 11:34 PM
you do have the auto play off right?

Dave
Chienworks wrote on 2/10/2006, 4:20 AM
Sorry, couldn't reproduce it. .mt2 files preview from the explorer window just fine on my system. Well, i only get about 4fps, but they do play without crashing.
epirb wrote on 2/10/2006, 7:12 AM
I have the same problem, but it happen to me even with the CFDI's but this is when using External preview. It'll lock up everytime.
rmack350 wrote on 2/10/2006, 7:55 AM
I just recently had an email exchange with product support about not being able to see MediaFX unless you put a clip onto the timeline. The support person pointed out that if you turn on autoplay then you can see the mediaFX.

The point is that they seem to expect you to use autoplay all the time. It's annoying to have a clip play every time you touch it, let alone Vegas crashing if you touch a clip in the pool.

Poor implementation all around.

Love Vegas though. The obvious solution for you is to turn off autoplay.

rob mack
mdopp wrote on 2/10/2006, 11:57 AM
I'm having the same problem. Let's face it: Vegas was perfectly stable up to version 5. Version 6 is a big letdown.
Very few new features (for me it's just HDV color space support) and tons of problems. I'm having so many issues here. Can't even use 6.0c because it crashes when rendering out long timelines - while 6.0b does not. I just hope Vegas 7 will be better.
Martin

rmack350 wrote on 2/10/2006, 1:38 PM
Autoplay isn't a new feature in V6. Recognizing M2T is, though. Isn't it?

If Vegas 5 could recognize an M2T file it's probably also crash when you try to autoplay it.

Rob
Jim H wrote on 2/10/2006, 9:22 PM
I can crash v6 by copying a mask keyframe and without closing the box, opening another event and trying to paste that keyframe over another. If I close the first event first, then open the crop dialog on the second task I'm ok.
mbryant wrote on 2/13/2006, 1:58 AM
I can't reproduce this - I don't get a crash when I select a m2t file via explorer... regardless of auto play on or off.

I HAVE had crashes in the past when I tried to do anything from Vegas with a m2t file created by the "HDV Split" free utility... so I gave up trying to use this... though I can't reproduce this with the latest version. I mention this as it was one of Laurence's posts which pointed me to HDV Split, this could be related to the problem?

Mark
Laurence wrote on 2/13/2006, 5:50 AM
Yeah the m2t files are created with the HDV Split utility. That could be the problem. On the other hand, I really love HDV Split. It only crashes when I try to play the clips from the Vegas Explorer window. The clips work fine on the Vegas timeline. The splitting of m2t clips is pretty important to me. I'd rather liver without being able to audition m2ts than I would with just one big m2t file.

By the way, there was a recent update to HDV Split that improved it quite a bit. If you are using it be sure you have the latest version.
mbryant wrote on 2/13/2006, 8:30 AM
Laurence,

Yes, I just downloaded the latest version... and with this I couldn't reproduce the crash. When I tried it on an earlier version, it would always crash if I touched the file via the Explorer window. So maybe if it is a problem related to HDV Split it is now fixed? Were your clips split with an older version of HDV Split?

Mark
Yoyodyne wrote on 2/13/2006, 10:38 AM
I've been having this as well - only happens with external preview on and only when I'm trying to preview mpeg 2/M2T from the trimmer or autoplay. Very annoying, my workaround has been to assign "preview to a second monitor" as an on/off button on my shuttle. The only hitch is remembering to hit the button, would love a fix for this one.
Laurence wrote on 2/13/2006, 6:14 PM
I'm using m2t files split with the most recent version of HDV Split and an external 1394 monitor preview. I am pretty sure it's a bug with Vegas.
mbryant wrote on 2/14/2006, 3:37 AM
Could be, though it doesn't seem to be a straight forward one. I've only had crashes when using HDV Split without external monitor preview... though now that works... seems different things are triggering the problem.

Mark
Laurence wrote on 2/16/2006, 10:36 PM
Well I just tried this in the new Vegas 6d. M2T preview over 1392 now begins to play (at about 4 fps) but you lose control as soon as playback begins and you need to end the process and restart Vegas to continue.

It still doesn't work, but it is a step in the right direction.