1
Visualisations / Re: Martins collection of milkdrop presets
« on: March 01, 2025, 05:03:28 PM »
Interesting. Alright, once I can get hold of an ATI card, I'll try.
Latest WACUP public preview for x86 & x64 is build #21640 (May 11th 2025) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #21640 (May 11th 2025) (x86 & x64 changelogs)
Unless I think you're going to be helpful, not all requests will be accepted but might still be later on. Remember that beta testing is to help me & the limitations currently works for my needs for this project.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
Visualisations / Re: Martins collection of milkdrop presets
« on: March 01, 2025, 04:35:18 PM »
Hi DrO
The common notion of shader models is not congruent with milkdrop's numbering, i.e. PSVERSION 4 may refer to something different that commonly understood as "shader model 4"... I don't remember the details but the ATI problem definitely occurs with the shader model that allows 1024 instructions rather than 512. I think that is model 3.
Back 2010, Eo.S posted an idea why this does not work, and proposed an easy fix. Sounds quite plausible but I am not an expert. Citation:
"Having run milkdrop through Microsoft's directx debugging tool PIX, I noticed that for presets that are running in pixel shader 3.0 mode, the vertex shader's are all compiled as shader model 1.1, while the pixel shaders are compiled as model 3.0.
ATI cards will not run ver 3.0 pixel shaders with non 3.0 vertex shaders. Any version of pixel shader below 3.0 can be combined with lesser versions of vertex shader, which is why 2.0 and 2.x presets still work in Milkdrop 2.
DirectX will actually issue a warning in regards to this, but not an actual error so it can be missed during development if using NVidia GPUs. I'm familiar with the error because Rendermonkey issues the warning. When I use Rendermonkey on our ATI GPU computers I have to set the vertex shader to compile for vs3.0 whenever I set the pixel shader to use PS3.0 or it doesn't render. On our Nvidia GPU computers it still issues the warning, but the GPU allows it and still renders.
This is a very easy fix codewise, as the fxc compiler just needs to be given the flag to compile VS as 3.0 for PS3 presets, so hopefully a winamp developer with access to the MD2 source can implement this fix.
It's possible this may not be the only issue, but having spent the last 6 years programming on both ATI/Nvidia GPUs I'm pretty positive this should be the whole of it.
Eo.S. "
The common notion of shader models is not congruent with milkdrop's numbering, i.e. PSVERSION 4 may refer to something different that commonly understood as "shader model 4"... I don't remember the details but the ATI problem definitely occurs with the shader model that allows 1024 instructions rather than 512. I think that is model 3.
Back 2010, Eo.S posted an idea why this does not work, and proposed an easy fix. Sounds quite plausible but I am not an expert. Citation:
"Having run milkdrop through Microsoft's directx debugging tool PIX, I noticed that for presets that are running in pixel shader 3.0 mode, the vertex shader's are all compiled as shader model 1.1, while the pixel shaders are compiled as model 3.0.
ATI cards will not run ver 3.0 pixel shaders with non 3.0 vertex shaders. Any version of pixel shader below 3.0 can be combined with lesser versions of vertex shader, which is why 2.0 and 2.x presets still work in Milkdrop 2.
DirectX will actually issue a warning in regards to this, but not an actual error so it can be missed during development if using NVidia GPUs. I'm familiar with the error because Rendermonkey issues the warning. When I use Rendermonkey on our ATI GPU computers I have to set the vertex shader to compile for vs3.0 whenever I set the pixel shader to use PS3.0 or it doesn't render. On our Nvidia GPU computers it still issues the warning, but the GPU allows it and still renders.
This is a very easy fix codewise, as the fxc compiler just needs to be given the flag to compile VS as 3.0 for PS3 presets, so hopefully a winamp developer with access to the MD2 source can implement this fix.
It's possible this may not be the only issue, but having spent the last 6 years programming on both ATI/Nvidia GPUs I'm pretty positive this should be the whole of it.
Eo.S. "
3
Visualisations / Martins collection of milkdrop presets
« on: March 01, 2025, 03:02:17 PM »
Hi there !
Long time no visit here. I am pleased to see that my old login still works, and that there is now a visualisation section. Great !
I'll take this opportunity to post my collection of milkdrop presets I made over the years. They were originally published on the winamp forum starting in 2008, but the future of that forum is uncertain, the owner does not seem to be interested and it was close to being shut down a couple of times already.
So... this pack includes not only new works but (most of) my early attempts... oh my
!
I went through all of them and made minor corrections where necessary to cope with the much faster modern GPUs, or to fix odd bugs. So if you happen to use my presets already, I recommend to replace them. They should all run ok with milkdrop v2.25c, although there's a few caveats:
- Do not use milkdrop v2.25d (comes with winamp 5.9x). It has no benefit, but it is buggy and cannot handle float to integer conversion.
- Shader model PSVERSION 4 (see at the top of the .milk files) does not work with ATI video cards, due to an old bug in the milkdrop dll I am unable to fix. Therefore I avoided model 4 where possible but there is one exception:
My latest work "emergency power supply only" is based on Nivush's ray marching code and needs PSVERSION_COMP=4, so won't run on ATI. Sorry for that. And it will take a few seconds to compile, so I recommed not to store it in your standard presets folder, as it will interrupt the smooth transition between presets. Other than that, it needs its "skin" martin_skin_emergency_power_supply.jpg, and loads three random textures found in its own folder or under the milkdrop textures folder.
If you find a problem or a missing image, please report here.
Enjoy!
Martin
Long time no visit here. I am pleased to see that my old login still works, and that there is now a visualisation section. Great !
I'll take this opportunity to post my collection of milkdrop presets I made over the years. They were originally published on the winamp forum starting in 2008, but the future of that forum is uncertain, the owner does not seem to be interested and it was close to being shut down a couple of times already.
So... this pack includes not only new works but (most of) my early attempts... oh my
! I went through all of them and made minor corrections where necessary to cope with the much faster modern GPUs, or to fix odd bugs. So if you happen to use my presets already, I recommend to replace them. They should all run ok with milkdrop v2.25c, although there's a few caveats:
- Do not use milkdrop v2.25d (comes with winamp 5.9x). It has no benefit, but it is buggy and cannot handle float to integer conversion.
- Shader model PSVERSION 4 (see at the top of the .milk files) does not work with ATI video cards, due to an old bug in the milkdrop dll I am unable to fix. Therefore I avoided model 4 where possible but there is one exception:
My latest work "emergency power supply only" is based on Nivush's ray marching code and needs PSVERSION_COMP=4, so won't run on ATI. Sorry for that. And it will take a few seconds to compile, so I recommed not to store it in your standard presets folder, as it will interrupt the smooth transition between presets. Other than that, it needs its "skin" martin_skin_emergency_power_supply.jpg, and loads three random textures found in its own folder or under the milkdrop textures folder.
If you find a problem or a missing image, please report here.
Enjoy!
Martin
4
Resolved Issues / Re: 100% CPU load when playing linein://
« on: November 12, 2019, 07:29:46 PM »
Hi DrO
I'm rather oblivious of skins and usually just keep the classic one. But, I just revisited the issue, and it does not seem to reoccur with WACUP. Sorry, I may have got confused with all the versions I installed and deinstalled.
The problem still reliably persists with winamp 5.8, fresh install, default settings, classic skin, and I'm fairly certain it is related to a windows update, as I would have noted it before. My father's old machine in particular, which used to work smoothly, now hardly responds at all when milkdrop is playing linein://
I will change to wacup.
Just for curiosity, I observed that WACUP is running CPU heavy milkdrop presets at a faster rate than winamp. That does not come for free, the CPU load also goes up proportionally. I have always ticked the "loosely enforce frame rate" box, so something seems to have changed in the fps control.
martin
I'm rather oblivious of skins and usually just keep the classic one. But, I just revisited the issue, and it does not seem to reoccur with WACUP. Sorry, I may have got confused with all the versions I installed and deinstalled.
The problem still reliably persists with winamp 5.8, fresh install, default settings, classic skin, and I'm fairly certain it is related to a windows update, as I would have noted it before. My father's old machine in particular, which used to work smoothly, now hardly responds at all when milkdrop is playing linein://
I will change to wacup.
Just for curiosity, I observed that WACUP is running CPU heavy milkdrop presets at a faster rate than winamp. That does not come for free, the CPU load also goes up proportionally. I have always ticked the "loosely enforce frame rate" box, so something seems to have changed in the fps control.
martin
5
Resolved Issues / 100% CPU load when playing linein://
« on: November 03, 2019, 02:16:36 PM »
Hi there
As of lately, when I select linein:// and press play, the PC gets sluggish, with CPU load close to 100%. No visualisation, just playing stereomix. Process Explorer indicates that the main load is caused by explorer exe; within the explorer, the main load is in shcore.dll.
When playing from CD or disk, this does not happen.
Same with all winamp versions as well as the wacup preview version. I am using windows 10 version 1903. Possibly this came in via a recent windows update, but I cannot revert to an older version to try. Issue is the same on my father's PC which is also at version 1903.
My only solution to this is to kill explorer.exe, and to restart it when I need the desktop back...
Martin
As of lately, when I select linein:// and press play, the PC gets sluggish, with CPU load close to 100%. No visualisation, just playing stereomix. Process Explorer indicates that the main load is caused by explorer exe; within the explorer, the main load is in shcore.dll.
When playing from CD or disk, this does not happen.
Same with all winamp versions as well as the wacup preview version. I am using windows 10 version 1903. Possibly this came in via a recent windows update, but I cannot revert to an older version to try. Issue is the same on my father's PC which is also at version 1903.
My only solution to this is to kill explorer.exe, and to restart it when I need the desktop back...
Martin
Pages: [1]