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
93
3rd Party Plugins - (fb2k) / Re: Columns UI
Last post by musicmusic -
I can't tell from your videos what keys are being pressed or what actions are being taken. Generally, though, the behaviour is supposed to match the details view in File Explorer. Centring an item vertically when pressing the Up, Down, PgUp or PgDn keys would've been a bug.
95
3rd Party Plugins - (fb2k) / Re: NEW ESLyric v0.5 - an alternative lyric show component
Last post by Defender -
Quote from: ohyeah on
Pseudo-transparency might still be used under PSS, but there probably aren't many other scenarios where it's applicable now. PSS hasn't been updated for a long time, and I hardly ever use it anyway.
PSS is what I have chosen.

The same issue applies when running ESlyrics from a more modern splitter that supports transparency like JSplitter, which I also use.
Point is that the standard solid background or just the cover as a background is not much use imo.
97
3rd Party Plugins - (fb2k) / Re: NEW ESLyric v0.5 - an alternative lyric show component
Last post by ohyeah -
Quote from: Defender on
Quote from: ohyeah on
Quote from: Defender on
Quote from: ohyeah on
ESLyric v1.0.2.0
Do you intend to restore (pseudo-)transparency support?
I think very few people would use this feature.
To clarify.

Last year I had to let go of LSP3 because in combination with multisource 32bit it crashed foobar.
After some experimenting and adjusting I ended up with ESlyrics 0.5.4.1028 beta which perfectly fitted (and still does) the things I like and need in a plugin (transparency) and as a result works perfectly in harmony with the background/art system I created and I'll describe below.

In my skin I control all panels and all button bars from PSS. In PSS I have a standardized routine I use for painting all of these elements in the skin (all controlled by some buttons):

1) Paint optional shadow bezel
2) Paint optional accent color
3) Paint optional blur (two different levels) based on current cover
4) Paint optional gradient

All are optional and all can be combined.

For the panels with a single PSS button you can select what art to display on top of this painted background:

1) No art
2) Logo 1 (NameLogo based on artist - more horizontal logo)
3) Logo 2 (BandLogo based on artist - more square logo)
4) Artist country flag
5) Recordlabel Logo
6) Genre logo
7) Artist picture
8) Cover
9) Personal selectable fixed logo/picture not artist related

In case of streams I deviate a bit from the above, 4, 5 and 8 are replaced by stream station related logo's/images.

This all works fine but needs a lot of code to sanitize tags for trackartist, artist, albumartist. For streams a whole lot more code needed to be added. All in all roughly 40K code to sanitize relevant tags and get the right art.
With the current state of your plugin I can use 8 and 9 at best (and that is without without painting the background I want).
Pretty much all plugins I use offer no art or just the cover as background, but one of those displayed is enough for me and the one I use for the cover is responding to a mousewheel to change between the different art displays I offer.


On a couple of occasions (first one on 2024-06-30) I expressed my disappointment that you decided to let go of transparency support.

Now when it seems imminent current version is maturing I want to take the time to express my humble request to reconsider bringing back transparency support as it was in 0.5. Even with modern DX12 plugins (like foo_vis_vumeter) transparency can be supported.

I took the time to compose this post since it is important to me and I don't want to end up with yet another dinosaur plugin (being 0.5.4.1028) I use that has no future support.

A small video highlighting ESlyrics 0.5 in combination with my art system is attached.

I do hope you reconsider and reinstate transparency support.

Pseudo-transparency might still be used under PSS, but there probably aren't many other scenarios where it's applicable now. PSS hasn't been updated for a long time, and I hardly ever use it anyway.
98
3rd Party Plugins - (fb2k) / Re: Columns UI
Last post by deus-ex -
Why is the cursor's behaviour advancing through the playlist with the pageup/-down keys different in all versions of UI Columns compared to v1.0?

I have been trying various versions of UI Columns in recent years. I even went to reconfigure my UI Columns setup from the ground up with new releases, all without success. I still cannot get the cursor to behave as in v1.0 from 2019 (example videos attached).

Any pointers/suggestions? Thanks.

99
AAC - General / Re: QAAC: discussion, questions, feature requests, etc.
Last post by w8ub6blw -
Quote from: nu774 on
You can download libsndfile (either win32 or win64) from here: https://github.com/libsndfile/libsndfile/releases.
In the zip file you only need sndfile.dll under the bin directory, which you can copy to the same directory as qaac.exe (or qaac64.exe)

again thanks for your comment. now all work fine.

just 2 question:
1. from my post above why copy-artwork isn't by default? like qaac encoder copy tag from source to target, i think also cover need to be add by default ...
2. technical question: from ogg 160 which is the right value (for same audio quality) to encode in m4a? 73?
100
Lossless / Other Codecs / Re: New lossless audio codec in development
Last post by Hakan Abbas -
Quote from: Porcus on
What does it do, really? Sure fixed predictors, then a Levinson-Durbin on who knows how you have (or have not) windowed the data - and then: Does the machine learning start to learn from there on, or from scratch?

And are those coefficients at the end really ... did a clever third-order really improve that much over a different least squares algorithm? It shouldn't ... should it? 
DLP is completely different from Levinson-Durbin. However, it can be thought of as a dynamic version of fixed estimators. The learning mechanism in DLP is actually trying to find the best case for a block selected from zero (e.g. 512 samples), i.e. the case with the least error. Here a decision is made by looking at only 2 or 3 samples. And the mistakes made are tried to be improved. This is not very interesting.

But what is interesting is that once the appropriate parameters are set, the best result can be obtained with the same parameters in the previous or subsequent blocks. Even if this depends on the shape of the data, in my tests it can sometimes be valid for hundreds of blocks before or after. you can see this by trying it immediately. Maybe we will also see the negative aspects of the method.