Hi, there are a lot of log files in:
AppData\Local\VEGAS Pro\23.0
I will email them to you as they may contain sensitive data.
Indecently the issue with the scenes seems to have fixed itself. When I go to customize each of my render templates, it now shows the correct Vouk scene. But then when I open the scene, scene designer is blank. (not sure if this is relevant / or expected)...
Beiträge von Funghie
-
-
Checked and double-checked license in Scene Designer and in \AppData\Local\VoukoderPro\license.txt
License is definitely my license for Vouk V2
I can repro the crash on render every time, but no log seems to be generated. I will attach the last log but I think it might not help.
Also, anomalies?- Select my Vouk preset in Vegas
- Click customize
- Then Open Scene Designer
- The Scene Designer shows blank page
- Load my Scene into the designer
- Save As but still shows blank
- Also, when selecting another Vouk preset in Vegas and clicking customize
- The Scene that is showing the Vegas customize dialog is always the same scene
Sorry, there is no way to upload a log file or zip file here in this forum. I don't want use file sharing I will email it to you. With title "Log from Funghie".
Cheers, -
2nd EDIT: Can the guys where Voukoder Pro is NOT running in VEGAS Pro 23 please try this update and tell me if it helps?
OK now the plugin is visible in V23 Render Window. Great stuff.
Unfortunately, now get the same error as with the beta version of Vouk 3. Rendering starts and then V23 crashes.
fwiw: Works as expected in V22, using the same Vouk scene and project settings. (Just one small media file for testing). -
English (United States)
English (United Kingdom) here.
But working fine in V22. -
Did you check the "Show all Formats" check box?
Yes, I had done that already and mentioned it in my first post.
Here is the image I could not upload when I mentioned it in the first post.OK I ran the analyser and it scanned all 6 of my SSDs. The only thing it showed was:
FFmpeg DLLs: Not found in PATH
I will check this and post back.Oh, I wish I could edit posts here. I should add that it scanned all 6 of my SSDs but Vegas exists on my C drive. I have no idea why it needed to scan all the other drives. Anyway, will post back. Cheers.
Ok checked the sys environment vars and both:
C:\Program Files\VoukoderPro\C:\Program Files\FFmpeg\
Appear at the top of the Path list
Also, the var: VOUKODERPRO_HOME contains C:\Program Files\VoukoderPro\Also, after checking using cmd:
>ffmpeg -version
ffmpeg version n7.1.1-2-g68b5db2464-20250310 Copyright (c) 2000-2025 the FFmpeg developers
built with gcc 14.2.0 (crosstool-NG 1.27.0.18_7458341)
configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static --pkg-config=pkg-config --cross-prefix=x86_64-w64-mingw32- --arch=x86_64 --target-os=mingw32 --enable-gpl --enable-version3 --disable-debug --enable-shared --disable-static --disable-w32threads --enable-pthreads --enable-iconv --enable-zlib --enable-libfreetype --enable-libfribidi --enable-gmp --enable-libxml2 --enable-lzma --enable-fontconfig --enable-libharfbuzz --enable-libvorbis --enable-opencl --disable-libpulse --enable-libvmaf --disable-libxcb --disable-xlib --enable-amf --enable-libaom --enable-libaribb24 --enable-avisynth --enable-chromaprint --enable-libdav1d --enable-libdavs2 --enable-libdvdread --enable-libdvdnav --disable-libfdk-aac --enable-ffnvcodec --enable-cuda-llvm --enable-frei0r --enable-libgme --enable-libkvazaar --enable-libaribcaption --enable-libass --enable-libbluray --enable-libjxl --enable-libmp3lame --enable-libopus --enable-librist --enable-libssh --enable-libtheora --enable-libvpx --enable-libwebp --enable-libzmq --enable-lv2 --enable-libvpl --enable-openal --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopenmpt --enable-librav1e --enable-librubberband --enable-schannel --enable-sdl2 --enable-libsnappy --enable-libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable-libuavs3d --disable-libdrm --enable-vaapi --enable-libvidstab --enable-vulkan --enable-libshaderc --enable-libplacebo --disable-libvvenc --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable-libzimg --enable-libzvbi --extra-cflags=-DLIBTWOLAME_STATIC --extra-cxxflags= --extra-libs=-lgomp --extra-ldflags=-pthread --extra-ldexeflags= --cc=x86_64-w64-mingw32-gcc --cxx=x86_64-w64-mingw32-g++ --ar=x86_64-w64-mingw32-gcc-ar --ranlib=x86_64-w64-mingw32-gcc-ranlib --nm=x86_64-w64-mingw32-gcc-nm --extra-version=20250310
libavutil 59. 39.100 / 59. 39.100
libavcodec 61. 19.101 / 61. 19.101
libavformat 61. 7.100 / 61. 7.100
libavdevice 61. 3.100 / 61. 3.100
libavfilter 10. 4.100 / 10. 4.100
libswscale 8. 3.100 / 8. 3.100
libswresample 5. 3.100 / 5. 3.100
libpostproc 58. 3.100 / 58. 3.100 -
OK did it all again. I'm afraid the results are the same. Vouk shows in V22 but even though it shows in V23 "about" area, it does not appear anywhere in the render options dialog.
I have the dll: voukoderproplug\voukoderproplug-vegas23.dll
Here: C:\Program Files\VEGAS\VEGAS Pro 23.0\FileIO Plug-Ins
And: VoukoderProVEGAS23-x64.fio2007-config
Here: C:\Program Files\VEGAS\VEGAS Pro 23.0 -
OK let me check all this. I did do a full uninstall. And don't worry this was not a complaint, I understand the issues with testing. I am sorry if it sounded like a complaint.
About image and edit, I meant on the forum. It is Ok in the beta forum but here those options don't seem to exist.
-
Also, cannot attach image and cannot edit typos... :-/
-
Thanks for adding the DL of v2. As I need to work, I had no choice but to install that and uninstall the beta of 3.
Notes:
- V2 does not recognise ethe newer version of FFMPGE that was installed for b3, so that had to be uninstalled and the older version, from the V2 page) reinstalled.
- Voukoder shows in the V3 about area - (funny many of us had tried copying and renaming those files previously)
- Unfortunately, Voukoder does not show up as an actual Render Option even when making sure that all options are displayed in the render window etc.
(Cannot attach image here to show above)
-
tbh honest, I only bought Vouk a few weeks before it stopped working V22 and then moved to V23. So, I think since purchase I must have used it for about 3 renders, haha.
This is not a complaint at all, but I think it would be nice to consider those of us who bought pro quite late in the day. -
Does the Designer work with beta3?
Yes, sorry I thought I had replied to this. The Designer is working fine now.
-
top/lower field first
As you can see in my project, I do not have those options.

