1
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.
2
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by Defender -0.9.5 released!Thx!
- Fix Columns UI fullscreen within Panel Stack Splitter (PSS) crash and skip GDI drawing when fullscreen. GDI drawing the (transparent) background is pointless because the parent PSS window is not fullscreen'd. So, the fullscreen entry methods are disabled in this context. In addition, even if not prevented, going fullscreen and returning loses the transparent background. I think this is a bug in PSS (or Columns UI) [windows hosting other windows not dealing with the fullscreen gracefully]. Only closing and reopening the player would bring back the transparency.
Just a quick reaction. In the attached screenshot I'm running 5x VU 2024 instances from CUI/PSS/JSplitter parent.
All instances are set to "Lock ratio on" and therefore don't stretch fill the parent panel they live in and therefore can show transparency of this parent panel. They all run fine and no issues with flickering needles or the like.
Of course I noticed transparency being lost when returning from fullscreen.
I paint background/art from the grandparent PSS panel (all the reddish backgrounds).
For testing purposes I changed one of the direct JSplitter parents to display a bright green background and thus overwriting the PSS painted reddish background/art.
Returning from fullscreen also the green background is lost.
PSS has nothing to do with this since the parent is a JSplitter.
Are you sure you are not disabling transparency in your code returning from fullcreen regardless of the nature of the splitter type of the parent?
3
3rd Party Plugins - (fb2k) / Re: Columns UI
Last post by dix-hill -I'm using a playlist to edit the genre fields of my tracks and I want the Genre column to have a green background, but only on the "Genres Playlist".
Thanks for any help!
4
3rd Party Plugins - (fb2k) / Re: [fb2k 2.0] Queue Viewer
Last post by Defender -I wouldn't know how even if I wanted to.Bummer.
Peter's excellent list controls in the SDK do all the heavy lifting. All my code does is fill values/update on queue changes, re-ordering etc. I don't need to know or care about any display related code. It's invisible to me. This is very different from JSP3 where every single aspect of display handling is entirely my own code.
Thanks for the answer.
5
3rd Party Plugins - (fb2k) / Re: [fb2k 2.0] Queue Viewer
Last post by marc2k3 -Peter's excellent list controls in the SDK do all the heavy lifting. All my code does is fill values/update on queue changes, re-ordering etc. I don't need to know or care about any display related code. It's invisible to me. This is very different from JSP3 where every single aspect of display handling is entirely my own code.
6
Other Lossy Codecs / Re: TOY, a lossy and experimental "do not use" codec
Last post by maikmerten -@Klymins The current encoder determines bands according to frequencies. Basically, for anything lower than 44.1 kHz, some bands would go unused. The current frequency layout is a vague approximation of the Opus band layout.
The band layout is transmitted in the TOY file and encoders can choose their own band layout. A proper, non-experimental codec would just go for a predetermined, fixed layout.
7
General - (fb2k) / Re: File operations - rename album folder to specific naming pattern?
Last post by Case -8
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by Majestyk -0.9.5 released!
I'm very happy with how development has been going. Lots is (small but) interesting problems solved, much documentation read and unfamiliar concepts learned, several moments of frustration turned to happiness when that "eureka" insight hit. Let's also keep up the good back-and-forth we're having in this thread. Thank you to for the trust and contributing through ideas, help, discussion, and, above all, testing.
This version is completely broken on my DarkOne tweak theme.
For previous versions I'm using these commands for the skin loading...
Code: [Select]
this.DarkOne4PEAK = function() {
fb.RunMainMenuCommand("View/Visualizations/Analog VU Meter skins/Peak Meter (Color Switch)/" + 0 + " " + display_system.display_arr[display_system.display_combi_colour]);
setTimeout(this.DarkOne4PEAK.bind(this), 150);
}
this.DarkOne4VU = function() {
fb.RunMainMenuCommand("View/Visualizations/Analog VU Meter skins/VU Meter (Color Switch)/" + 0 + " " + display_system.display_arr[display_system.display_combi_colour]);
setTimeout(this.DarkOne4VU.bind(this), 200);
}
In 0.9.5, all my meters are flickering back and forth between the two folders above. The only way to get it to stop doing that is to have one VU Meter only, which means things have reverted back to versions before 0.8.0.
9
General Audio / Re: How to remove certain "noise" from an audio
Last post by forart.eu -https://mvsep.com/en/homeOr, if you wanna inference locally (AND you own Intel-based CPU/GPU), give OpenVINO™ AI Plugins for Audacity a try:
https://github.com/intel/openvino-plugins-ai-audacity#readme
10
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by oops -I'm very happy with how development has been going. Lots is (small but) interesting problems solved, much documentation read and unfamiliar concepts learned, several moments of frustration turned to happiness when that "eureka" insight hit. Let's also keep up the good back-and-forth we're having in this thread. Thank you to for the trust and contributing through ideas, help, discussion, and, above all, testing.
Some detailed feature notes:
- Implement transparent bitmap extension to the BIN VU meter file specification. Expand the spoiler tag below for extensions to the BIN specification. The results shown in a previous thread can now be reproduced using the posted script.
- Extend render target for GDI-drawing into a texture 2-D resource to implement pseudo-transparency. Set "Enable Transparency" and "Remove Background" context menu options to enable. "Remove Background" removes the edge-sampled background and/or the included BG.png in the ZIP panel types.
- Add screenshot capability. Use Ctrl+Left Mouse Button on the VU Meter instance you wish to picture. A file named "screenshot.png" will be placed in the vumeter\ folder. The file is replaced every time the screen grab is triggered. To clarify it is just grabbing the pixels from the back buffer just before Present(). This only includes the client area of the single VU meter instance; not the whole screen or any of the other stuff in the player, in case that wasn't clear or properly implied.
- Centralize in-group meter switching to replace mailbox. This is a different implementation for those using the hidden main menu to switch skins. It does away with the mailbox method and watchdog timer. It should work much more reliably. The COM Automation shares this implementation so it can be used as an alternative, if desired.
- Add "Enable Transparency" and "Apply Inertia" context menu options. Their effects are described in other points.
- Add inertia envelope for audio levels. Disabling the "Apply Inertia" option will use a calculation where the next needle position is decoupled from the current position. The default value is enabled and the calculation that has been done in almost all of the previous versions.
- Add "Inertia" and "Level" options to tuning dialog. Self-explanatory, using the "Cancel" button reverts the changes.
- Fix Columns UI fullscreen within Panel Stack Splitter (PSS) crash and skip GDI drawing when fullscreen. GDI drawing the (transparent) background is pointless because the parent PSS window is not fullscreen'd. So, the fullscreen entry methods are disabled in this context. In addition, even if not prevented, going fullscreen and returning loses the transparent background. I think this is a bug in PSS (or Columns UI) [windows hosting other windows not dealing with the fullscreen gracefully]. Only closing and reopening the player would bring back the transparency.
- Adjust context menu logic for improved display of enabled and disabled options. Meaning the context menu is configuration aware. For example, from the previous point, the "Fullscreen" option is grayed out when Columns UI+Panel Stack Splitter+Apply Transparency.
- Update COM interface definition file and extend `IVUMeter` with additional methods. New interface methods include Print() and ComponentVersion(). Note, due to current architecture, there needs to be at least one instance of the VU Meter in the GUI for the COM Automation methods to not return E_POINTER error.
- Update advanced preferences. The updated "Debug output" option displays newly-categorized console messages for easier debug.
I'll work on summarizing these points into the manual. In the meantime, enjoy.
Spoiler (click to show/hide)