Wednesday, April 9, 2014

videoview seekto ()


Change with seekto () video playback progress, but does not seem accurate, for example, I want to seek to 10 seconds at the (film's duration is to get 61,068, I seekto (10000)), the results of which play in 12 seconds place; I seekto (duration ), it should be concluded, but also put a second look until the end. Help the younger Analysis This is how a thing ah!
<-! Main posts under Banner (D4) -><-! Posts under the main text (D5) ->
Reply:
seekTo (int) is asynchronous, immediately returned to the real seek operation may take some time to complete.
I understand you are in 10s when seekTo, video jumped 10s, began to prepare for work, but when it is ready to 12s, and then start playing.
SDK and stackoverflow has this description:
 The playback position can be adjusted with a call to seekTo (int ). 
Although the asynchronuous seekTo (int) call returns right way, the actual seek operation may take a while to finish, especially for audio / video being streamed. When the actual seek operation completes, the internal player engine calls a user supplied OnSeekComplete.onSeekComplete ( ) if an OnSeekCompleteListener has been registered beforehand via setOnSeekCompleteListener (OnSeekCompleteListener).

Reply:
cited a floor tantahe reply:
seekTo (int) is asynchronous, immediately returned to the real seek operation may take some time to complete.
I understand you are in 10s when seekTo, video jumped 10s, began to prepare for work, but when it is ready to 12s, and then start playing.
SDK and stackoverflow has this description:
 The playback position can be adjusted with a call to seekTo (int ). 
Although the asynchronuous seekTo (int) call returns right way, the actual seek operation may take a while to finish, especially for audio / video being streamed. When the actual seek operation completes, the internal player engine calls a user supplied OnSeekComplete.onSeekComplete ( ) if an OnSeekCompleteListener has been registered beforehand via setOnSeekCompleteListener (OnSeekCompleteListener).

Well, read, should be that for this reason, and seemingly no solution. .
Reply:
reference to the second floor shililang reply:
Quote: references to a floor tantahe reply:

seekTo (int) is asynchronous, immediately returned to the real seek operation may take some time to complete.
I understand you are in 10s when seekTo, video jumped 10s, began to prepare for work, but when it is ready to 12s, and then start playing.
SDK and stackoverflow has this description:
 The playback position can be adjusted with a call to seekTo (int ). 
Although the asynchronuous seekTo (int) call returns right way, the actual seek operation may take a while to finish, especially for audio / video being streamed. When the actual seek operation completes, the internal player engine calls a user supplied OnSeekComplete.onSeekComplete ( ) if an OnSeekCompleteListener has been registered beforehand via setOnSeekCompleteListener (OnSeekCompleteListener).

Well, read, should be that for this reason, and seemingly no solution. .

You can add an amount in advance to try their own, for example you want to jump to 10s, you jump to the code set 8s, can adjust the amount in advance, this can reduce the error.
Reply:
reference to the third floor tantahe reply:
Quote: references to the second floor shililang reply:

Quote: references to a floor tantahe reply:

seekTo (int) is asynchronous, immediately returned to the real seek operation may take some time to complete.
I understand you are in 10s when seekTo, video jumped 10s, began to prepare for work, but when it is ready to 12s, and then start playing.
SDK and stackoverflow has this description:
 The playback position can be adjusted with a call to seekTo (int ). 
Although the asynchronuous seekTo (int) call returns right way, the actual seek operation may take a while to finish, especially for audio / video being streamed. When the actual seek operation completes, the internal player engine calls a user supplied OnSeekComplete.onSeekComplete ( ) if an OnSeekCompleteListener has been registered beforehand via setOnSeekCompleteListener (OnSeekCompleteListener).

Well, read, should be that for this reason, and seemingly no solution. .

You can add an amount in advance to try their own, for example you want to jump to 10s, you jump to the code set 8s, can adjust the amount in advance, this can reduce the error.
Well, this is also a way Thanks, knot posted!

No comments:

Post a Comment