> gnome-mplayer --reallyverbose
> http://www.fileden.com/files/2006/12/11/497871/Private/tachikoma.mkv
works fine with 9.x and svn, with MPlayer svn rev 27776. IIRC there was
a patch [1] from Kevin for mkv files for get_property chapters, that may
be doing the trick.
[1]
http://lists.mplayerhq.hu/pipermail/mplayer-dev-eng/2008-September/058648.html
--
Onur Küçük Knowledge speaks,
<onur.--.-.pardus.org.tr> but wisdom listens
Onur Küçük wrote:
>
> On Sat, 15 Nov 2008 14:59:34 -0800 (PST)
> dk75 <ami...@gmail.com> wrote:
>
>> gnome-mplayer --reallyverbose
>> http://www.fileden.com/files/2006/12/11/497871/Private/tachikoma.mkv
>
> works fine with 9.x and svn, with MPlayer svn rev 27776. IIRC there was
> a patch [1] from Kevin for mkv files for get_property chapters, that may
> be doing the trick.
>
> [1]
> http://lists.mplayerhq.hu/pipermail/mplayer-dev-eng/2008-September/058648.html
>
I just found what is causing this, it seems the 'gio' support in
streaming_media. I think I have it worked out, but I want to do some
additional testing.
Kevin
- --
Get my public GnuPG key from
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7D0BD5D1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Remi - http://enigmail.mozdev.org
iEYEARECAAYFAkkgJGYACgkQ6w2kMH0L1dFicwCfczdRwgY8aTQD8i443L8JYRuV
4RUAnii8waT9HLU+2C0rkGqOa1uvBiRZ
=Rc3O
-----END PGP SIGNATURE-----
Krzysztof Duchnowski wrote:
>
> But... it brakes GECKO-mediaplayer compatybility - it's going play/pause
> all the time, with 1s period:
> http://www.gametrailers.com/player/42727.html
>
I tested this on my internet connection with both gecko-mediaplayer and
gnome-mplayer from SVN and I don't see the 1s, but I do have about 3s
once the cache is used up. I see you have a cache of 8196, and so I
would recommend that you raise it even more.
For an internet connection I use a 3G cell card, because DSL and Cable
are not available. So basically the slower your connection you should
either use more cache or play lower quality content.
Kevin
- --
Get my public GnuPG key from
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7D0BD5D1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Remi - http://enigmail.mozdev.org
iEYEARECAAYFAkkgcNIACgkQ6w2kMH0L1dEuDQCgjrG63vJaOkBVU2wlUFh4iCqq
bJQAn3g+2etiG+m6h/zpOvpfgufA/5J8
=9gFQ
-----END PGP SIGNATURE-----
Regards,
Starcrasher
--
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
Krzysztof Duchnowski wrote:
> Starcrasher pisze:
>
>>>> But... it brakes GECKO-mediaplayer compatybility - it's going play/pause
>>>> all the time, with 1s period:
>>>> http://www.gametrailers.com/player/42727.html
>
>>> I tested this on my internet connection with both gecko-mediaplayer and
>>> gnome-mplayer from SVN and I don't see the 1s, but I do have about 3s
>>> once the cache is used up. I see you have a cache of 8196, and so I
>>> would recommend that you raise it even more.
>
>>> For an internet connection I use a 3G cell card, because DSL and Cable
>>> are not available. So basically the slower your connection you should
>>> either use more cache or play lower quality content.
>
>> I noticed the same behaviour. I used the same cache setting for a long
>> time and didn't notice that before.
>> That's strange because if I hit media play/pause key on my keyboard, it
>> ends the loop and play normally.
>
> And more over it play/pause with full file buffered - so it's not a
> buffer/cache problem. It started just after GIO problem solving.
>
Can you recompile gnome-mplayer with the --without-gio option and see if
you get it working again?
Kevin
- --
Get my public GnuPG key from
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7D0BD5D1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Remi - http://enigmail.mozdev.org
iEYEARECAAYFAkkgkyIACgkQ6w2kMH0L1dE+JwCfbI+jYubdn/gStqQs77cpXGCW
yssAn1qBTxdjM0TAI3R0KCwQ03SEVSKC
=eAtF
-----END PGP SIGNATURE-----
Ok, so it does not appear to be the GIO code, but I did go in an rework
the autopause code so give that a try. I used to calculate based on
percent, now I base it on file size.
Kevin
- --
Get my public GnuPG key from
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7D0BD5D1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Remi - http://enigmail.mozdev.org
iEYEARECAAYFAkkhqBUACgkQ6w2kMH0L1dFH1gCggnOVLqjWv720kWM8C0VwyOJQ
Q24An1LUtudJfXrkmAUXy+2sYgWZ75uf
=pK5a
-----END PGP SIGNATURE-----
It plays fine at the beginning but when it reach buffer border it resets
to start possition and plays again from the beginning.
In r829 it worked with percent auto pause thought...
r829... ack, that is over 150 change sets apart. If you can find another
point that it worked closer to head I can look at it. I did look at the
change logs and found the conversion to internal uris around that point,
so I did fix that and made sure that g_stat was using a filename and not
a uri. The values now look sane to me for detecting when to autopause.
The reason it starts over is due to the website using the loop option,
so that is why it resets. mplayer seems to be hitting something in the
file and terminating, but if it caches more it seems to work fine. I
believe what it is hitting is an EOF in the mplayer cache as the file is
downloaded from the website.
It also seems that with mplayer SVN that it does not know that the file
has changed and so when it hits the point where the end of the file is
when mplayer starts. Basically it looks like it is seeing an EOF file
pointer and not seeing that file has changed on disk. Seems to be new
behavior with a recent mplayer cause it was not doing this earlier for me.
I have seen this problem with other media files, so this is common issue
in mplayer.
Kevin
- --
Get my public GnuPG key from
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7D0BD5D1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Remi - http://enigmail.mozdev.org
iEYEARECAAYFAkkhxYQACgkQ6w2kMH0L1dHTmwCfTmmxGEorUAi2GSLiwNr/3bz1
epkAoINXhsyFWnIiU8uXoUNjMapdJ/dH
=kalC
-----END PGP SIGNATURE-----
Krzysztof Duchnowski wrote:
Ok, I think I found a work around in the gnome-mplayer code, I'm telling
mplayer not to cache the file when playing that way. Still may be some
tuning as mplayer uses data quite fast on this file, but give r996 a try.
Kevin
- --
Get my public GnuPG key from
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7D0BD5D1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Remi - http://enigmail.mozdev.org
iEYEARECAAYFAkkhzGcACgkQ6w2kMH0L1dE5nQCfbEC+tOwmBf4ca6OwElB611nE
7wgAnRiHqZ0EPa6GfSWIy0TPgpksc98z
=xKhk
-----END PGP SIGNATURE-----
>> It plays fine at the beginning but when it reach buffer border it resets
>> to start possition and plays again from the beginning.
>> In r829 it worked with percent auto pause thought...
> r829... ack, that is over 150 change sets apart. If you can find another
> point that it worked closer to head I can look at it.
As I wrote at first post it was last revision working at all - rest just
hung out.
>>> Ok, so it does not appear to be the GIO code, but I did go in an rework
>>> the autopause code so give that a try. I used to calculate based on
>>> percent, now I base it on file size.
>> It plays fine at the beginning but when it reach buffer border it resets
>> to start possition and plays again from the beginning.
>> In r829 it worked with percent auto pause thought...
> Ok, I think I found a work around in the gnome-mplayer code, I'm telling
> mplayer not to cache the file when playing that way. Still may be some
> tuning as mplayer uses data quite fast on this file, but give r996 a try.
Partially.
I've used another video since first is buffered in browser cache. It is
1:37 runtime long. It's initially buffered to 20% before play, it played
to about 35% where it meet buffer border then it went to play/pause
state i which it meet 40s runtime and 65% buffer - then I've closed it.
As you can see 65% buffer is around 60-70s runtime and it's playing 40s
material and still making play/pause. It should stop to fill more buffer
than for initial play - that's how mplayer does.
Krzysztof Duchnowski wrote:
> Kevin DeKorte pisze:
>
>>> It plays fine at the beginning but when it reach buffer border it resets
>>> to start possition and plays again from the beginning.
>
>>> In r829 it worked with percent auto pause thought...
>
>
>> r829... ack, that is over 150 change sets apart. If you can find another
>> point that it worked closer to head I can look at it.
>
>
> As I wrote at first post it was last revision working at all - rest just
> hung out.
>
Oh, did you upgrade gecko-mediaplayer as well? Changes were made to it
at the same time.
I was testing today with gecko-mediaplayer and gnome-mplayer from SVN
and your issue seems to be fixed.
Kevin
- --
Get my public GnuPG key from
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7D0BD5D1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Remi - http://enigmail.mozdev.org
iEYEARECAAYFAkkh2vYACgkQ6w2kMH0L1dGoAgCgkkGLOcw+QHeBechXHO+7G7qT
EZwAniG8S45NgGTyFNFd3eJcN6PVPhSj
=N6Fs
-----END PGP SIGNATURE-----
Krzysztof Duchnowski wrote:
>
> Partially.
> I've used another video since first is buffered in browser cache. It is
> 1:37 runtime long. It's initially buffered to 20% before play, it played
> to about 35% where it meet buffer border then it went to play/pause
> state i which it meet 40s runtime and 65% buffer - then I've closed it.
> As you can see 65% buffer is around 60-70s runtime and it's playing 40s
> material and still making play/pause. It should stop to fill more buffer
> than for initial play - that's how mplayer does.
>
Ok, I did that the delta of 10% to take it out of autopause state so I
changed it from +10% to +20% (20% is how much mplayer buffers a file
before starting) and hopefully that will cache even more data. You must
have a pretty slow connection. The reason you are having so many issues
is that, that media is an HD file and will play nearly 375K/s or more.
So to keep up with it you need to have lots of bandwidth. My internet
connection is about 100K/s (which is on the low end in my location) and
I have to have a 5000K buffer and then I still get two or three stops
while watching it.
Kevin
- --
Get my public GnuPG key from
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7D0BD5D1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Remi - http://enigmail.mozdev.org
iEYEARECAAYFAkkh3coACgkQ6w2kMH0L1dGOLwCgiZJGkkTtvU0luSBAHIE1YIXr
E/IAoJNn/v3juVqp2W9gc92QXg8PoDsb
=eqxO
-----END PGP SIGNATURE-----
>> Partially.
>> I've used another video since first is buffered in browser cache. It is
>> 1:37 runtime long. It's initially buffered to 20% before play, it played
>> to about 35% where it meet buffer border then it went to play/pause
>> state i which it meet 40s runtime and 65% buffer - then I've closed it.
>> As you can see 65% buffer is around 60-70s runtime and it's playing 40s
>> material and still making play/pause. It should stop to fill more buffer
>> than for initial play - that's how mplayer does.
> Ok, I did that the delta of 10% to take it out of autopause state so I
> changed it from +10% to +20% (20% is how much mplayer buffers a file
> before starting) and hopefully that will cache even more data. You must
> have a pretty slow connection. The reason you are having so many issues
> is that, that media is an HD file and will play nearly 375K/s or more.
> So to keep up with it you need to have lots of bandwidth. My internet
> connection is about 100K/s (which is on the low end in my location) and
> I have to have a 5000K buffer and then I still get two or three stops
> while watching it.
Yes. I have slow connection - 240 KiB/s (2048 kbps listed at ISP)
But earlier GNOME-MPlayer cached more after meeting buffer end durring
playback so it was much desired feature. I think even bare MPlayer
buffer 20% at the beginning and then 50% after meeting buffer end.
And as for play/pause at lower runtime than the buffer it must be a
MPlayer playtime guessing feature... so I think play/pause bug is over.
Now it need's only some finetuning.