Especially since I didn't know that AAC requires ~200MHz just to decode, this data puts things into perspective. Thank you for sharing this!Strange again. Here are what I got with this two-disc album encoded into a single file.
System:
CPU: 12th Gen Intel(R) Core(TM) i3-12100, features: MMX SSE SSE2 SSE3 SSE4.1 SSE4.2
App: foobar2000 v1.6.16
Settings:
High priority: no
Buffer entire file into memory: yes
Warm-up: no
Passes: 1
Threads: 1
Postprocessing: none
Opening time: 0:00.000
Decoding time: 0:11.177
539.596x realtime
Opening time: 0:00.001
Decoding time: 0:02.763
2181.658x realtime
Opening time: 0:00.000
Decoding time: 0:12.665
476.231x realtime
Opening time: 0:00.000
Decoding time: 0:04.554
1324.298x realtime
4. Option to save sets of profiles for the Pregap/Data Track/Offset. This way you do not have to change settings each time there is not a match.The matching to other rips is automated, in that it's identifying rips with different offsets and data tracks that do/could match yours (it could be multiple of course), what's the point in plugging those values back in and running it again, the purpose is to verify your rip.QuoteNot sure what values you'd save here, but have you turned on detailed logging under 'Settings > Advanced > Detailed log: True' as it may give you the information you're looking for e.g. if your rip wasn't accurate, it'll tell you if it matched another rip with different pregap/data tracks (against CTDB).
This option also works well as it gives me the offset and pre-gap length I can use to match with other rips. I was just wondering if this could be automated in some way, i.e. if initial values did not match, then other values found could be populated automatically and attempted again.
Externally powered hubs are nice since you can pick the power supply. Usually doesn't matter, but for really sensitive instrumentation I've used low-noise linear power supplies with hubs before.
thank you sir! On that note, ive seen this on a pro audio forum :
The mic preamps are most-sensitive to noise since they are high gain and they amplify noise along with the signal.
"Because of the severe power constraints of USB bus powering, the headphone outputs, and often the phantom mic power (mic current capability) are limited to power levels that are far less than ideal"is there any truth to the notion that mic preamps,phantom power , headphone outputs etc will perform worse on bus power?
It's not a bad idea, but a lot of us have written our own things in the past and migrating it is almost never worth the hassle when we know how the code works and it's been well tested for years. That's why this kind of generic stuff is unlikely to catch on (unlike components, etc.)As long as people currently coding get involved, it should be pretty easy to migrate. 'The well tested for years', well SMP has been getting more and more updates and helpers from some years are deprecated, have problems in Wine, don't work on specific OS versions as expected, etc.