Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foo_vis_milk2 (Read 84127 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: foo_vis_milk2

Reply #175 –
Quote from: unekdoud on
Not sure if it's just me, but I crash every single time I try to move cursor up in code.
  • In visualization, press M
  • Press Down 6 times, then Enter to edit code
  • Press Up
Not just you. Thanks for the easy reproduction steps. I'll investigate.

Re: foo_vis_milk2

Reply #176 –
Still investigating the report from @unekdoud .

In the interim, new release: 0.3.3.

Re: foo_vis_milk2

Reply #177 –
Quote from: unekdoud on
Not sure if it's just me, but I crash every single time I try to move cursor up in code.
  • In visualization, press M
  • Press Down 6 times, then Enter to edit code
  • Press Up
Found and put in a temporary fix for the problem. Testing it out. For context, this is caused by an integer underflow in CPlugin::WaitString_SeekUpOneLine() in "plugin.cpp". This issue is in and exists in the MilkDrop 2 library. It manifests in here because I compile foo_vis_milk2.dll for foobar2000 with more run-time checking than the original vis_milk2.dll did for Winamp. Please be aware that there could be more problems hidden in these editing modes and I don't have enough time to hunt them down or rewrite the embedded editor.

Re: foo_vis_milk2

Reply #178 –
There is a minor issue. The visualization runs on 45 fps all the time, no matter if the power or the Nvidia control panel is set to high performance, or the game is running, but if I run an Android emulator, MuMu 12, Memu9, etc... I noticed it changes to max 60 fps. Is the 45 fps a system issue? What caused it to improve the fps when running an Android emulator?

My specs
CPU: Intel Core i7 9770k
GPU: Nvidia RTX 3060 (I used 3050 previously and also got same issue)
OS: Windows 11 24h2

Re: foo_vis_milk2

Reply #179 –
This is still using the original behavior. To the best of my understanding, the FPS setting is a maximum. So, it will always be at or below the selection. In all likelihood, the value you're seeing is because of Vsync. Even if screen tearing is allowed and the maximum FPS exceeds the monitor's refresh rate (unless you have a VRR monitor) the actual number of times the frames are "presented" to the screen will be at or below the monitor's capability. More frames might be processed but not displayed.

I do not use Nvidia Control Panel and have even less of an idea about foobar2000 in Android emulation.

Re: foo_vis_milk2

Reply #180 –
I don't use foobar2000 in Android emulator. I mean when I launch an emulator, the fps limit issue of milkdrop were removed like the emulator changed the system performance I have no idea how. When I close the emulator, it goes back to 45fps

Re: foo_vis_milk2

Reply #181 –
Forgot to mention, it does stutter a bit on fullscreen so I got around 39fps. I changed max to 144fps and I got around 65fps, no stuttering on fullscreen. It looks smoother than before. My monitor is 60hz, no VRR, so 60fps is enough. Again, when any Android emulator is running in the background, I got max 144fps, it is really strange. I don't have any performance issues on my system than foobar

Re: foo_vis_milk2

Reply #182 –
Hi, I just checked out your plugin foo_vis_milk2. It appears that custom font settings are saved but don't get applied.

Side note: The release page on GitHub hasn't been updated since v0.2.0.0 from November, 17th 2024.