Recherche avancée

Sur d’autres sites (14134)

• ffmpeg and hardcoding subtitles

  8 avril 2015, par Adin Gill

  I have a command like so

  ffmpeg -i "F:\Filebotted\Rail Wars\Season 1\Rail Wars.S01E07(7).You Look Good in That. 1080p.mkv" -map 0:0 -map 0:1 -b:v 750k -b:a 128k -c:v libx264 -c:a mp3 -ac 2 -filter_complex "subtitles=F:\Filebotted\Rail Wars\Season 1\Rail Wars.S01E07(7).You Look Good in That. 1080p.mkv,scale=-1:360" "C:\Users\Adin\Desktop\Testy mc test\Rail Wars.S01E07(7).You Look Good in That. 1080p.mkv"

  Yes it is long but unfortunatly ffmpeg chucks a hissy fit and spits out the following

  [subtitles @ 00000000050ce7c0] Unable to parse option value "FilebottedRail Wars
  
  Season 1Rail Wars.S01E07(7).You Look Good in That. 1080p.mkv" as image size
  
      Last message repeated 1 times
  
  [subtitles @ 00000000050ce7c0] Error setting option original_size to value Fileb
  
  ottedRail WarsSeason 1Rail Wars.S01E07(7).You Look Good in That. 1080p.mkv.
  
  [Parsed_subtitles_0 @ 0000000002c714c0] Error applying options to the filter.
  
  [AVFilterGraph @ 0000000002c5c540] Error initializing filter 'subtitles' with ar
  
  gs 'F:FilebottedRail WarsSeason 1Rail Wars.S01E07(7).You Look Good in That. 1080
  
  p.mkv'
  
  Error configuring filters.

  It works just fine when the file is in the same folder as ffmpeg (I found out that it doesn’t like ’ or - in the filename, but I just spent an hour trying to work out the issue with no avail.

  Any help will be appreciated :)

• Gstreamer + Logitech C920 h264 video lacks timing information, plus mp4mux not working

  30 mars 2015, par user1048388

  I’m currently getting the h264 encoded video and the audio from the C920 via gstreamer 1.2.4 :

  gst-launch-1.0 v4l2src device=/dev/video0 do_timestamp=true ! video/x-h264,width=1920,height=1080,framerate=30/1 ! h264parse ! muxout. pulsesrc device="alsa_input.usb-046d_HD_Pro_Webcam_C920_5530335F-02-C920.analog-stereo" ! queue ! audioconvert ! voaacenc bitrate=65536 ! muxout. matroskamux name=muxout streamable=true ! queue ! filesink location=/home/[omitted]/test.mp4 

  The main problem is that the resulting video lacks timing information. By that I mean seek is not possible and the duration is unknown. Adding do_timestamp=true changes nothing.
  Simply copying the file in ffmpeg/libav shows several instances of :

  Non-monotonous DTS in output stream 0:0 ; previous : 926, current : 807 ; changing to 927. This may result in incorrect timestamps in the output file.

  After this short process (seconds on an hour long file), the timing information suddenly works for the entire video.

  What do I need to do to make this happen during the gst-launch pipeline ?

  There are some other problems which may or may not be related :
  I am using matroskamux despite wanting a mp4 container because mp4mux simply does not work in the given launch command. I receive

  ERROR : Pipeline doesn’t want to pause.
  ERROR : from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0 : Cannot identify device ’/dev/video0’.
  Additional debug info :
  v4l2_calls.c(568) : gst_v4l2_open () : /GstPipeline:pipeline0/GstV4l2Src:v4l2src0 :
  system error : No such file or directory

  when replacing matroskamux with mp4mux.

  I am clueless as to why this happens. Any help would be appreciated.

• ffmpeg conversion dimension error

  7 mars 2015, par georgechalhoub

  I am writing a video conversion script using ffmpeg, it has been completed to full. Ideally, my video conversion script should output the video to many formats (similar to YouTube) :

  • 140p : 256 x 144
  • 240p : 426 x 240
  • 360p : 640  x 360
  • 480p : 854  x 480
  • 720p : 1280 x 720
  • 1080p : 1920x 1080

  The problem I am facing is that if a user uploads a 480p (854 x 480) video or close to 480p (854 x 480) the script will convert to all formats (1080p and 720p) which would seem like a waste of bandwidth and disk space in this case.

  The problem isn’t as easy as it seems. If a user uploads a 500 x 300 video I don’t want it to get converted to a 240p, there has to be some estimations.

  Is there some command in ffmpeg which does any help dealing with such type of problems ?