Advanced search

On other websites (4470)

• Can I use a text file's content to create a filtered list for ffmpeg?

  20 October 2022, by Angel Lopez Jr

  I am attempting to make a CMD script that will

  


  

  1. Create a text file that lists file names followed by video codec (using ffprobe)

  


  2. Create a new text from the list so that any file with x265 codec is removed from the list (and formated as
file "*filepath*"

  


  3. Run ffmpeg on the edited list to transcode remaining files to x265.

  


  


  I have a script that does #1

  


  for /R %%f IN (*.mkv,*.avi,*.mp4,*.m2ts,*.mts,*.rm,*.m4v) do echo "%%f" >>Probe.txt & ffprobe -v error -hide_banner -of default=noprint_wrappers=0 -print_format flat  -select_streams v:0 -show_entries stream=codec_name "%%f" >>Probe.txt & echo.  >>Probe.txt


  


  which outputs

  


  


  "filepath"
  
streams.stream.0.codec_name="codec"

  


  "filepath"
  
streams.stream.0.codec_name="codec"

  


  


  and I have a script that will do #3

  


  for /R %%f IN (*.mkv,*.avi,*.mp4,*.m2ts,*.mts,*.rm,*.m4v) do ffmpeg -hide_banner -hwaccel_output_format qsv -i "%%f" -c:v libx265 -c:a ac3 -x265-params crf=25 "%%f.mkv"


  


  I am not sure if #2 is even possible though.

  


  End result of task 2 should be that in probe.txt, any line that has a
streams.stream.0.codec_name value of anything besides hevc will have the line immediately above it written to a new txt file with the word file in front.

  


  final goal is getting all three tasks to run under one batch file (each task running sequentially)

  


  Is there any help on what I am missing to be able to unify these and get #2 to happen

  


• lavu/pixdesc: handle xv30be in av_[read|write]_image_line

  4 December 2022, by Philip Langdale

  lavu/pixdesc: handle xv30be in av_read_image_line
  xv30be is an obnoxious format that I shouldn't have included in the
  
  first place. xv30 packs 3 10bit channels into 32bits and while our
  
  byte-oriented logic can handle Little Endian correctly, it cannot
  
  handle Big Endian. To avoid that, I marked xv30be as a bitstream
  
  format, but while that didn't produce FATE errors, it turns out that
  
  the existing read/write code silently produces incorrect results, which
  
  can be revealed via ubsan.
  In all likelyhood, the correct fix here is to remove the format. As
  
  this format is only used by Intel vaapi, it's only going to show up
  
  in LE form, so we could just drop the BE version. But I don't want to
  
  deal with creating a hole in the pixfmt list and all the weirdness that
  
  comes from that. Instead, I decided to write the correct read/write
  
  code for it.
  And that code isn't too bad, as long as it's specialised for this
  
  format, as the channels are all bit-aligned inside a 32bit word.
  

  • [DH] libavutil/pixdesc.c

• swresample/resample: do not increase phase_count on exact_rational

  17 June 2016, by Muhammad Faiz

  swresample/resample: do not increase phase_count on exact_rational
  high phase_count is only useful when dst_incr_mod is non zero
  
  in other word, it is only useful on soft compensation
  on init, it will build filter with low phase_count
  
  but when soft compensation is enabled, rebuild filter
  
  with high phase_count
  this approach saves lots of memory
  Reviewed-by: Michael Niedermayer <michael@niedermayer.cc>
  
  Signed-off-by: Muhammad Faiz <mfcc64@gmail.com>
  

  • [DH] libswresample/resample.c
  • [DH] libswresample/resample.h