jackun
Developer
Weird. For comparison my R9 290 , FX 8320, 8GB 1866MHz. One thing is that R9 has these dual DMA engines, though.
Last edited:
OBS branch with AMD VCE support.
- Thread starter jackun
- Start date
Please disregard, I solved it.
ExEvolution
Member
Set my ram reference clock back to 1333, kept my CPU overclock nearly the same, threw some extra voltage into the MCH because of the 390MHz FSB overclock, did a little stability testing which seemed to work out, then tried to record again. Also just barely noticed OBS can automatically upload the log
Here's the log
https://gist.github.com/anonymous/1839a7f17ead226e8658
For comparison, here's a log using x264 with --ultrafast and --opencl which is my standard settings
https://gist.github.com/anonymous/1cb8c4b88f5bc01227f0
And just to try it, here is a log where instead of using game capture, I used window capture
https://gist.github.com/anonymous/339a73da0660d8e743c9
Here's the log
https://gist.github.com/anonymous/1839a7f17ead226e8658
For comparison, here's a log using x264 with --ultrafast and --opencl which is my standard settings
https://gist.github.com/anonymous/1cb8c4b88f5bc01227f0
And just to try it, here is a log where instead of using game capture, I used window capture
https://gist.github.com/anonymous/339a73da0660d8e743c9
Last edited:
jackun
Developer
Also reinstall VS2013 runtime from first port :D But srsly that thing should be in windows update >_>
I'll make next build static again as memory issues weren't (probably) caused by that.
Last edited:
Didn't really help.
Same encoder initialization failed error again and again: https://pastee.org/7urk6
How do I fix this? :(
How do I fix this? :(
jackun
Developer
OVE doesn't agree with some setting, probably recording fps.
hey guys i see some of you have problems but jackun has helped me out a bit and it works fine for me now.
here are my settings, note that i run a Q6600 @ 3.4Ghz and a 7850 with a little overclock. also i put OBS on 2 cores and the game on all 4 cores.
and here is how my video stream looks like https://www.youtube.com/playlist?list=PLbjri73c_pnYdtxQad-tY8XiV8JDfuQfW
and on twitch itself http://www.twitch.tv/truefawkes/profile
so... try that maybe?
if there is anything to make it even better please let me know
here are my settings, note that i run a Q6600 @ 3.4Ghz and a 7850 with a little overclock. also i put OBS on 2 cores and the game on all 4 cores.
and here is how my video stream looks like https://www.youtube.com/playlist?list=PLbjri73c_pnYdtxQad-tY8XiV8JDfuQfW
and on twitch itself http://www.twitch.tv/truefawkes/profile
so... try that maybe?
if there is anything to make it even better please let me know
can we just update via obs or do we need to download the new version?
also do we keep our settings?
@jackun CHECK THIS!!! i just got this e-mail from raptr
Our new Game DVR feature
brings continuous recording
to AMD gamers
Welcome truefawkes!
If you've already heard about the Game DVR beta, apologies in advance -- but we're kind of excited about this and want to make sure everybody knows. We've added the most requested feature to AMD Gaming Evolved: continuous gameplay recording so you never miss a highlight, as well as manual start/stop recording!
Our gameplay capture takes advantage of hardware-accelerated encoding via AMD's Video Codec Engine (VCE), which means you'll see virtually no performance impact while recording. Based on independent benchmarking performed by AnandTech.com, the difference in frames-per-second with Game DVR on versus off was "consistently less than 3%."
Our redesigned client UI makes it super easy to set up, too. From the Home tab in the client Control Center, simply click Record to turn on Game DVR. With our Replay capability, we automatically capture your last 15 seconds of gameplay time (by default -- you can bump that all the way up to 10 minutes), then save a clip when you hit Ctrl + /. And with Record, use Ctrl + ; to start and stop gameplay capture at any time. You can then use the Gallery to upload clips directly to YouTube.
Restart your AMD Gaming Evolved client to update to the latest version, or new users can download it here.
interesting huh?
Our new Game DVR feature
brings continuous recording
to AMD gamers
Welcome truefawkes!
If you've already heard about the Game DVR beta, apologies in advance -- but we're kind of excited about this and want to make sure everybody knows. We've added the most requested feature to AMD Gaming Evolved: continuous gameplay recording so you never miss a highlight, as well as manual start/stop recording!
Our gameplay capture takes advantage of hardware-accelerated encoding via AMD's Video Codec Engine (VCE), which means you'll see virtually no performance impact while recording. Based on independent benchmarking performed by AnandTech.com, the difference in frames-per-second with Game DVR on versus off was "consistently less than 3%."
Our redesigned client UI makes it super easy to set up, too. From the Home tab in the client Control Center, simply click Record to turn on Game DVR. With our Replay capability, we automatically capture your last 15 seconds of gameplay time (by default -- you can bump that all the way up to 10 minutes), then save a clip when you hit Ctrl + /. And with Record, use Ctrl + ; to start and stop gameplay capture at any time. You can then use the Gallery to upload clips directly to YouTube.
Restart your AMD Gaming Evolved client to update to the latest version, or new users can download it here.
interesting huh?
jackun
Developer
I'm no codec expert but at this point I'd say it is 'normal', in that OVE API doesn't seem to respect the set VBV buffer size and always sets it to its own values. As i get it, low motion is encoded at lower bitrate so VBV buffer isn't getting much new data (right?) and old data is sent off/ eaten by decoder. Then when encoding higher motion scene, buffer is pretty much empty, encoder fills it with higher bitrate frames and then levels off to previously set bitrate (right?) Anyway CBR probably acts too much like VBR though.
mournblade77
New Member
Hi, I've been messing around with this for the past couple of days and the performance is nice. But the latest build overwrites your scenes when being launched. I set it to it's own scene profile and that has fixed the issue, but I had to re-setup all my scenes a couple of times until I figured it out.
Thanks for the great work and keep it up!
Thanks for the great work and keep it up!