On 08/21/2018 09:59 AM, stan wrote: The video is from my father-in-law's iPhone (I do not know what version) of my 14yr old nephew playing his guitar at an old folk's home. Installing ffmpeg did not help out parole.  It is still reporting to install the decoder.  But I had mplayer and ran with that and that worked.  Here is the interesting messages from the terminal window: MPlayer SVN-r38113-8 (C) 2000-2018 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 /home/rgm/Videos/BenyominMoshe/IMG_0723.MOV. libavformat version 58.12.100 (external) libavformat file format detected. [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f3cf5431660]Protocol name not provided, cannot determine if input is local or a network protocol, buffers and access patterns cannot be configured optimally without knowing the protocol [lavf] stream 0: video (h264), -vid 0 [lavf] stream 1: audio (aac), -aid 0, -alang und VIDEO:  [H264]  1920x1080  24bpp  29.970 fps  11268.2 kbps (1375.5 kbyte/s) Failed to open VDPAU backend libvdpau_r600.so: cannot open shared object file: No such file or directory [vdpau] Error when calling vdp_device_create_x11: 1 ========================================================================== Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family libavcodec version 58.18.100 (external) Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264) ========================================================================== Clip info:  major_brand: qt  minor_version: 0  compatible_brands: qt  creation_time: 2018-07-05T19:47:28.000000Z  com.apple.quicktime.location.ISO6709: +42.5123-083.2824+217.055/  com.apple.quicktime.make: Apple  com.apple.quicktime.model: iPhone 5s  com.apple.quicktime.software: 11.4  com.apple.quicktime.creationdate: 2018-07-05T15:47:28-0400 Load subtitles in /home/rgm/Videos/BenyominMoshe/ ========================================================================== Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders AUDIO: 44100 Hz, 1 ch, floatle, 62.6 kbit/4.44% (ratio: 7831->176400) Selected audio codec: [ffaac] afm: ffmpeg (FFmpeg AAC (MPEG-2/MPEG-4 Audio)) ========================================================================== AO: [pulse] 44100Hz 1ch floatle (4 bytes per sample) Starting playback... Movie-Aspect is undefined - no prescaling applied. VO: [xv] 1920x1080 => 1920x1080 Planar YV12 [ASPECT] Warning: No suitable new res found! [ASPECT] Warning: No suitable new res found! A:   6.0 V:   1.7 A-V:  4.324 ct:  0.003   0/  0 294% 44% 52.6% 50 0            ************************************************            **** Your system is too SLOW to play this!  ****            ************************************************ Possible reasons, problems, workarounds: - Most common: broken/buggy _audio_ driver   - Try -ao sdl or use the OSS emulation of ALSA.   - Experiment with different values for -autosync, 30 is a good start. - Slow video output   - Try a different -vo driver (-vo help for a list) or try -framedrop! - Slow CPU   - Don't try to play a big DVD/DivX on a slow CPU! Try some of the lavdopts,     e.g. -vfm ffmpeg -lavdopts lowres=1:fast:skiploopfilter=all. - Broken file   - Try various combinations of -nobps -ni -forceidx -mc 0. - Slow media (NFS/SMB mounts, DVD, VCD etc)   - Try -cache 8192. - Are you using -cache to play a non-interleaved AVI file?   - Try -nocache. Read DOCS/HTML/en/video.html for tuning/speedup tips. If none of this helps you, read DOCS/HTML/en/bugreports.html. A:  30.5 V:   9.4 A-V: 21.032 ct:  0.001   0/  0 265% 23% 42.5% 283 0 Exiting... (Quit)

On Fri, 2018-08-24 at 09:20 +1000, Cameron Simpson wrote: As far as I was aware (with over 2 decades of working in video production), there never was any predetermined definition of what data a .mov file contained. It was a simply some kind of movie file container, and over many years the .mov container has carried on existing with ever-changing types of content. Likewise with .avi files on Windows: All manner of CODECs could have been used with its contents. And there's quite a few other container formats. The filename suffix gives little clue about the content. It's been an utter disaster for us, as you get asked if you can handle a .mov file, only to have to say that we didn't know until we tried. Or the opposite, of someone saying they wanted a .mov file, and you'd ask them for more information about content, and they couldn't answer because they have no idea. Likewise with avi, mpg, mpeg, etc. You could end up going through a seriously annoying run of test files trying to find compatible formats.