OBS branch with AMD VCE support.

dping

Active Member
Um don't get me wrong, but why would he deserve a mod status?! o_O
It's cool what he does with VCE and all that but how does that makes me deserve the mod status??
Is he activly moderating other spots of the forum or something i don't know about?

Well they need some sort of icon, Maybe a Dev icon on the forums? I dont know, this will help people highlight posts from the Devs :) just saying.

either way, I'm excited to try this when I get home. Did anyone verify the compatability with Win7 64? I know there were certain issues with the MSVC120D.dll file or whatever...
 

OliverMD

Member
Maybe a Dev icon on the forums? I dont know, this will help people highlight posts from the Devs
A tag of some sort makes sense, but adding him to the Moderator crew is non-sense :P
Did anyone verify the compatability with Win7 64?
The dll issue is fixed since yesterday, but i sadly can't confirm that it's working on Win7. Can all be read on the last page.
 

jackun

Developer
Last edited:

sneaky4oe

Member
Did you stop streaming/recording and then crashed? Looks like OBS hit debug break in Stop() function. It was caused by encode thread not quitting before 30 second timeout, hmm.


E: For some reason AMF seems to pass OpenCL buffer to VCE by converting it to D3D11 resource or something. Eh?

Ah, maybe that is the wrong log... Probably it is, sorry. I remember now that I was streaming afterwards... :-(
Anyways, if I'll meet that error again, I'll report instantly.
I was playing counter-strike: go.
 

OliverMD

Member
Pretty much the same code as the debug build, just in release now: 32bit, 64bit
I was just going to post "get AMF working on Win7 already :P" but then i had an interesting happening.
When i tried the "new" build it didn't instantly crashed while using AMF but took a bit longer til the bitrate started going.

The interesting part though is that it didn't crashed because of d3d11.dll, but the OBS.exe itself (according to windows)
Still al ot of "Failed to create D3D11 texture." according to the main log.
Code:
This crash appears to have occured in the 'c:\users\olivermd\desktop\obsvce_2014-09-08\obs.exe' module.

**** UNHANDLED EXCEPTION: c0000005
Fault address: 00B0A323 (c:\users\olivermd\desktop\obsvce_2014-09-08\obs.exe)
OBS version: Open Broadcaster Software v0.63b (test build 3)
Windows version: 6.1 (Build 7601) Service Pack 1
CPU: Intel(R) Core(TM) i5-3450 CPU @ 3.10GHz

Crashing thread stack trace:
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
0E55FE08 00B0A323 00279880 0E55FEEC 76F49F72 00279880 obs.exe!Convert444Thread+0x163
0E55FEA8 7695338A 00279880 7B581CC9 00000000 00000000 kernel32.dll!0x7695338a
0E55FEB4 76F49F72 00B0A1C0 00279880 00000000 00000000 ntdll.dll!0x76f49f72
0E55FEF4 76F49F45 00B0A1C0 00279880 00000000 00000000 ntdll.dll!0x76f49f45

A minidump was saved to C:\Users\OliverMD\AppData\Roaming\OBS\crashDumps\OBSCrashDump2014-09-08_8.dmp.
Please include this file when posting a crash report.

List of loaded modules:
Base Address Module
 

Attachments

  • OBSCrash.jpg
    OBSCrash.jpg
    92.2 KB · Views: 27
  • OBSCrashDump2014-09-08_8.dmp
    429.1 KB · Views: 32
Last edited:

OliverMD

Member
Last edited:

dping

Active Member
Pretty much the same code as the debug build, just in release now: 32bit, 64bit

I'll try make some space for win7 install :P
I'm upgrading with 8.1 right now to keep with the times. I looked through some of your code and saw a lot that was talking about windows 8.1 only with stuff so I bit the bullet and bought it.
 

Scyna

New Member
any idea why i get this message when i stream with amd 290? its been slowly increasing. I have been streaming for 3 hours.
  • Max keyframe interval is currently at 18.0 seconds. Please set it to 2 seconds.
 

dping

Active Member
any idea why i get this message when i stream with amd 290? its been slowly increasing. I have been streaming for 3 hours.
  • Max keyframe interval is currently at 18.0 seconds. Please set it to 2 seconds.
what do you have your idr set to under vce settings? Should be double your fps
 

vbdkv

Member
I'm upgrading with 8.1 right now to keep with the times. I looked through some of your code and saw a lot that was talking about windows 8.1 only with stuff so I bit the bullet and bought it.
Windows 9 coming this month on the 30th. With a start menu.
 

oma

New Member
Windows 9 coming this month on the 30th. With a start menu.

And still you should avoid the new Windows "9" for the first year because it will be filled with bugs and driver issues, trust me if you want to upgrade to the new windows wait at least half a year propably to be on safer side wait for one full year.
 

OliverMD

Member
Uh, ofcourse DXGI_FORMAT_NV12 is not supported on on Win7 :P
So no OBS+AMF on Win7 or what? No idea but Valve got it somehow running too and this Splashtop thing i guess.
I know I'm smartassing too much right now with my "superficial knowledge" sorry :P
And still you should avoid the new Windows "9" for the first year because it will be filled with bugs and driver issues, trust me if you want to upgrade to the new windows wait at least half a year propably to be on safer side wait for one full year.
This^ - Pretty much the basic rule for a new OS.
To make it short: Win8 is trash in my eyes and many others and the "good, bad" statistic doesn't matter after Win8.

NOW i think we should go back to the main topic of this thread before it derails too much.
 
Last edited:

jackun

Developer
@OliverMD nope ;) (as in, yes, should work on win7 too)

2014-09-10 AMF: Using host memory for surfaces (and looks like dx9 interop): 32bit, 64bit.
But setting AMF's "EngineType" property to 1 seems to make AMF use DX9. Anyway, taskmanager doesn't show weird memory fluctuations so that is nice.
 
Last edited:
Top