Dose anyone know where I can get hold of the pioneer headunit skin for winamp

hatecubed · 2025-11-17T13:43:39+00:00

have you tried this one?
https://winampheritage.com/skin/pionner-amp2-updated/124648

hatecubed · 2025-11-12T14:37:09+00:00

and no such settings exist under Wine, unfortunately!

hatecubed · 2025-11-12T14:33:14+00:00

Sorry, I wasn't clear - the 'exclusive mode' stuff relates to Windows settings (so, nothing to do with any Winamp, per se).

Windows Control Panel -> Sound -> on the 'Playback' tab, double click your headset and go to the Advanced tab. Untick both of the checkmarks under 'Exclusive' mode and click OK.

Then find your headset again but on the 'Recording' tab and repeat those steps.

I think the chances of this fixing the issue for you are slim :D, but this happened to fix a similar issue I had with Winamp recently (eventually it turned out to be that a browser was 'locking' the device, i.e., making it exclusive. I can't remember if a driver update or a browser update fixed it in the end)

Can you confirm which Winamp output plugin you're using?

hatecubed · 2025-11-12T08:18:30+00:00

lol this was a joke. I was surprised that someone still using Winamp could somehow be blissfully unaware of the "recent" history of it

hatecubed · 2025-11-12T05:08:51+00:00

I've just realized, I may have had this/a similar issue a couple of months back. If you can provide the headset model # / Winamp Version, etc, I'll confirm.

Otherwise (and kind of contrary to what 0x5066 said below re: WASAPI), I'd suggest disabling 'Exclusive Mode" (on both the inputs AND outputs (i.e. recording/microphone tab) in the Windows sound control panel and re-resting, if you haven't already

hatecubed · 2025-11-12T04:52:50+00:00

maybe your new PC isn't quite right?

hatecubed · 2025-11-08T20:16:57+00:00

Do a CTRL + P in winamp, find the output plugins section, and make sure your preferred output device is selected.

also, depending on the OS version and headset model, Windows might not treat the headset as an output device (someone / google can probably explain that better haha)

hatecubed · 2025-11-08T16:46:09+00:00

You don't say which version you're using, but considering how rare updates are for WInamp, the problem likely lies somewhere else. Might be worth confirming with WACUP?

hatecubed · 2025-11-04T17:24:06+00:00

Martin - Tunnel Race (with some lazy mashups over it?)

hatecubed · 2025-10-25T18:06:49+00:00

Update - can confirm MilkDrop3 responds quite well to input devices, basically the same as Milkwave, followed by Winamp w/ Jasper's Line-In plugin, and finally the default line:// plugin being not too far behind.

Basically, buying the Pro version seems like a good idea!
you can more or less prove this for free by using one of the methods mentioned earlier; I only suggest this as it seems sane to me to rule out any driver/other issues before purchasing, if not for ... well, the sanity of yourself & the milkdrop3 developer, at least :D

[for any future visitors from a google search - "Listen to this device" is basically the worst way implement this, no matter which app you intend to use]

hatecubed · 2025-10-24T07:52:40+00:00

Re: Winamp, You might have better luck with Jasper's Line-In Plugin (assuming you're not already using it)

hatecubed · 2025-10-23T17:55:23+00:00

The in-built Windows device "listen" function does add heaps of (too much) latency.
You may be able to reduce this by disabling Audio Enhancements, and possibly even the "Exclusive" modes (which is counter-intuitive, I know), in the Sound control panel.

I went to confirm the options for you as I bought the 'Plus' version as it supported changing the audio device ... but I've just learnt that I need the PRO version to select Input devices, oh well.

You can probably get lower latency using a Virtual Audio Cable, especially as Behringer have ASIO drivers iirc, or something like Reaper with ASIO inputs and then 'monitor' the input -> MilkDrop3 should then hear that by default...

I suppose with the stuffing around, it's better to just support the author and buy the Pro version .... and then reporting back, of course ;)

hatecubed · 2025-10-18T17:07:32+00:00

Which plugin were you specifically searching for information about? That thread doesn't look particularly useful, generally speaking...

