Question / Help Razer Ripsaw Doesnt work in OBS Windows 10 Black Screen

[Ayamarka]

I m using Razer Ripsaw in 2 PC streaming setup but even if my streaming pc recognises the card I get OBS Studio black screen when I use Video Capture.
Thank you in advance!

Streaming PC OBS Log :

Here is OBS Log :

11:42:58.010: CoInitializeEx succeeded: 0x00000001
11:42:58.010: CPU Name: AMD Phenom(tm) II X4 955 Processor
11:42:58.010: CPU Speed: 3222MHz
11:42:58.010: Physical Cores: 4, Logical Cores: 4
11:42:58.010: Physical Memory: 8189MB Total, 5243MB Free
11:42:58.010: Windows Version: 10.0 Build 18363 (release: 1909; revision: 778; 64-bit)
11:42:58.010: Running as administrator: true
11:42:58.011: Aero is Enabled (Aero is always on for windows 8 and above)
11:42:58.011: Windows 10 Gaming Features:
11:42:58.012: Sec. Software Status:
11:42:58.013: Windows Defender Antivirus: enabled (AV)
11:42:58.013: Windows Firewall: enabled (FW)
11:42:58.014: Current Date/Time: 2020-04-17, 11:42:58
11:42:58.014: Browser Hardware Acceleration: true
11:42:58.014: Portable mode: false
11:42:58.281: OBS 25.0.4 (64-bit, windows)
11:42:58.281: ---------------------------------
11:42:58.298: ---------------------------------
11:42:58.298: audio settings reset:
11:42:58.298: samples per sec: 48000
11:42:58.298: speakers: 2
11:42:58.299: ---------------------------------
11:42:58.299: Initializing D3D11...
11:42:58.299: Available Video Adapters:
11:42:58.302: Adapter 0: NVIDIA GeForce GTX 750 Ti
11:42:58.302: Dedicated VRAM: 2105147392
11:42:58.302: Shared VRAM: 4293519360
11:42:58.302: PCI ID: 10de:1380
11:42:58.302: Driver Version: 26.21.14.4587
11:42:58.303: output 0: pos={0, 0}, size={1920, 1080}, attached=true, refresh=59, name=W2442
11:42:58.305: Loading up D3D11 on adapter NVIDIA GeForce GTX 750 Ti (0)
11:42:58.373: D3D11 loaded successfully, feature level used: b000
11:42:58.373: DXGI increase maximum frame latency success
11:42:58.373: D3D11 GPU priority setup success
11:42:59.068: ---------------------------------
11:42:59.068: video settings reset:
11:42:59.068: base resolution: 1920x1080
11:42:59.068: output resolution: 1920x1080
11:42:59.068: downscale filter: Bicubic
11:42:59.068: fps: 60/1
11:42:59.068: format: NV12
11:42:59.068: YUV mode: 601/Partial
11:42:59.068: NV12 texture support enabled
11:42:59.070: Audio monitoring device:
11:42:59.070: name: Default
11:42:59.070: id: default
11:42:59.071: ---------------------------------
11:42:59.073: [CoreAudio encoder]: CoreAudio AAC encoder not installed on the system or couldn't be loaded
11:42:59.074: Failed to load 'en-US' text for module: 'decklink-ouput-ui.dll'
11:42:59.115: [AMF] Unable to load 'amfrt64.dll', error code 126.
11:42:59.117: [AMF] AMF Test failed due to one or more errors.
11:42:59.117: Failed to initialize module 'enc-amf.dll'
11:42:59.139: [obs-browser]: Version 2.8.6
11:42:59.142: NVENC supported
11:42:59.199: Couldn't find VLC installation, VLC video source disabled
11:42:59.205: A DeckLink iterator could not be created. The DeckLink drivers may not be installed
11:42:59.206: No blackmagic support
11:42:59.210: ---------------------------------
11:42:59.210: Loaded Modules:
11:42:59.210: win-wasapi.dll
11:42:59.210: win-mf.dll
11:42:59.210: win-dshow.dll
11:42:59.210: win-decklink.dll
11:42:59.210: win-capture.dll
11:42:59.210: vlc-video.dll
11:42:59.210: text-freetype2.dll
11:42:59.210: rtmp-services.dll
11:42:59.210: obs-x264.dll
11:42:59.210: obs-vst.dll
11:42:59.210: obs-transitions.dll
11:42:59.210: obs-text.dll
11:42:59.210: obs-qsv11.dll
11:42:59.210: obs-outputs.dll
11:42:59.210: obs-filters.dll
11:42:59.210: obs-ffmpeg.dll
11:42:59.210: obs-browser.dll
11:42:59.210: image-source.dll
11:42:59.210: frontend-tools.dll
11:42:59.210: enc-amf.dll
11:42:59.210: decklink-ouput-ui.dll
11:42:59.210: coreaudio-encoder.dll
11:42:59.210: ---------------------------------
11:42:59.210: ==== Startup complete ===============================================
11:42:59.214: All scene data cleared
11:42:59.214: ------------------------------------------------
11:42:59.273: WASAPI: Device 'Speakers (Razer Ripsaw HD)' [48000 Hz] initialized
11:42:59.274: Switched to scene 'Scene'
11:42:59.274: ------------------------------------------------
11:42:59.274: Loaded scenes:
11:42:59.274: - scene 'Scene':
11:42:59.274: ------------------------------------------------
11:42:59.422: [ffmpeg] [AVIOContext @ 000001d83bb08b40] Statistics: 386 bytes read, 0 seeks
11:43:13.230: User added source 'Video Capture Device' (dshow_input) to scene 'Scene'
11:43:13.231: Video Capture Device: DecodeDeviceId failed
11:43:13.231: Video Capture Device: Video configuration failed
11:43:13.315: ---------------------------------
11:43:13.315: [DShow Device: 'Video Capture Device'] settings updated:
11:43:13.315: video device: Razer Ripsaw HD HDMI
11:43:13.315: video path: \\?\usb#vid_1532&pid_0d01&mi_00#8&1e5996ab&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global
11:43:13.315: resolution: 1920x1080
11:43:13.315: flip: 0
11:43:13.315: fps: 60.00 (interval: 166666)
11:43:13.315: format: YUY2

 

