Recherche avancée

Sur d’autres sites (14500)

• Video encoded with ffmpeg not playing in Chrome

  15 décembre 2014, par Meep3D

  I’ve been trying just about every single permutation of options on ffmpeg to try to get a transcoded video to display on Chrome - OSX 39.0.2171.71 (64-bit) - so far nothing has worked.

  The settings I am currently using look like :

  /usr/local/Cellar/ffmpeg/2.4.3/bin/ffmpeg -i source.m4v -vcodec libx264 -pix_fmt yuv420p -profile:v baseline -level 3.0 -preset slower -crf 23 -vf scale=640:360 target.mp4

  but I’ve tried various options from various other answers with no success.

  The video-js demo video works fine, so it must be possible somehow. Here’s a dump of the encoded video :

  *** General Parameters ***
  
  - Name:  test-1 (2).mp4 
  
  - Container:  MP4 - QuickTime 
  
  - Size:  3.45 MB 
  
  - Duration:  32s 299ms 
  
  - Bitrate:  856 Kbps 
  
  
  
  *** Video Track Parameters ***
  
  - Format:  H.264/MPEG-4 AVC 
  
  - Bitrate:  Max.: --- / Average: 721 Kbps / Min.: --- 
  
  - Frame rate (fps):  Max.: --- / Average: 30.000 / Min.: --- 
  
  - Encoding profile:  Baseline@L3.0 
  
  - Image size:  640*360 
  
  - Pixel Aspect Ratio:  Undefined 
  
  - Display Aspect Ratio:  16:9 
  
  - Interlacing:  Progressive 
  
  
  
  *** First Audio Track Parameters ***
  
  - Format:  AAC - MPEG-4 audio 
  
  - Bitrate:  128 Kbps 
  
  - Resolution:  Undefined 
  
  - Rate:  44.1 KHz 
  
  - Channel(s):  2 (stereo) 
  
  - Position:  Front: L R 

• Revision 9c061ef506 : Properly validate data size With "show_existing_frame" frames : Minimum data siz

  5 janvier 2015, par Yaowu Xu

  Changed Paths :
   Modify /vp9/vp9_dx_iface.c

  
  
  Properly validate data size

  With "show_existing_frame" frames :
  Minimum data size for profile 0 and 1 is 1 byte (8bits)
  Minimum data size for profile 2 and 3 is 2 bytes (9bits)

  Otherwise :
  Minimum data size is 8 bytes.

  This resolves the VP9 failure in fuzzing test build #56.

  Change-Id : I146d9d37688f535dd68d24aacc76d464ccffdf04

• ffmpeg options that work with Chrome

  21 avril 2015, par James

  I am trying to find the magic options that make mp4 work in Chrome. I think my videos were working, but don’t seem to any more after Chrome updated.

  Chrome, Version 41.0.2272.101 (Windows)

  I tried some other machines and found some of the videos worked on older versions, and my Mac seems to still work on the latest Chrome.

  I am using the ffmpeg options to convert from png series,

  ffmpeg -framerate 10 -i dance%02d.png  -r 10 -pix_fmt yuv420p dance.mp4

  Some videos work, some don’t, some work some of the time, or stop half way through.

  I tried various other options like,

  ffmpeg -start_number 16 -framerate 10 -i dance%02d.png -r 10 -an -s hd720 \
  
  -vcodec libx264 -pix_fmt yuv420p -preset slow -profile:v baseline \
  
  -movflags faststart -y dance.mp4

  but this just seemed to make things worse.

  here is one of the videos,
  http://www.botlibre.com/media/a786625.mp4

  and another one,
  http://www.botlibre.com/media/a812450.mp4

  Firefox seems to work no problem, on any version, grey background though.
  IE works fine, white background.
  Safari works, grey background.

  Another thing, they videos used to have white background on older Chrome version, but now are grey, except on Mac still white.

  and one more thing. Webm format works, but anyone know the option to remove transparency ? I’m using,

  ffmpeg -i dance%02d.png  -r 10 -c:v libvpx -crf 10 -b:v 512k -c:a libvorbis dance.webm

  just want a solid white background.