Reply to thread

Message

<blockquote data-quote="Oxan" data-source="post: 768227" data-attributes="member: 97484">Regarding the problems on the Galaxy Tab:There were indeed some playback problems on the original Galaxy S. Not sure if that's true with the Galaxy Tab 10.1 too. The error you get is MEDIA_ERROR_SERVER_DIED, which usually indicates some bug in the Android firmware in combination with the current stream. We probably need to set some different parameters, but I don't have any Honeycomb hardware to test it with. The docs indicate that it's the same as the support in Gingerbread - which is weird, because that works for me. I've one idea what it can be though: could one of you try what DieBagger suggested above and change -acodec aac -ab 256k -ac 2 -strict experimental to -an in config.xml and then check if the changed profile works? There is a remember checkboxDepends on your source file, HTPC and device, but if you've a reasonably powered device then it's usually the HTPC or the wifi.</blockquote>

[QUOTE="Oxan, post: 768227, member: 97484"] Regarding the problems on the Galaxy Tab: There were indeed some playback problems on the original Galaxy S. Not sure if that's true with the Galaxy Tab 10.1 too. The error you get is MEDIA_ERROR_SERVER_DIED, which usually indicates some bug in the Android firmware in combination with the current stream. We probably need to set some different parameters, but I don't have any Honeycomb hardware to test it with. The docs indicate that it's the same as the support in Gingerbread - which is weird, because that works for me. I've one idea what it can be though: could one of you try what DieBagger suggested above and change [i]-acodec aac -ab 256k -ac 2 -strict experimental[/i] to [i]-an[/i] in config.xml and then check if the changed profile works? There is a remember checkbox Depends on your source file, HTPC and device, but if you've a reasonably powered device then it's usually the HTPC or the wifi. [/QUOTE]

Verification