Last post by IgorC -
More likely it's Intensity Stereo (IS). IS is beneficial for bitrates less than 130 kbps. IS is applied on frequency range of 12-20 kHz (at 96 kbps), 15.6-20kHz(128 kbps) and it's completely deactivated at 130+ kbps.
Last post by TuNk77 -
As the title says, I would like some help with "cursor follows playback" since it is misbehaving. By misbehaving I mean that "cursor follows playback" does not land the highlighted track in the middle of the playlist, as I expect it to, the highlighted track is either on the top of the playlist or on the bottom.
Sometimes it helps to restart foobar2000, but it can take several restarts to make it behave normally.
This issue is present in foobar2000 v1.3.17 and v1.4 beta 15.
I did a clean portable install and the issue still persist.
The only component I installed is foo_playcount v3.0.2. Then I made a new theme in the scratchbox and applied it.
Last post by maikmerten -
Note that Opus splits audio into frequency bands and distributes bits along those. I imagine those bands to be "buckets" that bits can be allocated to.
The complete range from 15600 to 20000 Hz is coded in one "bucket" - band 20 to be more precise (c.f. table 55 in https://tools.ietf.org/html/rfc6716). Apparently the psychoacoustic model in Opus determined that while some energy is needed in this band, the detailed structure wasn't of high importance compared to the other bands. Thus the band was filled somewhat uniformly, which is why things from 15600 to 20000 Hz look somewhat flat.
Last post by drisc32 -
OK, i just installed "Free Encoder Pack 2018-05-22" . Now my foobar directory has the "encoders" folder plus the old LAME folder i had created years ago. Will foobar automatically go for the LAME in the encoders folder?
The behaviour is simply due to Opus "making stuff up" above 15.6 kHz at that bitrate. This saves many bits that can be used to make the encoded file sound better and it's hard to hear the difference because the ear isn't very sensitive at that frequency. The encoder *could* code that band better, but it would require many bits (taken from lower frequencies) and the result would likely be worse.
Thank you. I wasn't trying to "listen with my eyes" as I mentioned that my hearing above 16 kHz sucks and I can't ABX the 96 kbps Opus file. This was just to try and understand how the codec is working, and to see if I could investigate why some golden ears can ABX Opus up to 160 kbps. Seeing that roll off at 15.5 kHz got me to wondering because it looks like the energy "saved" by that roll off is more than offset by the extra energy between about 17 kHz and 19.5 kHz, where the Opus file has more energy than the source. My rudimentary knowledge had me thinking that if that extra energy could be used to keep the energy between 15.5 kHz and 17 kHz similar to the source material, it might make it more difficult for golden ears to ABX Opus at this bitrate and above. However, that's assuming the relative energy of various frequency bands is what they're hearing. It could be other effects.