Question / Help OBS Settting Dubble check (solved)

Status
Not open for further replies.

t8z5h3

New Member
i pulled my log from when i start a stream and i want to know if there is any thing i can do the make the quality better, the stream goes a bit fuzzy/pixelated when i am moving Twitch says everything is excellent and i not dropping frames ether... i Broadcast to www.twitch.tv/t8z5h3 and there should be a archive of video's
and ideas or thoughts about setting would be good and tested thanks.

16:36:58: Open Broadcaster Software v0.613b - 64bit ( ^ω^)
16:36:58: -------------------------------
16:36:58: CPU Name: AMD Phenom(tm) II X6 1055T Processor
16:36:58: CPU Speed: 2800MHz
16:36:58: Physical Memory: 16383MB Total, 12796MB Free
16:36:58: stepping id: 0, model 10, family 16, type 0, extmodel 8, extfamily 0, HTT 1, logical cores 6, total cores 6
16:36:58: monitor 1: pos={0, 0}, size={1920, 1080}
16:36:58: Windows Version: 6.1 Build 7601 S
16:36:58: Aero is Enabled
16:36:58: -------------------------------
16:36:58: OBS Modules:
16:36:58: Base Address Module
16:36:58: 000000003FDB0000 OBS.exe
16:36:58: 00000000EA2F0000 OBSApi.dll
16:36:58: 00000000F0A80000 DShowPlugin.dll
16:36:58: 00000000F0FA0000 GraphicsCapture.dll
16:36:58: 00000000F0F80000 NoiseGate.dll
16:36:58: 00000000F2420000 PSVPlugin.dll
16:36:58: ------------------------------------------
16:36:58: Adapter 1
16:36:58: Video Adapter: NVIDIA GeForce GTX 680
16:36:58: Video Adapter Dedicated Video Memory: 2087387136
16:36:58: Video Adapter Shared System Memory: 2147807232
16:36:58: Video Adapter Output 1: pos={0, 0}, size={1920, 1080}, attached=true
16:36:58: ------------------------------------------
16:36:58: Adapter 2
16:36:58: Video Adapter: NVIDIA GeForce GTX 680
16:36:58: Video Adapter Dedicated Video Memory: 2087518208
16:36:58: Video Adapter Shared System Memory: 2147676160
16:36:58: =====Stream Start: 2014-03-24, 16:36:58===============================================
16:36:58: Multithreaded optimizations: On
16:36:58: Base resolution: 1920x1080
16:36:58: Output resolution: 1920x1080
16:36:58: ------------------------------------------
16:36:58: Loading up D3D10 on NVIDIA GeForce GTX 680 (Adapter 1)...
16:36:58: ------------------------------------------
16:36:58: Audio Format: 44100 Hz
16:36:58: ------------------------------------------
16:36:58: Audio Channels: 2 Ch
16:36:58: Playback device {0.0.0.00000000}.{992ad8a3-db80-45c6-ad5c-922038583369}
16:36:58: ------------------------------------------
16:36:58: Using desktop audio input: Speakers (Sound Blaster X-Fi Xtreme Audio)
16:36:58: ------------------------------------------
16:36:58: Using auxilary audio input: Microphone (Sound Blaster X-Fi Xtreme Audio)
16:36:58: Using Mic QPC timestamps
16:36:58: ------------------------------------------
16:36:58: Audio Encoding: AAC
16:36:58: bitrate: 160
16:36:58: ------------------------------------------
16:36:58: device: Logitech HD Webcam C615,
16:36:58: device id \\?\usb#vid_046d&pid_082c&mi_02#7&34487801&0&0002#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bbefb6c7-2fc4-4139-bb8b-a58bba724083},
16:36:58: chosen type: I420, usingFourCC: false, res: 320x240 - 320x240, frameIntervals: 333333-2000000
16:36:58: use buffering: false - 0, fourCC: 'I420'
16:36:58: audio device: Disable,
16:36:58: audio device id Disabled,
16:36:58:
16:36:58: Using directshow input
16:36:58: Scene buffering time set to 400
16:36:58: ObsNvenc{32,64}.dll not present
16:36:58: Successfully loaded ObsNvenc.dll
16:36:58: ObsNvenc initialized successfully
16:36:58: CUDA loaded successfully
16:36:58: 2 CUDA capable devices found
16:36:58: [ GPU #0 - < GeForce GTX 680 > has Compute SM 3.0, NVENC Available ]
16:36:58: [ GPU #1 - < GeForce GTX 680 > has Compute SM 3.0, NVENC Available ]
16:36:59: NVENC internal init finished successfully
16:36:59: NVENC supports 7 h264 presets
16:36:59: ------------------------------------------
16:36:59: Video Encoding: NVENC
16:36:59: fps: 30
16:36:59: width: 1920, height: 1080
16:36:59: preset: hq
16:36:59: profile: main
16:36:59: level: autoselect
16:36:59: keyint: 60
16:36:59: CBR: yes
16:36:59: CFR: yes
16:36:59: max bitrate: 3500
16:36:59: avg bitrate: 3500
16:36:59: buffer size: 3500
16:36:59: ------------------------------------------
16:36:59: Syncing audio to video time (WARNING: you should not be doing this if you are just having webcam desync, that's a separate issue)
16:36:59: Audio timestamp for device 'Microphone (Sound Blaster X-Fi Xtreme Audio)' was behind target timestamp by 3
16:37:00: Using RTMP service: Twitch / Justin.tv
16:37:00: Server selection: rtmp://live-jfk.justin.tv/app
16:37:00: Interface: Bigfoot Networks Killer Ethernet Controller (ethernet, 1000 mbps)
16:37:00: Completed handshake with rtmp://live-jfk.justin.tv/app in 219 ms.
16:37:01: SO_SNDBUF was at 8192
16:37:01: SO_SNDBUF is now 65536
16:37:03: ++++++++++++++++++++++++++++++++++++++++++++++++++++++
16:37:03: New Scene
16:37:03: Using graphics capture
16:37:09: Total frames encoded: 274, total frames duplicated: 4 (1.46%)
16:37:09: Total frames rendered: 278, number of late frames: 0 (0.00%) (it's okay for some frames to be late)
16:37:09: RTMPPublisher::SocketLoop: Graceful loop exit
16:37:09: Average send payload: 7806 bytes, average send interval: 18 ms
16:37:09: Number of times waited to send: 0, Waited for a total of 0 bytes
16:37:09: Number of b-frames dropped: 0 (0%), Number of p-frames dropped: 0 (0%), Total 0 (0%)
16:37:09: Number of bytes sent: 3411297
16:37:09: Encoder closed
16:37:09: NVENC deinitialized
16:37:09:
16:37:09: Profiler time results:
16:37:09:
16:37:09: ==============================================================
16:37:09: video thread frame - [100%] [avg time: 1.761 ms] [children: 28.6%] [unaccounted: 71.4%]
16:37:09: | scene->Preprocess - [13.7%] [avg time: 0.242 ms]
16:37:09: | GPU download and conversion - [14.8%] [avg time: 0.261 ms] [children: 11.3%] [unaccounted: 3.52%]
16:37:09: | | flush - [7.95%] [avg time: 0.14 ms]
16:37:09: | | CopyResource - [1.31%] [avg time: 0.023 ms]
16:37:09: | | conversion to 4:2:0 - [2.04%] [avg time: 0.036 ms]
16:37:09: Convert444Threads - [100%] [avg time: 1.881 ms] [children: 99.2%] [unaccounted: 0.797%]
16:37:09: | Convert444toNV12 - [99.2%] [avg time: 1.866 ms]
16:37:09: encoder thread frame - [100%] [avg time: 4.172 ms] [children: 0.671%] [unaccounted: 99.3%]
16:37:09: | sending stuff out - [0.671%] [avg time: 0.028 ms]
16:37:09: ==============================================================
16:37:09:
16:37:09:
16:37:09: Profiler CPU results:
16:37:09:
16:37:09: ==============================================================
16:37:09: video thread frame - [cpu time: avg 0.899 ms, total 250 ms] [avg calls per frame: 1]
16:37:09: | scene->Preprocess - [cpu time: avg 0 ms, total 0 ms] [avg calls per frame: 1]
16:37:09: | GPU download and conversion - [cpu time: avg 0.168 ms, total 46.875 ms] [avg calls per frame: 1]
16:37:09: | | flush - [cpu time: avg 0.168 ms, total 46.875 ms] [avg calls per frame: 1]
16:37:09: | | CopyResource - [cpu time: avg 0 ms, total 0 ms] [avg calls per frame: 1]
16:37:09: | | conversion to 4:2:0 - [cpu time: avg 0 ms, total 0 ms] [avg calls per frame: 1]
16:37:09: Convert444Threads - [cpu time: avg 1.604 ms, total 1687.5 ms] [avg calls per frame: 4]
16:37:09: | Convert444toNV12 - [cpu time: avg 1.589 ms, total 1671.88 ms] [avg calls per frame: 4]
16:37:09: encoder thread frame - [cpu time: avg 1.371 ms, total 359.375 ms] [avg calls per frame: 1]
16:37:09: | sending stuff out - [cpu time: avg 0 ms, total 0 ms] [avg calls per frame: 1]
16:37:09: ==============================================================
16:37:09:
16:37:09: =====Stream End: 2014-03-24, 16:37:09=================================================
 

Jack0r

The Helping Squad
The nvenc is actually more meant for recording at high quality or streaming over a local network at high bitrates. You probably see the pixelation because of this.
Switching to the x264 encoder would definitely increase the quality. But you will have to test that performance wise. It might be too much for your CPU.
 

t8z5h3

New Member
The nvenc is actually more meant for recording at high quality or streaming over a local network at high bitrates. You probably see the pixelation because of this.
Switching to the x264 encoder would definitely increase the quality. But you will have to test that performance wise. It might be too much for your CPU.

anything else?
 

Jack0r

The Helping Squad
You could downscale to 720p to increase the quality a bit further. (Notice, overall quality will increase, text might look partially less good because of the smaller resolution)
Bitrate wise you are set to the maximum recommended, so I would keep it that or lower it, but definitely not increase it.
 

t8z5h3

New Member
You could downscale to 720p to increase the quality a bit further. (Notice, overall quality will increase, text might look partially less good because of the smaller resolution)
Bitrate wise you are set to the maximum recommended, so I would keep it that or lower it, but definitely not increase it.
thank you so much,
another question will moving to 64 bit help to?
 

Jack0r

The Helping Squad
The difference between encoding in the 32 or 64 bit version is very small actually. Normally below a few percent. It doesnt hurt either (unless you use a webcam or capture card that has no 64bit drivers).
 

t8z5h3

New Member
The difference between encoding in the 32 or 64 bit version is very small actually. Normally below a few percent. It doesnt hurt either (unless you use a webcam or capture card that has no 64bit drivers).

thanks for your support is there a way to fix my logs showing that my mic is out of sync?
 

Jack0r

The Helping Squad
You tried sapiens suggestion yet but still have the sync messages in your log?
Is the mic definitely not in sync on stream as well? The message itself does not necessarily mean that its noticeable.
 

t8z5h3

New Member
You tried sapiens suggestion yet but still have the sync messages in your log?
Is the mic definitely not in sync on stream as well? The message itself does not necessarily mean that its noticeable.

i think it's jest the log... so i won't worry about it at most it's like 0.75 or os.
 

Jack0r

The Helping Squad
Yup, that should be fine then, thanks for reporting back :)
I will mark the thread as solved, if you have further questions or problems, just start a new one!
 
Status
Not open for further replies.
Top