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.
As long as there are separate tracks the work can be spread across multiple threads. You can look at task manager and you should see possibly even 100% CPU usage for foobar2000, as long as you aren't bottlenecked by storage.
Can confirm. Ran some more tests (always on NVME Gen4 storage).
Interesting to see that SACD is by far the heaviest to scan (not only for truepeak scanner but also foobar RG). Must be the underlying process of the underlying SACD component I guess.
Roughly speaking SACD scan runs at 49x, DTSMA at 430x, DVDA at 500x and normal FLAC8 at 1500x. Time that the scanner needs for additional LRA, DR and clipping pos is neglectible (up to 10% extra time).
(especially those with a completely empty upper half of the spectrum)
Oh, and that maybe makes it even more interesting - those signals appear to be the ones where -e matters, i.e. the model choice algorithm is less reliable. If such ones can be "identified" (not surely, but with enough statistical association), then we might be in for some fun ... uh, assuming that developer and testers have infinite amount of spare time of course.
TT, I notice you're using Biography 1.4.2, which has the fixed AllMusic. But as noted in the Biography thread, 1.4.2 can sometimes crash fb2k on exit. Was there ever a fix for this?
I think you are talking about regor's fix here: https://github.com/Wil-B/Biography/pull/7/files The fix is already included in Georgia-ReBORN when I updated the Biography scripts to v1.4.2.
Other foobar users who are using the original Biography v1.4.2 and not Georgia-ReBORN should also clear the interval in their scripts/allmusic.js -> send function.
-TT
Just an FYI... Biography's Allmusic is still crashing fb2k on exit. If you click on an artist that you've never loaded before, and exit while it's loading, it can crash. I'd say it does this 20 to 30% of the time.
It's doing it with your theme and my Darkone tweak theme. I even used your allmusic file on my Darkone tweak theme (yes, I removed all the modded 'bio' references) and it does the same thing.
The crash on exit goes away when Allmusic is disabled.
Supposing it's related to the fetch function and a crash due to wrong activex handling, adding a signal at the on_unload callback to stop fetching could solve the issue.
TT, I notice you're using Biography 1.4.2, which has the fixed AllMusic. But as noted in the Biography thread, 1.4.2 can sometimes crash fb2k on exit. Was there ever a fix for this?
I think you are talking about regor's fix here: https://github.com/Wil-B/Biography/pull/7/files The fix is already included in Georgia-ReBORN when I updated the Biography scripts to v1.4.2.
Other foobar users who are using the original Biography v1.4.2 and not Georgia-ReBORN should also clear the interval in their scripts/allmusic.js -> send function.
-TT
Just an FYI... Biography's Allmusic is still crashing fb2k on exit. If you click on an artist and exit while it's loading (1 to 2 seconds after loading is best), it can crash. I'd say it does this 20 to 30% of the time. Of course, be sure you don't have the artist/album files already downloaded.
It's doing it with your theme and my Darkone tweak theme. I even used your allmusic file on my Darkone tweak theme (yes, I removed all the modded 'bio' references) and it does the same thing.
The crash on exit goes away when Allmusic is disabled.
Last post by Squeller -
Really great initiative of you. Still happy. CASE, on top of your web page, can you also link Peters official component page? I felt the itch, others may feel the same, to look and compare, thx.
Last post by Squeller -
I'd recommend you to find Gurus listening tests and go for a robust, very compatible (maybe you want to use your converted files elsewhere) and space saving format: Apple LC AAC. Become more opportunistic and don't waste too much energy into theoretical problems. Example: In one car, I can only use 16 GB sticks, so I encode to Q64 or Q73 (say, q64, depending on the audio, ranges from ~130 down to 80 kbps, pads, lowpassed, piano music, in general few transients seem to qualify for low bitrates). Totally perfect. In another car, I use LAME mp3 @V2 - just because that one does not display embedded album art from the AAC files. Good headphone, I personally would probably go for Apple AAC @ q82 or q91 And don't hunt for problems, it's the beginning of the end. It distracts. Enjoy the music. Don't forget, your cat walking by has a bigger impact on your audible experience than the almost academic problems we tend to find.
I'm saying that, because in the past I perfectly heard if magnetic tape heads were not correctly adjusted. Hence I couldn't 100% enjoy the music, everyone else could.
Learn to make things right but then free yourself from over-critical listening ("i feel like i'm able to hear small differences in background drums"). It makes few sense. In a concert, there is huge differences at every moment because of the audience.
Last post by ktf -
Thanks. It turns out that some changes I made when working out the 32-bit encoder/decoder did affect the 24-bit part more than I thought. I was under the impression the code paths meant for 32-bit audio were only seldomly used for 24-bit audio, but it turns out certain kinds of 24-bit audio (especially those with a completely empty upper half of the spectrum) do use these code paths a lot, and they are much slower.
So, these changes make the choice between these code paths more strict: that choice was rather made rather roughly (on the safe side of course), but now the encoder goes through a little bit more math to only choose the slow code path when absolutely necessary.
The speed-up is highly dependent on source material. Audio with a high samplerate in which the upper frequencies are fully 'utilised' do not see any change at all, most audio I've tested sees quite some improvement at preset 8, and those where really no audio exists above 20kHz see most improvement at preset 5, but are still slow at preset 8.
-extraportable is the lowest LossyFLAC preset. Quality seems really high but I don't think it's supposed to be fully transparent.
lossyWAV Beta 1.4.3c includes, for testing at this time, four more quality options below extraportable (-q -5): "unadvised" (-q -10), "dubious" (-q -8.75), "questionable" (-q -7.5) and "aggressive" (-q -6.25). These will yield lower resultant lossyFLAC bitrates, with the consequent increased risk of noticeable added noise as the quality numeral reduces.