| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0018241 | MMW 5 | Sync | public | 2021-09-02 00:05 | 2024-02-20 16:39 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Target Version | 5.1 | Fixed in Version | 5.1 | ||
| Summary | 0018241: Device sync: add auto-conversion for artwork files | ||||
| Description | Some devices do not support Specific JPG formats. Tested and confirmed issue on - Ford Flex 2013 with Ford Sync 2 (User Car) - Honda CR-V 2015 With HondaLink - Suzuki Vitara 2015 with bosch infotainment With all systems album art is not shown even it is embed and rest of Metadata is read normally. Attaching both working and not working Album art image. Looks like problem is not directly related to MM and how it tags files as adding same JPGs by using other apps result is same eg. not showing the Album Art image. NOTE: From what I have found both are 500x500 96DPI, but headers are bit different. | ||||
| Additional Information | https://www.mediamonkey.com/forum/viewtopic.php?p=500906#p500906 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2800 | ||||
|
|
working img specs.jpg (47,842 bytes) not working img specs.jpg (45,573 bytes) |
|
|
The non working version is in progressive JPEG, the working version is baseline (standard) JPEG. I guess the devices do not support progressive JPEGs, could you confirm this? The quickest way is searching "FF DA" in hexa (the next byte is usually 00), baseline images have it only near the beginning, progressive have several instances of this header (for each "detail iteration" of the image). |
|
|
Did you test whether JPG created by MM5 is readable by the devices (e.g. with Sync Profile -> Tagging -> [x] Copy artwork to file tags)? We could add kind of auto-convert config there then. |
|
|
Original Image was not an external image, but extracted from File tag which was fetched using MM5 Auto Lookup Image and save option. In remote session last night I compared alredy tagged one with first choice from lookup image and they were identical. After that i converted that JPG to various JPG formats including "JPEG TrueColor v1.2/v1.1", Progressive/Optimized/Standard/... and then we copied to number of files, each one tagged with different JPG file and then he went to insert USB to Ford Flex and play them. Working one is result of these tests as one that works on all Cars I tested later with. FYI If we decide to add Auto Correction we should consider to resize image to 500x500 or even 300x300 because he said that if image is larger there is delay on playback start. |
|
|
Ok, so we could add another settings into Device > Sync Profile -> Tagging [x] Convert all Artwork images to [JPG^], max. resolution: [500] px to be placed probably below current [..] Copy Artwork to file tags Assigned to Rusty to review wording (with 5.1 target) |
|
|
[ ] Resize artwork: . . . . . Max. resolution: _500_px . . . . . Format: _[[jpg], png, any]_v_ Note: - the only new string is 'Resize artwork' - the reason for the suggested change in layout is so that it's clearer that it's primarily for changing the _size_ of the artwork and that artwork will be converted even if the format doesn't need to be changed. |
|
|
OK, but isn't something like this more versatile ? : [..] Convert all Artwork images to [JPG^] -- [..] Max. resolution: [500] px i.e. allowing the format convertion without degrading the resolution? |
|
|
OK I guess that's fine. I'd assumed that the issue would be thought of by most users as 'the images are too large' rather than 'they're in the wrong format. If it's really about format, then is this ok? [..] Convert artwork to [JPG^] -- [..] Max. resolution: [500] px Or did you mention '...all artwork..' because every single image should be converted? |
|
|
OK, looks good, changing target to 5.1 as this requires new strings and there are more severe issues to fix for 5.0.4 atm |
|
|
Implemented in 5.1.0.2800 |
|
|
Verified 2834 |
