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.
Last post by Azuriye -
Hello @marc2k3 I've backed up my system and restored foobar2k with all my plugins to my new install, it was all good till I updated from 3.4.17 to 3.5.1... This piece of code seems to be broken which I'm not sure why?
Also I wanted to let you know that while I downgraded to an older version to check, I've lost all my tags set by JScript3... Luckily I have a backup of my old foobar2k but it would be better if you could put a huge red box to prevent users from downgrading... it looks like when I downgraded in Playback Statistics page you mentioned about how changing the title formatting will just erase the entire database, looks like downgrading did exactly that which caused this issue... Any idea what could be the reason behind this as well?
This would seem to me to be a bug specific to the Plex player (omitting the first line of lyrics saved with BOM) that should be addressed by the Plex developer, and not a cause for alarm for anyone who "accidentally" saved their embedded lyrics fom ESLyric that way. I let ESLyric save into tag on a test leaving the BOM box checked (its default setting), and the lyrics were all there and perfectly readable starting with the first line of the panels in the AIMP and MusicBee players as well as the standards-picky Kid3 tagger.
Correct, it is a bug in Plex, but others may be using Plex and experience the same behavior. I don't see it as an issue with ESLyrics, just more of an FYI for those who saved as +BOM and are using Plex.
A quick note for anyone who accidentally saved their lyric files as UTF-8-BOM. In the lyric save settings page there is a check box for encoding saved files as "+BOM". Can't remember if it was set that way as default, but the lyrics I saved that way were not showing properly in my Plex media player. The first lyric line was being omitted
This would seem to me to be a bug specific to the Plex player (omitting the first line of lyrics saved with BOM) that should be addressed by the Plex developer, and not a cause for alarm for anyone who "accidentally" saved their embedded lyrics fom ESLyric that way. I let ESLyric save into tag on a test leaving the BOM box checked (its default setting), and the lyrics were all there and perfectly readable starting with the first line of the panels in the AIMP and MusicBee players as well as the standards-picky Kid3 tagger.
Could someone please explain what is wrong with new versions of ffmpeg? Should we use 6.1 or 7.0 or 7.0.1 or older versions? I heard that there were/are some personal issues but do those affect the product in any way?
It goes more into corporate network bubble with making personal networking between current devs and their business and various corporations. Its mostly now low-effort, by state sponsored maintenance work over auto-detected issues in source code - of questionable outcomes and benefit. Still extreme low effort is taken on fixing user reported regressions and bug fix/feature requests reports. And new features are limited or buggy in some usecases. There is some cool and nice stuff, like cleanups and refactoring but net results is still negative.
Last post by musicmusic -
Thanks. As you stated, the configuration in the file still seems to be intact. That somewhat implies the problem is happening when reading the settings, rather than when writing them.
Could you provide a little bit more information about your hardware (e.g. what CPU do you have)? Could you also check if it still happens with a new portable installation of foobar2000 (with Columns UI and Album list panel as the only additional components)? (You can copy your foo_uie_albumlist.dll.cfg over to it when foobar2000 is closed.)
Thank you very much for making a 64-bit version of this. Installed and used it extensively this past weekend, and it performed extremely well with one exception: if a folder contained files of mixed type (FLAC + MP3, for example), it crashed foobar2000. Though probably not very common with single albums, I have multiple folders of mixed files downloaded from various online sellers that would love it if this could be corrected. Appreciate the consideration.
). Please give it another try.