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.
Hi NEMO: Thank you for creating the 64.bit version. I used it for a long time on my old 32.bit version. I installed it and noticed that a bug that the 32.bit version already had is still present in the 64.bit version. It would be very favorable for me if it could be corrected. It is that when applying to a button the Quicksearch for same/Album property it does not find the album if in the %album% metadata there is any double quotation mark.
Yeah the search query builder doesn't seem to like double quotes at all. I'll try to figure out a good way to fix this.
Last post by mortalis -
Hi. Maybe someone had this problem or could point me to its root... Trying to call GetOpenFileName() method from Windows SDK (comdlg32.h), but during linking it fails with the following:
Checked in the project properties that it points to that version. And the .lib is there of course. The verbose build log also contains the path to the directory with the .lib, although it's huge and I'm not exactly sure where to look. I can attach the full log if someone needs it, but it should be reproducible on another PC I think.
Weird thing is that I found GetOpenFileName in the shared library in the foobar SDK, and it builds.
Also, when I build a minimal console app in Visual Studio with that chunk, plus include <windows.h>, it build without errors (in exe and dll modes).
Last post by Klymins - @Porcus At a low sampling rate like 5512.5Hz, you can't even access to 4kHz. Having another option for higher quality does not hurt someone.
Last post by ngs428 -
Also, is there a way to bulk download lyrics? I noticed that when you select multiple items in the playlist and right click, there isn't a context menu for ESLyrics. That is an important feature.
Hello, I have a small doubt regarding this gap when changing the window size... Any idea how to resolve this or why it's happening in the first place? I'm not blaming the plugin since this seemed to happen with other spectrum analyzer programs as well unless I change the note range and bands per octave to somewhat eliminate this gap. You can see when windowed there's a-lot of gap present at the beginning of the note compared to full-screen but I want to totally eliminate this gap.
BTW, that start and end "gap" do exist in original foo_musical_spectrum when the horizontal screen resolution is not an integer factor of number of actual bands, which is absent in this CodePen project and even older version of this component