1
General - (fb2k) / Re: [Suggestions / Wishlists] for future updates
Last post by Wombat -Is there the chance to add the option in foobar changing the gap behaviour for the CUE from nearest to CD frame to always backwards?
What CPU do you have?https://imgur.com/a/khrP2OF
What about e.g. View/Visualizations/Oscilloscope?Same effect, the processing of the oscilloscope is halted while scrolling the playlist.
Not that his problem persists, in a limited way, with latest 2.25 preview: Associated art is not called up for any .flac streams (I have 6 or so in my playlist of 350 stations that stream in .flac format). .flac streams immediately call up stub image. This did not happen with 2.24. Streams in all other formats work as previously. Thanks, N.Please forgive the typos. I meant, "Note that this problems persists..." Persists also with new beta dated today. N.
The latest JavaScript engine does not like the native JavaScript .bind method anymore?The latest engine does handle binding functions differently compared to ESR102. I am gradually bringing these code sections in line with the new behaviour of the engine with respect to them. I think I just fixed "COM bug", check it yourself with 4.0.3 that I'm releasing today
@LUR what's your intention with updating the engine on every release?Research motives, to know what's changing, and it also makes sense as I'm getting closer to a stable version with each release. That's why the 3.7.x branch with stable engine interaction was created, to compare their work in the process. Moreover ‘refreshing’ every time a minor version of the engine is not a problem, significant changes in the engine are made only in major ESR releases, it's just that I am still in the process of adjusting changes from ESR102
I also think it's being counterproductive to the development and usage of the component by other people. You may not agree, that's ok.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 process
So imo, the new JSPlitter v4.x versions with the latest JS Engine 128.9.0esr, should be renamed to alpha or beta and testedThere 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.
more carefully by LUR with my Georgia-ReBORN x64 or your scripts and/or by other devs before releasing it as v4.x.