[carlmmii]

Change the resolution from "Device Default" to "Custom", and set the resolution manually to 1920x1080.

 

[Ayamarka]

Thank you for answering!Didnt work :( do want me to paste the new log?

 

[carlmmii]

No need.

Unfortunately, the ripsaw has a known issue with not wanting to play nice with 1080p60 feeds. I would try deactivating and reactivating to see if somehow that can kick it into getting a proper handshake, but every experience I've had with my own ripsaw resulted in the 1080p feed ultimately freezing after a certain amount of time randomly, which could only be fixed by the deactivate/reactivate.

720p60 always worked just fine for me, fwiw.

 

[Ayamarka]

Sigh I have the same problem when I connect her on another pc she freezes after some time randomly..So you suggest to change OBS output to 720p60?

 

[carlmmii]

If it will let you. I can't remember if it can actually deal with changing the resolution directly to 720p60, or if the input signal has to be 720p60 itself.

I will mention, something you may want to try is using a different HDMI cable for the 1080p capture. This is one instance where cable quality absolutely does matter.

Also, in case you're plugging the ripsaw into front-panel USB... don't. Always plug directly into the motherboard ports.

 

[Ayamarka]

Nah I have it alone in rear usb controller..Plus I use the same HDMI cable which I ve test her in the other pc and it worked..she doesnt let me change the signal in 720p :S Sight I m pretty sure this is just synapse doing all this mess...Seriously Razer make some proper drivers for your hardware..I mean its a pity.Thank you for answering me mate really appreciate it

 

[vapeahoy]

when i used usb capture cards, i always had to rewrite the display resolution of the capture card for 1080p but i also found benefits for 720p ie to make it fit close to a 59.993hz or +/- to finetune it to be in effect full 60hz. System timer also matters here. Im not familiar with the ripsaw but iirc there was something about it using the same components as the avermedia lgx extreme. Regardless, try tweaking the resolution with custom resolution utility or modding the driver itself. 1080p is however best used for painting streams to showcase your work imo, where you can combine it with other settings to max the picture quality. Another thing i found best usecase for with usb capture card was to use internal motherboard header and directly connecting the capture card to that. Which removed some cases of black screen by simply being just a few percent of a milliseconds faster. It was a really ridiculous solution of extremely small but cumbersome adjustment that made it all just work much better.
In the end i let it go as a permanent solution due to overheating over time, but i could have fixed that with just taping a fan to the capture card, but eh. If you have intel chipset for usb, always use that. The smallest things can have the greatest impact..

 

[Ayamarka]

Problem is that i cant do anything with this ridiculous Synapse thing..I mean this software is a joke.Giving a capture card with no software to make adjustments is just a joke..Apart from that I ve tried the rest plus my mobo has not intel usb I think..This is the mobo https://www.gigabyte.com/Motherboard/GA-990XA-UD3-rev-30/support#support-dl-driver-usb30.But the thing is that windows fully recognise the card which makes me sceptical bout the obs settings or just u know a little adjustment to obs might make it work

 

[King James 911t]

I've had this happen too. I play on xbox and use a Ripsaw HD to my laptop. I find that when I plug my capture card in I see the video settings window pop up. After that I have to reboot my computer with the USB plugged in from a fresh reboot then it will show in OBS.. If i dont half the time OBS won't see the feed or it dies after a few mins.. If I do the plug in, reboot fresh and start again trick it seems to work every time with no black screen or dropping after a few mins.. Not sure what the deal is but it seem that it doesn't like to be plugged in and work right away.

Not sure if that will help you but I had the same problem and its resolved it for me. Good luck.

 

[vapeahoy]

IIRC i had the very latest SB950 am3+ motherboard at the time with asmedia usb 3 controller, which at least exists to this day on many motherboards. Cant recall etron being a large chip maker, seems like a specific thing for that motherboard series by gigabyte. I bought an adapter which allowed me to attach the capture card directly to the motherboard. I've put it away in some box but it was something like this : https://www.cablesdirect.co.uk/images/usb-3-0-motherboard-header-adapter-p2688-6337_image.jpg
Not exactly tho but similar.
The problem still is that USB has been thru so many incarnations even in usb 3.0 itself. It hasn't been made more intuitive either with the latest changes to it's naming scheme. The main problem going thru with it is controlling latency to a silly degree. And i hate to say it, but cabling quality matters, but unfortunately chipset even more so. The advantage of putting it directly to motherboard was, on the motherboard i had, that it was it's own dedicated slot and not shared by anything. I had an asus m5a97 mobo iirc, sold it all long ago to a good friend for the cost of the monitor i gave along with it.

If we look at it from a technical standpoint, usb 3.0 was the first viable option for higher resolution, 720p/1080p-60fps- with little overhead left.
720p will claim about 3gbps bandwidth, 1080p about 4.2, this being peak numbers. USB 3 capable of delivering 5gbps. Having some overhead for the bandwidth, regardless if we talk about usb or ethernet or whatever, is generally a good idea. "Prepare for unforseen consequences" - as it were. It's generally just a good idea to have some safety net and not push everything to the max to have some assurance that your system ought to be capable of whatever it is set to do.

When it comes to synapse or drivers in general, you should still be able to modify the "monitor" of your capture card with custom resolution utility, alltho i havent tried this capture card i dont know how synapse controls it. For all i know, it will potentially overwrite any such changes, which means, install the driver but dont allow synapse to run.

IIrc on the LGX avermedia cards i have i could also edit the color profile. If you cant really do any such changes on your device, i would consider returning it. The best use case for such products would be to capture consoles output easily with little work.

The thing is tho that these devices simply have been killed off on a value perspective in their use cases as we today have better solutions for cheaper or same cost. They also leave all the work in general up to the computer, so if the usb chipset greatly or rather inefficiently i should say utilize the cpu/ram to the extent it becomes a bottle neck for other things, as gaming, that becomes a big problem. And that is a real concern as IRQ priority will take place, even tho most devices today are possible to be MSI controlled, it will still be an extra load on voltage for the computer that is shared for other devices. Hence the importance of trying to separate the capture card from other usb devices by attaching it to it's own usb hub.

tldr: usb capture cards is painful, certainly at least with first gen usb 3 motherboards and inefficient usb chipsets.