VAAPI Encoder 0.4.1

[Tuna]

Tuna submitted a new resource:

VAAPI encoder - GStreamer based VAAPI encoder

GStreamer based VAAPI encoder implementation. Taken out of the GStreamer OBS plugin as a standalone plugin. Simply because the FFMPEG VAAPI implementation shows performance bottlenecks on some AMD hardware.

Read more about this resource...

 

[Tuna]

Tuna updated VAAPI Encoder with a new update entry:

0.2.0

• Support for new VA plugins from GStreamer 1.22.
• Previous encoders are labeled "Legacy", but are still select-able.
• Support for low power encoder variants (by kode54).
• Support for AV1 encoder (AV1 is WIP by upstream, expected to hit in the next GStreamer cycle).
• Support for more input color formats.
• Much more informative logging all over the place.
• Probably other small fixes and hiccups.

Starting with this version the minimum required OBS version is now...

Read the rest of this update entry...

 

[Tuna]

Tuna updated VAAPI Encoder with a new update entry:

0.3.0

• Change encoder search approach. Should pick up encoders on multi-gpu setups.
• Encoder IDs have changed. You will have to reconfigure your encoder.
• Log only prints discovered encoders now. Logs current used encoder.

Read the rest of this update entry...

 

[Tuna]

Tuna updated VAAPI Encoder with a new update entry:

0.3.1

Fix some encoder strings names being garbage.

Read the rest of this update entry...

 

[Tuna]

Tuna updated VAAPI Encoder with a new update entry:

0.4.0

• Lookup human readable render device names for easier selection.
• Use postproc element from the selected encoder device to avoid cross GPU transfers.
• Legacy encoder also uses legacy postproc. Makes device selection easier. Move to new encoders if issues pop up. (But no need to have new va plugin installed if only interested in legacy encoders )
• Some internal restructuring. Fingers crossed I didn't break anything by accident..

Read the rest of this update entry...

 

[Tuna]

Tuna updated VAAPI Encoder with a new update entry:

0.4.1

Fix a potential segmentation fault while enumerating devices.

Read the rest of this update entry...

 

[ProtoDot]

Quick question: how do the various QP settings relate to the single QP setting in OBS' default encoders?