Details
-
Bug
-
Resolution: Done
-
P2: Important
-
6.2.0
-
None
-
-
0c1bb90691780703eabc7ed1954d6b49fe5da580 (qt/qtmultimedia/dev) 51667b5b214d5d29589f44f4d65428924dc064ce (qt/qtmultimedia/6.2)
-
2021wk42POAndroid&Mobile, 2021wk44POAndroid&Mobile
Description
Kit: Android Qt 6.2.0 Clang armeabi-v7a
Video Source: https://bhaart.s3.ap-south-1.amazonaws.com/sri_ramachandra_kripalu.mkv
Note that I did use a local copy of the above video (on my Android device).
Reproduction Steps
I tried testing the "seek" behavior programmatically using the mediaPlayer.position property. Per specification, I can specify a time up to millisecond accuracy.
Below is the code snippet.
Window {
MediaPlayer {
...
}
VideoOutput {
...
TapHandler {
property int seekPos: 96000
onSingleTapped: {
mediaPlayer.position = seekPos
seekPos += 100
}
}
}
}
However, it is observed that the seek happens in steps of 5 seconds.
For example, if I seek to a value between 91 and 96 seconds, the video would actually seek to 91st second itself. Similarly, if I seek to a value between 96 and 101 seconds, the video would actually seek to 96th second.
This variance is clearly unacceptable to our use case.
I did not try with a remote video file (network location), but I am assuming the behavior will not be any better.
Questions
- Am I missing any configurations here?
- Would the millisecond seek accuracy be technically feasible to support in Qt6 (in future versions)?
Attachments
Issue Links
- mentioned in
-
Page Loading...
For Gerrit Dashboard: QTBUG-97415 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
380396,2 | Change Android MediaPlayer SeekTo to the Closest Frame | dev | qt/qtmultimedia | Status: MERGED | +2 | 0 |
380513,2 | Change Android MediaPlayer SeekTo to the Closest Frame | 6.2 | qt/qtmultimedia | Status: MERGED | +2 | 0 |