1
Other Lossy Codecs / Re: lossyWAV 1.4.2 Development (was 1.5.0)
Last post by C.R.Helmrich -Chris
# 1.62.25.05.13Finally can save into fpl playlists. Is it possible to load a fpl playlist as a handle list (skipping the UI)?
-Add `FbMetadbHandleList` `SaveAs`. Saves using native `.fpl`
format so you should use that as the file extension. The
parent folder must already exist.
-Add `fb.ShowPictureViewer(image_path)`. This uses the imageWill add that one to biography, which was the missing bit for art.
viewer built in to `foobar2000`.
Don't understand the question. He's done his homework!The sample Brand linked is interesting, though the claim that higher the bitrate the worse it sounds isn't entirely correct.
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.
Do you have a source for this?
The sample Brand linked is interesting, though the claim that higher the bitrate the worse it sounds isn't entirely correct.
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.
SMPThank you. This is very helpful and by far the most clear and understandable post about this issue and the way things work under the fooBar hood.