Last post by Case -
It's a problem with the fixes. They were not supposed to slow the resampler down. Accuracy isn't affected.
True Peak scanning is not a requirement. Knowing the intersample peaks only allow protecting against clipping that could happen after resampling or in DAC. If you use ReplayGain without using extra loudness boosts you most likely won't run into clipping anyway.
I think that pattern broke because eight is good and 10 sucks. You only need to replace the start menu and it's much like 7, only more efficient. Meanwhile 10 brings perpetual performance issues, severe bugs, pointlessly removed features
Last post by Case -
That was enough details to find a problem. True peak scanning with PPHS resampler has gotten dramatically slower. Assumedly from the "PPHS resampler bug fixes (inaccurate reported latency, crashing with extreme sample rates)." changes.
I checked the accuraterip tag box on verify and had CDTOC on true, but cuetools isn't writing the tags when I go to verify the album. I tested both 2.1.7 and 2.1.6. I have no clue if i encountered a bug or not.
Hm. Did you look at the preset in the upper-left corner? Did you ask it to skip recently verified, or verify only if found?
I cannot test right now, but I could possibly have populated the ACCURATERIPID tag myself, rather than having CUETools do it. (I just looked up Crimson in my library ...) Since I rip with dBpoweramp, which writes the ID to a different tag, I could have extracted it to CUETools' tag once upon a time. See last paragraph for details about those tags.
If you want the ID for manual tagging - and then subsequent CUETools treatment - you can try https://www.dbpoweramp.com/perfecttunes.htm . Move all your single-track CDs over to a separate parent directory, let it AccurateRip scan that parent folder. It finds some albums that CUETools cannot. Generally speaking, not so relevant for single-track albums: you can tag an entire album manually, you do not need to tag each track - see next paragraph. Now if it is already AR verified, you do not need to run it through CUETools - but if it needs repair, then you want CUETools to find it.
Longer story, and I think CUETools reads more tags now: dBpoweramp writes an "ACCURATERIPDISCID" tag, which is really a disc+track ID: 001-0002bf63-00057ec7-02096001-1 where the leading triplet is the total number of audio tracks (why a third figure is needed, beats me) - and the final "-1" is the number of the actual track, as AccurateRip is basically track-based and not disc-based. CUETools is disc-based, and its tag of choice is ACCURATERIPID, which is formed out of characters 5 through 30, same tag for all tracks in an album.
Blah blah blah unstructured ... ask if I was too unclear about something that you actually care about.
Last post by magicgoose -
1) yes the distortion from simple rounding will be impossible to hear in the vast majority of real life cases and with normal listening volume. and there are also no downsides from enabling the dithering except that this will increase the file size a little (after lossless compression with codecs like FLAC) but this is also going to be extremely little
2) if the original recording doesn't have "true peaks" above 0 dBFS, then no; a proper resampler will not produce peaks higher than that no matter what sample rate you use. but if it has such peaks, then it depends. but from my math intuition, if you're downsampling and using an integer fraction (here you're going to subsample by exactly 1/2), that's relatively unlikely. besides clipping, there are no other possible negative effects if you use a good resampler (such as SoX).
some explanation: 1/2 downsampling can be equivalent to these 2 actions: 1) remove all frequencies above 1/4 of the current sample rate with a linear phase filter (this is extremely unlikely to create higher peaks, but afaik this is possible with things like square waves) 2) skip every odd (or every even) sample (this will obviously not create any higher peaks)