Thanks John,

Project:
1920x1080@ 29.970
pixel aspect ratio 1.000
pixel format 8-bit
field order none progressive scan
deinterlace method: blend fields

I also render out these same setting except in 2.7k as well.

The media specs are All GoPro Hero 3+ Black files. ranging from 1080 35mb a sec.
to 2.7k 48mb a sec. fps 60fps to 24

I may not get to this for a while.

Same problem here, instant crash, regardless of what type of project or media. Render as... crash.

Same problem with me as well. Worked fine in the first release but the recent new build (9860) I get an error as soon as I try to render any video or audio.

I tried Vegas Pro 13 on my Windows 10 test machine and it failed not only on GoPro video, but GH3 video and video from a Canon G15. It appears to be dead in the water.

I received a Windows Update on Friday that made the machine unable to boot to a desktop. On Monday, I restored the image back to the original installation but didn't test Vegas Pro or anything else. Today, I get this message when attempting to render anything where it had worked before.

Looks like it might have lost the smarts to do fan control, also. It sounds like a wind tunnel in here. I'm going to power this rig down for a couple of days.

Out of curiosity installed V12 and it works fine, so it's something with 13.

Cheers.

J\

Yea I installed my Vegas Pro 11 and it will render everything with CPU only. but When it comes to Open CL it brings up errors.

So it may be a video driver issue then since I can render under OpenCL on Vegas 12 just fine.

I just installed the latest build last night, no change, still vegas render instant crash.

Anyone from Sony monitoring this? I realise that Windows 10 is beta software but still, would be nice to see if Sony is even aware. And for the record, it was was working fine on the initial build, but subsequent releases have had this crashing issue.

in all honesty i DON'T want scs wasting time and resources playing around with a beta operating system - and if you're serious (using it professionally - ie. making money with it) then you really only have yourself to blame for any problems you encounter....

i have no objection to people experimenting with their software, we all do, but to expect ANY form of manufacturers support in this case is truly beyond the pale.

Since I just saved a system image after installing the Vegas 2 Handbrake tools, I decided to test the latest Windows 10 code. I did an in-place upgrade on my primary edit machine and I was greeted with this on my first render attempt. I've rendered that project five times just today on Windows 7.

I managed to complete a quick render with Vegas Pro 12.

I'll save the WIndows 10 system image so I can come back to it later.

Windows Media Player doesn't seem to have an MPEG-2 decoder even though it worked before the in-place upgrade.

I repro also with Vegas 13. build 1428 on Win 10 build 9926, fully patched. I bypassed MPEG-2 and tried Windows wmv too. Compatibility mode fails and Windows flags the app as incompatible. The cynic in me suspects that we won't get a fix without upgrading Vegas...hope I'm wrong. Of course it's also on Microsoft not to break something as basic as file I/O. Nuts!

I completely disagree. The way you get a stable release is testing; those of us who do so help that cause. Sony developers should certainly be aware of this and working on it. And how do you know it's not a minor fix? I've not yet seen anything else crash immediately trying to write a file.

Also, let's recall the misery many of us had when Vegas first shipped this release - lots of crashing, accompanied by complete silence from Sony...plus a lot of posts sugesting than since their systems did not crash then it must be our fault.

Sorry, the last post was unclear - looks like I'm disagreeing with myself (happens some times) but it was directed towards ushere - rebuking a beta tester.