After reinstalling Vegas Pro 19 Edit on a clean Windows 10 installation. Can not be rendered. The program crashes when "Render As" is clicked. The same thing happens in Vegas Pro 18 Edit and in Vegas Studio Platinum 17.
Have you also reinstalled all the graphics drivers?
Check Vegas Pro under "Help - Check for driver updates".
Yes, all drivers are up to date and the current graphics driver is 472.12 (NVIDIA).
The programs ran before a clean install of Windows 10 took place.
@Hans-Jorgen-Sindholt - Now do a series of regression testing.
How about some hints as to the issue.
What media, what render templates, what hardware are you using?
Do all renders fail? Can you render a benchmark project? https://www.vegascreativesoftware.info/us/forum/benchmarking-results-continued--118503/
You're probably way ahead of me - nearly everyone else is - but I'll say this because I had the same issue with Vegas 18 recently.
It was on a new Alienware laptop with an RTX 3060 with the studio driver as yours - 472.12
I had been able to render some other work that I'd already finished editing on an old desktop (no usable GPU).I'd also been able to render some "clean" test files on the laptop.
I had transferred all the Vegas settings from the old desktop to the new laptop using Vegas's newish Export>Import functionality.
I tinkered with Options > Preferences > File I/O and found that the "Hardware Decoder To Use" was at Off. I changed that to Auto NVIDIA NVDEC and that did the trick.
Here is the error message after shutting down.
Problem Description
Application Name: VEGAS Pro
Application Version: Version 19.0 (Build 341)
Problem: Unmanaged Exception (0x40010006)
Fault Module: C:\WINDOWS\SYSTEM32\ntdll.dll
Fault Address: 0x000000007700CFEA
Fault Offset: 0x000000000008CFEA
Fault Process Details
Process Path: C:\Program Files\VEGAS\VEGAS Pro 19.0\x86\FileIOSurrogate.exe
Process Version: Version 19.0 (Build 341)
Process Description: File I/O surrogate (not visible)
Process Image Date: 2021-08-10 (Tue Aug 10) 22:38:58
It won't hurt to try a reset.
Can you answer any of the other questions?
Process Path: C:\Program Files\VEGAS\VEGAS Pro 19.0\x86\FileIOSurrogate.exe
Do you have QuickTime installed on your system and/or have turned on the depreciated QuickTime support in VEGAS?
One of the last things Vegas does when you click "render As" is to survey all the codecs. On my system a few years ago Vegas crashed in that process. So another good question is what codecs have you installed. Codec packs? Other video editors that may have installed codecs, etc?
Yes, but when I can not even enter the menu and select codecs and the program crashes, it is not so easy.
The program also crashes if I want to render to another track. Well really a natural consequence.
Also, I have not installed any more codecs ..
But I have then noticed that
Shift + B
"Build Dynamic RAM preview" - works very fine.
----
Shift + M
"Selectivily Prerender Video ..." - works very fine
-
VegasDerek asked if I had QuickTime installed or enabled in Vegas. My answer is simply "no".
It's tiring with this error, because I've been using Vegas Movie studio for many years and only now got upgraded to Vegas pro 18/19 Edit.
I do not intend to replace Vegas with anything else, as the program is incredibly appropriate to work with when you are a happy amateur.
@ Hans-Jorgen-Sindholt
Is that crash always with every project or file?
When only at a certain project(type), which one and which type of sourcefiles are used?
I have had several camera types for many years. In recent years, using files from a canon camera - MTS - and from a GoPro Hero 7 Black - MP4. These files have never caused any problems.
In addition, I have so far without any problems edited old video recordings from VHS from the eighties and Sony HI8 from the nineties.
In connection with my work, I had access to programs from Adobe (Premiere Pro), but privately it was the Vegas Studio series - (Sony Vegas) inspired by a local TV station, where Vegas Pro was the preferred software
The problems have been few. But now it's so wrong.
.
Is it possible to show here the MediaInfo of those MTS files following this tutorial?
My own MTS cannot be used if they are used as 5.1 surround audio and gave the same symptons.
Yes, here is data from a single file (MTS) is recorded with a Canon camcorder.
General
Complete name :J:\Videoredigering\01 Rå optagelser - kopier fra Canon SD\08-06-2018 - Ida og Martin fjerner stræstub\08-06-2018 Martin og Ida fjerner træstub.MOV
Format :MPEG-4
Format profile :QuickTime
Codec ID :qt 2007.09 (qt /CAEP)
File size :109 MiB
Duration :19 s 720 ms
Overall bit rate :46.5 Mb/s
Encoded date :UTC 2018-06-08 15:50:48
Tagged date :UTC 2018-06-08 15:50:48
Video
ID :1
Format :AVC
Format/Info :Advanced Video Codec
Format profile :Baseline@L5
Format settings :1 Ref Frames
Format settings, CABAC :No
Format settings, Reference frames :1 frame
Format settings, GOP :M=1, N=12
Codec ID :avc1
Codec ID/Info :Advanced Video Coding
Duration :19 s 720 ms
Bit rate :44.9 Mb/s
Width :1 920 pixels
Height :1 080 pixels
Original height :1 088 pixels
Display aspect ratio :16:9
Frame rate mode :Constant
Frame rate :25.000 FPS
Color space :YUV
Chroma subsampling :4:2:0
Bit depth :8 bits
Scan type :Progressive
Bits/(Pixel*Frame) :0.867
Stream size :106 MiB (97%)
Language :English
Encoded date :UTC 2018-06-08 15:50:48
Tagged date :UTC 2018-06-08 15:50:48
Color range :Full
Color primaries :BT.709
Transfer characteristics :BT.709
Matrix coefficients :BT.601
Codec configuration box :avcC
Audio
ID :2
Format :PCM
Format settings :Little / Signed
Codec ID :sowt
Duration :19 s 720 ms
Bit rate mode :Constant
Bit rate :1 536 kb/s
Channel(s) :2 channels
Channel layout :L R
Sampling rate :48.0 kHz
Bit depth :16 bits
Stream size :3.61 MiB (3%)
Language :English
Encoded date :UTC 2018-06-08 15:50:48
Tagged date :UTC 2018-06-08 15:50:48
Then you have not the same problem as I did.
Sorry I cannot help, did you followed the advice of @VEGASDerek?
Grazie asked earlier in this thread if the dot.netframe was up to date.
Yes. This file has been updated.
Thank you for your bid.
Solved
Many thanks for the help.
VEGASDerik inspired me to uninstall C: \ Program Files \ VEGAS \ Movie Studio Platinum 17.0 \ x86 \ FileIOSurrogate.exe.
Voila - the problem was solved and now the Vegas programs are running fine.
Sincerely
Hans-Jørgen
Thanks Hans-Jorgen. I wonder why? Does VMS17 Platinum still work okay as well as VP?
It has also amazed me that this is the case, but now "rendering" works in both Vegas Studio Platinum 17, Vegas pro 18 Edit and Vegas pro 19.
Also after restarting the computer.
Now I'm not a programmer at all. just user of Windows 10 - and of course the programs that are installed. But it could be interesting to get an explanation for it - and whether the removal of the file has consequences elsewhere in the programs.
Very interesting. I wonder if your FileIOSurrogate.exe got corrupted. If you look in the folder has a new file appeared?
Hi, I just resolved the same issue in my Vegas Pro 18, the program crashed each time after selecting [Render As] in the File menu (tried different solutions like disabling the GPU rendering, setting RAM to zero, cleaning temp folder, ... all of it you can read in other threads). The solution was to delete the file "c:\Program Files\VEGAS\VEGAS Pro 18.0\x86\FileIOSurrogate.exe". I am not sure what this file does but removing it simply helped.
.tb_button {padding:1px;cursor:pointer;border-right: 1px solid #8b8b8b;border-left: 1px solid #FFF;border-bottom: 1px solid #fff;}.tb_button.hover {borer:2px outset #def; background-color: #f8f8f8 !important;}.ws_toolbar {z-index:100000} .ws_toolbar .ws_tb_btn {cursor:pointer;border:1px solid #555;padding:3px} .tb_highlight{background-color:yellow} .tb_hide {visibility:hidden} .ws_toolbar img {padding:2px;margin:0px}