0.56.04 madness build - features plus encoding changes
- Thread starter Lain
- Start date
- Status
Re: 0.56.03 MADNESS build - features plus encoding changes
Well I was just meaning to the frequency of framedrops, it sends out frames out at a different frequency than before, but generally yea, if you're dropping any frames you definitely have something wrong with your configuration.
Well I was just meaning to the frequency of framedrops, it sends out frames out at a different frequency than before, but generally yea, if you're dropping any frames you definitely have something wrong with your configuration.
Re: 0.56.03 MADNESS build - features plus encoding changes
thx for adding the colormatrix/range flags
viewtopic.php?f=7&t=6680
but this is not done with quicksync and mostlikely not possible ?
orginal picture http://picload.org/image/oodicoa/testpictrure.png
obs recording renderd with a proper video renderer http://picload.org/image/oodicor/ob2test.mp4_snap.png
just greate work!
i reported an issue with 120 fps quicksync and force CFR.
with this version it is not possible to record with quicksync at 120 fps at all it doesn't work with or without Force CFR
madness error:
log
still works fine with 0.554b odc i checked the 120 recording and they are true 120 fps
thx for adding the colormatrix/range flags
viewtopic.php?f=7&t=6680
but this is not done with quicksync and mostlikely not possible ?
orginal picture http://picload.org/image/oodicoa/testpictrure.png
obs recording renderd with a proper video renderer http://picload.org/image/oodicor/ob2test.mp4_snap.png
just greate work!
i reported an issue with 120 fps quicksync and force CFR.
with this version it is not possible to record with quicksync at 120 fps at all it doesn't work with or without Force CFR
madness error:
Code:
OBS has encountered an unhandled exception and has terminated. If you are able to
reproduce this crash, please submit this crash report on the forums at
http://www.obsproject.com/ - include the contents of this crash log and the
minidump .dmp file (if available) as well as your regular OBS log files and
a description of what you were doing at the time of the crash.
This crash appears to have occured in the 'c:\windows\system32\kernelbase.dll' module.
**** UNHANDLED EXCEPTION: 80000003
Fault address: 000007FEFDA83C72 (c:\windows\system32\kernelbase.dll)
OBS version: Open Broadcaster Software v0.56.03 MADNESS
Windows version: 6.1 (Build 7601) Service Pack 1
CPU: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
Crashing thread stack trace:
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
000000000019F1E8 000007FEFDA83C72 000007FEF2CF5880 0000000000007530 000000000019F148 000000000019F3B0 kernelbase.dll!0x7fefda83c72
000000000019F1F0 000007FEF2B6D5A3 0000000000001389 0000000000000000 00000000001903D6 0000000077599AA6 obsapi.dll!OSTerminateThread+0x33
000000000019F220 000000013FB7DB9B 0000000000001389 000000000019F3B0 0000000000000111 FFFFFFFF00000000 obs.exe!OBS::Stop+0x6b
000000000019F2B0 000000013FB9D62E 0000000000000070 FFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFF 0000000077599B43 obs.exe!OBS::OBSProc+0xa8e
000000000019F440 0000000077599BD1 00000000008625C0 000000013FB9CBA0 00000000FFFFFED1 00000000001903D6 user32.dll!0x77599bd1
000000000019F500 0000000077596AA8 00000000001105B2 0000000000000111 0000000000001389 000007FEFBF60A29 user32.dll!0x77596aa8
000000000019F590 0000000077596BAD 0000000000239E50 0000000000000001 0000000000000000 0000000000000001 user32.dll!0x77596bad
000000000019F5E0 000007FEFBF60BBF 00000000001903D6 0000000000000001 0000000000239E50 000007FEFF5C1D18 comctl32.dll!0x7fefbf60bbf
000000000019F620 000007FEFBF647FE 000000000000FF00 0000000000030000 0000000000000202 0000000000000000 comctl32.dll!0x7fefbf647fe
000000000019F6E0 0000000077599BD1 000000000019F9C8 000007FEFBF63B20 00000000008625C0 0000000000861B10 user32.dll!0x77599bd1
000000000019F7A0 00000000775998DA 0000000000000000 0000000000000000 000007FEFBF63B20 0000000000000001 user32.dll!0x775998da
000000000019F820 00000000775967C2 00000000003B019D 00000000003B019D 000007FEFF5C2164 0000000000390000 user32.dll!0x775967c2
000000000019F8B0 000000013FB71AB9 0000000000000000 0000000000000000 000000013FB50000 0000000000000000 obs.exe!WinMain+0x9c9
000000000019FE50 000000013FBE6C00 0000000000000000 0000000000000000 0000000000000000 0000000000000000 obs.exe!__tmainCRTStartup+0x154
000000000019FF00 000000007769652D 0000000000000000 0000000000000000 0000000000000000 0000000000000000 kernel32.dll!0x7769652d
000000000019FF30 00000000777CC521 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!0x777cc521
A minidump was saved to C:\Users\Administrator\AppData\Roaming\OBS\crashDumps\OBSCrashDump2013-09-06_3.dmp.
Please include this file when posting a crash report.
List of loaded modules:
Base Address Modulelog
Code:
21:49:12: Open Broadcaster Software v0.56.03 MADNESS - 64bit ( ^ω^)
21:49:12: -------------------------------
21:49:12: CPU Name: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
21:49:12: CPU Speed: 3500MHz
21:49:12: Physical Memory: 15824MB Total, 13368MB Free
21:49:12: stepping id: 9, model 10, family 6, type 0, extmodel 1, extfamily 0, HTT 1, logical cores 8, total cores 4
21:49:12: monitor 1: pos={0, 0}, size={1920, 1080}
21:49:12: monitor 2: pos={-1920, 0}, size={1920, 1080}
21:49:12: Windows Version: 6.1 Build 7601 S
21:49:12: Aero is Enabled
21:49:12: -------------------------------
21:49:12: OBS Modules:
21:49:12: Base Address Module
21:49:12: 000000003FB50000 OBS.exe
21:49:12: 00000000F2B40000 OBSApi.dll
21:49:12: 00000000F40B0000 DShowPlugin.dll
21:49:12: 00000000F5570000 GraphicsCapture.dll
21:49:12: 00000000F5790000 NoiseGate.dll
21:49:12: 00000000F5930000 PSVPlugin.dll
21:49:12: ------------------------------------------
21:49:12: Adapter 1
21:49:12: Video Adapter: NVIDIA GeForce GTX 760
21:49:12: Video Adapter Dedicated Video Memory: 2091581440
21:49:12: Video Adapter Shared System Memory: 2147807232
21:49:12: ------------------------------------------
21:49:12: Adapter 2
21:49:12: Video Adapter: Intel(R) HD Graphics 4000
21:49:12: Video Adapter Dedicated Video Memory: 536870912
21:49:12: Video Adapter Shared System Memory: 1308622848
21:49:12: =====Stream Start: 2013-09-06, 21:49:12===============================================
21:49:12: Multithreaded optimizations: On
21:49:12: Base resolution: 1920x1080
21:49:12: Output resolution: 1920x1080
21:49:12: ------------------------------------------
21:49:12: Loading up D3D10 on NVIDIA GeForce GTX 760...
21:49:12: ------------------------------------------
21:49:12: Audio Format: 48000hz
21:49:12: Playback device Default
21:49:12: ------------------------------------------
21:49:12: Using desktop audio input: Lautsprecher (Creative SB X-Fi)
21:49:12: ------------------------------------------
21:49:12: Using auxilary audio input: Mikrofon (Creative SB X-Fi)
21:49:12: ------------------------------------------
21:49:12: Audio Encoding: AAC
21:49:12: bitrate: 160
21:49:12: Using graphics capture
21:49:12: Found QSV hardware support
21:49:12: ------------------------------------------
21:49:12: QSV version 1.6 using MFX_IMPL_HARDWARE_ANY | MFX_IMPL_VIA_ANY (actual: MFX_IMPL_HARDWARE2 | MFX_IMPL_VIA_D3D9)
21:49:12: Using 13 encode tasks
21:49:12: ------------------------------------------
21:49:12: Video Encoding: QSV
21:49:12: fps: 120
21:49:12: width: 1920, height: 1080
21:49:12: target-usage: MFX_TARGETUSAGE_BEST_QUALITY
21:49:12: CBR: no
21:49:12: CFR: no
21:49:12: max bitrate: 30000
21:49:12: buffer size: 30000
21:49:12: ------------------------------------------
21:49:12: MMDeviceAudioSource: Frequency for device 'Lautsprecher (Creative SB X-Fi)' is 1536000, samples per sec is 192000
21:49:12: MMDeviceAudioSource: Frequency for device 'Mikrofon (Creative SB X-Fi)' is 768000, samples per sec is 96000
21:49:12:
21:49:12: Profiler result for the last frame:
21:49:12: ==============================================================
21:49:12: video thread frame - [time: 0.255 ms (cpu time: 0 ms)]
21:49:12: | frame preprocessing and rendering - [time: 0.249 ms (cpu time: 0 ms)]
21:49:12: | | scene->Preprocess - [time: 0 ms (cpu time: 0 ms)]
21:49:12: | GPU download and color conversion - [time: 0.004 ms (cpu time: 0 ms)]
21:49:12: | | flush - [time: 0.004 ms (cpu time: 0 ms)]
21:49:12: ==============================================================
21:49:12:
21:49:13: Error: all encode tasks in use, stalling pipeline
21:49:13: Error: encoder is taking too long, consider decreasing your FPS/increasing your bitrate
21:49:47: WARNING: Forcibly terminating a thread after 30000 ms timeout!still works fine with 0.554b odc i checked the 120 recording and they are true 120 fps
Re: 0.56.03 MADNESS build - features plus encoding changes
for the same reason people play on 120 hz displays is much smoother and there is only a little motion blur left.
if you think "the human eye can't do anything with 120 hz"
just have a look at this
http://www.testufo.com/#test=framerates
with my 120 hz lightboost monitor i can see the white dots on the ufo clearly
on an normal lcd is just a white unsharp line and mostlikely the hole ufo is unsharp(ofc it looks even better on a 120 hz crt)
for the same reason people play on 120 hz displays is much smoother and there is only a little motion blur left.
if you think "the human eye can't do anything with 120 hz"
just have a look at this
http://www.testufo.com/#test=framerates
with my 120 hz lightboost monitor i can see the white dots on the ufo clearly
on an normal lcd is just a white unsharp line and mostlikely the hole ufo is unsharp(ofc it looks even better on a 120 hz crt)
Re: 0.56.03 MADNESS build - features plus encoding changes
That is not the point of the graph. The point of the graph as far as recording and streaming with OBS is concerned is this -- assuming a constant bitrate, the quality of QuickSync will generally be considerably less than x264. Just because its compression is far more inefficient.
That is not the point of the graph. The point of the graph as far as recording and streaming with OBS is concerned is this -- assuming a constant bitrate, the quality of QuickSync will generally be considerably less than x264. Just because its compression is far more inefficient.
Re: 0.56.03 MADNESS build - features plus encoding changes
what's your point?
what does this have to do with the problem?
quicksync is about even with x264 on very fast- super fast "this is bad".
did you even try to record 120 fps with x264 and that on a better preset then very fast so you get better compression?
with x264 i got an huge impact on y in game fps with quicksync i didn't get any notible inmapct on y game fps.
if you ask me quicksync does a pretty good work in this case far far better then x264.
i don't think so.
on top of it what settings are used for x264 in this test ? what clip and so on.
what's your point?
what does this have to do with the problem?
quicksync is about even with x264 on very fast- super fast "this is bad".
did you even try to record 120 fps with x264 and that on a better preset then very fast so you get better compression?
with x264 i got an huge impact on y in game fps with quicksync i didn't get any notible inmapct on y game fps.
if you ask me quicksync does a pretty good work in this case far far better then x264.
i don't think so.
on top of it what settings are used for x264 in this test ? what clip and so on.
Re: 0.56.03 MADNESS build - features plus encoding changes
It's too bad I don't have a modern enough CPU, otherwise I would demonstrate it to you. That it is in fact far, far more inefficient than x264. Just have a look on Google, see all the people complaining about QuickSync's relative poor performance as far as quality and compression are concerned.
QuickSync was not meant for "professional" recording and despite efforts of Intel to make it better, they still have to deliver. Yet another on-going discussion which you can find all over the web.
Based on what?freehuhn said:
It's too bad I don't have a modern enough CPU, otherwise I would demonstrate it to you. That it is in fact far, far more inefficient than x264. Just have a look on Google, see all the people complaining about QuickSync's relative poor performance as far as quality and compression are concerned.
QuickSync was not meant for "professional" recording and despite efforts of Intel to make it better, they still have to deliver. Yet another on-going discussion which you can find all over the web.
Re: 0.56.03 MADNESS build - features plus encoding changes
@Kharay
thx Xphome
the quality with x264 is not better because you have to use a very bad preset for recording 120 hz.
btw this is just offtopic if you you can make a posting a point out how bad quicksync is.
very fast x264 at way more than 120 fps for nearly zero cpu usage is not bad at all...
@Kharay
Xphome said:
thx Xphome
the quality with x264 is not better because you have to use a very bad preset for recording 120 hz.
btw this is just offtopic if you you can make a posting a point out how bad quicksync is.
very fast x264 at way more than 120 fps for nearly zero cpu usage is not bad at all...
- Status