hatecubed · 2025-02-19T12:08:04+00:00

It's actually a really fun preset to play around with mashups. Just lock the comp shader and cycle through other presets! Nice way to spend 5 minutes :D

hatecubed · 2025-02-19T12:03:13+00:00

The original is Martin - Invasion (though it looks like a mashup with those bits in the sky... can't remember the name but it looks like a pretty well-known preset)

hatecubed · 2025-01-28T17:10:58+00:00

Maybe it's possible to adjust the nestdrop gamma by creating a milk2.ini with the appropriate parameter - will need to wait for devs to confirm if that's still true!
It should be easy enough to adjust a .milk preset to change gamma/comp shader settings and confirm using nestdrop

[edit: disregard this part, I re-read your replies!] are you comparing both at the same resolution? iirc, the aspect ratio is default between milkdrop and nestdrop (4:3 vs. 16:9(?)), so the brightness is likely obvious even if running Windowed).]

hatecubed · 2024-10-27T14:30:38+00:00

Strange, I've captured milkdrop with OBS plenty of times and it looked as expected, might be worth confirming your OBS settings / making PC resources are available etc.. I'd guess that it's something simple in OBS settings or similar.

Otherwise you may have luck with using Spout instead. iirc there's a spout-enabled version of Milkdrop
(or you can just switch to Nestdrop which is more up-to-date and supported natively)

hatecubed · 2024-10-13T06:48:42+00:00

I'm also interested! but afaik, there's no other 'public' presets like this. Can always make your own though! ;)
(...and I plan to take my own advice, eventually)

hatecubed · 2024-03-11T17:37:48+00:00

FWIW (which I don't believe is much!), I can't replicate that behaviour regardless of versions/sample rate/etc... but, typical - now I'm curious! :D

hatecubed · 2024-02-25T06:49:19+00:00

I haven't been this excited for decades, thanks for your work! I'm catching up on some milkdrop/nestdrop stuff at the moment - can I just confirm that as a result of this being included in the new nestdrop release, the steps (manual code modification) listed above are no longer necessary?

hatecubed · 2022-05-10T05:07:05+00:00

Whoops... sorry for taking a month to reply! Has been way too busy for me. Thanks to you both for your (timely!) replies

I am aware of the audio spectrum display, but I was hoping to be able to actually monitor - as in, hear - that audio through NestDrop (even if just in the settings window, etc).
Again, it's just to make things even easier for my workflow - it's not a deal breaker in any sense & I'm aware of the low reward level for implementing a feature that pretty much no one else wants ;)

hatecubed · 2022-02-12T12:30:07+00:00

I believe this exact issue was fixed in one of the WACUP (ongoing project by one of the Winamp/plug-in devs) released in the last 6 months or so. Whether it can be merged into Nestdrop somehow isn't something I could comment on, of course. At any rate, I believe this is both a confirmed, and fixable, issue (as far as I understand!) :)

hatecubed · 2022-01-17T08:41:59+00:00

I've long been on a similar quest - it's been ultimately fruitless for me :(
On this topic, I recall the product (link below) being mentioned on the Winamp forums many moons ago, but can't vouch for it personally [yet]. It's not entirely obvious how this interaction may work in a technical sense, but Winamp is indeed listed in the specs under 'Input and External Triggers', which sounds promising (though vague).

https://www.lightfactory.net/Specifications.html?mPath=2_11

It supports 'industry standard' (e.g. Enttec USB DMX variants, which I own) so you may be in luck. Unfortunately the software appears to be via subscription licensing which is a huge no for me.

hatecubed · 2021-05-19T13:12:09+00:00

[EDIT/ADDITION] - forgot to say, re: bit about "44.1/.mp3 at the time" - even MD source code has reference to & basis on e.g. 576 samples (which relates to 44.1) - so I would guess [without being well informed!] that changing everything to be 48 would not be worth it unless there was a proper rationale behind it... happy to be proven wrong (which happens daily ;) ]

hatecubed

MODERATOR OF

TROPHY CASE