lists | 1 Mar 01:31 2007

Re: Re: [BUG] movie-aspect autodetection failes for mkv in r22325

On Thu, 1 Mar 2007, ajaxas wrote:

>> AVI, as well, has been failing for me since around 22229.

> Um, well. There's a patch, use it together, use it in peace.

Thanks.  I've been trying to follow the patches, but with so much going on 
it's been an uphill struggle.

> As far as i was told, it actually reverts r22295, anyway - it works.

Yeah, best as I can tell 22299 was the last working revision, but ffmpeg 
is in such a state of flux right now that regression testing 
is...difficult.
Bo Liu | 1 Mar 05:22 2007
Picon

Does mplayer support non-fullscreen mode on an arm board?

Hi

I want to use mplayer on embedded platform like ARM.I know some people
already cross compiled it on ARM board, and I wonder if mplayer
only works in fullscreen mode on the LCD, or we can play a video file which
is "smaller" than the LCD size? and the video is played right in the middle
of the LCD with black border around it?

please let me know if there is any way to play a small video file.

thanks for your time.

--

-- 
platinum.liu
Sichuan University
Louis Patterson | 1 Mar 08:42 2007
Picon

I want to use mplayer-only and mencoder-only features in the same command line.

I have written a script for the conversion of various computer files
to DVD-videos. It uses mplayer to do decompression and demuxing [-vo
file &c], various other programs to process the video and audio
seperately and remux them [the mjpeg tools, mostly]; it's working
fairly well.

However, it doesn't appear to support variable frame rate materials.
To do this I apparently need to use -ofps framerate, but mplayer
doesn't support this, only mencoder.

However, mencoder only appears to support a single output stream, so
if I shifted to mencoder I'd need a seperate demuxer [probably,
ironicaly enough, mplayer!].

This doesn't appeal to me. Is there something I've missed that would
provide an easier way?
Nico Sabbi | 1 Mar 09:35 2007
Picon

Re: I want to use mplayer-only and mencoder-only features in the same command line.

Louis Patterson wrote:

> I have written a script for the conversion of various computer files
> to DVD-videos. It uses mplayer to do decompression and demuxing [-vo
> file &c], various other programs to process the video and audio
> seperately and remux them [the mjpeg tools, mostly]; it's working
> fairly well.
>
> However, it doesn't appear to support variable frame rate materials.
> To do this I apparently need to use -ofps framerate, but mplayer
> doesn't support this, only mencoder.
>
> However, mencoder only appears to support a single output stream, so
> if I shifted to mencoder I'd need a seperate demuxer [probably,
> ironicaly enough, mplayer!].
>
> This doesn't appeal to me. Is there something I've missed that would
> provide an easier way?

mencoder can generate mpeg files either with -of mpeg or with -lavf
(but in this case don't use b-frames).
As for demuxers, mpeg2desc from dvdauthor is an option (small
size, fast)

 
 --
 Email.it, the professional e-mail, gratis per te: http://www.email.it/f

 Sponsor:
 Refill srl il paradiso della tua stampante - cartucce e toner compatibili, inchiostri e accessori per la
(Continue reading)

Guillaume POIRIER | 1 Mar 10:14 2007
Picon

Re: Does mplayer support non-fullscreen mode on an arm board?

Hi,

On 3/1/07, Bo Liu <platinum.liu <at> gmail.com> wrote:
> Hi
>
> I want to use mplayer on embedded platform like ARM.I know some people
> already cross compiled it on ARM board, and I wonder if mplayer
> only works in fullscreen mode on the LCD, or we can play a video file which
> is "smaller" than the LCD size? and the video is played right in the middle
> of the LCD with black border around it?
>
> please let me know if there is any way to play a small video file.

I haven't tested, but I do think it should work, because it's usually
more expensive to upscale to fit the whole screen than leaving the
video size untouched.

Guillaume
Gianluca Fiore | 1 Mar 10:21 2007
Picon

Re: Compiling MPlayer fails

On Thu 01 Mar, 2007 at 00:31:25 +0600, ajaxas wrote:
> 
> Well, read The Wanderer, and also read ./configure --help:
> 
> "This configure script is NOT autoconf-based, even though its output is similar.
> It will try to autodetect all configuration options. If you --enable an option
> it will be forcefully turned on, skipping autodetection. This can break
> compilation, so you need to know what you are doing."
> 
> That's it.

Yes, I read it. I was only wondering why this message, because if I
remember correctly it wasn't before (and with before I mean "some months
ago").
> 
> -- 
> ajaxas <ajaxas <at> gmail.com>
> _______________________________________________
> MPlayer-users mailing list
> MPlayer-users <at> mplayerhq.hu
> http://lists.mplayerhq.hu/mailman/listinfo/mplayer-users
Gianluca Fiore | 1 Mar 10:35 2007
Picon

Re: Compiling MPlayer fails

On Wed 28 Feb, 2007 at 07:18:54 -0500, The Wanderer wrote:
> Gianluca Fiore wrote:
> 
>>May I ask why this kind of behaviour? I'm a long time cvs/svn mplayer
>>user and for many years enabling options from the configure script
>>was *ok*. Now why isn't so anymore?
> 
> In MPlayer's configure script, '--enable' means "do not perform any
> autodetection; assume that everything necessary for this feature is
> present, including all necessary special compiler options". If you use
> it, you need to explicitly specify include directories and linker flags
> via the appropriate configure options.
> 
> This is not a change; it has been the case for quite literally as long
> as I have been following MPlayer development (i.e. since the 0.90
> release series), although for some while in the "early" years it was not
> consistent across the entirety of configure (and in some places it may
> still not be).
> 
> If it "worked" for you before, that was a coincidence; all of your
> necessary header files and libraries happened to be in places where
> MPlayer (and/or the compiler) knew to look for them by default, and no
> specific linker flags were necessary.
> 
> Personally, I find it a little implausible that MPlayer was ever able to
> find the XviD libraries with no linker options (i.e. '-lxvidcore'), but
> I have no particular reason to accuse you of lying about it.
> 
I've been using these options to configure for a long time (around a
year) without any problem, until two weeks ago when it stopped the
(Continue reading)

