megaphone66640
New Member
https://gist.github.com/825885a994c66186cbc85588116609ac
13:08:33.193: ==== Startup complete ===============================================
13:08:33.196: All scene data cleared
13:08:33.196: ------------------------------------------------
13:08:33.263: WASAPI: Device 'Speakers (Realtek High Definition Audio)' initialized
13:08:33.265: Switched to scene 'Scene 1'
13:08:33.265: ------------------------------------------------
13:08:33.265: Loaded scenes:
13:08:33.265: - scene 'Scene 1':
13:08:33.265: - source: 'ripsaw' (dshow_input)
13:08:33.265: ------------------------------------------------
13:08:33.269: ripsaw: DecodeDeviceId failed
13:08:33.269: ripsaw: Video configuration failed
13:08:33.310: adding 42 milliseconds of audio buffering, total audio buffering is now 42 milliseconds
13:08:33.439: Update check: last known remote version is 0.16.2
13:09:14.676: ==== Shutting down ==================================================
This is a two pc setup. The video capture device is a Razer Ripsaw. It captures from my gaming pc via hdmi and transmits to streaming pc via usb 3.0. Streaming pcs both have obs studio and both are running OBS studio 64. I project the gameplay with game capture on gaming pc to the ripsaw monitor (gaming pc is 144hz and ripsaw is 60hz) with obs' project full screen preview to select monitor feature.
I have reinstalled w10 pro from media creation tool. I can't roll back to a previous build (I saw the sticky). I have tried uninstalling synapse and deleting all razer files from windows (including x86, programdata, and %appdata%), and reinstalling and switching usb ports. RipsawUSBPortChecker service is running and on automatic startup.
The ripsaw worked after anniversary update up until the last few days. There are a couple threads about this and there might not be a fix yet, but I am definitely asking for someone here to consider our issues. I tried to upload the log files here but I dont know how your upload thingy works, so theres the url to github. Thanks in advance
*I just tried to use the ripsaw on another pc I used to stream from and it worked. That pc was also a streaming pc in a two computer setup. It is using windows 10 home, instead of windows 10 pro. It is also up to date with the latest windows build. I am at a loss.
**my streaming pc wasnt completely up to date, downloading the recent revision to 14393 and I will try again
***everything is up-to-date. still no go with the ripsaw detection by obs studio
13:08:33.193: ==== Startup complete ===============================================
13:08:33.196: All scene data cleared
13:08:33.196: ------------------------------------------------
13:08:33.263: WASAPI: Device 'Speakers (Realtek High Definition Audio)' initialized
13:08:33.265: Switched to scene 'Scene 1'
13:08:33.265: ------------------------------------------------
13:08:33.265: Loaded scenes:
13:08:33.265: - scene 'Scene 1':
13:08:33.265: - source: 'ripsaw' (dshow_input)
13:08:33.265: ------------------------------------------------
13:08:33.269: ripsaw: DecodeDeviceId failed
13:08:33.269: ripsaw: Video configuration failed
13:08:33.310: adding 42 milliseconds of audio buffering, total audio buffering is now 42 milliseconds
13:08:33.439: Update check: last known remote version is 0.16.2
13:09:14.676: ==== Shutting down ==================================================
This is a two pc setup. The video capture device is a Razer Ripsaw. It captures from my gaming pc via hdmi and transmits to streaming pc via usb 3.0. Streaming pcs both have obs studio and both are running OBS studio 64. I project the gameplay with game capture on gaming pc to the ripsaw monitor (gaming pc is 144hz and ripsaw is 60hz) with obs' project full screen preview to select monitor feature.
I have reinstalled w10 pro from media creation tool. I can't roll back to a previous build (I saw the sticky). I have tried uninstalling synapse and deleting all razer files from windows (including x86, programdata, and %appdata%), and reinstalling and switching usb ports. RipsawUSBPortChecker service is running and on automatic startup.
The ripsaw worked after anniversary update up until the last few days. There are a couple threads about this and there might not be a fix yet, but I am definitely asking for someone here to consider our issues. I tried to upload the log files here but I dont know how your upload thingy works, so theres the url to github. Thanks in advance
*I just tried to use the ripsaw on another pc I used to stream from and it worked. That pc was also a streaming pc in a two computer setup. It is using windows 10 home, instead of windows 10 pro. It is also up to date with the latest windows build. I am at a loss.
**my streaming pc wasnt completely up to date, downloading the recent revision to 14393 and I will try again
***everything is up-to-date. still no go with the ripsaw detection by obs studio
Last edited:
