View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007110 | MMW v4 | Synchronization | public | 2011-01-03 00:35 | 2011-03-02 23:21 |
| Reporter | Assigned To | ||||
| Priority | immediate | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | Windows | OS | 7 | OS Version | - |
| Product Version | 4.0 | ||||
| Target Version | 4.0 | Fixed in Version | 4.0 | ||
| Summary | 0007110: USBMass device plugin Scans Device on each startup | ||||
| Description | possibly intended, but different behavior than mm3 on startup MM indicates scanning of usbmass device. more details, I have a usbmass device profile setup to sync my library to an mp3 only mapped network drive M. Approx 200k files are synced via this profile (entire audio library). this is helpful for me to consolidate all mixed mp3/flac/m4a/etc files to a single mp3 only network share for other users and programs. on startup, mm scans (but not sync) the device which takes 2 or 3 or so minutes to complete. this profile was imported from mm3 settings, but I double checked for any options to background/startup scan on new profile page. auto-sync as soon as the device is connected is disabled | ||||
| Additional Information | attached exported device profile | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | 1351 | ||||
|
|
Not quite sure I understand what the bug is. Are you saying that the device shouldn't be scanned? |
|
|
I am saying: a) mm3 does not do this b) in my opinion, device should not be touched unless 1) auto sync on connect is enabled or 2) device sync (or any other device access) is initiated by user |
|
|
How can I prevent MM4 from rescanning my devices at startup? I do not want MM4 to reload/rescan every time I start MM. The only time I want MM4 to touch any device is when I tell it to sync. |
|
|
This really might be an issue for some users and/or some devices. As discussed over IM with Ludek, the best approach seems to be to add an option to the Summary sheet of Device configuration: [x] Scan as soon as the device is connected in case it's unchecked, device content would be read only when the node is focused or synchronization started. |
|
|
Fixed in build 1351. |
|
|
Verified in 1351 |