-
-
This error is actually misleading. It complains that no interlace type has been set (-1). Can you check what type you have set in your project? Upper first, lower first or progressive?
Ahh that explains that then, I have Interlace Type set to Blend Fields but often turn it off completely. Also, fwiw, Resample is always disabled here.
I did try some other settings for Interlace Type but still get the crash. The render immediately goes to 100%, no file is created, and Vegas then crashes. -
I thought it might be useful to post my scene. This is basically the only one I ever use. Although there are a couple of versions of it.
scene.zip -
OK Installed b3. No crash on opening the designer.
But still crashing on render in Vegas 23:
Problem Description
Application Name: VEGAS Pro
Application Version: Version 23.0 (Build 289)
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Fault Address: 0x00007FFA482728C3
Fault Offset: 0x00000000000128C3Fault Process Details
Process Path: C:\Program Files\VEGAS\VEGAS Pro 23.0\vegas230.exe
Process Version: Version 23.0 (Build 289)
Process Description: VEGAS Pro
Process Image Date: 2025-09-15 (Mon Sep 15) 18:52:24
Attaching latest logs. I see:
2025-09-27 21:10:39 (info) [VoukoderPro.cpp:628] Unsupported pixel format: -1At the end of the log.
This was just 4K project with nothing in except a little generated media. -
Do you still need the log file? If so, please direct me to where it stored: (Windows 11). Thanks.
-
Vegas 23 On starting Render, (using nVidia in my Voukoder design), I can hear my video card fans spin up to full speed (4090) goes crazy, but the render does not happen.
And then Vegas 23, freezes and either crashes or must be closed manually.
If there any logs I can send, please let me know, it is easily reproducible.
W11 | Intel i9 | 128GB RAM | nVidia 4090 (4K @ 65") | FF UCX | UAD2 QUAD
-
Just to add that on starting Render, (using NV in my design), I can hear my video card fans spin up to full speed (4090) goes crazy, but the render does not happen. And then Vegas 23 either crashes or must be closed manually.
Sorry I realise that this is separate issue, and you requested one post per issue. I will start a new topic for this.
-
Standalone only
Then started Vegas
I don't tend to do designer inside Vegas.