1
3rd Party Plugins - (fb2k) / Re: foo_openlyrics (not my release)
Last post by matafana -Using openlyrics 1.12
Foobar v2.24.4 [x86] on windows 7
Is there a way to make it work?
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.
Using openlyrics 1.12
Foobar v2.24.4 [x86] on windows 7
Is there a way to make it work?
2
3rd Party Plugins - (fb2k) / Re: Columns UI
Last post by musicmusic -Are these issues rooted in Columns UI, or do they relate to the individual plugin code?The latter.
Preferences pages from third-party components can indicate to the foobar2000 core whether they support dark mode. If they don't, the core switches the entire dialogue to light mode while that page is open.
In the case of Ganbatte!, apparently its preferences page is indicating that it supports dark mode, without actually supporting it (or having some bug in its implementation).
3
Other Lossy Codecs / Re: SBR usage of xHE-AAC at 72kbps, 80kbps, and 96kbps
Last post by celona -Do not consider my messages from three or more years ago, I am an early adopter, for example about Opus I wrote the worst infamies (I say this jokingly), at the beginning I did not like it, little by little it improved and perhaps I understood better where the project was going and today it is one of my favorites for speech. Time forces us to update our opinions.
Also on Exhale I made tables to show the inconsistencies in the use of the bitrate for each combination of bit, kHz, mono or stereo, etc. and today it is much more linear and predictable, but I do not use it for speech (I bought a paid encoder), nor for music.
Maybe for the use you want to make of it the Fraunhofer xHE-AAC encoder does not make much sense, to hear the music well you have to go up to bitrates very similar to those of AAC-LC and therefore you will not find great advantages.
I do not think that stubbornness to stay within a certain bitrate will repay you in the future for the effort and time you are spending. Use AAC-LC and don't care, you will not have SBR in your compressed files, the important thing is to be satisfied with the content. You will not throw away the uncompressed files anyway.
Now you know why I am not very present here, I love our paranoia, but in the end they lead to almost nothing.
4
foobar2000 mobile / Re: Certain mp3-files break playback
Last post by Case -5
General Audio / Re: Can higher bitrates sometimes sound worse than lower ones
Last post by Case -At certain bitrates Opus refrains from trying to encode the noise between ~12 kHz and ~15 kHz, but once bitrate increases above those thresholds it stupidly encodes parts of that frequency range. For example 128 kbps is worse than 150 kbps, and while 256 kbps sounds worse than 150 kbps, 320 kbps is once again better than 150 kbps.
It's not doing a worse job because bitrate increases, it just doesn't seem to understand what it's encoding and sprinkles the extra bits randomly leading to awful artifacting.
6
foobar2000 mobile / Re: Certain mp3-files break playback
Last post by AlexForFoo -First I was listening to some podcasts and then one of my mix music folders with mp3 files from different sources. I made a phone call and went back to foobar2k resuming music playback. When one of my "breaking" files was reached in that folder, playback was "stuttering" all of a sudden. The sound was similar to the one in this video (sec 4-6 in https://www.youtube.com/watch?v=2gC3nh3AvV0&t=4s) and was slowed down, also. Skipping to the next song brought no help, stuttering was still there. Closing the app "repaired" playback for other files, only the initial "breaking" file was still affected. Then I stopped playback and went home.
Two hours later at home, I reopened the app to record the stuttering sound. But all seemed fine again, even the "breaking" file was played clear. I.e., I cannot reproduce the error at the moment. I'll continue testing and let you know, if there's something to report.
Regards, Alex.
7
Development - (fb2k) / Re: New filesystem redirector service for relative paths in portable install
Last post by Montchenot -The Folder Name and File Path in the Details tab in Properties for the same track show:
* Absolute path for the instance that was already there at startup time (folder opening worked), and
* Relative path for the added instance to the same playlist (failed to open).
8
3rd Party Plugins - (fb2k) / Re: foo_midi (foobar2000 v2.0)
Last post by deus-ex -Screenshot 1 Screenshot 2
9
3rd Party Plugins - (fb2k) / Re: Columns UI
Last post by deus-ex -With Columns UI's dark mode activated, I identified two plugins, Ganbatte! and Hively Tracker decoder, where the dark mode theme isn't properly applied to their config dialogs.
Upon selecting the Hively Tracker decoder in foobar2000's decoding dialog, the dark mode even is disabled for the entire UI, and when selecting any other entry, the UI dark mode is restored.
Screen capture: https://imgur.com/a/E0pqCUb
Are these issues rooted in Columns UI, or do they relate to the individual plugin code?
10
General Audio / Re: The "business model" of hybrid codecs with correction files
Last post by Porcus -AAC [...] also decodes faster, for what it's worth.
I did a test on older Android phones: https://hydrogenaudio.org/index.php/topic,124857.0.html I did not test LossyFLAC nor WavPack Lossy though.
But apparently, doing FLAC by the OS' native decoding was lighter on battery. Suggesting that for battery life, one would choose a codec that is natively supported, AND a player application that would use that.
Also, avoid VLC.
No idea what happens on an iPhone, but if battery life is a concern then maybe one could test a couple of contenders.