• The preset loader is rather broken when invoked with the help opened
• The song title seem to come straightly from the playlist. I would love to get an evaluated one in the mood of the Window title for example, in order to get the details from streams
• The title animation at song change doesn't seem to work
• Changing basic component parameters while it is working doesn't seem to make it crash most of the time, but the changes often require a foobar restart to be applied
• The framerate limiter doesn't seem to work above 40 fps which seem the highest I could get

• I'll look into the preset loader rendering. It was working fine for me and could navigate the whole directory tree up/down--scary enough that I put a limiter so it can't easily jump out the foobar2000 profile directory. I'll try hard to make it look bad so that I can fix it.
• Not exactly, the song title field comes from the metadata and simply grabbing "%title%". Am I understanding correctly that what you want is to be able to customize that into say any arbitrary metadata display? Complex stuff like these or something else?
  
  Code: [Select]

  [%album artist% - ]['['%album%[ CD%discnumber%][ #%tracknumber%]']' ]%title%[ '//' %track artist%]
  %codec% | %bitrate% kbps | %__bitspersample% bit$ifequal(%__bitspersample%,1,,s) | %samplerate% Hz | $caps(%channels%) | %playback_time%[ / %length%]

  May be a nice addition to the preferences.
• Do you mean the 3D flying animated song title that is in the DirectX 9 version? If so, I haven't ported that yet and forgot to grey out that and the custom messages which are definitely works-in-progres.
• Unless you're changing the advanced preferences the changes should take without restarting on the next frame render. Some might be unstable if changed during running. If I'm not mistaken Winamp makes you stop the visualization to launch the configuration window. (BTW, have not found how foobar2000 lets components know changes have been applied in advanced prefs).
• The frame rate runs off the Win32 timer, you're seeing basically the limit of how fast that can pump messages into the window. I don't think it'll run in single-digit milliseconds. If the limiter is faster, it will not be the limiting factor. I'm looking into migrating to the threadpool timer, a timer queue or (my preference) the StepTimer that uses QFC directly. Just be careful to not burn out your GPU.

I'll look into the preset loader rendering. It was working fine for me and could navigate the whole directory tree up/down--scary enough that I put a limiter so it can't easily jump out the foobar2000 profile directory. I'll try hard to make it look bad so that I can fix it.

Not exactly, the song title field comes from the metadata and simply grabbing "%title%". Am I understanding correctly that what you want is to be able to customize that into say any arbitrary metadata display? Complex stuff like these or something else?

Code: [Select]

[%album artist% - ]['['%album%[ CD%discnumber%][ #%tracknumber%]']' ]%title%[ '//' %track artist%]
%codec% | %bitrate% kbps | %__bitspersample% bit$ifequal(%__bitspersample%,1,,s) | %samplerate% Hz | $caps(%channels%) | %playback_time%[ / %length%]

May be a nice addition to the preferences.

Do you mean the 3D flying animated song title that is in the DirectX 9 version? If so, I haven't ported that yet and forgot to grey out that and the custom messages which are definitely works-in-progres.

Unless you're changing the advanced preferences the changes should take without restarting on the next frame render. Some might be unstable if changed during running. If I'm not mistaken Winamp makes you stop the visualization to launch the configuration window. (BTW, have not found how foobar2000 lets components know changes have been applied in advanced prefs).

The frame rate runs off the Win32 timer, you're seeing basically the limit of how fast that can pump messages into the window. I don't think it'll run in single-digit milliseconds. If the limiter is faster, it will not be the limiting factor. I'm looking into migrating to the threadpool timer, a timer queue or (my preference) the StepTimer that uses QFC directly. Just be careful to not burn out your GPU.

Thanks for the feedback.

• This is a personal project for which I had never had any intention to grow beyond a single user (me). All development has been done in my spare time, outside of my professional obligations.
• I am not a graphics programmer nor have any professional experience in that area.
• I have only tested the component on a single machine, a single graphics card and a single monitor.
• I do not code sign the DLL, so be cautious of the provenance of your builds.
• While the DLL is linked to NOT have any UAC or elevated privileges beyond what the application loading the DLL has, foobar2000 does try to elevate during install and at other times. Be mindful of security and run your applications and this DLL in the most isolated environment practicable.
• I am not affiliated with the foobar2000 developers, the projectM developers, the Winamp team or Nullsoft.
• Regarding licensing, I tried to be thorough in documenting provenance of all source code. Nevertheless, there might be some oversights.

1>-- Could NOT find BISON (missing: BISON_EXECUTABLE) (Required is at least version "3.8")
1>-- Could NOT find FLEX (missing: FLEX_EXECUTABLE) (Required is at least version "2.6")

• Install Visual Studio 2022 and Git. Clone the repository. "Open a project or solution" and point it to the foo_vis_milk2.sln file.
• Ensure you have all you need for Visual Studio by doing Tools->Get Tools and Features... In the installer that comes up hit the More dropdown and select Import configuration. In the file selection dialog, point it to .vsconfig in the repo to install things like NuGet, ATL and a few other things.
• In Solution Explorer, if the "foo_vis_milk2" project is not bold font, right click on it and select Set as Starter Project
• In Solution Explorer again, right click on the Solution 'foo_vis_milk2' line at the top and select Manage NuGet Packages for Solution. Use the tab that comes up to install DirectXTK and WTL; they should be pre-populated but you can search if not. I ignore dependencies, but you can install XAudio if you find it simpler than tinkering with the options.
• Download the foobar2000 SDK and place it in the external directory according to the file layout in the README. Then use the CLI (PowerShell below) to patch it:
  
  Code: [Select]

  Set-Location -Path "path\to\repo"
  Set-Location -Path "$(Get-Location)\external"
  git init
  git add foobar2000\ libppui\ pfc\
  git commit -m 'Initial commit'
  git apply --ignore-whitespace --whitespace=nowarn --verbose "$(Get-Location)\fb2ksdk.patch"
  Remove-Item -Path "$(Get-Location)\.git" -Recurse -Force

• Clone the projectm-eval repo into the external directory and patch it in a similar manner to the SDK:
  
  Code: [Select]

  Set-Location -Path "path\to\repo"
  Set-Location -Path "$(Get-Location)\external\projectm-eval"
  git apply --ignore-whitespace --whitespace=nowarn --verbose "$(Get-Location)\..\pmeel.patch"

• Then just select your desired build configuration, for example Debug x64 and do Build->Build Solution.
• For quick debugging I have this in my foo_vis_milk2.vcxproj.user (obviously all configs but only including Debug x64 to illustrate--obviously your install locations may be different). It includes how to attach foobar2000 to the debugger and update the version of the component DLL with the most recent build:
  
  Code: [Select]

  <?xml version="1.0" encoding="utf-8"?>
  <Project ToolsVersion="Current" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">
      <LocalDebuggerCommand>$(LocalAppData)\Programs\foobar2000_x64\foobar2000.exe</LocalDebuggerCommand>
      <LocalDebuggerDebuggerType>NativeOnly</LocalDebuggerDebuggerType>
      <DebuggerFlavor>WindowsLocalDebugger</DebuggerFlavor>
    </PropertyGroup>
    <ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">
      <PostBuildEvent>
        <Command>copy "$(TargetPath)" "$(LocalAppData)\Programs\foobar2000_x64\profile\user-components-x64\foo_vis_milk2"</Command>
      </PostBuildEvent>
      <PostBuildEvent>
        <Message>Copying "$(TargetFileName)" to components directory...</Message>
      </PostBuildEvent>
    </ItemDefinitionGroup>
  </Project>

• As a bonus, for the Columns UI SDK you can download it and place it in the external directory. Then in Solution Explorer, right click on the Solution 'foo_vis_milk2' line at the top and select Add->Existing Project.... In the file picker find columns_ui-sdk-public.vcxproj and click the Add button. Then follow their documentation.

• It appears that setting mesh size to anything other than minimum (8x6) consistently crashes foobar for me (If I'm not mistaken, this is default, despite 48x36 being labeled as default)
• The "Reset page" button on the context menu doesn't appear to work
• It's a minor detail, but the time between automatic preset changes and the threshold for hard cuts were both set to minimum when I finally got the component working, so the display was initially strobing like crazy.
• The keyboard menus can cause crashes. Pressing L twice or scrolling to the bottom of the presets menu consistently crash foobar for me.
• The "previous preset" button on the context menu appears to make the preset title in the context menu get stuck.

there is something called milkdrop3. it works on ANY audio source.

... I assume there must've been some leftover glitched out configuration from the previous version that was cleaned up when playing with the settings (It may have been the same thing Wabznazm was experiencing). ...

• It appears that setting mesh size to anything other than minimum (8x6) consistently crashes foobar for me (If I'm not mistaken, this is default, despite 48x36 being labeled as default)
• The "Reset page" button on the context menu doesn't appear to work
• It's a minor detail, but the time between automatic preset changes and the threshold for hard cuts were both set to minimum when I finally got the component working, so the display was initially strobing like crazy.
• The keyboard menus can cause crashes. Pressing L twice or scrolling to the bottom of the presets menu consistently crash foobar for me.
• The "previous preset" button on the context menu appears to make the preset title in the context menu get stuck.

Regardless, I'm really enjoying this component, all the patches I've tried seem to work pretty well and run very smoothly and I've been having lots of fun trying them out! Thanks for sharing this great work and even making it open source!

• On the mesh sizes, I don't know much about them. I'll have to read the original MilkDrop source to have an answer. The preferences page simply aims to pass the "original" INI file options directly to the library; the defaults were taken from the assignments in the source code.
• The "Reset page" button and the change detection does appear to work in the MilkDrop preferences page. This has been untouched for a bit so not sure if I can reproduce this.
• This is likely due to my mishandling of the preferences version update. Should not be an issue going forward and new installs should have "safe" defaults.
• I believe I've fixed these preset loading menu navigation and crashes in version 250.
• The previous preset behavior you see is a strange one. You need to create a history/stack of presets before you can go back to previous. But your observation is correct, the context menu preset name can go out-of-sync with the actual visualizer state. I believe this is a bug in the original. I've added a few extra calculations to keep the preset loading menu as well as the context menu in sync with the state in version 250.

there is something called milkdrop3. it works on ANY audio source.

... Firstly, right clicking on the Milkdrop window instantly crashes Foobar (bug report sent).

Secondly, changing the default preset folder in the Advanced Preferences doesn't stick. ...

• There is no change notification in the SDK for Advanced Preferences.
• Consequently, changes are only detected during initialization and (for now) those initial values are written back on quit. My reasoning for this is that the Advanced Preferences are sensitive values and easy to cause misbehavior, so all of the validation happens at the start and a working configuration should not be overridden at runtime.

Yea but I like in the UI as its on a tab below my playlist where I can pick other visualizers.

... One thing I noticed is that if I right click on the tab of milkdrop it crashes foobar every time. I used to run an older integration of milkdrop and I think that used to have a right click menu where you could pick the option to go fullscreen.

One other issue at the moment, when I set foobar to always on top, when I double left click on milkdrop tab then it goes a type of fullscreen but foobar is still over the top. ...

Other than that its working perfect.

Only one suggestion for this component so far: An option to skip conversion to 8-bit samples (thus skipping mapping from 0...255 to -1...+1 values since floating-point samples already have -1...+1 range to begin with)

Since foobar2000 obviously gives an array of 64-bit floating point samples to visualizations, which contains some samples outside -1...+1 range (aka. above 0dBFS samples) and aren't clipped nor wrapped-over ...

• With foobar2000 there is no "obviously". While the SDK is very thorough, it is not documented at all so there is nothing obvious about any of the things it does. See fullscreen being different between embedded and windowed or the very aggressive topmost behavior as examples.
• Looked into this and it requires changes to the `vis_milk2` audio processing internals. I'm not experienced enough in DSP to get this even remotely close to correct without many attempts.

Thanks for all the effort.  Really nice to have these visualizations

Is there a way to adjust the resolution of the full screen?  There is a thin white pixelated border around the visualization window, even with a dark theme installed.   My concern is screen burn in.   Any tips would be greatly appreciated

• At the bottom and right side there is some flashing/strobing. I managed to isolate it to the blending of the comp[osite] shader. This one, I don't know whether it's a rounding error or something else. I'll let someone more familiar with graphics programming chime in.
• The 1 pixel border around all 4 screen edges. This one does not seem to come from the DirectX rendering. I tried many ways to get rid of it such as blacking out the screen before drawing each frame and adjusting the viewport a couple of pixels to hide it but haven't zeroed in on the right code. Think I stumbled on the solution by accident in version 250. Let me know if it's gone.

@oops
Hi.
It seems to crash if the path of "foobar2000.exe" contains double-byte characters (Japanese).