Recherche avancée

Sur d’autres sites (3488)

• Android : mp4 file plays when downloaded but when choosing "Video" player gets "Cannot play video"

  14 janvier 2014, par gview

  I've converted the video to an mp4 with ffmpeg using the h264 codec and AAC, and used the baseline profile.

  Videos are 540x360x250kbps

  I then ran qt-faststart on the file to move the atoms into the right order.

  I've stuck the file up on a wiki we use and created a link to it.

  My test phone is a Samsung Galaxy S3.

  When I browse to the page that has links to the mp4's on it, and I click on them, I get a popup window with 2 options : Internet and Video.

  If I download the videos using the "Internet" option, I can play them on the phone without issue.

  I've done other encodings with the main profile as well, and these also play fine. I thought that a powerful phone like the s3 would be able to handle the more advanced compression schemes available in h264, however I've also browsed the Android docs in regards to supported video formats, and it seems to state that only the "baseline" compression profile is supported.

  Regardless, what doesn't work is trying to use the "Video" option which I assume tries to stream the video.

  For the wiki in question, clicking on the link reveals that the content-type and content-length headers are being set :

  Content-Length  6175996
  
  Content-Type    video/mp4;charset=UTF-8

  Clicking on the link with a browser invokes a player (Quicktime in most cases) that can play the mp4's.

  Is there more to having the file HTTP streamable beyond making a link to it ? Why won't my Android 4 play these files ?

  UPDATE :
  I decided to make a quick HTML5 page using the video tag, and the videos do play on both my Galaxy S3 and the latest IOS.

• Can you "stream" images to ffmpeg to construct a video, instead of saving them to disk ?

  8 juillet 2016, par Brandon

  My work recently involves programmatically making videos. In python, the typical workflow looks something like this :

  import subprocess, Image, ImageDraw
  
  
  
  for i in range(frames_per_second * video_duration_seconds):
  
      img = createFrame(i)
  
      img.save("%07d.png" % i)
  
  
  
  subprocess.call(["ffmpeg","-y","-r",str(frames_per_second),"-i", "%07d.png","-vcodec","mpeg4", "-qscale","5", "-r", str(frames_per_second), "video.avi"])

  This workflow creates an image for each frame in the video and saves it to disk. After all images have been saved, ffmpeg is called to construct a video from all of the images.

  Saving the images to disk (not the creation of the images in memory) consumes the majority of the cycles here, and does not appear to be necessary. Is there some way to perform the same function, but without saving the images to disk ? So, ffmpeg would be called and the images would be constructed and fed to ffmpeg immediately after being constructed.

• NDK r8c warning for asm objects regarding "Cortex-A8 erratum" - should I be worried ?

  7 décembre 2012, par Alex Cohn

  Question : What is the meaning of this warning ? If there are no real-life consequences, I can live with it for a while... But I am concerned with what will happen if our program gets loaded on one of the faulty chips.

  Background : With NDK r8c, linking of X264 encoder issues warnings :

  cannot scan executable section 1 of libx264.a(dct-a.o) for Cortex-A8 erratum because it has no mapping symbols

  ... same warning for all assembly files in libx264.

  libx264.a itself was cross-compiled on the same machine with the same 4.6 toolchain taken from NDK.

  Here are the instructions to easily reproduce the problem (Ubuntu or MacOS) :

  1. Download x264-snapshot-20121203-2245 from ftp://ftp.videolan.org/pub/x264/snapshots/last_x264.tar.bz2

  2. Run ./configure --enable-pic --enable-strip --enable-static --cross-prefix=~/android-ndk-r8c/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86/bin/arm-linux-androideabi- --sysroot=~/android-ndk-r8c/platforms/android-14/arch-arm --host=arm-linux

  3. Run ~/android-ndk-r8c/prebuilt/linux-x86/bin/make

  It will build the static library, and after that display the Cortex-A8 warning while linking the x265 executable. I am not worried about the compiler warnings, because building libx264.a is done offline, it is not part of our official daily build.

  I have reported this as http://code.google.com/p/android/issues/detail?id=40794.

  I tried to add the mapping symbols manually to dct-a.S following the ARM.com instructions, but this had no effect.