View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0022577 | MMW 5 | DB / Backup | public | 2026-11-08 23:53 | 2026-11-10 17:31 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Target Version | 2027.0 | Fixed in Version | 2027.0 | ||
| Summary | 0022577: Monitoring: Can interrupt Migration of Library | ||||
| Description | On startup/Continuous folder monitoring interrupts Media Migration and should be prevented By asking user for confirmation. Solution for Steps below would be, that in Case there is no Available MM library Media with Drive letter F:\ accessible File Monitor is not executed and throw Toast MSG "Monitored Media F:\ is Missing [Check Locations]" which if Clicked would focus on expanded Entire Library -> Locations, that will clearly show OLD USB do not have drive letter. After that User needs to Edit Media Properties and assign new Drive letter for the drive. | ||||
| Steps To Reproduce | 1. Insert USB Drive 2. Scan that USB (F:\)into MM library 3. Assign Monitor On startup/Continuous on USB drive Letter (F:\) 4. Close MM 5. COPY Tracks and File Structure to New USB Drive and Disconnect Old one 6. Assign Same Drive Letter to new Drive (F:\) 7. Start MM 8. MM will start to fill MM library with New Drive and you could not use Scan moved or change Drive letter in Media properties of old drive. Which result on corrupted MM library | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 3531 | ||||
|
|
I suggest this behavior: 1. Associate monitored folders with the expected library media. Store its IDMedia alongside the folder path and compare the connected volume against that media record. Referencing the record lets an intentional migration through Media Properties update the expected identity. 2. Validate before automatic scanning makes library changes. If the expected drive is absent or a different drive occupies its letter, pause both startup scanning and continuous monitoring for the affected location. Other locations continue normally. Recheck after drive reconnection and before processing queued work, so swapping drives while MM is running is covered too. 3. Show a persistent, actionable notification. For the reported scenario, I’d use: A different drive is connected at F:. Monitoring is paused to protect your existing library. [Check locations] “Monitored media is missing” is appropriate when nothing is connected, but is less clear when a replacement drive is present. 4. Make “Check locations” select the original media under expanded Entire Library → Locations, including when that media is offline. The user can then use Media Properties or Locate moved/missing files. Dismissing the notification must leave monitoring paused, including after restarting MM. 5. Allow intentional replacement as a separate choice. “Monitor this drive as a new location” should require confirmation explaining that its files will be added separately from the old library entries. Completing migration should instead revalidate the original media association and resume monitoring. The existing Media Properties flow currently requires a restart for this identity change. Two implementation details matter: - Blocking only the startup scan is insufficient: continuous events, queued scans, and automatic missing-file removal also need the safeguard. - Existing monitoring settings have no saved media association. Bind them from existing library information only when unambiguous; blindly adopting whatever drive is connected on first startup would reproduce this bug. |
|
|
Implemented in 3531: - Monitoring pauses when a drive is missing or its identity changes, including across restarts. - Check locations opens the original library media. - Queued events and scans respect the pause. |
