Repository navigation
1.9.12+ win10/11 -t spout opens explorer folder \AppData\Roaming\Spout not Spout source #487
Description
Windows 10/11 PRO
On version 1.9.12 - 1.10.1 When using Spout as source the command line opens an explorer window to
(user)\AppData\Roaming\Spout and then closes the uv.exe process
This happens on each run even if the directory already exists
1.9.12 SpoutLibrary.dll 469kb
1.9.11 SpoutLibrary.dll 2899kb
`C:>C:\ug\1_9_12\uv.exe -t spout:name=test -d gl
UltraGrid 1.9.12 (tags/v1.9.12 rev 669a27d built Oct 21 2025 08:14:30)
Display device : gl
Capture device : spout
Audio capture : none
Audio playback : none
MTU : 9000 B
Video compression: none
Audio codec : PCM
Network protocol : UltraGrid RTP
Audio FEC : none
Video FEC : none
GL setup: fullscreen: OFF, deinterlace: OFF
[GL] OpenGL 2.0 is supported...
[GL] Buffer depth - R: 8b, G: 8b, B: 8b
[spout cap.] initialized successfully, waiting for input...
Control socket listening on port 52703
Setting GL size 512x512 (512x512).`
working as expected
`C:>C:\ug\1_9_11\uv.exe -t spout:name=c1 -d gl
UltraGrid 1.9.11 (tags/v1.9.11 rev dd95a8a built Aug 20 2025 11:23:37)
Display device : gl
Capture device : spout
Audio capture : none
Audio playback : none
MTU : 9000 B
Video compression: none
Audio codec : PCM
Network protocol : UltraGrid RTP
Audio FEC : none
Video FEC : none
GL setup: fullscreen: OFF, deinterlace: OFF
[GL] OpenGL 2.0 is supported...
[GL] Buffer depth - R: 8b, G: 8b, B: 8b
[spout cap.] initialized successfully, waiting for input...
Control socket listening on port 49387
Setting GL size 512x512 (512x512).
[spout cap.] Server updated - name: c1, size: 1280x720, fps: 60, codec: RGB
SSRC 0x7ed8ce37: 128/128 packets received (100.0000%), 0 lost, max loss 0
[video dec.] New incoming video format detected: 1280x720 @60.00p, codec RGB
[display] Successfully reconfigured display to 1280x720 @60.00p, codec RGB
Setting GL size 1280x720 (1280x720).
[GL] 1 frame(s) dropped!
Last message repeated 6 times
Video dec stats (cumulative): 111 total / 104 disp / 7 drop / 0 corr / 0 miss
Pbuf: total 6290176/6290176 packets received (100.00000%).
Exit`
Activity
MartinPulec commentedon Jan 9, 2026
Thanks for reporting. I could have been able to reproduce the problem. I'll take a look into it in a near feature.
It seems like there might be some compatibility issues between UltraGrid and the Spout library. As you noticed the size change, this is because the Spout dependency needed to be updated due to the upstream changes (see da5c166). It doesn't seem to be much harmful but there werent't much other changes around this time so I don't know. I'll keep you updated.
CI Win: temporarily revert to Spout 2.007.016
[Win] set NvOptimusEnablement=0 (or by env var)
MartinPulec commentedon Jan 13, 2026
Ok, I've got some news. First of all, the problem was caused by UltraGrid incompatibility with Spout v2.007.017, which was used since the above linked commit.
Unfortunately I didn't manage to fix the compatibility with current Spout code yet but I managed to revert to the version 2.007.016, which seem to be working right now. I'm going to fix the compatibility with 2.007.017 later on.
I came across a different problem with NVIDIA Optimus. The capture didn't work unless explicitly set rendering via Intel (window displayed on notebook display). Interestingly it didn't occur in that version v1.9.11. Not sure why but I've created a workaroud for that (in referenced commit above). NVIDIA is no longer enforced (don't know what caused that).
The fixes should be already included in continuous build and it will also land to v1.10.2 later (most likely this month)
CI Win: temporarily revert to Spout 2.007.016
[Win] set NvOptimusEnablement=0 (or by env var)
vanderhoff commentedon Jan 19, 2026
Thanks for tracking this down so quickly and applying a intermediate fix @MartinPulec, will take a look and confirm
CI Win Spout2: fix MinGW vtable incompat
MartinPulec commentedon Feb 17, 2026
Hi, an update - I believe that I've fixed the issue with current Spout2 code.
The problem was perhaps introduced by a change in SpoutLibrary compatibility layer provided by Spout. We need this layer because interface of C++ code compiled by Microsoft compiler is incompatible with Clang compiler used on Windows by the UG CI with some exceptions. As the functions in the library were mingled, instead of what was intended in UG code, I believe that ShowSpoutLogs was called, opening the File Explorer, which is the thing that you observed.
The workaround patching the SpoutLibrary code in CI is already merged in Git and it is also already built to continous builds. I don't plan to back-port it to 1.10.X stable release because I believe that the previous workaround using the earlier Spout version also works (seems like Spout has quite stable interface allowing sender/receiver to use different versions of Spout).
add Spout semi-weekly test
add Spout semi-weekly test + vcap/spout hook
add Spout semi-weekly test + vcap/spout hook
MartinPulec commentedon Jul 21, 2026
Forgot to confirm - the fix landed in v1.10.2 (present thorough all newer releases) is also in continuous. In UG 1.10.x branch it is done by reverting to Spout 2.007.016 which didn't expose the problem. In UG continuous/development version, the Git version of Spout is used but I apply my fix.
Provided that the future version of Spout fixes the compatibility problem, we may switch to stable version of Spout as well... Although not necessarily - the current (for UG problematic) release 2.007.017 is from Oct 2025 so that Spout release publishing is relatively slow while from the Spout Git log there are some fixes above it (although not the one I need) so it may worth it to use rather the Git version.
I am closing the issue now because from my point of view it is fixed at this moment. Feel free to reopen or write updates. From UG perspective there may be some changes depending on the Spout upstream development.
CI semi-weekly tests: test also the release