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.
Recent Posts
1
3rd Party Plugins - (fb2k) / Re: NEW ESLyric v0.5 - an alternative lyric show component
Last post by Defender -
Hope this portable helps ...
To be honest, the transparent background shown in the screenshot above does not attract me. The layout function + dynamic blur is more attractive in terms of overall UI coordination and the readability of the lyrics.
Of course, it depends on whether the above example attracts the author of ESLyric.

If you use JSplitter, you can take a look at [Default UI theme] foobox.
It was not meant to be attractive :-) Just to be very clear which parts are backgrounds, gradients and art that I paint as a background underneath a transparent plugin/component. I guess the pink got your attention.

Also this portable is only 17MB, The skin where I actually use the same methods would be more than 1.5GB including art.

Nice layout you made. I have made something similar using JS3 components. With some button presses I can change the layout of the skin to have a very similar look to yours.
2
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by oops -
Hi,  I don't know if it's supposed to work the same way as the old component but I installed and copied all .bin skins I had but the meters are not moving like a VU Meter at all, way too fast and jumpy even on the slower settings.  The old version was not that far from a real VU Meter movement.
It is only loading the BIN files created for the old component. It is not a behavioral reproduction for the reason that I'm very confident that the "old" version is not close to modeling a "real" VU meter's movement.

A VU meter has a very specific ballistic characteristic, that is, it responds to changing audio signals at a very precise speed, rising from no signal to 99% of 0VU when a 1kHz sine wave tone is applied for 300ms (The ballistic characteristics of the device do not permit it to accurately register transient signals shorter than 330ms).  The needle is also supposed to fall in 300ms.
I too can also read and quote Wikipedia.

Instead of preaching please share constructive suggestions on settings of how to achieve more accuracy. There are many knobs to tweak that will give different results. You can control the window width and other parameters.

What follows below is the method I used to model the needle movement. This is my wheelhouse, if you pardon the expression, so the technical level of the conversation will be raised quite substantially. If you can do better or have suggestions on how to improve it, please share. If not, please don't add your voice to the chorus of critics in these audio forums demanding perfection.

I started with the circuit from my own stereo VU meter as pictured below. I traced the PCB and got all the component values to translate it into a SPICE netlist. I even built my own model for the NJM4565 since I couldn't find an existing version. I simulated the netlist, instrumented in the standard ways to get the step/transient and impulse responses of the "system". These will come in handy later. Keep in mind that the VU meter face plate is logarithmic and so the circuit involves analog differentiator, integrator and summer circuits. Putting an oscilloscope probe on the various points of the working circuit helps in figuring out what's going on. Fun times.

Once I had the characteristics of the driving circuit I turned my attention to the needle. The needle can be modeled as a mass-spring system. So, setting up the ODE for the system (with some minor guesses) provides the behavior characteristics of the needle. This is a common second-order system with known roots, so not much to add to it.

So, after all of the pen-and-paper prework was completed, how is it actually implemented in the component? From the response of the circuit and simply looking around at real VU meters it is obvious (in general) these are set up underdamped. What is one simple way to simulate these physical characteristics on a computer animation? A PID controller! It can be implemented in about 15 lines of C++ and uses simple arithmetic. The PID coefficients are derived from the transient and impulse response targets of the SPICE simulation as those come from the voltage levels (closest to the visualization audio levels provided by foobar2000). To make it simpler for users I abstracted out the PID coefficients into simpler numbers called "rise" and "decay"--where the larger number means faster. Also "jitter" which is a control on the minimum increment to the error accumulator.

This is the method I chose to approximate the analog behavior of the needle in a discrete simulation. If you prefer another component's behavior, use that one. Or write your own as plugin makers for other players like MusicBee have done with their own spin on the simulation methodology. Or even better yet, build or buy a real analog VU meter and plug it into your DAC!

In engineering, it is a skill to know what a good enough approximation is and where to draw the line. This was clearly not the case here ;) I honestly don't think many have and would go through the trouble. That you think other components/plugins are more accurate is an illusion; not that this component is accurate either.

I hope the takeaways here are that there is some sound reasoning (no pun intended) behind the method to how the simulation is done and that I think you can achieve the desired ballistic movement with the tuning knobs provided. But it will take time and experimentation.

3
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by Chibisteven -
Hi,  I don't know if it's supposed to work the same way as the old component but I installed and copied all .bin skins I had but the meters are not moving like a VU Meter at all, way too fast and jumpy even on the slower settings.  The old version was not that far from a real VU Meter movement. 

A VU meter has a very specific ballistic characteristic, that is, it responds to changing audio signals at a very precise speed, rising from no signal to 99% of 0VU when a 1kHz sine wave tone is applied for 300ms (The ballistic characteristics of the device do not permit it to accurately register transient signals shorter than 330ms).  The needle is also supposed to fall in 300ms.


You need to enable the "Apply Inertia" option.  You can then try changing the decay rate after enabling the first option.  I also recommend turning cubic interpolation on if your system can handle it.
4
3rd Party Plugins - (fb2k) / Re: NEW ESLyric v0.5 - an alternative lyric show component
Last post by always.beta -
Hope this portable helps ...
To be honest, the transparent background shown in the screenshot above does not attract me. The layout function + dynamic blur is more attractive in terms of overall UI coordination and the readability of the lyrics.
Of course, it depends on whether the above example attracts the author of ESLyric.

If you use JSplitter, you can take a look at [Default UI theme] foobox.
5
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by SkyTrax26 -
Hi,  I don't know if it's supposed to work the same way as the old component but I installed and copied all .bin skins I had but the meters are not moving like a VU Meter at all, way too fast and jumpy even on the slower settings.  The old version was not that far from a real VU Meter movement. 

A VU meter has a very specific ballistic characteristic, that is, it responds to changing audio signals at a very precise speed, rising from no signal to 99% of 0VU when a 1kHz sine wave tone is applied for 300ms (The ballistic characteristics of the device do not permit it to accurately register transient signals shorter than 330ms).  The needle is also supposed to fall in 300ms.
6
Other Lossy Codecs / Re: ADC (Adaptive Differential Coding) My Experimental Lossy Audio Codec
Last post by Nania Francesco -
Just tested, with -t320 and with random audio FLAC sample down-mixed to mono, trimmed from start to 30 sec duration.
There is strange noisy sound at start of audio that is not present in source.
The high-end spectrum content is too much distorted for -t320 IMHO.
the -t320 option is not to be used because the -t options range from -t0 , -t1 .... -tx at most and have a function only with -h active to apply a sort of filter with t0 on a large range, with tx on a small data range. If you put the test sound online I can verify.  The factor that determines the quality is -q h and it ranges from -q20 to -q511 but these are quantization values ​​not kbps, in general your version with -q60 should produce around 300-320 kbps stereo and 160 kbps mono . The factor that determines the quality is -c h and it ranges from -q20 to -q511 but these are quantization values ​​not kbps, in general your version with -q60 should produce around 300-320 kbps stereo and 160 kbps mono   Another important thing. The audio to test must not contain images or other extra data because at the moment I have not implemented the recognition of extra data of the wav header. If it reads here data for him it is music and causes distortion. Thanks for the test
10
FLAC / Re: Flac Decode CPU requriemets by preset ?
Last post by sven_Bent -
Thank you so much for the info. I just peaked at wavepack and while it seems to do slightly better than flac in compressed size the decoding is much worse.
Not that it is important  in my current scenario  just trying to find an overall best way to do my archiving.

Flac for lossles backup and listen on computer.
and encode to mp3/aac when needed for portable use

The info was helpful . thank you