Resolume 5 and nvidia optimus how to#
Resolume 5 and nvidia optimus driver#

In any case, I don't mean to pull your thread too far OT and I do hope you find a solution for your GPU issues. In practice NDI performs so much better over typical gigabit networks that I find I prefer it, and its flexibility to handle floating point audio and different video encodings (YUV, higher bit depths etc) means it's very useful alongside tools like Notch and Smode. To be sure Spout2NDI and NDI2Spout are likely going to have some sort of queue depth internally to handle the translation, even if the buffer is only 1-2 frames. So I didn't use it enough to notice any latency issues. I was never able to handle both NDI input & output at the same time using the builds that were available for Magic when I tested it, and similarly when I was using the modules in parallel as you're using them there was some instability as well.

This might be the implementation for Magic? When implemented in hardware they tout 16 scan lines or one field of latency, and even implementations prior to 2016 were one frame (not one field, though this is less of a differentiator in the progressive scan era). I haven't even begun in that direction though.Д®dit: if there was anyway for me to set a flag on a shortcut to change the title or the output title for each instance of the SpoutLink it would help me with the output organization naming.

Resolume 5 and nvidia optimus driver#

I super appreciate everyone's involvement in trying to solve this with me (OffWorldLive, Spout, & MMV folks as well), since this is a problem with AMD if there is a way for me to connect the actual source of the issue - AMD and their driver support - I'm going to look for that contact information as well and try to file a bug report through that.

It also does not consistently work in the same way that the SpoutSender does where it will send the entire Magic source out instead of only the source input that it is in line with. NDI has a noticeable lag when used on the same machine though, so Spout is my preference. The things I want to do with TD involve the requirement of an Nvidia card, so that will be a totally unknown amount of time in the future. I was only using TD as a link so I can now eliminate TD until I am actually using it for visuals. I have tested using multiple open copies of SpoutLink and can pull each output source exactly as expected and bring them in to OBS as expected as well. The workflow includes some NDI outputs because I've been going between Spout and NDI to try to figure this issue out (they are currently on bypass). I have included a link to a screenshot on what my workflow looks like for outputting to Spout. You'll have to forgive me for neglecting to give that bit of info as well. One piece of information I forgot to mention is that I am using a MMV Plugin given to me by Scottie Fox that allows you to Spout out and name the source.

Obviously I don't want to have to run a middle program just to get MMV into OBS.ДЇor my system I'm running AMD CPU & GPU: Ryzen 5 3600X & Radeon RX 6700 XT Attachments Distortion happening from Spout MMV -> OBS obs-mmv-issue1.png (786.22 KiB) Viewed 3456 times chabuku Posts: 16 Joined: Tue 6:39 pm The workaround I've been using for the last month is Spouting out from MMV into TouchDesigner works fine, and Spouting out from TouchDesigner to OBS works fine as well. If I use the Spout Sender from the SpoutSDK into OBS it works, if I use the Spout Receiver to check what is coming out of MMV it works. It only seems to happen directly when importing into OBS from MMV.

Resolume 5 and nvidia optimus how to#

Looking for ideas on how to fix this issue. The issue started with OBS 26 (over a month ago) and the previous stable version of Spout-OBS. I opened an issue on the Off-World Spout-OBS github, and have installed a clean OBS (without any other plugins - only Spout-obs), but that did not seem to work at all. I'm having an issue where using Spout to output to OBS is causing some glitches in OBS.