[Al Bergstein]

I’ve not tried Zoombrowser, because my clips haven’t crashed my machine up to now. But, these latest clips are the longest I’ve shot. So I will try using that. Cineform did not change the problem at all. Once converted the clips, when I reached a certain length, still crashed Vegas.

Alf

[Al Bergstein]

The latest AVCHD renders did not crash Vegas. But I can replicate the crashes with MOV files. They even crash Vegas when they are converted to AVI with Neoscene. By the way, it seems I can get about three or four clips dropped in before this starts crashing the application. (My machine does not blue screen).

I think I’ll start a new thread to capture this.

Alf

[Al Bergstein]

Also,did anything change in the hardware configuration lately? These days, BSOD often are indicative of a hardware driver or component failure. Did you add/remove hardware lately? Upgrade drivers???

What’s your format that you are rendering? HD? SD? which manufacturer, like HD AVCHD,HD AVCHD lite, HD MOV, etc…. Some odd stuff is manufacturer specific, it seems.

Alf

[Al Bergstein]

Yes, the fact that the clip only crashes on Vegas on the *exact same machine and hardware configuration* certainly seems to point to a bug with Sony. Be aware that you may have to eventually get through to a second tier support if they have it. Sometimes I’ve heard that the first tier support is, to say it mildly, not quite up to par. But that’s second hand information from previous posts I’ve seen and I only tell you that to have a bit of patience on the entry point (I’ve dealt with a huge number of tech support groups over the years, they vary wildly).

Also, a clarification. My current problems did not occur with AVCHD, but with MOV files from a Canon T2i. This is important. I’m running another batch of renders right now with AVCHD and I’ll see if the problem travels with the clips. As mentioned, there had not been any problems with hours of AVCHD rendering, and suddently it started after a bunch of shooting done on my newer T2i. BUT, this was after doing a video project with the T2i a month before that went fine. So something changed.

Alf

[Al Bergstein]

Ken, a few thoughts. After decades in high tech, and working on dozens of computers in my day, I would not guess that the graphics card is to blame here. I am not Sony, so I can’t have access to their internal database of bugs and problems, but from what I’ve read of your problem, I would doubt the graphics, because usually it would either totally take down your machine, or throw some hardware error, maybe a BSOD.

Does Vegas exit gracefully, meaning it simply end the program and in 9.e give you a box to enter extra information about what you were doing when the program stopped functioning?

If I had to suspect anything, it would be your RAID controller. It *sounds* like a bad clip with some kind of corruption. It is odd that another Windows program can pick it up fine. Maybe Vegas lacks some kind of error checking or handling of corruption in the file or data messed by the controller. You didn’t state whether your clip was actually brought up on the exact same machine using that other package, and with the same hardware and RAID controller. I assume it was. Could you bypass the RAID controller to isolate the problem further?

But you are right, it *could* be a bug or other known issue to Sony internally. Given your frustration, the $150 to get direct Sony support seems reasonable, and you have probably wasted more than that up to this point, given whatever you charge by the hour. By paying it you likely could at least convince yourself you gave Sony every opportunity to help you and if some other package does the job without the crash, well what could I or anyone say?

I have had some problems crop up since loading some third party addons in to Windows 7 w/Vegas 9.e. Vegas was loading everything I threw at it, then I loaded some add ons, and pow, a few clips started failing, usually after I had loaded a couple of clips ahead of them. But I suspect it was memory corruption. I’ve backed them out and the problems have cleared. But I’m very suspicious of 9.e and what appears to be some kind of memory corruption with very large AVCHD files I’m dealing with. I’ve tried converting to AVI with Neoscene. It *seems* to make the matter worse, so that leads me to suspect the file size loading into memory. (I have 8GBs of RAM). I also don’t know how well Sony vets it’s third party add ons. I suspect not at all. Given this, I am making sure I have complete backups of non crashing systems, set a restore point in Windows before loading new software thus giving me a rollback plan in the event of problems showing up that didn’t before. I do this on the Mac already, though they don’t support restore points, that I’m aware of.

Anyway, I would bite the bullet and pay Sony tech support. You are going to spend a lot to relearn something else. $150 is not much money given the hours you will spend doing that. I don’t guarantee you a thing, but it’s what I would do. And I might if this problem keeps popping up as I add third party add ons. For some reason I have not seen that happen on my “other” platform I use for work occassionally. The other editor is a more difficult editor, but it doesn’t crash loading files. I’ve changed to that other platform for the last two days, just to hit a deadline, but intend to try and replicate the problem over the next few days and see if I can get it isolated. Then I’ll call Sony and pay them to answer a few pointed questions. Or I’ll call the third party.

Hope this helps save you some time.

Alf

[Al Bergstein]

John points out that 9.x is the only Vegas version supported on W7. So you *could* be experiencing something in Vegas 8. But I doubt it. Anyway, get on the current version of Vegas if you aren’t already.

But back to the net card, I would *guess* that the wake up value is for a network wakeup for pushing software to the card, not something you would care about. But the “disabled” fuction on Row Control for the old card vs. Auto might mean something. I’d try setting it at disabled, rebooting, and running a test. If nothing happens, reset it to Auto.

I have not done much network based Vegas file transfers though. Have you tried FTP’ing the files as I suggested, and timing the transfer? That would tell you whether it’s the card, or something else. If both FTP and Vegas file transfers were the same, (meaning both slow), then you known it’s under that layer in the computer OS, or the network card and it’s drivers. (or the server connection). But if you experience slow Vegas and fast FTP of the same file, then you know that it’s a Vegas or the way it’s mounted (i.e. Windows connecting via some login to the server).

Alf

[Al Bergstein]

Also don’t rule out the server side. Is the OS there Mac, UNIX/Linux or Windows (and which version). There could be a problem with the version of OS at that end. Also isolate whether the file transfers are slow using FTP, which pretty much helps isolate it also. If FTP transfer is fast on XP & W7, and using the server mount is slow, you’ve pointed away from the network card, to something at the OS level. Best of luck.

Alf

[Al Bergstein]

Has this just started happening? Did something change (i.e. you upgraded, added some software or hardware recently?). Can you open the projects on a different computer? (i.e. load them temporarily on a laptop rather than a desktop, or vice versa?) Try and isolate the problem as best you can. Sometimes crashes can be corruption from disk failure, etc.Being able to test that the files work on a different machine may eliminate Vegas as the problem, and point to something else, like a virus, hardware, etc. Is there anything unusual about the files? New Huge files for example? Do you have backups to try (don’t use them directly but copy them to the disk in question). etc.

Sorry for being vague, but there are a bunch of possible things here. Isolating it to Vegas is worth doing.

Alf

[Al Bergstein]

Carlos, there is a similar thread just below yours on the thread list, a person from Guatemala. Please review the links that I posted on that thread see if any of them work, and then come back to us with a more specific problem definition. As you can see, there could be a lot of reasons for this change. You need to work through a few of them first.

Alf

[Al Bergstein]

I don’t know anything about this card, but the reviews on Amazon are a really mixed bag

https://www.amazon.com/Avertv-Definition-Analog-Capture-MTVHDDVRR/product-reviews/B002SQE1O0/ref=cm_cr_dp_all_helpful?ie=UTF8&coliid=&showViewpoints=1&colid=&sortBy=bySubmissionDateDescending

It certainly sounds like the problems encountered by recording audio at 44kHz rather than 48kHz. You get ‘audio drift’ a few minutes in… check the specs. If it’s recording at 44 you may be unable to fix it.

Alf