Keep processing the same download folder with KNAS Music Organizer
2026-08-13
Music libraries rarely stop changing after one organization pass. You may keep downloading music on a PC and synchronize the same download folder to your NAS. The old files remain in place, while only the latest batch needs processing.
KNAS Music Organizer supports active incremental scans. After a task is complete, choose Scan for New Files from its menu. The app reuses the original source folder, target folder, and organization structure, then creates a new task containing only new paths or files whose output is missing.
What an incremental scan compares
After a file is processed successfully, the app records its source root, target root, archive layout, relative source path, and output path. On the next scan with the same source, target, and layout, a file counts as already processed when both conditions are true:
- Its relative source path has a successful record.
- The recorded output file still exists.
New source paths enter the next task. If a previous output was removed, its source is included so the output can be rebuilt. While an existing output remains present, the app keeps it authoritative even if the source size or modification time changes, so it is never overwritten automatically.
Why the app does not watch folders continuously
NAS folders may be updated by PC synchronization, network shares, batch copies, or third-party download tools. Continuous file watching adds background overhead and must account for outages, offline synchronization, moves, and deletions.
An active scan fits this workflow better. Trigger it after a synchronization batch, and the app compares the current directory with successful history. It does not need a permanent watcher and cannot miss a change merely because an event was not delivered.
Moves and task deletion
The relative path is part of the incremental record. A moved or renamed source file is treated as a new path. A source file that has been deleted is simply absent from the scan; the app never deletes the corresponding target music automatically.
Incremental history is stored independently from the task list. Deleting a completed task removes its task results and error log, but it does not make all successfully processed files reappear on the next scan.
How this differs from retrying failures
Retry Failed Files only retries failed items from the original task. Use it after fixing a permission or source-file problem. Scan for New Files reads the current source directory again and is intended for the next synchronized batch.
You can use both: retry old failures first, then scan for new files, or scan the current folder directly to create a task for new paths and missing-output items.
Existing output is still never overwritten
Incremental processing does not weaken the existing safety boundary. Before writing, KNAS Music Organizer checks the destination again. If an output already exists, the conflict is skipped instead of overwritten. New output continues to use a temporary file and atomic promotion.
Recommended workflow
- Synchronize newly downloaded music from your PC into the existing NAS source folder.
- Open KNAS Music Organizer and choose Scan for New Files on the relevant completed task.
- Review the To Process and Already Processed counts, folders, and structure.
- Create and start the new task.
- If anything fails, fix the permission or source issue and use Retry Failed Files.
This keeps a separate task record for each batch while avoiding repeated decryption and organization of old files, making it practical to maintain a NAS music library that grows over time.