Recherche avancée

Sur d’autres sites (11417)

• android chromecast mp4 by ffmpeg - shorter files play, some longer ones buffer but dont play

  20 octobre 2014, par Robert Rowntree

  Using Android SDK for CC, CCL, and ’styled receiver’ CC app.

  Video Files created by a heroku/ffmpeg bin that will play on any other client i tried (VLC ubuntu... ) and that will even play in chrome on a tab that’s being cast to chromecast will NOT PLAY natively on chromecast apps. They will appear as normal load in the UI of the app. CCL logs will show them buffering OK , but they never enter a play state from the buffering state. Debugging the receiver shows nothing unusual ( network tab, or Console ). They just buffer and dont play.

  If a slightly shorter version of the same , 2 ffmpeg input files is prepared and hosted, it seems to play fine in shorter versions under about 14 seconds long but will not play if a 16 second version is created.

  I used a number of chromecast apps including Allcast to test this. always got same result.

  2 dropbox mp4 links created with the ffmpeg cli here are below. A 14 second version of the output mp4 file plays fine on several Chromecast/android apps and a 16 second version fails.

  file len 14s

  file len 16s Wont play in CC apps

  ffprobe output on the files at :

  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'tst-nonplay-shorter_14s.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf54.29.105
  
    Duration: 00:00:14.07, start: 0.046440, bitrate: 311 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuvj420p, 1080x614 [SAR 1535:1539 DAR 100:57], 199 kb/s, 1 fps, 1 tbr, 16384 tbn, 2 tbc
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 22050 Hz, mono, s16, 110 kb/s
  
      Metadata:
  
        handler_name    : SoundHandler

  and the file 2 seconds longer that wont play

  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'tst-nonplay-shorter_16s.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf54.29.105
  
    Duration: 00:00:16.06, start: 0.046440, bitrate: 286 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuvj420p, 1080x614 [SAR 1535:1539 DAR 100:57], 174 kb/s, 1 fps, 1 tbr, 16384 tbn, 2 tbc
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 22050 Hz, mono, s16, 110 kb/s
  
      Metadata:
  
        handler_name    : SoundHandler

  Used ’qtfaststart’ and checked for MOOV ATOM issues and dont think that’s relevant.

  I think i can limit recordings in my app to 14 seconds and avoid problems that way, but I would like to understand what is up with the chromecast GETS on MP4’s generated by ffmpeg.

• How to add Qt to an existing C program and compile ?

  26 juin 2015, par El Sampsa

  I have a small Qt program I have compiled with qmake and make. When I launch make, I get the following commands for compilation :

  g++ -c -m64 -pipe -O2 -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I/usr/lib/x86_64-linux-gnu -I/usr/include/SDL -I. -o simpleqt.o simpleqt.cpp

  (.. lets call that (**)) and

  g++ -m64 -Wl,-O1 -o qt simpleqt.o -L/usr/lib/x86_64-linux-gnu -lSDL -lX11 -lQtGui -lQtCore -lpthread

  .. and the program is compiled without problems.

  On the other hand, I have the ffmpeg library which has the "ffplay" program. I want to put some Qt things into ffplay. In the ffmpeg config files I tell to the make process (using "common.mak") that it should be verbose and when issuing "make ffplay", it gives me the following monster :

  gcc -I. -I./ -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DZLIB_CONST -I/home/sampsa/ffmpeg/build/include -std=c99 -fomit-frame-pointer -pthread -I/usr/include/freetype2 -I/usr/include/fribidi -I/usr/include/freetype2 -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -g -Wdeclaration-after-statement -Wall -Wdisabled-optimization -Wpointer-arith -Wredundant-decls -Wwrite-strings -Wtype-limits -Wundef -Wmissing-prototypes -Wno-pointer-to-int-cast -Wstrict-prototypes -Wempty-body -Wno-parentheses -Wno-switch -Wno-format-zero-length -Wno-pointer-sign -O3 -fno-math-errno -fno-signed-zeros -fno-tree-vectorize -Werror=format-security -Werror=implicit-function-declaration -Werror=missing-prototypes -Werror=return-type -Werror=vla -Wformat -Wno-maybe-uninitialized -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -MMD -MF ffplay.d -MT ffplay.o -c -o ffplay.o ffplay.c

  (lets call that monster (++)).

  So far, so good, I have two commands, one (**) for compiling Qt programs and another one (++) for another project (in this case, ffmpeg’s ffplay)

  How do I combine these two ?

  I have tried merging the flags in (**) into command (++). It compiles OK, but the moment I am adding

  #include <qtgui> 
  
  </qtgui>

  into "ffplay.c", all hell breaks loose and the compiler tells me (among many other things) :

  In file included from /usr/include/qt4/QtCore/qobjectdefs.h:45:0,
  from /usr/include/qt4/QtCore/qobject.h:47,
  from /usr/include/qt4/QtCore/qabstracteventdispatcher.h:45,
  from /usr/include/qt4/QtCore/QtCore:3,
  from /usr/include/qt4/QtGui/QtGui:3,
  from ffplay2.c:61 :
  /usr/include/qt4/QtCore/qnamespace.h:51:1 : warning : return type defaults to ‘int’ [enabled by default]
  QT_MODULE(Core)
  ^
  /usr/include/qt4/QtCore/qnamespace.h:51:1 : warning : function declaration isn’t a prototype [-Wstrict-prototypes]
  /usr/include/qt4/QtCore/qnamespace.h : In function ‘QT_MODULE’ :
  /usr/include/qt4/QtCore/qnamespace.h:54:1 : error : unknown type name ‘namespace’
  namespace
  ^
  ...
  ...

  If I combine flags in (**) to (++) and change the compiler from "gcc" to "g++", I get all kinds of errors, this time related to the "ffplay.c" source code.

  What is going on ?

