View Issue Details

IDProjectCategoryView StatusLast Update
0020412MMW 5Syncpublic2023-12-04 18:50
Reporterpeke Assigned To 
PriorityurgentSeveritymajorReproducibilityunable to reproduce
Status resolvedResolutionunable to reproduce 
Target Version5.1.1 
Summary0020412: Sync Fail on Pixel 8 Pro Using Surface Tablet from 2017
DescriptionThis is not a bug directly as I think it is not related to MM itself, but anyway I fetched Debug log and MMA Logs to try to get to bottom of similar reports.

System is older Surface Tablet on Windows 10 22h2 with Only 4GB of RAM and soldered 120GB SSD, User is using external storages (due the single USB available on Tablet) thru USB HUB that serves a HUB to connect two additional monitors alongside keyboard and storages. That same HUB is used to try syncing with pixel 8 Pro and it fail with lack of free space on PC to Convert all tracks.

Library consist of MP3s 99.99% + 8 WMAs and 9 WAV files. All conversions were disabled in profile.

The problem he observes is that when he tries to either play or Sync with MM5 from MMA (WiFi) he gets Server inaccessible and MM5 throws error not enough space to convert files.

I upgraded him to 2824 and it started to sync, but still claim converting the files and Sync is progressing very slow (not done till this was written).

Test observation: System resources are topped eg. CPU is 4 Cores 1.6Ghz (usage commonly around 86-95% on all cores) and RAM is 3.6-3.9 GB used (95%), User asked me to suggest a newer laptop to upgrade so that he could migrate MM5.DB to it.

On both MMA and MM5 I do not see any issues, MM5 server seen and accessible, but after he tries to play it MMA report fail.

There is possibility that some files are missing/inaccessible but not all.

Here are the MM5 logs (from 2692) and also MMA log (LOG ID: BLHV8EFJCA) after it threw Server inaccessible.
Additional InformationTicket # 6508
TagsNo tags attached.
Fixed in build

Relationships

has duplicate 0020415 resolvedLudek MM5 stalls on sending data causing MMA WiFi sync fail with timeouts 

Activities

Ludek

2023-11-22 14:39

developer   ~0073609

In the log I see lines like:
TMediaServer.ServeMediaFile: File need to be converted : H:\Music\???\08 Have a Drink On Me.mp3 -> D:\MM Transcoded Files Temp\440.MP3
TMediaServer.ServeMediaFile: On-the-fly transcoding

So there needs to be auto-coversion rules that forces MP3 -> MP3 encoding, is this intentional?
Do you have screenshot of his auto-conversion rules?


>>On both MMA and MM5 I do not see any issues, MM5 server seen and accessible, but after he tries to play it MMA report fail.<<
>>There is possibility that some files are missing/inaccessible but not all.<<
Can you elaborate what exactly do you mean by these two sentenses?

peke

2023-11-22 19:18

developer   ~0073616

No there is no intentional rules, actually User profile is set to support all formats of supported extensions.

Ludek

2023-12-04 17:15

developer   ~0073713

The reason for converting everything (also MP3 -> MP3) seems to be
'[x] Level volume when syncing audio'

But in the log I noticed that the conversion was performed "on-the-fly" which is not expected for Wi-Fi sync...
The reason is that MMA requests the file without the 'DeviceID=' part so MM5 can't pair it with corresponding device profile..

Going to discuss with Martin..

Ludek

2023-12-04 17:20

developer   ~0073715

Last edited: 2023-12-04 17:33

i.e. MMA asked links to the files like
http://192.168.86.160:15074/%5CPlaylists%5C0a14a58d-3e65-43cc-a78b-039b18561636%5Cc8e8a27a-ccf9-4647-abcb-61920d1fbb56%5CItemID=23.mp3
instead of
http://192.168.86.160:15074/DeviceID=10cfd498-6aec-3582-93c9-012be0694ef9.0.0af16c98-19bb-4705-8eaf-091a4cd1dc1c_ItemID=23.mp3

But there are missing also a lot of requests related to Wi-Fi sync in the log (for some unknown reason)..

Ludek

2023-12-04 18:48

developer   ~0073716

Last edited: 2023-12-04 18:50

ok, actually 'Pixel8 UpNP fail.rar' is not Wi-Fi sync, but standard UPnP browsing from MMA, so explained...

And the reason for converting all files was
'[x] Level volume when syncing audio'

So in summary the question is whether there is still an issue?
If you are still seeing any, please re-opened with a debug log..