Last post by Apesbrain -
If transition between source tracks is gapless, you can get audible clicks between tracks after resampling.Interesting. I've never noticed this issue using the "Resampler (Sox)" component in foobar2000. Typically, I'm converting FLAC 24/96 or 24/192 to 16/44.
-L (linear phase response) is used by default.
-v (very high quality) seems like overkill for 16 bit, -h (also a default) should be enough:
Also, regarding dither, by default it uses TPDF noise, it needs -s option to use noise shaping. I can't say which is better or if I would notice the difference between the two (or even if I would notice a lack of dither :-)), certainly not with vinyl rips.
I thought that getting loud enough was not the way these things are analyzed.
It might be loud enough, but if the amp of a unit is being driven to its max, then perhaps some distortion is creeping in.
The main things to look at are:
- do your headphones get loud enough?
- is there an audible noise floor? (this can be a problem with sensitive in-ear headphones)
- is there a high output impedance? (which can mess up the headphone frequency response)
The AK70 specs say it has a 2 ohm output impedance. That should be fine with 16 ohm (and up) headphones.
Aside from that, if the max volume and noise floor are satisfactory for you, I don't think there will be anything to improve on.
(P.S. - And should I be using a portable amp with the HD600?)The only reason to is if they don't get loud enough. I use mine out of a macbook pro and it's just loud enough for me (I put the volume at 100% volume very rarely, for quiet / classical music).
Last post by Shinsekai -
That's not possible with Default UI AFAIK, but it can be done using Columns UI (not 100% sure).
Btw, this thread belongs in the foobar2000 forum not HA's off-topic. There you will receive better advice.
@Viniman, why are you still using the old v0.9.1 foobar2000 ?
If you upgrade your foobar you'll be able to use Playback Statistic version 3 (was released on 2011-07-13). There's no lag time on version 3. Version 3 introduced new data pinning scheme : "Playback statistics are now pinned to a combination of artist + album + disc number + track number + track title information, contrary to pre-3.0 versions which would pin data to file paths".
I don't use SoX, but I agree. Your settings are fine (for both the digital and digitized vinyl).
all this so I can free up space and still have good quality for archival.WAV files? FLAC will cut your file size almost in half (losslessly) and tags (metadata) is better-supported.
It's very unlikely that you'll hear any very-slight and very-short duration clipping caused by re-sampling, but still, it's good practice to guard against clipping. Other processes, such as EQ or mixing are more-likely to boost the peaks/levels and that's where you have to be careful about clipping. The vinyl may not even be 0dB normalized so there may be some headroom in those files, and they probably aren't digitally-limited so if they are normalized there should be fewer 0dB peaks to begin with.
Dither is generally also good practice when downsampling. But, at 16-bits or better it's not audible under any normal/reasonable conditions so practically speaking, it shouldn't make any difference. And since dither is noise, it's not necessary with (already noisy) digitized vinyl. Theoretically, you wouldn't want to add any noise to vinyl. But, the dither is very low level compared to the existing vinyl noise so it won't do any harm.
Clipping from resampling is generally inaudible. If you use guard against clipping and convert tracks separately, it can change loudness difference between tracks in album.
If transition between source tracks is gapless, you can get audible clicks between tracks after resampling.
Example. 2 source files 96/24 with gapless transition - https://www.dropbox.com/s/hvwc9mx4h77afur/96-24%20gapless.zip?dl=0
Converted to 44/16 with sox (sox.exe" %%A -b 16 "%~dp0%%~nA--.wav" rate -v 44100 dither) - https://www.dropbox.com/s/l0l0ynkyb1ga1nh/44-16%20click.zip?dl=0
Between 44/16 files there is clearly audible click. Solution for this can be merge files before conversion, then split after conversion.
Last post by LigH -
So it might have been a mistake of e.g. accidently copying from an extracted QTFiles directory into an existing QTFiles64 ... OK, surely a helpful analysis.
P.S.: Apparently the used makeportable batch was too old (in 2014, it could only handle 32-bit installers; the 2015 update supports iTunes 64-bit correctly).
Last post by nu774 -
But another user reported in the German doom9/Gleitz board that he gets "ERROR: 193: CoreAudioToolbox.dll" when running "qaac64 --check" with the "makeportable" results of different more recent iTunes64 installers; only an older version from 2015 seems to work for him. Could you explain what this error is supposed to mean?193 is ERROR_BAD_EXE_FORMAT.
This error happens when qaac64.exe can find only 32bit CoreAudio DLLs.
If the user has correctly copied QTfiles64 and still see that error, then I don't know.