WACUP

Preview Build Discussion => Preview Build Discussion => Topic started by: ada101 on October 13, 2026, 05:29:12 AM

Title: in_url claims unknown URL schemes ahead of third-party input plugins
Post by: ada101 on October 13, 2026, 05:29:12 AM

Environment
WACUP 1.99.55.25130 (x86)
Streaming Url Processor v3.11.1 (in_url.dll)
Third-party plugin: Winamp Tools WASAPI Loopback Input v0.1.1 (in_svloopback.dll), from https://github.com/JeremiahFD/winamp-tools
Windows 11

Issue
The WASAPI Loopback Input plugin registers a loopback:// scheme so visualisers can react to system audio. It loads fine and is listed under Input plug-ins. But with in_url enabled at startup, opening loopback:// is claimed by in_url:
Format Info shows “Generic”.
kbps/kHz stay blank and the loopback plugin never receives the URL.

What I’ve found
Disabling in_url makes loopback:// work, but internet radio and other streams then stop working.
Disable in_url → restart → re-enable in_url without restarting = both work: loopback:// goes to the loopback plugin and streams still play. Presumably the runtime re-enable puts in_url after the third-party plugin in the input list.
Renaming the third-party DLL to sort first (in_aaa_loopback.dll) changed nothing, and I couldn’t find a load-order setting in the ini files. So it looks like in_url is given priority over third-party input plugins regardless of name.

Request
Could in_url skip URL schemes it doesn’t actually handle, so other plugins get a chance? Alternatively, could it be consulted after third-party input plugins, or could there be a user-configurable input plugin priority or exclusion list? Thanks! And thank you for your continued development of Winamp!