: Updates to fields such as "Location" (moved to bottom of edit screen), and changing "Collection Status" to a dropdown menu.
: Supports exporting collection data to CSV or XML files and offers cloud backup through the CLZ Cloud. Critical Availability Note Music Collector desktop software - Club CLZ
: Introduction of macOS Dark and Light mode compatibility.
Music Collector Pro 20.3.2 is a specific legacy version of the music cataloging software developed by (formerly Collectorz.com). While newer versions (such as v23.1) are available, v20.3.2 remains a functional release for users of the desktop application. Version 20.3.2 Overview
The software is designed for professional DJs and serious collectors to manage physical (CDs, vinyl) and digital music.
: Added support for syncing many new fields, including back cover images , with the CLZ Cloud .
Music Collector Pro 20.3.2 Info
: Updates to fields such as "Location" (moved to bottom of edit screen), and changing "Collection Status" to a dropdown menu.
: Supports exporting collection data to CSV or XML files and offers cloud backup through the CLZ Cloud. Critical Availability Note Music Collector desktop software - Club CLZ Music Collector Pro 20.3.2
: Introduction of macOS Dark and Light mode compatibility. : Updates to fields such as "Location" (moved
Music Collector Pro 20.3.2 is a specific legacy version of the music cataloging software developed by (formerly Collectorz.com). While newer versions (such as v23.1) are available, v20.3.2 remains a functional release for users of the desktop application. Version 20.3.2 Overview Music Collector Pro 20
The software is designed for professional DJs and serious collectors to manage physical (CDs, vinyl) and digital music.
: Added support for syncing many new fields, including back cover images , with the CLZ Cloud .
This could have to do with the pathing policy as well. The default SATP rule is likely going to be using MRU (most recently used) pathing policy for new devices, which only uses one of the available paths. Ideally they would be using Round Robin, which has an IOPs limit setting. That setting is 1000 by default I believe (would need to double check that), meaning that it sends 1000 IOPs down path 1, then 1000 IOPs down path 2, etc. That’s why the pathing policy could be at play.
To your question, having one path down is causing this logging to occur. Yes, it’s total possible if that path that went down is using MRU or RR with an IOPs limit of 1000, that when it goes down you’ll hit that 16 second HB timeout before nmp switches over to the next path.