Beiträge von Joe24

Zitat von Vouk

I can't include x264 and x265 because of licensing reasons.

Understood. Is this still in the works for the paid version of VoPro?

If you want to hardware-encode to h.264 format on an old computer, just buy a cheap video card and use the card's built-in NVENC or AMF hardware encoder (shown in your list above). Doesn't matter how old your CPU is for that.

Or you can use the x264 software encoder, which will be very slow but should still work on older CPUs. Voukoder classic includes the x264 encoder. VoukoderPro so far does not.

Haven't found it yet. Vegas Pro 20, Voukoder 13.0.2. So far I've tried:

• Muting the master audio bus.
• Muting all individual audio tracks.
• Deleting all audio tracks.
• Options -> Mute All Audio.

No worries, I'll just use VoukoderPro.

Zitat von Vouk

It should be present in Voukoder classic.

Am I looking in the wrong place? I don't see anything that says Animated GIF.

Zitat von mamomo

I don't see any option to export in GIF format

I don't either . . . Sounds like a Vouk-level question.

It's one of the 3 default templates that come with VoukoderPro. Start with this template, link your desired Scene to it (Customize Template . . .), and rename it to your liking.

I don't know if it will solve your GIF issues, but that's how you export transparency (alpha).

I've never worked with GIFs, but for transparency renders you'll need to start with the YUVA template in Vegas -> Render As -> VoukoderPro. Then link your desired Scene and save the template as whatever name you want.

In the Vegas "Render As" menu, make sure you have "Show Favorites Only" de-selected.

If neither Voukoder nor VoukoderPro works on your rig, there's something screwy with your system settings. Lots of successful users with Vegas 21.

Your vRender times are 100x higher (slower) than mine.... and my system is not new. Some of your vRender times (the time Vegas takes to render the frame before it gets fed into Voukoder/VoPro) are over 1 second, which is bonkers. On a system like yours, I'd expect at least double-digit fps . . . not <1 fps.

[20:02:18] Frame #49: vRender: 798341 us, vProcess: 0 us, vEncoding: 3036 us, aRenderEncode: 906 us, Latency: 802295 us
[20:02:19] Frame #50: vRender: 1071685 us, vProcess: 0 us, vEncoding: 4496 us, aRenderEncode: 566 us, Latency: 1076763 us

Are you trying to run any other programs at the same time (e.g., mining?), or is Vegas running out of RAM? To be clear, you're saying that all projects malfunction, without exception? Have you tried creating a simple new project and rendering that?

Does it render without using Voukoder? Or using Voukoder but software rendering, like x264? Are your video drivers up to date?

Yes VoukoderPro works fine in Vegas 21. On the other hand, Voukoder 13 predates Vegas 21, so possibly there are some issues there?

When you install VoukoderPro, you have to manually select your NLE (Vegas 21, etc.) from the setup menu. This is not automatic. Seems to confuse a lot of people.

Always stops on frame #102? That's odd. Do you have "Render Loop Regions Only" set in Vegas render options?

Can you elaborate on what you mean by the render "freezing"? Do you have to force-close Vegas, or what?

No errors that i can find in the logs. Maybe somebody else can see something. The fact that it's rendering at all is puzzling.

The AAC codec in FFmpeg used to have a bug that would glitch on anything over 48 kHz sample rate, although i thought that was fixed years ago. Did you try 48 kHz?

Also, maybe try changing video and audio formats, see if you can pin the error down to some specific setting or format.

Does VoukoderPro give you the same problems?

Can you enable low-level logging in your Voukoder options?

Tried your settings in Vegas 20 with the same version of Voukoder, and it works . . .

[20:14:06] - Audio -------------------------------------
[20:14:06] Timebase:        1/192000
[20:14:06] Channels:        2
[20:14:06] Encoder:         aac
[20:14:06] Options:         _sampleFormat=fltp b=192000 profile=aac_low
[20:14:06] Side data:       <none>
[20:14:06] Filters:         filter.adelay#delays=8525S:all=1
[20:14:06] ---------------------------------------------
[20:14:06] Opening codec: h264_nvenc with options: gpu=0|multipass=disabled|preset=p6|profile=high|qp=15|rc=constqp
[20:14:06] Opening codec: aac with options: b=192000|profile=aac_low
[20:14:06] Failed opening codec: aac
[20:14:06] Unable to open audio encoder: aac
[20:14:06] Closing encoders ...
[20:14:07] Opening encoder failed! Aborting ...
[20:14:07] Unable to open encoder.

