Sorry was looking at the wrong thing.
Sorry, How do I know it's at the clock I bought it at? :x
AMD auto-detect told me I have the latest drivers, but I'll try manualling installing the 15.5
OBS branch with AMD VCE support.
- Thread starter jackun
- Start date
Sorry was looking at the wrong thing.
Sorry, How do I know it's at the clock I bought it at? :x
AMD auto-detect told me I have the latest drivers, but I'll try manualling installing the 15.5
Well that should be close enough. I think they are supposed to run at 1833 but I could be wrong.Sorry was looking at the wrong thing.
Sorry, How do I know it's at the clock I bought it at? :x
AMD auto-detect told me I have the latest drivers, but I'll try manualling installing the 15.5
Ah so any recommendations on what I should do?
Did you attempt a full driver wipe with DDU then reinstall? make sure there is a restart to safemode with DDU, it will guide you.
Does running OBS as admin or 32bit mode run better.
jackun
Developer
2015-06-18: [32bit] [64bit] Update to git head and merge Kobata's h264 profile level and no resolution checking patch.
As of now no resolution checking is done (future VCE may support larger resolution sizes like tonga/fiji support 4k), unsupported settings give the "encoder init failed" message box. Check the logs to be sure.
Also it seems you get no email alerts when not logged in which I always forget to do :P
As of now no resolution checking is done (future VCE may support larger resolution sizes like tonga/fiji support 4k), unsupported settings give the "encoder init failed" message box. Check the logs to be sure.
Also it seems you get no email alerts when not logged in which I always forget to do :P
Last edited:
Yes, started in safemode with ddu, full uninstall driver and reinstall fresh from website
Lucil
Member
does this new integration allow for 1080 @48 on quality now? or allow @30?
Kobata
Member
The limits are based on what your card can do, and to some extent how much you bandwith you can use.
VCE1/2 cards (everything current except R9 285, R9 380, Carrizo APU, and presumably fury-based cards) can do 1080p30 quality, and somewhat higher framerates at speed setting. VCE3 can do up to ~4k30/1080p120 quality. Realistically, either way 1080p30/720p60 is about the maximum you can get passable quality out of at twitch bandwidth (3500 max). Offline recording and some other streaming sites allow higher bandwidth, which can let you do more.
Mantle or DX11?
kamild_
Member
@jackun
Not sure if I'm being ignored but 5 "pages" ago I've reported an issue which is still happening on v0.651b.
Using the latest beta drivers, HIS Radeon R9 280X, not overclocked. If there's anything I can help with troubleshooting the issue, just let me know :) I wanted to report an issue on GitHub but I can't see the "Issues" section.
Also are changes submitted by @Kobata important for people who are using OBS for local recording instead of streaming?
Not sure if I'm being ignored but 5 "pages" ago I've reported an issue which is still happening on v0.651b.
Also I've just upgraded OBS to the latest version and while playing CS:GO the driver suddenly "stopped responding" - it hung for 10 seconds, then the game started working but OBS refused to work until I've restarted the computer.
Using the latest beta drivers, HIS Radeon R9 280X, not overclocked. If there's anything I can help with troubleshooting the issue, just let me know :) I wanted to report an issue on GitHub but I can't see the "Issues" section.
Also are changes submitted by @Kobata important for people who are using OBS for local recording instead of streaming?
Last edited:
There were resolution limits placed by Jackun for anything over 1080@60 to error out quickly instead of having the driver fail later down the line, jackun removed them to accommodate for the r9 285 (and other GCN 1.3 cards).
it shouldn't affect streaming or anyone currently using resolutions since, if your streaming, you shouldn't be doing it at 2k or 4k.
does the replay buffer just not work at all? is your issue occasional? does it matter how long? do hotkeys change the result, as in, being in game when you start-stop the replay buffer?
kamild_
Member
I've never crashed the way I mentioned earlier until I updated to 0.651b, which crashed in the first 5 minutes. I'm going to play some CS:GO right now with replay buffer enabled and I will let you know ASAP. Regarding the hotkeys, I actually have problems with them not working sometimes - although I can start replay buffer manually but I can't save it.
EDIT: It must have been some really bad luck back then. Now I played the game for over an hour and OBS worked fine, except when I wanted to save a replay after 30 minutes of playing (the replay buffer is set to 10 minutes), my PC started lagging badly, OBS was like "CPU is overwhelmed with encoding" and it finally crashed. Probably should have reduced the replay buffer, hmm...
Last edited:
Matthew M. Dean
Member
If I use b-frames and save a VOD, both MPC-HC and VLC will drop frames and blur the picture.
core warning: picture is too late to be displayed (missing 101 ms)
Disabling H/W decoder has no effect. Using the x264 encoder bframes works fine.
Setting b-frames to 0 fixes the problem. Radeon 7790.
core warning: picture is too late to be displayed (missing 101 ms)
Disabling H/W decoder has no effect. Using the x264 encoder bframes works fine.
Setting b-frames to 0 fixes the problem. Radeon 7790.
Last edited: