Recherche avancée

Sur d’autres sites (9982)

• Detect if "faststart" has been applied to video

  26 juin 2024, par Will Ashworth

  When running "qt-faststart" on an MP4, you're essentially taking the meta data from the back and placing it at the front of the file. In my case, so Flash can properly start playing the video before it's fully done loading.

  



  I have a large number of videos that I'm running through a shell script to encode overnight. When I upload, however, I won't necessarily know in my final folder of videos (on the server) have "qt-faststart" run on it.

  



  My goal is to find the straggler videos and run qt-faststart on them manually, but I'll need a way to compile a list. Is there any way to check for this meta data information with PHP or something ? Wondering how I can tell if a video has already had qt-faststart run on it or not.

  


• How to avoid the "text relocation" error by ffmpeg library on Android x86

  16 octobre 2017, par Tank2005

  My environment is Qt 5.9 for Android on Windows 10 64bit. NDK is r10e and SDK Level is 16(Those sdks are recommended version by Qt development team).

  I built a ffmpeg 3.4 source code as .so files on Ubuntu 16.04.3 LTS. Those library has no error on ARM architecture Android. But, on x86 Emulator, "Text realocations" alart is shown like this.

  

  I rewrite configure with "disable-asm, disable-yasm" referd from this site’s old posts.

  This hereby removed some errors. But only one library has a problem.
  

  I also tried the method of deleting "strtod.o", But it seems no effect. My current build configure is that. Does anyone know a better way ?

  #!/bin/bash
  
  NDK=/home/my/data/ndk
  
  SYSROOT=$NDK/platforms/android-14/arch-x86/
  
  TOOLCHAIN=$NDK/linux-x86-48
  
  CPU=x86
  
  PREFIX=$(pwd)/android/x86
  
  PATH=$TOOLCHAIN/bin:$PATH
  
  
  
  function build_one
  
  {
  
  ./configure \
  
      --cc="$TOOLCHAIN/bin/i686-linux-android-gcc-4.8" \
  
      --enable-cross-compile \
  
      --target-os=linux \
  
      --arch=x86 \
  
      --prefix=$PREFIX \
  
      --enable-shared \
  
      --disable-static \
  
      --disable-avdevice \
  
      --disable-doc \
  
      --disable-encoders \
  
      --disable-decoders \
  
      --enable-decoder=h264 \
  
      --enable-decoder=aac \
  
      --disable-protocols \
  
      --disable-demuxers \
  
      --disable-muxers \
  
      --disable-filters \
  
      --disable-network \
  
      --disable-ffplay \
  
      --disable-ffmpeg \
  
      --disable-ffprobe \
  
      --disable-ffserver \
  
      --enable-parsers \
  
      --cross-prefix=i686-linux-android- \
  
      --enable-cross-compile \
  
      --target-os=linux \
  
      --arch=x86 \
  
      --disable-doc \
  
      --sysroot=$SYSROOT \
  
      --disable-x86asm -disable-yasm --enable-pic \
  
      --extra-cflags="-std=c99 -O3 -Wall -fpic -pipe -DANDROID -DNDEBUG -march=atom -msse3 -ffast-math -mfpmath=sse" \
  
      --extra-ldflags='-lm -lz -Wl,--no-undefined -Wl,-z,noexecstack' \
  
      $ADDITIONAL_CONFIGURE_FLAG
  
  make clean
  
  rm -f $(pwd)/compat/strtod.o
  
  rm -f $(pwd)/compat/strtod.d
  
  make 
  
  make install
  
  }
  
  build_one

• h264 inside AVI, MP4 and "Raw" h264 streams. Different format of NAL units (or ffmpeg bug)

  24 octobre 2019, par bukkojot

  TL ;DR : I want to read raw h264 streams from AVI/MP4 files, even broken/incomplete.

  Almost every document about h264 tells me that it consists of NAL packets. Okay. Almost everywhere told to me that the packet should start with a signature like 00 00 01 or 00 00 00 01. For example, https://stackoverflow.com/a/18638298/8167678, https://stackoverflow.com/a/17625537/8167678

  The format of H.264 is that it’s made up of NAL Units, each starting
  with a start prefix of three bytes with the values 0x00, 0x00, 0x01
  and each unit has a different type depending on the value of the 4th
  byte right after these 3 starting bytes. One NAL Unit IS NOT one frame
  in the video, each frame is made up of a number of NAL Units.

  Okay.

  I downloaded random_youtube_video.mp4 and strip out one frame from it :

  ffmpeg -ss 10 -i random_youtube_video.mp4 -frames 1 -c copy pic.avi

  And got :
  
  Red part - this is part of AVI container, other - actual data.
  As you can see, here I have 00 00 24 A9 instead of 00 00 00 01

  This AVI file plays perfectly

  I do same for mp4 container :
  

  As you can see, here exact same bytes.
  This MP4 file plays perfectly

  I try to strip out raw data :
  ffmpeg -i pic.avi -c copy pic.h264
  

  This file can’t play in VLC or even ffmpeg, which produced this file, can’t parse it :
  

  I downloaded mp4 stream analyzer and got :
  

  MP4Box tells me :

   Cannot find H264 start code
  
   Error importing pic.h264: BitStream Not Compliant

  It very hard to learn internals of h264, when nothing works.

  So, I have questions :

  1. What actual data inside mp4 ?
  2. What I must read to decode that data (I mean different annex-es)
  3. How to read stream and get decoded image (even with ffmpeg) from this "broken" raw stream ?

  UPDATE :

  It seems bug in ffmpeg :

  When I do double conversion :

           ffmpeg -ss 10 -i random_youtube_video.mp4 -frames 1 -c copy pic.mp4
  
           ffmpeg pic.mp4 -c copy pic.h264

  

  But when I convert file directly :

  ffmpeg -ss 10 -i random_youtube_video.mp4 -frames 1 -c copy pic.h264
  

  I have NALs signatures and one extra NAL unit. Other bytes are same (selected).

  This is bug ?

  UPDATE

  Not, this is not bug, U must use option -bsf h264_mp4toannexb to save stream as "Annex B" format (with prefixes)