← Back to context

Comment by sandreas

1 day ago

Maybe for archival Purposes you could use `redumper` (https://github.com/superg/redumper) to prevent ripping mistakes.

My personal workflow:

  - rip the audio CD via EAC with acousticID (flac)
  - retrieve metadata via beets in a script completely automated
  - convert flac to mp3 via beets inplace convert (see below)
  - backup the flac files to another location
  - self-host navidrome and use the substreamer / dsub app and smart playlists to listen "on the go" (The Apple usb-c-to-audiojack adapter is pretty decent)
  - transfer this via iTunes VM to my good old iPod Nano 7g as main listening device for audiobooks

If anyone is looking for fast and accurate ripping hardware, recently I updated my recommended hardware list including a linked tutorial for EAC:

https://pilabor.com/blog/2022/10/audio-cd-ripping-hardware/

beets convert config:

  convert:
    auto: no
    ffmpeg: /usr/bin/ffmpeg
    opts: -codec:a libmp3lame -qscale:a 0 -ac 2 -ar 48000 -map_metadata 0 -movflags use_metadata_tags
    max_bitrate: 192
    threads: 1

~Why use MP3 instead of opus, vorbis or AAC ? All of them have (most of the time) better compression ratio (and better quality) than MP3. Is it for compatibility reason ?~

edit: Ah, I missed the ipod nano part

  • Just compatibility and "high enough" quality. Works in my car, on my iPod, on my Phone, on my kitchen radio and is the most common format in general.

  • iPod Nano 7th gen. does support AAC (AIFF & WAV too).

    • All iPods except for the very first and second one have supported AAC out of the box, and I believe there was a firmware update even for the two that didn't. Apple didn't invent the format, but was definitely its biggest proponent from early on.

      1 reply →