seek in millisecond position

Hi,

how can i seek  in millisecond position instead of second. in addition what
is the difference between seek and setting the value of time_pos

> how can i seek  in millisecond position instead of second.

This can only be useful if you have a keyframe-only file. Otherwise, 
every seek would land on a near keyframe, which leads to a granularity 
usually bigger than one second. Therefore, seek positions with higher 
accuracy are quite rarely needed.

Greets,
Kiste

On 07/02/2012 06:03 AM, Oliver Seitz wrote:
>
>> how can i seek  in millisecond position instead of second.
>
> This can only be useful if you have a keyframe-only file. Otherwise,
> every seek would land on a near keyframe, which leads to a granularity
> usually bigger than one second. Therefore, seek positions with higher
> accuracy are quite rarely needed.
>Isn't the upper limit in millisecond granularity defined by the formula 
1000/fps?  29.97 fps video would thus be limited to a 33.3667 ms resolution.

Anyway, what about MJPEG?  It's files are huge, but that *should* let 
you easily step frame by frame.-- 
"There is usually only a limited amount of damage that can be
done by dull or stupid people. For creating a truly monumental
disaster, you need people with high IQs."
Thomas Sowell

On 02.07.2012 14:03, Ron Johnson wrote:
> On 07/02/2012 06:03 AM, Oliver Seitz wrote:
>>
>>> how can i seek in millisecond position instead of second.
>>
>> This can only be useful if you have a keyframe-only file. Otherwise,
>> every seek would land on a near keyframe, which leads to a granularity
>> usually bigger than one second. Therefore, seek positions with higher
>> accuracy are quite rarely needed.
>>
>
> Isn't the upper limit in millisecond granularity defined by the formula
> 1000/fps? 29.97 fps video would thus be limited to a 33.3667 ms resolution.
>
> Anyway, what about MJPEG? It's files are huge, but that *should* let you
> easily step frame by frame.Right. MJPEG is keyframe-only, so mplayer could jump to any desired 
frame. MJPEG is often used for editing, but rarely for distributing and 
playing of videos. You said it, files are quite big.

MPlayer is made for playing, not for editing. So it aims mainly at 
codecs which are mostly used for playing, and these codecs use P- and/or 
B-frames. So, codecs which are mostly played do not support simple seeks 
to each frame. Then, a software which is mostly used for playing does 
not need to support a seek to each frame.

Well, ok, it wouldn't hurt either ;-) I'd prefer a means to seek to a 
certain frame number, not fractions of a second.

By the way, slave.txt does not state that fractions of a second were not 
supported. Did anyone actually try seeking to fractions of a second in a 
keyframe-only file?

Greets,
Kiste

On Mon, 2012-07-02 at 13:03 +0200, Oliver Seitz wrote:
> falcon sheep wrote:
> > how can i seek  in millisecond position instead of second.The seek command takes a float argument; nothing limits precision to
whole seconds.> This can only be useful if you have a keyframe-only file. Otherwise, 
> every seek would land on a near keyframe, which leads to a granularity 
> usually bigger than one second. Therefore, seek positions with higher 
> accuracy are quite rarely needed.MPlayer 1 is limited to keyframes only, but mplayer2 can seek to any
frame.

Am 02.07.2012 22:25, schrieb Uoti Urpala:
> On Mon, 2012-07-02 at 13:03 +0200, Oliver Seitz wrote:
>> falcon sheep wrote:
>>> how can i seek  in millisecond position instead of second.
>
> The seek command takes a float argument; nothing limits precision to
> whole seconds.Thanks! I did presume so, but I haven't tried yet :-)

Greets,
Kiste

On Mon, Jul 2, 2012 at 3:03 PM, Oliver Seitz  wrote:

>
>  how can i seek  in millisecond position instead of second.
>>
>
> This can only be useful if you have a keyframe-only file. Otherwise, every
> seek would land on a near keyframe, which leads to a granularity usually
> bigger than one second. Therefore, seek positions with higher accuracy are
> quite rarely needed.
>
>Actually I'm using it for audio only and 'fraction of a second' makes a big
different in my case.On Tue, Jul 3, 2012 at 12:25 AM, Uoti Urpala wrote:

> On Mon, 2012-07-02 at 13:03 +0200, Oliver Seitz wrote:
> > falcon sheep wrote:
> > > how can i seek  in millisecond position instead of second.
>
> The seek command takes a float argument; nothing limits precision to
> whole seconds.
>
>Thanks

> Actually I'm using it for audio only and 'fraction of a second' makes a big
> different in my case.Ok, this is very true. I did not think of "Audio only". Now it all makes 
sense ;-)

Greets,
Kiste