Latest WACUP public preview for x86 & x64 is build #25464 (November 6th 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #25464 (November 6th 2026) (x86 & x64 changelogs)

Author Topic: [FIXED] in_url claims unknown URL schemes ahead of third-party input plugins  (Read 29276 times)

ada101

  • Newbie
  • *
  • Posts: 1
    • View Profile
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!
« Last Edit: October 24, 2026, 01:13:25 PM by dro »

dro

  • Admin / WACUP Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 5989
    • View Profile
    • WACUP (Winamp Community Update Project)
Re: in_url claims unknown URL schemes ahead of third-party input plugins
« Reply #1 on: October 16, 2026, 12:14:17 PM »
in_url wasn't meant to be taking anything that's not a [http|https]:// like url but an internal api change some time back meant it was taking anything that's :// without knowing it.

Due to the order in which the input plug-ins are loaded (there are no options to control this nor will changing the filenames help) & thus queried it means the wacup plug-ins are usually processed before any 3rd party plug-ins & in this case in_url was incorrectly claiming things preventing any other plug-ins yet to be queried as part of the "find the plug-in to use" loop. This is the inherent downside of winamp's isourfile(..) method being a first match gets it which is why I generally try to avoid using that method when it comes to wacup's implementation of the plug-in handling but for url like options it's basically the only way to do things.

I've now got things changed in in_url for the next build so it'll limit what it's trying to claim to just [http|https]://.

For aiding in debugging, prefs -> about|updates -> about tab has a box at the bottom which will show what the active input & output plug-in are to know what is trying to be used though the alt+3 dialog for url like options is also a way to figure it out.
« Last Edit: October 16, 2026, 12:20:45 PM by dro »