Lower the audio sample rate of your Vegas project and try again. AAC has a limit of 96 kHz.

Log file?

Zitat von JJM

using Voukoder 13.1

And there's your problem. Use version 13.0 instead.

See this forum: Output file is not playable on Windows

Zitat von buddhabas

What's the correct configuration of ffmpeg?

What i mean to say is that something about your audio/video output format from Vegas needs changing. It's probably nothing major.

What specifically are you trying to do? What is your video project resolution, framerate, format, etc? What is your audio sample rate and bit depth?

Post your most recent logfile from your %localappdata%\VoukoderPro\logs folder. That will likely tell us what the problem is.

Are you using Voukoder, or VoukoderPro? Which version?

Excellent!

Confirmed working in version 0.7.5. It is now possible to run complex filters on any of the 3 GPUs in the system, or shuffle video data back and forth between the GPUs as desired. Thanks!

Updated 3-GPU test scene (extremely inefficient, just a proof-of-concept), works in VoukoderPro 0.7.5: 3-GPU test scene for VoukoderPro 0.7.5.zip

Confirmed working. Thanks!

The following may be the problem:

Zitat von Vouk

Code

hwupload_cuda=gpu=1

Correct syntax should be: hwupload_cuda=1

It is in fact possible to use multiple GPUs from a single FFmpeg command line. There doesn't seem to be a lot of information out there on this topic. However, the following example uses GPU0 to perform resolution-scaling, then GPU1 and GPU2 to encode different formats (1080p, 720p).

In FFmpeg command line, assigning each NVENC encoder "-gpu 1" or "-gpu 2" is completely pointless, as the encoder always uses whatever GPU was targeted by the previous hwupload_cuda command, regardless of NVENC GPU preference in the command line. If you (nonsensically) specify separate GPUs for Upload and Encode, the Upload GPU setting overrides the Encode GPU setting, and both actions take place on the Upload GPU. So adding/removing the NVENC "-gpu" options makes no difference in function.

Using 3 GPUs is hilariously inefficient for such a small job, but the following command is a working example of FFmpeg running a complex operation using 3 GPUs at once. Using uncompressed AVI file input, which seems the most similar to what VoPro is doing (no hardware decoding):

ffmpeg -y -probesize 42M -analyzeduration 10 -i "d:\temp\input.avi" -filter_complex:a "[0:a]asplit [asplit1][asplit2]" -filter_complex:v "[0:v]hwupload_cuda=0, split [split1][split2], [split1]scale_cuda=1920:1080:interp_algo=4:format=yuv420p:force_original_aspect_ratio=1, hwdownload, hwupload_cuda=1 [split1scaled],[split2]scale_cuda=1280:720:interp_algo=4:format=yuv420p:force_original_aspect_ratio=1, hwdownload, hwupload_cuda=2 [split2scaled]" -map "[asplit1]" -c:a ac3 -b:a 96k -map "[split1scaled]" -c:v h264_nvenc -gpu 1 -2pass 0 -b:v 2500k -maxrate 5000k -bufsize 5000k -bluray-compat 1 -coder 1 -cq 0 -g 48 -level 4 -preset:v p7 -profile:v high -rc:v vbr -rc-lookahead 20 -tune:v hq "output_1080v4.9.mp4" -map "[asplit2]" -c:a aac -profile:a aac_main -b:a 96k -map "[split2scaled]" -c:v h264_nvenc -gpu 2 -2pass 0 -b_ref_mode:v middle -preset:v p7 -profile:v 2 -qp 30 -rc 0 -rc-lookahead 20 -tune:v hq "output_720v2.1.mp4"

Corresponding VoPro Scene would be something like this: 3-GPU.scene.zip This cannot yet be tested due to the current bug (as of version 0.7.4).