Recherche avancée

Sur d’autres sites (8098)

• Invalid data found when processing input on ffmpeg m4s to mp4 transfer

  1er mars 2020, par keith scott

  The result of the power shell window

  I saw a post on here about converting m4s to mp4 and I have followed the steps of concatenating all the files into another m4s file that I called all.m4s and when I use the command ffmpeg -i allm4s.m4s -c copy video.mp4. I made the combined m4s file by coding an exe to add all the m4s files that have the word video in them to the m4s file. Here is the source code written in c# if you compile the code then that is the code I have used to make the m4s

  using System;
  
  using System.Collections.Generic;
  
  using System.Linq;
  
  using System.Text;
  
  using System.Threading.Tasks;
  
  using System.IO;
  
  
  
  namespace files
  
  {
  
      class Program
  
      {
  
          static void Main(string[] args)
  
          {
  
              string dir = Directory.GetCurrentDirectory();
  
              string[] info = Directory.GetFiles(dir);
  
              Console.WriteLine(dir + "\\allm4s.m4s");
  
              Console.ReadKey();
  
              foreach (string name in info)
  
              {
  
                  if (Path.GetFileName(name).Contains(".m4s") && Path.GetFileName(name).Contains("video"))
  
                  {
  
                      using (Stream srcStream = File.OpenRead(name))
  
                      {
  
                          using (Stream destStream = File.OpenWrite(dir+"\\allm4s.m4s"))
  
                          {
  
                              srcStream.CopyTo(destStream);
  
                              Console.WriteLine(destStream+name);
  
                          }
  
                      }
  
                  }
  
              }
  
              Console.ReadKey();
  
          }
  
      }
  
  }

  I think if there is to be an issue it is to do with this allm4s.m4s file as the file size is about 1.5mb even though each segment m4s is about 750kb each and there are quite a lot.If anyone has a way of adding concatenating lots of files together through a program/application that would be useful.

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

  20 octobre 2022, par 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 décembre 2022, par 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