Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #221966 > unrolled thread

mplayer can't play big file by mencoder

Started byLong Wind <longwind2@yahoo.com>
First post2020-04-26 22:00 +0200
Last post2020-04-29 19:20 +0200
Articles 11 — 5 participants

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  mplayer can't play big file by mencoder Long Wind <longwind2@yahoo.com> - 2020-04-26 22:00 +0200
    Re: mplayer can't play big file by mencoder Nemeth Gyorgy <lists@friczy.net> - 2020-04-27 18:00 +0200
      Re: mplayer can't play big file by mencoder <tomas@tuxteam.de> - 2020-04-27 18:00 +0200
      Re: mplayer can't play big file by mencoder Long Wind <longwind2@yahoo.com> - 2020-04-27 21:10 +0200
        Re: mplayer can't play big file by mencoder <tomas@tuxteam.de> - 2020-04-27 21:20 +0200
          Re: mplayer can't play big file by mencoder Long Wind <longwind2@yahoo.com> - 2020-04-27 23:00 +0200
            Re: mplayer can't play big file by mencoder Nemeth Gyorgy <lists@friczy.net> - 2020-04-28 17:20 +0200
              Re: mplayer can't play big file by mencoder Nicolas George <george@nsup.org> - 2020-04-28 17:30 +0200
                Re: mplayer can't play big file by mencoder Long Wind <longwind2@yahoo.com> - 2020-04-29 00:00 +0200
                  Re: mplayer can't play big file by mencoder Charles Curley <charlescurley@charlescurley.com> - 2020-04-29 07:10 +0200
                    Re: mplayer can't play big file by mencoder Long Wind <longwind2@yahoo.com> - 2020-04-29 19:20 +0200

#221966 — mplayer can't play big file by mencoder

FromLong Wind <longwind2@yahoo.com>
Date2020-04-26 22:00 +0200
Subjectmplayer can't play big file by mencoder
Message-ID<zZVBv-4SF-5@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

i use stretch's mencoder to record a/vand use mplayer to play them, it works well
yesterday i record a big file, about 4GBmplayer fails to play it,any idea or player that might help? Thanks!
below is error msg by mplayer:
 zhou@debian:~$ mplayer /mnt/play/output/output192.avi 
MPlayer 1.3.0 (Debian), built with gcc-6.2.1 (C) 2000-2016 MPlayer Team
do_connect: could not connect to socket
connect: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing /mnt/play/output/output192.avi.
libavformat version 57.56.101 (external)
Mismatching header version 57.56.100
AVI file format detected.
[aviheader] Video stream found, -vid 0
[aviheader] Audio stream found, -aid 1
Seek failed
AVI: ODML: Building ODML index (2 superindexchunks).


MPlayer interrupted by signal 11 in module: demux_open
- MPlayer crashed by bad usage of CPU/FPU/RAM.
  Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
  disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
 [ This binary of MPlayer in Debian is currently compiled with
   '--enable-debug'; the debugging symbols are in the package
   'mplayer-dbgsym'.]


[toc] | [next] | [standalone]


#222003

FromNemeth Gyorgy <lists@friczy.net>
Date2020-04-27 18:00 +0200
Message-ID<A0ekN-8av-5@gated-at.bofh.it>
In reply to#221966
2020. 04. 26. 21:52 keltezéssel, Long Wind írta:
> i use stretch's mencoder to record a/v
> and use mplayer to play them, it works well
>
> yesterday i record a big file, about 4GB
> mplayer fails to play it,
> any idea or player that might help? Thanks!
>
> below is error msg by mplayer:
>
> zhou@debian:~$ mplayer /mnt/play/output/output192.avi
> ....

> Seek failed
> AVI: ODML: Building ODML index (2 superindexchunks).


Perhaps a filesystem problem? If it is a mounted external drive: what
kind of filesystem has it?

[toc] | [prev] | [next] | [standalone]


#222004

From<tomas@tuxteam.de>
Date2020-04-27 18:00 +0200
Message-ID<A0ekN-8av-3@gated-at.bofh.it>
In reply to#222003

