How fiso64/slsk-batchdl works
Main Components Identification
a) Core Components:
• Input Processing System (Extractors)
• Search Engine
• Download Manager
• File Management System
• Configuration Manager
b) External Services:
• Soulseek Network
• Spotify API
• YouTube API
• Bandcamp Integration
• yt-dlp (optional component)
┌─ Input Layer ─────────────────────────┐
• CSV Files - Spotify │
• YouTube - Bandcamp │
• Text Files - Direct Search │
• ┬───────────────────┘
• ↓
┌─ Processing Layer ────────────────────┐
• ┌─ Extractors ──┐ ┌─ Search ───────┐│
• Spotify │ │ - Query Builder││
• YouTube │→ │ - Rate Limiter ││
• Bandcamp │ │ - Result Filter││
• CSV │ └───────────────┘ │
• ┘ ↓ │
• ┌─ Download Manager ─────────────────┐│
• Concurrent Downloads ││
• Progress Tracking ││
• File Validation ││
• ┘│
• ┬───────────────────┘
• ↓
┌─ Output Layer ──────────────────────┐
• File System Management │
• M3U Playlist Generation │
• Index File Management │
• ┘
Important Relationships
• Bidirectional connection between Search Engine and Soulseek Network
• One-way flow from Input Layer through Processing to Output
• Configuration Manager's influence on all components
• External API connections for Spotify, YouTube, and Bandcamp
Implementation Details
Technical aspects:
• C# implementation (.NET)
• File format handling (mp3, flac, etc.)
• Concurrent download management
• Configuration file locations
• Docker volume mappings
Operational Flows
Key processes:
• Search and download workflow
• Album download process
• Aggregate mode operation
• File validation and conditions checking
This design captures both the high-level architecture and the important implementation details while remaining clear and maintainable. It reflects the project's focus on flexibility in input sources and robust download management while adhering to Soulseek's constraints.