• Compile ffmpeg with x264 shows : ERROR : libx264 not found

  6 mai 2019, par NKam

  Trying to install ffmpeg from source with libx264 package. When I compile ffmpeg can’t find x264 because it is not installed.
  I followed ffmpeg installation guide.

  I tried to install and compile ffmpeg locally and found out in folder ffmpeg_build/include I don’t have x264 files installed.

  To compile libx264 I used :

  cd /ffmpeg_sources &&

  git -C x264 pull 2> /dev/null || git clone —depth 1 https://code.videolan.org/videolan/x264.git &&

  cd x264 &&

  PATH="$HOME/bin :$PATH"

  PKG_CONFIG_PATH="$HOME/ffmpeg_build/lib/pkgconfig" ./configure —prefix="$HOME/ffmpeg_build" —bindir="$HOME/bin" —enable-static —enable-pic &&

  PATH="$HOME/bin :$PATH" make &&

  make install

  I changed url to https://code.videolan.org/videolan/x264.git, because this url https://git.videolan.org/git/x264 from guide not working

  Here how config.log’s last lines look like

  test_cflags -Wmaybe-uninitialized
  
  test_cc -Wmaybe-uninitialized
  
  BEGIN /tmp/ffconf.1LD1vklR/test.c
  
      1   int x;
  
  END /tmp/ffconf.1LD1vklR/test.c
  
  gcc -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC -I/home/nurs/ffmpeg_build/include -std=c11 -fomit-frame-pointer -fPIC -pthread -I/home/nurs/ffmpeg_build/include -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/fribidi -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/opus -I/usr/include/opus -I/usr/include/alsa -g -Wdeclaration-after-statement -Wall -Wdisabled-optimization -Wpointer-arith -Wredundant-decls -Wwrite-strings -Wtype-limits -Wundef -Wmissing-prototypes -Wno-pointer-to-int-cast -Wstrict-prototypes -Wempty-body -Wno-parentheses -Wno-switch -Wno-format-zero-length -Wno-pointer-sign -Wno-unused-const-variable -Wno-char-subscripts -O3 -fno-math-errno -fno-signed-zeros -fno-tree-vectorize -Werror=format-security -Werror=implicit-function-declaration -Werror=missing-prototypes -Werror=return-type -Werror=vla -Wformat -fdiagnostics-color=auto -Wmaybe-uninitialized -c -o /tmp/ffconf.1LD1vklR/test.o /tmp/ffconf.1LD1vklR/test.c

  I want to know what I missed. I want ffmpeg to find x264, if it is not installed how can I find way to install.