Maybe someone here since the old 32-bit foo_vis_vumeter.dll days would be kind enough to create a newly-written step-by-step guide on how to use the "VUEditor.exe" tool to edit existing or create new BIN meters. I surely need one.
Just open VUEditorGUI and load the Teac.vu sample. That has a needle and LED so you can see how it works. Then, just replace the elements you'd like to make a new skin (Back, Needle, Lamps, Glass). There are 3 steps to walk through: Moving, Angles, Lights.
Select each step and right-click on the window to get a set of options for that step. The knots option in the Angles and Lights steps sets the angle/intensity of the respective parameter at the different dB levels. There are just a few key points to snap the angles, the editor interpolates between them. Use the Preview step periodically to check the result. Finally, just export the configuration; I recommend BZIP2 and 1024 angles for the best result using Catmull-Rom interpolation (the samples use 200-ish angles).
Unfortunately you don't want to offer your plugin for CUI 
I would have loved to see it there too.
It is not that I don't want to. It is a resource management decision. I have finite leisure time to work on the component. I choose to spend it on the features I'd like to have myself and limit the possibility that other users see instabilities (or worse) by targeting a configuration that I run every day which I can personally "battle test/dogfood." But you're in luck...if you feel strongly enough about CUI you are empowered to do something about it. Let me clarify:
This component uses almost the exact structure to the MilkDrop 2 component. That code base is publicly available and if you can get that one properly working in CUI I will happily merge it into both. Fair warning: looking at how
foo_vis_spectrum_analyzer has implemented the CUI/DUI support, it will involve a multi-thousand line refactor plus a whole lot of testing of very marginal scenarios such as crashing the graphics device/docking/undocking/hibernating/sleep and all permutations of window sizing/creation/destruction. You'd also need to instrument the CUI SDK to track down and isolate/fix all of the inevitable sanitizer and fuzzer failures. Failing to do this will result in a long chain of crash messages from users and increased support burden. Lastly, CUI does not support ARM64* targets so you'd have to manage special case build configurations between Intel and Arm. None of this is fun--very much a frustrating exercise but have at it.
Topic: foo_vis_vumeter (Read 22633 times)
previous topic - next topic