View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0016672 | MMW 5 | Sync | public | 2020-05-28 22:59 | 2020-06-02 17:19 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0 | Fixed in Version | 5.0 | ||
| Summary | 0016672: MMA<->MM5 track pairing process on the first sync can fail with specific MM5 search settings | ||||
| Description | Tested an S7 syncing to MM5 build 2253 (that had previously successfully synced with MMW4 and MM5--not sure which was last synced). 1 In MMA, changed the sync server to sync with MM5 2 In MMA, modified the sync list (to contain a playlist and an autoplaylist) 3 Initiated sync --> 'Sync incomplete' each time (soon after 'Matching tracks'). Is there some user error that I'm overlooking? MMA debug log: 81CWAUTDQ6 | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | 2254 | ||||
|
|
There is a problem in the pairing process (on MM5 side), it uses strange and unexpected SQL (according to MM5 log), assigning to myself to look into it. EDIT: It seems related to Rusty's configuration somehow. In my case it uses correct SQL using SQlite's FTS4, to find more... BTW: the pairing process is there only if you change MM instance/db to sync with MMA. Typically changing sync server in MMA from MM4 to MM5 or vice versa. Then all tracks are re-paired based on metadata, and this is the part of process that works strangely in the Rusty's case (based on log) |
|
|
oh, I've got it finally, the key to replicate is to go to MM5 > Options > Search > Search mode: [Ignore diacritics / search work prefix (fastest)] and change it to [respect diacritics / search word infix] With this non-default settings the MMA<>MM5 pairing process fails and takes too long (so MMA resulted in the "Sync Incomplete" because of a timeout). i.e. this is long-standing issue, but hard to notice as it appears only with non-default configs and only when pairing process is needed at all (when sync server is changed in MMA) |
|
|
Fixed in 2254 |
|
|
Note: I can confirm that upon retesting build 2253 with my S7 and with diacritics ignored, sync works correctly again (side note: the issue described in 0016673 did not occur). |
|
|
Verified 2254. Closing. |
