Opened 4 years ago

Last modified 4 years ago

#11724 new defect

SWORD25: Slow video and out of synch audio on old Android devices

Reported by: antoniou79 Owned by:
Priority: low Component: Engine: Sword25
Version: Keywords: Android, out of synch, slow, video, theora
Cc: antoniou79 Game: Broken Sword 2.5


Seems that some optimizations are needed for the engine's decoder, since on my old Android devices (Xperia Z5 Compact, Huawei Y550) the video in the main menu (upon launch) and more noticeably the intro cutscene plays too slow -- and out of synch with the audio that plays at normal pace.

This does not occur on a more recent Android device, with the same ScummVM app version (tested on 2.2.0, 2.2.1pre and 2.3git release builds).

Thus, it is probably an engine issue rather than an Android port issue

Change History (2)

comment:1 by raziel-, 4 years ago

Could you please check if this a dupe of #7063?

comment:2 by antoniou79, 4 years ago

Replying to raziel-:

Could you please check if this a dupe of #7063?

@raziel- it seems at least somewhat related, but I did not get the screen completely stuck on my testing yet. Maybe this could happen on an even older device.

The video does play slower than the audio, and so at some point the audio ends and the video goes on without it; I'm not sure I noticed the video going faster after that point, but it might.

However, the desynch is present throughout the video playback, meaning that it's noticeably off even at the very first seconds of the intro.

Also, it seems to be a general video playback issue for the game, as the video playing (looping) in the menu scene (the fire flames in the background) is noticeably slow as compared to it running on a faster device. And the mouse cursor on that screen is significantly laggy / slow responding.

My testing was done on two Android devices:

  • MediaPad M5 10" (Android 9, arm64_a8v)
  • Xperia Z5 Compact (Android 7.1.1, arm64_a8v)

The issue was consistently there on the Xperia Z5 Compact device. On the Huawei, with a release build I never got it, but with a debug build it did occur sometime -- this might be due to the device being low on power at the time of testing and thus running in limited performance mode.

Last edited 4 years ago by antoniou79 (previous) (diff)
Note: See TracTickets for help on using tickets.