[Multipart message — attachments visible in raw view] — view raw

On Mon, Apr 27, 2020 at 05:55:03PM +0200, Nemeth Gyorgy wrote:
> 2020. 04. 26. 21:52 keltezéssel, Long Wind írta:
> > i use stretch's mencoder to record a/v
> > and use mplayer to play them, it works well
> >
> > yesterday i record a big file, about 4GB
                                         ^^^
> > mplayer fails to play it,
> > any idea or player that might help? Thanks!
> >
> > below is error msg by mplayer:
> >
> > zhou@debian:~$ mplayer /mnt/play/output/output192.avi
> > ....
> 
> > Seek failed
> > AVI: ODML: Building ODML index (2 superindexchunks).
> 
> 
> Perhaps a filesystem problem? If it is a mounted external drive: what
> kind of filesystem has it?

Isn't 4G a file size limit for FAT based file systems?

Cheers
-- t

[toc] | [prev] | [next] | [standalone]


#222010

FromLong Wind <longwind2@yahoo.com>
Date2020-04-27 21:10 +0200
Message-ID<A0hiF-1H7-3@gated-at.bofh.it>
In reply to#222003

[Multipart message — attachments visible in raw view] — view raw

 zhou@debian:~$ ls /mnt/play/output/output192.avi -l
-rwxr-xr-x 1 zhou root 4294967295 Apr 26 17:59 /mnt/play/output/output192.avi

it's vfat, it's on same disk as debian, i think disk is ok
zhou@debian:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            1.5G     0  1.5G   0% /dev
tmpfs           304M  4.5M  299M   2% /run
/dev/sda2       9.8G  6.0G  3.4G  65% /
tmpfs           1.5G  4.8M  1.5G   1% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           1.5G     0  1.5G   0% /sys/fs/cgroup
/dev/sda3       269G  219G   50G  82% /mnt/play
/dev/sda1        20G  9.4G   11G  47% /mnt/work
tmpfs           304M  4.0K  304M   1% /run/user/1000

i think mencoder and mplayer are by same developers, 
but they still have compatible problem
    On Monday, April 27, 2020, 11:56:00 PM GMT+8, Nemeth Gyorgy <lists@friczy.net> wrote:  
 
 2020. 04. 26. 21:52 keltezéssel, Long Wind írta:
> i use stretch's mencoder to record a/v
> and use mplayer to play them, it works well
>
> yesterday i record a big file, about 4GB
> mplayer fails to play it,
> any idea or player that might help? Thanks!
>
> below is error msg by mplayer:
>
> zhou@debian:~$ mplayer /mnt/play/output/output192.avi
> ....

> Seek failed
> AVI: ODML: Building ODML index (2 superindexchunks).


Perhaps a filesystem problem? If it is a mounted external drive: what
kind of filesystem has it?

  

[toc] | [prev] | [next] | [standalone]


#222012

From<tomas@tuxteam.de>
Date2020-04-27 21:20 +0200
Message-ID<A0hsl-1Kg-1@gated-at.bofh.it>
In reply to#222010

[Multipart message — attachments visible in raw view] — view raw

On Mon, Apr 27, 2020 at 06:58:19PM +0000, Long Wind wrote:
>  zhou@debian:~$ ls /mnt/play/output/output192.avi -l
> -rwxr-xr-x 1 zhou root 4294967295 Apr 26 17:59 /mnt/play/output/output192.avi
> 
> it's vfat, it's on same disk as debian, i think disk is ok

If it's vfat, then there is your problem. A single file can't be
bigger than 4G on a vfat file system. Probably it got truncated
when copying.

Thank Microsoft for that :-/

Cheers
-- t

[toc] | [prev] | [next] | [standalone]


#222018

FromLong Wind <longwind2@yahoo.com>
Date2020-04-27 23:00 +0200
Message-ID<A0j18-2vt-5@gated-at.bofh.it>
In reply to#222012

[Multipart message — attachments visible in raw view] — view raw

 You are right. Thanks! 
