Bug #2915

Audio/Video playback not in sync

Added by Y A almost 5 years ago. Updated over 2 years ago.

Status:AcceptedStart date:11/23/2015
Priority:NormalDue date:
Assignee:Andreas Smas% Done:

0%

Category:Video playback
Target version:5.2
Found in version:4.99.462.g91dd2 and previous version Platform:Android

Description

Some video playback are okay, some are not with slow motion and warning message that "CPU is too slow to decode this video". However, in both occasions, audio/video are out of sync.

CPU: Arm Dual Core.
Platform: Android 4.2.2
OpenGlES: Mali 400 MP

movian-0.log (27.3 KB) Y A, 11/24/2015 02:56 AM

movian-3.log (16.8 KB) Y A, 01/05/2016 06:58 PM

movian-0.log (4.6 MB) Y A, 01/05/2016 06:58 PM

Associated revisions

Revision b323b4e4
Added by Andreas Smas almost 5 years ago

android: Add setting for hardware accelerated video decoding

refs #2915

Change included in version 4.99.569

Revision 252382b6
Added by Andreas Smas almost 5 years ago

android: Improve debug for accelerated video decoders

refs #2915

Change included in version 4.99.638

Revision 63a99b89
Added by Andreas Smas almost 5 years ago

android: Pass frame duration to display

refs #2915

Change included in version 4.99.639

History

#1 Updated by Andreas Smas almost 5 years ago

  • Status changed from New to Need feedback
  • Target version set to 5.0

You need to attach samples so I can test.

#2 Updated by Y A almost 5 years ago

Sorry, there are no samples. These are just streams from youtube/navi-x plugins.
I am attaching the log file.

#3 Updated by Y A almost 5 years ago

Any feedback??

#4 Updated by Andreas Smas almost 5 years ago

Maybe the system overall is too slow for playback. Movian does not currently use hardware accelerated video decoding at all on Android.

It's the best bet I have.

#5 Updated by Andreas Smas almost 5 years ago

I've added hardware acceleration behind a setting (default off)

Go to settings -> video and enable "Hardware accelerated decoding", see if it helps

#6 Updated by Andreas Smas almost 5 years ago

Any feedback on this?

#7 Updated by Y A almost 5 years ago

Did not work. Better off without it.
With Hardware accelerated decoding setting on, video playback is like Charlie Chaplin motion (fast motion) and then freezes while audio is way ahead.
Just wondering if it is an issue with the libav library.
While this could be a slow system (dual core arm), other apps like mxplayer is able to play fine mkv and 3D contents.
Is there a branch with ffmpeg?

#8 Updated by Andreas Smas almost 5 years ago

Y A wrote:

Is there a branch with ffmpeg?

No, and I don't think the performance difference between libav and ffmpeg is that big (if any?)

#9 Updated by Aben Escalante almost 5 years ago

I have this same issue on the PS3, but in my case I think that the PS3 hardware is to low to handle "Movian Bleeding Edge", I have a Galaxy S4 and Nvidia Shield tv and Movian Bleeding Edge runs perfect on those.

#10 Updated by Andreas Smas almost 5 years ago

Hi

Being at my parents place over the holidays allows me to test the video acceleration on more devices. So far I've not managed to get it to fail like you describe though :-(

I have added more (optional) debug though and better error checking in 4.99.639.

Please try again (With acceleration turned on) and also open settings:dev in the search bar on home page, go to bottom and turn on "Debug MediaCodec", this will log more info to the log.

Please rerun your problematic videos again and attach the logfiles.

Thanks
/Andreas

#11 Updated by Y A almost 5 years ago

Hi Andreas,

Thanks for your outstanding work.
Playback has now been much better with "Acceleration on" though at times in the beginning of the video it can be jerky and then smooth out afterwards. While it is playing, movian would suddenly quit without warning.
Please see log attachments,

Regards

#12 Updated by Y A over 4 years ago

Hi,
Any update? Any chance to look at the log regarding the sudden exit

#13 Updated by Andreas Smas over 4 years ago

I've looked briefly but the log didn't help much.

To capture a log with the crash I probably need output from adb log (not sure if that can be captured on-device or if you need to attach a USB-cable or adb remote)

Apart from the crash, is av-sync still problematic?

#14 Updated by Y A over 4 years ago

av-sync no longer a big issue, see my previous comment (#11), just the crash for now. i'll see if I can capture adb log.

#15 Updated by Andreas Smas over 4 years ago

Great, that can perhaps give a clue

#16 Updated by Andreas Smas over 4 years ago

  • Target version changed from 5.0 to 5.2

#17 Updated by Leonid Protasov over 2 years ago

  • Status changed from Need feedback to Accepted

Also available in: Atom PDF