NAD C700 v2 — SSD Indexing Failure (Progress Loop 1,5,10,50,100,200, COMPLETE → repeats) – Request for Improved Error Handling and Logging

Dear Bluesound Support team,

I am experiencing a persistent and reproducible indexing issue with my NAD C700 v2 when using an SSD containing about 40,000+ tracks. This problem did not occur previously — the same SSD was able to be fully indexed and all tracks were playable.

Issue Summary

• Device: NAD C700 v2 (via Bluesound ecosystem interface)

• Music Library Size: ~40,000 tracks (previously indexed successfully)

• Storage Medium: SSD (verified healthy, no hardware failure)

• Symptom: During library indexing, the progress indicator repeatedly cycles through:
  1, 5, 10, 50, 100, 200, COMPLETE → then starts over again (1, 5, 10...) in an endless loop.

• The SSD itself is intact and previously worked without issue.

Impact

• Indexing never completes, so newly added tracks are not properly registered.

• Some existing tracks may not be accessible or playable due to the incomplete indexing state.

Requested Improvements

1. Improve error handling during indexing: If certain files cause errors, the indexer should skip them and continue with the rest, instead of restarting or looping endlessly.

2. Identify problematic files in the UI: When errors occur, the system should display which file(s) or track(s) failed, or at least provide error codes.

3. Generate exportable log files: The system should log details (timestamp, file path, error type/message, handling outcome) and allow users to export or share them with support. For example:

    

   2025-09-07 09:12:03 | /Music/Artist/Album/01 - Long Filename Example.flac | ERROR | Filename contains invalid characters / path length > 255 2025-09-07 09:12:03 | /Music/Artist/Album/02 - TrackName.mp3 | SKIPPED | Unsupported metadata encoding

4. Provide documentation of common causes of indexing failure, such as:

   • Filenames with special/non-UTF-8 characters (e.g., emoji, rare symbols)

   • Excessive path/filename length (beyond filesystem or indexer limits)

   • Corrupted or non-standard metadata (ID3 / Vorbis comments / encoding errors)

   • Unsupported file extensions or containers

   • Extremely deep folder structures or very large quantities of small files stressing memory/buffer handling

Requested Support Actions

1. Please advise how I can obtain detailed indexing/system logs (or enable debug mode).

2. Confirm if this is a known firmware/indexing bug specific to NAD C700 v2, and if so, provide available patches or expected fix timelines.

3. If needed, I can provide: SSD model, filesystem type (exFAT/NTFS/ext4), firmware version (please let me know where to retrieve this), and sample problematic filenames/paths for investigation.

Expectation

• Please escalate this to the engineering team for investigation.

• Kindly provide any interim workarounds (e.g., filename/path sanitization, metadata re-tagging, or methods to isolate problematic files) and an estimated timeline for a permanent fix.

• If you require logs or sample file paths, please let me know the preferred method for submitting them (email attachment, upload portal, etc.).

This indexing loop issue severely affects usability, and I would greatly appreciate a prompt response with guidance on debugging steps or firmware fixes.

Thank you very much for your assistance.

Best regards,