but mencoder return normally, i didn't see any error msgmaybe i have to delete it.

    On Tuesday, April 28, 2020, 3:17:28 AM GMT+8, <tomas@tuxteam.de> wrote:  
 
 On Mon, Apr 27, 2020 at 06:58:19PM +0000, Long Wind wrote:
>  zhou@debian:~$ ls /mnt/play/output/output192.avi -l
> -rwxr-xr-x 1 zhou root 4294967295 Apr 26 17:59 /mnt/play/output/output192.avi
> 
> it's vfat, it's on same disk as debian, i think disk is ok

If it's vfat, then there is your problem. A single file can't be
bigger than 4G on a vfat file system. Probably it got truncated
when copying.

Thank Microsoft for that :-/

Cheers
-- t  

[toc] | [prev] | [next] | [standalone]


#222032

FromNemeth Gyorgy <lists@friczy.net>
Date2020-04-28 17:20 +0200
Message-ID<A0AbE-4X4-3@gated-at.bofh.it>
In reply to#222018
2020. 04. 27. 22:57 keltezéssel, Long Wind írta:
> You are right. Thanks!
> but mencoder return normally, i didn't see any error msg
> maybe i have to delete it.
>
> On Tuesday, April 28, 2020, 3:17:28 AM GMT+8, <tomas@tuxteam.de> wrote:
>
>
> On Mon, Apr 27, 2020 at 06:58:19PM +0000, Long Wind wrote:
> >  zhou@debian <mailto:zhou@debian>:~$ ls
> /mnt/play/output/output192.avi -l
> > -rwxr-xr-x 1 zhou root 4294967295 Apr 26 17:59
> /mnt/play/output/output192.avi
> >
> > it's vfat, it's on same disk as debian, i think disk is ok
>
> If it's vfat, then there is your problem. A single file can't be
> bigger than 4G on a vfat file system. Probably it got truncated
> when copying.
>
> Thank Microsoft for that :-/
>
> Cheers
>
> -- t

The problem is not mplayer nor mencoder but the vfat. Though the vfat
can store max 4GB file but the seek parameter on vfat is a signed
integer instead of an unsigned so the seek is not possible on larger
than 2GB files.

[toc] | [prev] | [next] | [standalone]


#222034

FromNicolas George <george@nsup.org>
Date2020-04-28 17:30 +0200
Message-ID<A0Alk-506-3@gated-at.bofh.it>
In reply to#222032

[Multipart message — attachments visible in raw view] — view raw

Nemeth Gyorgy (12020-04-28):
> The problem is not mplayer nor mencoder but the vfat. Though the vfat
> can store max 4GB file but the seek parameter on vfat is a signed
> integer instead of an unsigned so the seek is not possible on larger
> than 2GB files.

You are clearly confusing several issues. Seeking is not something that
resides in the filesystem, it is something that is done with it: there
have been limits on seeking, but they were not connected to the
filesystem, they were connected to the libc and the way the program was
compiled. These limits are still there on 32 bits systems if one is not
careful.

The AVI format, or more precisely the RIFF meta-format, has a limit at
4 Go, but it is possible that some standard Windows libraries have a
lower limit at 2 Go. There is an extension, ODML, to go beyond.

VFAT also has a limit on the size of the files, 4 Go, again possibly
with Windows enforcing a smaller size on the files it creates.

The size of the file causing the issue is exactly 0xFFFFFFFF, which
means it is obviously a problem caused by the size limit on VFAT. I
would not put it past mencoder to ignore write errors on the output
file.

But mplayer should not segfault on an input file, however malformed. The
AVI demuxer in mplayer is bogus, for other aspects too. I strongly
suggest not to use it, and use the libavformat demuxer instead: -demuxer
lavf, which can be automated by putting "demuxer=lavf" under
"[extension.avi]" in .mplayer/config.

While we are at it, for the last ~10 years, recommendations should say:

Do not use mencoder, unless you are specifically ripping an DVD (and
even in that case, try to nut use mencoder much): use ffmpeg instead.

Do not use the AVI format, unless it is the only format supported by
your target. If in doubt, use Matroska.

