thanks a lot, i got them and will try importing and see what happens.
They are both built for very high-quality render using nVidia GPU but at least you will be able to see how they are put together.
thanks a lot, i got them and will try importing and see what happens.
They are both built for very high-quality render using nVidia GPU but at least you will be able to see how they are put together.
Here's a couple of my scenes. You can open the designer and import them:
This is a WeTransfer link, I only have a free account so it is valid for 3 days max.
Actually scrap that, I have no idea what to do haha.
Basically I now get these few YUVA options, whichever I clicked, I go to customise template which then opens Voukoder (designer thing?) and then I have no idea what to click in order to change the settings. If I just try to render by clicking one of these YUVA options then it says No Voukoder Pro scenes are defined yet. Please Create and select a scene first.
[Blockierte Grafik: https://ibb.co/yMHcMG8]
All seems so much more complex than when I had Vegas Pro 22
Yes, you need to create some scenes. I have always thought it would be handy to have some default presets already created there.
I could upload some of mine for you, but it is not possible to attach files in this area of the forum, and I really don't want to use filesharing.
Here are the steps that worked for me in case it helps:
You have to choose one or the other - I am currently using the V3 2026 beta option below. (But I did both these and they both work - just not together):
For Voukoder version 2:
For Voukoder version 3 2026 (beta):
Installing and running great stuff. Rendering did seem to be a lot slower than previously, but I think that might just be at my end. Anyway, bottom line 2026 working in V23. Well done.
I fixed the VEGAS Pro plugins in Voukoder Pro 2026.
That's great, I was wondering if the fix might roll over from V2. Testing it now. Will report back,
Confirm V2 working in V23. (with the new VoukoderPro-2_VEGAS_Pro_23-v3 files copied to the correct places), Nice one.
Sorry, also got confused. Can you move this to my report about V3 failing to render in Vegas 23?
Just to update here:
If there is anything I can check please do let me know.
Hi this is not solved, at least not at this end V23 is still crashing on render with Vouk, sorry.
Yes, that is fine. I only mentioned it in case it was relevant to the crash.
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)...
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?
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:
(Cannot attach image here to show above)