1
Support - (fb2k) / Re: 2.25 preview uPnP bug
Last post by clark8888 -What is your UPnP renderer device?album player, old uPnP plugin 1.4 has same hires pausing problem for all uPnP renderers.
What is your UPnP renderer device?album player, old uPnP plugin 1.4 has same hires pausing problem for all uPnP renderers.
Could that cause any issues?Low pass filters do not have a specific cut off frequency, they have a transition band where attenuation gradually increases.
Many encoders employ cutoffs that appear to be as sharp as they can be. This is easily verifiable by looking at the spectrograms.
Can confirm the stars do not update. But it is just a callback that is not performed in your wrapper code.Ehm, so not sure it is a callback.
I checked running my modded Smooth Playlist next to one wrapped in your wrapper (both SMP and JSplitter 4.03).@regor The script loads but does not work as it should. Clicking on the star does not workWill look at it, as the thread states, some functions may not work. But I think those should work fine... Please lets move further discussion about that at the wrapper thread I linked before, not here. Since this is not related to JSplitter anymore.QuoteI checked and it seems the smooth js files you included are exactly the ones provided with JS3 3.8.5.Thanks for checking. Note any "error" is either a bug on my side (the wrapper) or a limit which I can not solve, so it's probably 99% sure not a problem on the scripts.
On this one, I agree with TT. We may know 3.7.x is stable, but you should not expect other users to have such info.I may have been a bit loud and harsh about the price of progress, but you should understand me too. I don't create commercial software, I don't have a personal site to publish it on, and I don't take much responsibility for what I do. I just develop a plugin in my spare time and post the results of my work so people can find it useful or not. What can I say, this thread doesn't even belong to me, I'm just here as a contributor who posts new versions for you to try and give feedback. As the topic starter, you could post the current versions in the header and declare the 4.x branch temporarily unstable, since the topic already exists, why create a new one.
So imo, the new JSPlitter v4.x versions with the latest JS Engine 128.9.0esr, should be renamed to alpha or betaOk, the next time a bug is found the version will be called 4.0.x-beta
The dark mode rendering of menus is handled entirely by Windows (and so Columns UI has no control over it, I'm afraid). When it comes to old Win32 functionality, in general, Microsoft only bothered with adding dark mode support to things that they wanted to use. Given the rarity of multi-column menus, I'm not surprised that they do not support dark mode. I recall that another dark mode bug was also reported with menus, IIRC it was with the scroll buttons for a long menu.Thanks for the hint.
@regor The script loads but does not work as it should. Clicking on the star does not workWill look at it, as the thread states, some functions may not work. But I think those should work fine... Please lets move further discussion about that at the wrapper thread I linked before, not here. Since this is not related to JSplitter anymore.
I checked and it seems the smooth js files you included are exactly the ones provided with JS3 3.8.5.Thanks for checking. Note any "error" is either a bug on my side (the wrapper) or a limit which I can not solve, so it's probably 99% sure not a problem on the scripts.
Yeah, I disagree. By the way it is with the help of forum members and "other people" I find bugs in the interaction with the new engine. I consider it the price of progress, don't you? It's a normal processThanks for explaining your reasons.
There is a reason in your words, but I will not change the direction, since the versions are released this way already. Especially everyone here knows that 3.7.x is stable, and 4.x is not yet, so no one prevents you from using the 3.7.x branch in your releases, and we will test 4.x together, at least I hope so.On this one, I agree with TT. We may know 3.7.x is stable, but you should not expect other users to have such info. There is a lot of people with limited PC knowledge which are already struggling installing a component and a script... so expecting they also know that by installing the 4.x branch, they are using a not so stable version, does not sound right to me. Info on a forum is also easily lost in a few days.