Regards,

-- 
  Nicolas George

[toc] | [prev] | [next] | [standalone]


#222063

FromLong Wind <longwind2@yahoo.com>
Date2020-04-29 00:00 +0200
Message-ID<A0GqK-9h-5@gated-at.bofh.it>
In reply to#222034

[Multipart message — attachments visible in raw view] — view raw

 Thank Nicolas George for expert advice!
but i don't have energy to learn new toolsand mencoder work fine most of time4G limit can be avoided by 
using several files (instead of single file) to record
i use avi because mplayer's manual use it as example
my policy is use less energy to get more work done

    On Tuesday, April 28, 2020, 11:25:11 PM GMT+8, Nicolas George <george@nsup.org> wrote:  
 
 Nemeth Gyorgy (12020-04-28):
> The problem is not mplayer nor mencoder but the vfat. Though the vfat
> can store max 4GB file but the seek parameter on vfat is a signed
> integer instead of an unsigned so the seek is not possible on larger
> than 2GB files.

You are clearly confusing several issues. Seeking is not something that
resides in the filesystem, it is something that is done with it: there
have been limits on seeking, but they were not connected to the
filesystem, they were connected to the libc and the way the program was
compiled. These limits are still there on 32 bits systems if one is not
careful.

The AVI format, or more precisely the RIFF meta-format, has a limit at
4 Go, but it is possible that some standard Windows libraries have a
lower limit at 2 Go. There is an extension, ODML, to go beyond.

VFAT also has a limit on the size of the files, 4 Go, again possibly
with Windows enforcing a smaller size on the files it creates.

The size of the file causing the issue is exactly 0xFFFFFFFF, which
means it is obviously a problem caused by the size limit on VFAT. I
would not put it past mencoder to ignore write errors on the output
file.

But mplayer should not segfault on an input file, however malformed. The
AVI demuxer in mplayer is bogus, for other aspects too. I strongly
suggest not to use it, and use the libavformat demuxer instead: -demuxer
lavf, which can be automated by putting "demuxer=lavf" under
"[extension.avi]" in .mplayer/config.

While we are at it, for the last ~10 years, recommendations should say:

Do not use mencoder, unless you are specifically ripping an DVD (and
even in that case, try to nut use mencoder much): use ffmpeg instead.

Do not use the AVI format, unless it is the only format supported by
your target. If in doubt, use Matroska.

Regards,

-- 
  Nicolas George  

[toc] | [prev] | [next] | [standalone]


#222071

FromCharles Curley <charlescurley@charlescurley.com>
Date2020-04-29 07:10 +0200
Message-ID<A0N8R-4Nf-1@gated-at.bofh.it>
In reply to#222063
On Tue, 28 Apr 2020 21:50:44 +0000 (UTC)
Long Wind <longwind2@yahoo.com> wrote:

> but i don't have energy to learn new toolsand mencoder work fine most
> of time4G limit can be avoided by using several files (instead of
> single file) to record

Or record to a partition that isn't VFAT.

If you have to use a USB device, create an EXT? (for Linux) or NTFS
(Windows) partition for large files.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]


#222105

FromLong Wind <longwind2@yahoo.com>
Date2020-04-29 19:20 +0200
Message-ID<A0Yxj-3zD-5@gated-at.bofh.it>
In reply to#222071

[Multipart message — attachments visible in raw view] — view raw

 i don't have free disk space for new partition4G limit isn't big problem for me 
actually small files are preferred for video editingi've deleted the big file


    On Wednesday, April 29, 2020, 1:09:38 PM GMT+8, Charles Curley <charlescurley@charlescurley.com> wrote:  
 
 On Tue, 28 Apr 2020 21:50:44 +0000 (UTC)
Long Wind <longwind2@yahoo.com> wrote:

> but i don't have energy to learn new toolsand mencoder work fine most
> of time4G limit can be avoided by using several files (instead of
> single file) to record

Or record to a partition that isn't VFAT.

If you have to use a USB device, create an EXT? (for Linux) or NTFS
(Windows) partition for large files.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

  

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web