View Issue Details

IDProjectCategoryView StatusLast Update
0012688MMW v4Synchronizationpublic2015-04-01 21:13
Reporterpeke Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status assignedResolutionopen 
Product Version4.1.6 
Target Version4.1.7 
Summary0012688: iPod Classic: Sync Structure and issues
DescriptionLooks like there is an isue (conflict with ipod Devices that are seen on PC as Drive letters) like iPod Classic 5.5

There is few conflicts with Device profile and actual representation of device in MMW. Even device is assigned drive letter it acts like an regular iOS device and should be handled as such.

1. Copy/Paste error -> user can copy/paste tracks to device even they are not in supported format
2. Sync Error -> Send to should comply with Sync settings in profile like (conversion and namings) which as result end in Grayed/Non-Playable tracks
3. Duplicates -> there is high risk of duplicates as auto-sync can be easily overridden by using Send to
TagsNo tags attached.
Fixed in build

Relationships

related to 0012691 feedbackrusty Send to (Synchronize) is confusing 

Activities

peke

2015-04-01 00:05

developer   ~0042392

Based on number of tests cunducted iver remote session I would sugegst that if iPod Classic ID is detected MMW should ignore Drive letter and use Air Sync to access/sync with device

Ludek

2015-04-01 09:57

developer   ~0042393

Last edited: 2015-04-01 09:58

Peke, iPod Classic isn't running iOS at all, so Air Sync cannot be used. MM writes the metadata into iTunesCDB file that is subsequently read by the iPod firmware.

1. As for the confusion about the copy/paste. The same issue happens with any file browser. i.e. Simply copying MP3 file using Total Commander or Windows Explorer also results in non detected file by iPod. It has always worked like this.

2&3: I believe that Send to -> iPod works right, i.e. it takes auto-conversion settings from the device profile and copies the files in the iPod special path format like:
/iTunes_Control/Music/F19/RNMO.mp3
There shouldn't be any duplicates.

peke

2015-04-01 11:38

developer   ~0042395

I know all what you wrote but in past month I had 3 Users on remote session that FLAC files ended in /iTunes_Control/Music/ using Copy/Paste and Send To in MMW log file show normal Copy of files to /iTunes_Control/Music/ where user would expect that it is converted and copied to /iTunes_Control/Music/F19/RNMO.mp3

I was marely reffering to AirSync as looks like Apple users expect that all Devices (they often have both Classic and iPhone) act same and sync in same manner.

They find current behavior very annoying and like in 0012691 I would go with more unified sync process no matter of device even possibly that some features would not be used on devices that support them.

Maybe we should lower priority and discust for MM5?

peke

2015-04-01 21:13

developer   ~0042397

As talked on IM this is left for Ludek to obtain Device for testing and hammer down what should we do in order to evade future confusions along with 0012691 changes