Daniel Svensson | 1 Mar 10:58 2007
Picon

Flash Video over HTTP issues

Hi,

I've noticed a problem with playing Flash Video (.flv) files over
HTTP. It seems that if the server doesn't have 'Accept-Ranges' header
mplayer fail to play the file. This is very odd because to remedy this
I wrote a proxy in python that sets the 'Accept-Ranges' header, this
makes mplayer play the file correctly, but it never sends any 'range'
requests to the proxy so it doesn't really use any features made
available by 'Accept-Ranges'.
To prove my point I edited streams/http.c to always set the seekable
flag to 1 and now mplayer could play all the streams without any
problems. (this is _obviously_ not a fix, just a demonstration)

Here is the critical log output of mplayer failing:
LAVF_check: flv format
libavformat file format detected.
cache_stream_seek: WARNING! Can't seek to 0xFFFFFFFFFFFFFFFF !
cache_stream_seek: WARNING! Can't seek to 0xFFFFFFFFFFFFFFFC !
Stream not seekable!
cache_stream_seek: WARNING! Can't seek to 0xFFFFFFFFB9B3A9FC !
Stream not seekable!
[flv  <at>  0x8814fa8]skipping flv packet: type 74, size 16658666, flags 0
Stream not seekable!
(where the last two messages are repeated with diffrent values, "forever")

And the same point where it works:
LAVF_check: flv format
libavformat file format detected.
cache_stream_seek: WARNING! Can't seek to 0xFFFFFFFFFFFFFFFF !
cache_stream_seek: WARNING! Can't seek to 0xFFFFFFFFFFFFFFFC !
(Continue reading)

The Wanderer | 1 Mar 13:22 2007
Picon
Picon

Re: Compiling MPlayer fails

Gianluca Fiore wrote:

> On Wed 28 Feb, 2007 at 07:18:54 -0500, The Wanderer wrote:
> 
>> Gianluca Fiore wrote:
>> 
>>> May I ask why this kind of behaviour? I'm a long time cvs/svn
>>> mplayer user and for many years enabling options from the
>>> configure script was *ok*. Now why isn't so anymore?
>> 
>> In MPlayer's configure script, '--enable' means "do not perform any
>> autodetection; assume that everything necessary for this feature
>> is present, including all necessary special compiler options". If
>> you use it, you need to explicitly specify include directories and
>> linker flags via the appropriate configure options.
>> 
>> This is not a change; it has been the case for quite literally as
>> long as I have been following MPlayer development (i.e. since the
>> 0.90 release series), although for some while in the "early" years
>> it was not consistent across the entirety of configure (and in some
>> places it may still not be).
>> 
>> If it "worked" for you before, that was a coincidence; all of your
>> necessary header files and libraries happened to be in places where
>> MPlayer (and/or the compiler) knew to look for them by default,
>> and no specific linker flags were necessary.
>> 
>> Personally, I find it a little implausible that MPlayer was ever
>> able to find the XviD libraries with no linker options (i.e.
>> '-lxvidcore'), but I have no particular reason to accuse you of
(Continue reading)

Risto Suominen | 1 Mar 13:31 2007
Picon

Crash on OS X 10.3.9

I installed MPlayer OSX PPC binary package on my iMac DV 400 MHz (G3).
First it started ok, but didn't play a URL, before I created a
symbolic link at /usr/lib/libncurses.5.4.dylib pointing at
/sw/lib/libncurses.5.dylib (Fink, OS X included version was 5.0.0).

Then it played the video URL without video, i.e. black screen and ok
audio. Then I decided to install the Codec package (rp9). It made no
difference, and I decided to restart the player. Now it crashed on
startup.

I undid the changes (the link and the codecs), re-installed the
player, even re-booted the machine, but no help. A crash report of 14
k is generated, maybe too much to attach here? I might make it
downloadable if there is interest...

Gmane