View Issue Details

IDProjectCategoryView StatusLast Update
0008542MMW v4Synchronizationpublic2021-05-25 10:50
ReporterLudek Assigned To 
PriorityurgentSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version4.0 
Target Version4.1Fixed in Version4.1 
Summary0008542: Device Sync: Auto-converted tracks shows incorrect bitrate in MM interface
Description- start mm4 1446
- define auto-conversion (if mp3 > 192kbps then do mp3 = 160 kbps)
- select entire album from list
- right click and choose 'send to xperia arc'

=> the tracks under the device node in the Media Tree shows incorrect bitrate (192 kbps instead of 160 kbps).
Additional Informationhttp://www.mediamonkey.com/forum/viewtopic.php?f=6&t=61253#p315259
TagsNo tags attached.
Fixed in build1648

Relationships

related to 0011012 closedLudek MMW v4 MMW prompts to reverse sync unchanged tracks and playlists over USB 
parent of 0009946 closedLudek MMW v4 Auto-converted tracks are always re-synced (regression in 4.1) 
related to 0010183 closedLudek MMW v4 Incorrect file size shown in MM for files after auto-sync to iPhone (regression) 
related to 0005995 closedLudek MMW v4 Visual bug: Incomplete lyrics on iPods (just in MM interface) 
related to 0017913 closedLudek MMW 5 iPod Nano files shown without Bitrate 

Activities

Ludek

2011-10-19 11:00

developer   ~0028391

Fixed in build 1448.

stephen_platt

2011-10-21 02:54

developer   ~0028426

According to the original user that reported the issue it is still not showing correct bitrate/file size

Ludek

2012-02-04 12:11

developer   ~0030274

Last edited: 2012-02-04 13:05

Note that according the users only bitrate is now displayed wrongly and only for android devices in MTP mode (without drive letter).

My android device cannot connect in MTP mode, so I can't test/confirm/fix.
Moving target to 4.0.4

@Jiri, as I know you have an android device connecting in MTP mode, so could you look why bitrate is not read correctly in DeviceWMDM.MetadataToTrackData ?
Anyhow, I don't see this issue as urgent.

jiri

2012-03-01 15:00

administrator   ~0030598

Last edited: 2012-03-01 15:27

The problem is caused by the fact that Android devices don't report Bitrate over MTP protocol and MM obviously uses the only know information it has - the bitrate of track in Library.

We probably should store such format specific information (mainly Bitrate, Samplerate and Channels) in DeviceTracks table, so that we have it accessible and can show the correct info. It would be a nice to have feature in order to avoid any confusion caused by the incorrect bitrate, but it probably isn't too urgent.

Note: It's most obvious by comparing Device\Music (where bitrate from MM DB is shown) and Device\Folders\.. (where no bitrate is shown). This discrepancy is probably ok though, since Folders node is supposed to show the actual content of the device by browsing it (i.e. something like My Computer vs. Library nodes).

Ludek

2012-03-08 15:08

developer   ~0030647

Fixed in build 1601.

lowlander

2012-04-27 04:09

developer   ~0030953

This affects iOS5 devices too: http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=65755

peke

2012-12-19 23:52

developer   ~0034034

Verified 1615

lowlander

2012-12-20 03:17

developer   ~0034046

Tested with 1615 to an iPod Nano and some of the tracks show no bitrate (shows -).

Ludek

2012-12-20 20:49

developer   ~0034083

Martin, I haven't been able to replicate with MMW 1615 and iPod Nano 7, but I guess that it could be just a survival from 4.0 ?

i.e. If you re-sync the tracks using 1615, does it still show unknown bitrate?

peke

2012-12-21 02:48

developer   ~0034090

Note me neither, but I was using clean iPod and MMW.

lowlander

2012-12-21 18:55

developer   ~0034108

Verified on 1615.

lowlander

2013-02-14 16:50

developer   ~0034923

Although eventually the correct file size is shown (bitrate shows as - though) this is not the case when opening the Videos node for the iPod in MediaMonkey.

In my experience the wrong amount (32) of files and the wrong filesize was shown on opening the Videos node (with status reading files...) and then the view refreshes to show the correct amount (25) of files and the correct filesize (no bitrate though).

It seems MediaMonkey reads from its own DB on opening the node (unexpected) and then when it finishes reading the device it show what's actually on the device. [debug2.zip]

Ludek

2013-02-14 19:46

developer   ~0034936

Yes, this works exactly like you said and like was designed in the past.

When device is plugged and the content has not been scanned yet then MM uses content from its own DB (this content MM remembers as synced to the device) and once the scanning finishes then the real content is shown.

lowlander

2013-02-14 21:12

developer   ~0034940

Then there is a bug that MediaMonkey thinks more files are on the device then actually are on the device. However I don't know why MediaMonkey thinks those files are on the device.

Ludek

2013-02-14 23:07

developer   ~0034942

e.g. because they were deleted from the device meanwhile?

lowlander

2013-02-14 23:19

developer   ~0034943

Nothing has been deleted from the device and I don't think they were using iTunes. If anything was manually deleted it would have been with MediaMonkey.

Ludek

2013-02-15 13:06

developer   ~0034957

Last edited: 2013-02-15 13:12

Actually I found that there was a regression and bitrate was not shown at all for tracks on an android phone connected over MTP.

Fixed in build 1625.


Note that the other issue that Lowlander observed is now tracked as 0010534

peke

2013-04-27 10:53

developer   ~0035822

Verified 1634 using Sony xperia Tipo

Ludek

2013-07-12 10:09

developer   ~0036834

Note that it still doesn't seem to be fully fixed.

It works fine for CBR, but if user uses VBR then the tracks still appear as 128/CBR in MMW interface.

Ludek

2013-07-12 10:51

developer   ~0036835

Fixed in build 1648.

rusty

2013-07-18 20:21

administrator   ~0036915

Verified 1651.