Status
Not open for further replies.

ball2hi

Member
II have upgraded to Win10 and am using the RC4 plugin.

Unfortunately, it doesn't seem to have solved the local recording corruption issue.
 

RuBisCO

New Member
encoder overload issue solved at rc4. FINALLY, i can record 1080p@60fps with VCE!!!
BUT, IT has too much perfomance impact. average framerate drop down 30% :(
 

Attachments

  • AMDVCEPLUGIN.png
    AMDVCEPLUGIN.png
    475.5 KB · Views: 119
  • normal.png
    normal.png
    476.8 KB · Views: 108

Xaymar

Active Member
Xaymar updated AMD Advanced Media Framework Encoder Plugin for OBS Studio with a new update entry:

1.3.0rc5 - The AMF SDK Path

  • Fixed: Localization should now fall back to en-US instead of showing untranslated strings.
  • Fixed: Debug Tracing code in Advanced interface now matches Simple interface.
  • Fixed: Bitrate shown in FLV files should now match Target Bitrate.
  • Changed: Internally now using a Single-Threaded approach.
  • Changed: Some parameters have been moved to the expert category in the Simple interface.
  • Changed: Presentation and Decode Timestamp are now the same again (fixes ffmpeg muxing issue).
  • Updated: Languages en-US (American English), de-De (German) and es-ES (Spanish).
  • Added: Ability to select Backend (Memory and Compute Type).

Read the rest of this update entry...
 
Last edited:

ball2hi

Member
Changed: Presentation and Decode Timestamp are now the same again (fixes ffmpeg muxing issue)

Oh my god! if this fixes the recording issue, I'll be happy! The tournament is going to be starting soon :)
 

Xaymar

Active Member
Oh my god! if this fixes the recording issue, I'll be happy! The tournament is going to be starting soon :)

Well, no it didn't. rc6 seems to fix it though, 44 minute recording is 757 mb big instead of the 70 mb like before.
 

seronx

New Member
Since, VCE is an IP for generating compressed bit-streams, which is based on the Tensilica Xtensa microprocessor.

Why hasn't anyone(/AMD) built x264_xtensa or x265_xtensa? Instead, choosing to provide an unknown home-grown h264 encoder.

Get Xtensa/VCE media foundation... cut out the abominable h264 code... implement x264_xtensa.dll into;
AMDh264Enc__.dll
 
Last edited:

Xaymar

Active Member
Since, VCE is an IP for generating compressed bit-streams, which is based on the Tensilica Xtensa microprocessor.

Why hasn't anyone(/AMD) built x264_xtensa or x265_xtensa? Instead, choosing to provide an unknown home-grown h264 encoder.

Get Xtensa/VCE media foundation... cut out the abominable h264 code... implement x264_xtensa.dll into;
AMDh264Enc__.dll

How would one do that? Googling x264_xtensa brough me to a bunch of fishy looking sites.
 

seronx

New Member

Xaymar

Active Member
Xaymar updated AMD Advanced Media Framework Encoder Plugin for OBS Studio with a new update entry:

1.3.0 - New Presets, updated Translations.

  • Added: 'High Quality', 'Indistinguishable' and 'Lossless' preset to Simple interface.
  • Removed: DirectCompute Compute Type since it was a misunderstanding on my part.
  • Changed: DirectX 9 is now Windows XP or greater only, DirectX 11 is Windows 8 or greater only.
  • Changed: Internal Log logic to reduce disk-related encoding slowdown.
  • Changed: 'Twitch' Preset in Simple interface now uses 'High' Profile.
  • Changed: Translations have been updated from CrowdIn.
  • Fixed: Memory Type 'Host' should now work properly.

Read the rest of this update entry...
 

Xaymar

Active Member

ball2hi

Member
How will we go about updating/using this in the current version of 0.16 by the way, since it comes pre-installed. Will your installer just over-ride/uninstall the current versions?
 

ball2hi

Member
This is very bad, I thought the issue was fixed! Maybe I messed with something I should not have. Here is an OBS log:
https://gist.github.com/b0c6864a1e475a5802e5ce52871c4f57

I have the video on my hard-drive, but it's over over 4gigs so I don't know if I could easily upload this somewhere to be easily downloaded. The matches are being scheduled for this Friday/Saturday/Sunday...! Maybe the CABAC option broke it, because I have it force enabled. Currently using the most up to date OBS + that version of the plugin (I uninstalled the plugin before installing the new OBS with the full installer)
 
Status
Not open for further replies.
Top