Page 1 of 1
'Unsupported format' error after playing video [#11540]
Posted: Tue Dec 03, 2013 5:53 am
by rivorson
Every time I finish playing a video file in MMA I get an error message that states 'Unsupported format'. MMA plays the video successfully so I assume the error is caused by trying to update the play count. I am currently using build 189 but this also occurred in every build for at least the last two months.
If I stop a video part way through then the bookmark position and last played time will be updated in MMW on the next sync, but if I play from start to finish then it acts like the file has not been played.
I have submitted debug log A8BTB5L08L.

Re: 'Unsupported format' error after playing video
Posted: Tue Dec 03, 2013 5:57 am
by rivorson
Also, all of the videos files on the device were transcoded to mp4 by MMW during sync.
Re: 'Unsupported format' error after playing video
Posted: Wed Dec 04, 2013 8:53 am
by rusty
Hi,
Thanks for the report.
What phone are you using, and what version of Android?
Thanks.
-Rusty
Re: 'Unsupported format' error after playing video [#11540]
Posted: Wed Dec 04, 2013 1:33 pm
by rivorson
Hi Rusty
The log was created on a Nexus 7 running stock Android 4.4, but I have the same issue on my Nexus 4 with the same Android version.
With further testing I have discovered that the error only occurs for video files that have been transcoded by MMW. I found a video in my library that didn't need transcoding which played without the error and updated the play count in MMW appropriately. Then I manually transcoded that same video in MMW and downloaded it to the device using a file manager app. The transcoded file played but gave the error message at the end of the file.
Re: 'Unsupported format' error after playing video [#11540]
Posted: Thu Dec 05, 2013 12:21 pm
by rusty
Thanks. It'll be fixed in the next build.
-Rusty
Re: 'Unsupported format' error after playing video [#11540]
Posted: Mon Dec 16, 2013 1:03 pm
by rivorson
I've played several videos in build 202 and haven't seen the error once, so can confirm that it is fixed. Thanks, Rusty.