Stream with Waveform 12 into OBS with Reastream..does it work?
-
- KVRer
- 2 posts since 28 Oct, 2022
1 step forward.....
Input monitoring does "solve" the problem of getting the live audio + pre-recorded backing tracks into Streamlabs/OBS kinda (you need to set the input to enable recording as well), but it's not ideal as I get an echo.
The echo can be removed if I set my audio interface to only monitor it's inputs however, this comes at the expense of muting any pre-recorded backing tracks I want to play along with! Perhaps the trick here is to calibrate the input latency compensation to remove the echo?
EDIT: Lowering the audio buffer size does help reduce the echo.
Input monitoring does "solve" the problem of getting the live audio + pre-recorded backing tracks into Streamlabs/OBS kinda (you need to set the input to enable recording as well), but it's not ideal as I get an echo.
The echo can be removed if I set my audio interface to only monitor it's inputs however, this comes at the expense of muting any pre-recorded backing tracks I want to play along with! Perhaps the trick here is to calibrate the input latency compensation to remove the echo?
EDIT: Lowering the audio buffer size does help reduce the echo.
-
- KVRian
- 502 posts since 3 Dec, 2021
Ok, I'm at my pc now. Settings/Advanced/Audio Engine - 'Run audio engine when stopped' must be selected. Add the inputs, arm them by clicking the red dot, and make sure 'Live input monitoring' is on.
-
- KVRian
- 502 posts since 3 Dec, 2021
tubes7, yeah the echo is annoying, you can drop the master volume to zero in waveform, reastream will still send, and then in the audio settings in OBS you can choose to monitor/monitor and output etc. So I just worked out it has to be 'monitor and output'. If you are playing along to a prerecorded backing track you should be able to just monitor through OBS and have Waveform master fader at zero, but you may have latency issues I guess. I've not tried that.
-
- KVRist
- Topic Starter
- 237 posts since 9 Dec, 2016 from Grand Rapids, Michigan USA
Hey! Fantastic! This seems like real progress, thanks folks! I can't wait to try it out. I won't be able to until tomorrow, I have a show today. I will let you know how it goes.
-
- KVRist
- Topic Starter
- 237 posts since 9 Dec, 2016 from Grand Rapids, Michigan USA
I am working with this right now and everything seems good EXCEPT the damn echo. It's still there, after trying all of these suggestions. So near, yet so far!
-
- KVRist
- Topic Starter
- 237 posts since 9 Dec, 2016 from Grand Rapids, Michigan USA
I think that for me this about as far as I can get. I don't think my computer is able to process things fast enough to make the echo go away. I have only a few plug ins running across nine tracks and Waveform's CPU meter is already hitting yellow. If I lower the buffer setting that gets worse. I notice the same delay when I listen to live input monitoring, before I even use OBS.
I wish there was a way to speed my machine up, running a 3rd gen i7 but I still I have some issues.
I wish there was a way to speed my machine up, running a 3rd gen i7 but I still I have some issues.
-
Peter Widdicombe Peter Widdicombe https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=336849
- KVRian
- 1205 posts since 29 Aug, 2014
Do you get a repeated echo, or a one-shot repeat?
A repeated echo would indicate a return path error (loop), so it's regenerating somewhere.
A one-shot repeat could be the original signal plus delay coming from ASIO. Plus, you may HEAR it, but it may not show up in the OBS stream, as it may only get the output from Waveform and not the original signal.
Plus - you are monitoring via headphones and not getting a room-audio back into the microphone feedback?
A repeated echo would indicate a return path error (loop), so it's regenerating somewhere.
A one-shot repeat could be the original signal plus delay coming from ASIO. Plus, you may HEAR it, but it may not show up in the OBS stream, as it may only get the output from Waveform and not the original signal.
Plus - you are monitoring via headphones and not getting a room-audio back into the microphone feedback?
Waveform 13; Win10 desktop/8 Gig; Win11 Laptop; MPK261; VFX+disfunctional ESQ-1
-
- KVRist
- Topic Starter
- 237 posts since 9 Dec, 2016 from Grand Rapids, Michigan USA
Thanks for your help, let me respond to each of your questions...
Do you get a repeated echo, or a one-shot repeat?
I believe it's a one shot repeat, but a bit hard to tell until I look once again, later on today.
A repeated echo would indicate a return path error (loop), so it's regenerating somewhere.
A one-shot repeat could be the original signal plus delay coming from ASIO. Plus, you may HEAR it, but it may not show up in the OBS stream, as it may only get the output from Waveform and not the original signal.
I think it's an ASIO issue too and I am testing by having OBS record the test takes in video so I can watch back and see what would be sent out if I were streaming and the echo is there.
Plus - you are monitoring via headphones and not getting a room-audio back into the microphone feedback?
That's right, the room speakers are off so no room audio is being sent back. Thanks for your help!
Do you get a repeated echo, or a one-shot repeat?
I believe it's a one shot repeat, but a bit hard to tell until I look once again, later on today.
A repeated echo would indicate a return path error (loop), so it's regenerating somewhere.
A one-shot repeat could be the original signal plus delay coming from ASIO. Plus, you may HEAR it, but it may not show up in the OBS stream, as it may only get the output from Waveform and not the original signal.
I think it's an ASIO issue too and I am testing by having OBS record the test takes in video so I can watch back and see what would be sent out if I were streaming and the echo is there.
Plus - you are monitoring via headphones and not getting a room-audio back into the microphone feedback?
That's right, the room speakers are off so no room audio is being sent back. Thanks for your help!
