View Issue Details

IDProjectCategoryView StatusLast Update
0008076MMW v4Synchronizationpublic2015-02-05 15:13
Reporterrusty Assigned To 
PriorityhighSeveritymajorReproducibilityhave not tried
Status assignedResolutionreopened 
Product Version4.0 
Target Version4.0.7Fixed in Version4.0 
Summary0008076: iOS device browsing: fails to show Audible (extended) tracks
DescriptionAccording to UI (the NL translator), MM4 breaks Audible tracks on an iPod Touch.

e.g.
1 installed the latest MM3 and started it -- it shows iPhone audiobooks in the Audible folder.
2 run MM4 and check the Audible folder
--> it's gone!
Tagstodoc-help
Attached Files
MM4_AUDIBLE.rar (457,188 bytes)
Fixed in build1406

Relationships

related to 0005981 closedLudek Tracks purchased directly to iPhone don't show up in MM interface 

Activities

jiri

2011-07-07 13:28

administrator   ~0026605

I don't have Audible files for testing, but it's hard for me to believe that it's really a regression, since I don't see any change that would significantly modify the way DB is written. I need to know:
1. Is it really a regression? I.e., if a track is synced (or the Touch otherwise modified) by MM 3 (the latest version), do Audible tracks really work?
2. If so, a test of some earlier 4.0 releases would be helper in order to reveal when such a problem appeared in MM 4.0.

rusty

2011-07-11 20:38

administrator   ~0026720

Last edited: 2011-07-11 21:14

Tested build 1404.

The regression is that when browsing an iPhone with MM3, the Audible Audiobooks synced by iTunes were displayed sub to the Artists node. In MM4, though, such audiobooks appear neither in the Artists node nor in the Audiobooks > Artists node.

Note: although the audiobooks don't appear when browsing the device with MM, syncing with MM has no effect on the tracks--i.e. they can still be browsed/played via the device.

Note: Audiobooks purchased via iTunes don't exhibit this problem.

iTunes_Control uploaded to the ftp server

Ludek

2011-07-12 10:18

developer   ~0026732

Fixed in build 1406.

rusty

2011-07-13 21:25

administrator   ~0026777

Last edited: 2011-07-14 02:24

On my machine/device, this issue has been resolved.

However, the bug's reporter is finding that there's still a problem:
Situation:
- When MM is loaded and an iPhone is connected, the Audible-folder on the iPhone is droped in the chain it's in.
Normally: audiobooks -> Audible -> title -> Part 1;2;3, etc.
When connnected when MM is loaded it becomes: audiobooks -> title -> Part 1;2;3, etc.
The books can't be played anymore. When starting iTunes, the original chain is restored and the books can be played again.

In the attatched log, please find the line "iPhne van hs.......". That's probably the place to start.

Some other remarks:
- when iTunes is started, the folder reapears immediatelly;
- I cannot reproduce this when connecting the iPhone first and starting MM after that. It's about one in ten that it goes wrong then as well.
- During my last attempt to reproduce, the iPhone crashed while MM was syncing it. It got stuck displaying: Cancelling synchronisation.
- when iTunes and MM are both loaded, this problem does not seem to occur.

Ludek

2011-07-13 21:58

developer   ~0026781

The books can't be played where? In MM interface or in the iPhone? I believe that MM's never could play AA files.

rusty

2011-07-14 02:25

administrator   ~0026787

On the iPhone. i.e. he's saying the MM's updates to the iPhone's DB cause the iPhone to not be able to play the audible tracks.

Ludek

2011-07-19 23:17

developer   ~0026919

Last edited: 2011-07-20 09:47

My test results are same as Rusty's.

MM moves the books from
Audiobooks -> Audible -> title -> Part 1;2;3, etc.
to
Audiobooks -> title -> Part 1;2;3, etc.
when synchronizing, but the files are still playable.

While iTunes moves the books from
Audiobooks -> title -> Part 1;2;3, etc.
back to
Audiobooks -> Audible -> title -> Part 1;2;3, etc.
on startup.

Same behaviour when testing with MM3.

rusty

2011-07-21 04:06

administrator   ~0026942

Last edited: 2011-07-21 04:08

Further testing by the user reveals that the problem isn't a regression, but rather a lack of support by MM of the newest audible extended format (.aax). i.e. Audible format 3 works correctly with MediaMonkey (even when the location of the file is changed), however the newest audible extended format doesn't.

This may alsos explain why MM crashes when it scans the user's audible download folder--It cannot handle the new file format.