I have just spent all day editing a video, about 40 mins total finished length, and when I render it, it gets to about 2% and them bombs out with this error
http://peter-ftp.co.uk/screenshots/2017-08-28_175736.jpg
The source is 1080P 50fps XAVCS and I have successfully rendered this before many times.
Space on drives? Overheating? Any odd mixes of Media? Try a reboot and start over.
Right.
I have done all that. 500GB HD space, 24GB RAM. Nothing obvious there. The rendering template make some difference; with the Mainconcept .mp4 bombing out at 2% but with the XAVCS Long GOP reaching something like 20%, though the latter does a nice BSOD and crashes the whole machine!
I also tried reverting to v13 which was a lot less buggy but it can't open the ex-v14 .veg file, unsurprisingly.
Total size of this project is about 270GB (video mostly of course) so I can't send a DVD with Magix - even if they were interested!
It clearly isn't a particular point in the source material. It is some sort of memory or stack leak. I am now rendering with a third different template, to an mp4. It is a 2-pass one and it is 10% into the source material and still running.
I have done much bigger projects than this. Some had 10hrs of source material, rendered to 10hrs of 50mbps mp4 (as a pre-render). Most had lens correction (Newbluefx) but not this one. I would hate to lose a day's work. I woul rather put all the stuff onto a 1TB USB drive and send it to Magix to fix the bug.
That looks brilliant - thank you :) I will try it if it bombs again.
I also have V12 which was solid, and V11 (on winXP) which I used for years and which never showed a bug let alone crashed.
Using the MainConcept Internet HD 1080 2-pass 50fps template, it did the whole thing.
It takes about 5hrs.
I am doing a new render with some small text edits and then after I have that rendered I will go back to the previous templates to see if they still crash.
Funny, I have used Vegas for more than 7 years and rarely got errors. However, just recently I started working on a feature length project and all of the sudden, started getting errors similar to the one you posted. On my particular project, it kept crashing on render and gave a similar message. The only thing unusual and it really isn't that unusual was I had taken an audio clip from another video clip on the timeline, duplicated it twice, and then cross faded them together. I had these audio files on their own track. When I deleted that audio track, it would finally render. I'm not sure that applies to your situation, but that's what happened to me. I've also had freezes for the hard drive being full and renaming a file after start up and I guess Vegas not being able to find it. I just wish the error would be more specific. Not helpful to say it cannot be determined. Something is causing a problem and it should be identifiable somewhere. I do believe the system is more likely to crash when the videos are being rendered to the same drive as the source files, although I can't confirm this 100% and Magix has never officially said if there was a best practice in that regard. But I do like to keep my source files on a drive different from the drive being rendered to. Looks like you got a lot of work you did there. I hope you can resolve it.
I have everything in c:\video, with the project file in c:\video\veg
Oddly enough I did import one of the two audio tracks again, onto another timeline track, to extract a small piece out of it, and then deleted it.
I will know more when the current render completes (I am not stopping it - way too valuable!) but it could be that certain operations corrupt something. Vegas restart definitely doesn't make any difference to the problem, so it looks more like OS corruption - which should be fairly hard to do under Windows (win7-64).
The BSOD was something like a clock signal not reaching a processor core... really obscure and in 30 years of building IBM compatible PCs I have never seen it before.
I have also disabled all GPU options, as far as possible. That was necessary in v13 to get it to render at all (GTX750 KALM X) and in v14 the options are different. The config is also all over the place. There was another thread on this here, or another video forum (there are many). I use Vegas every few weeks which is not enough to remember all the details. But the projects are fairly big, with 5-10hrs of 1080P 50-60mbps video and a sound track, edited down to 20-30 mins. But otherwise the jobs are simple and I can do all of it in MSP11, now that I am using a different camera which doesn't need lens correction (that drove me to NewblueFX and Pro 13 which was much more buggy than MSP).
The BSOD on the Sony Long GOP render option is repeatable, though not always in the same place in the rendering progress.
http://peter-ftp.co.uk/screenshots/2017-08-30_090751.jpg
If Magix want to paypal me the cost of a 1TB USB drive I will happily send them the data :)
The BSOD on the Sony Long GOP render option is repeatable, though not always in the same place in the rendering progress.
Sony Long GOP...: Sony XAVC / XAVC-S ?
I had that similar issue too when exporting to XAVC format.
This one:
http://peter-ftp.co.uk/screenshots/2017-08-30_093158.jpg
This one worked:
http://peter-ftp.co.uk/screenshots/2017-08-30_093246.jpg
but as you can see that template is slightly customised for a specific bitrate (I have to fit videos into 5GB for Vimeo upload)
http://peter-ftp.co.uk/screenshots/2017-08-30_093329.jpg
However I have used that Long GOP (and the others from Sony) many times before so there is something in this project which causes the crash.
If Magix want to fix bugs (rather than release v15 with more of them) they should fix this one because it would probably fix many others at the same time (I am a hardware/software developer).
We know there are unresolved decoding issues with playback and loading of XAVC long-GOP files. I guess your encoding issue may be related. I would just avoid encoding to that format for the time being, and use AVC for web upload, as you have done. But please report this issue at at https://support2.magix.com/customer/en/vegas/form , including as much detailed information about the problem as you can. That's the best way of getting issues into the devs' backlog. Include your O/S and make sure you're on build 270.
I have done the report; thank you.
However I think there is also an issue with *loading* Sony files because I managed to crash Vegas when rendering via a template other than the long GOP. The Mainconcept template seems to work OK.
The computer is rock solid in all other respects.
Very interesting Nick to read the above issues with XAVC-L. Fortunately my X3000 camera seems to generate AVC or XAVC-S only, .mp4 always.
I also can't see the point of rendering to XAVC-L.
This is the BSOD I got when rendering to Sony Long GOP