wiki: bringing in a file that was not recorded here A page for the Upload tab, and the four places that had to learn about it: the sidebar, the step table on the home page, the interface tour's description of the mode tabs, and troubleshooting. It says the things somebody finds out too late otherwise - that a lossy source stays lossy, that resuming means picking the same file again because a browser cannot re-read one across a reload, and that a gapless album gives the fit nothing to snap to. It also says when not to use it at all: a purchased download is usually already one file per track, and those should go straight to beets. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EccMM65NcsTYoCm84gnJDU
wiki: the port example is the default, not a deployment's The example changed the port to a specific one for no reason the page gave. The thing that has to change to reach it from another machine is the address; the port is whatever is free, and the default is the clearer example. Also states the configuration path without claiming it is Linux-only - it follows XDG_CONFIG_HOME everywhere. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Gp3TbiAQ4h1VKSEMtA9qzq
wiki: the manual Eighteen pages covering how to use RipDoctor: installing it, configuring the pool and the capture device, setting beets up, and then each step of a record - rip, first pass, checking boundaries by ear, cutting, importing, cover art, archiving - plus re-ripping a side, punching a track, the command line, what is on disk, and troubleshooting. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Gp3TbiAQ4h1VKSEMtA9qzq
Initial Home page