Recherche avancée

Sur d’autres sites (9132)

• c# NReco.VideoConverter Ubuntu 16.04

  19 septembre 2018, par Neyt Chi

  I’m trying to use the functionality of the NReso library. VideoConverter. The program is launched from Ubuntu OS 16.04 in the MonoDevelopment environment. The operating system is 64 charging. I installed the application FFMpeg and it works fine.
  And I have a problem that does not make a lot of sense. I’m trying to use code NReso.VideoConveter from the site official site https://www.nrecosite.com/video_converter_net.aspx :

  try
  
  {
  
       string [] paths = {"1.mp4",
  
       "1.mp4",
  
       "1.mp4"};
  
       ConcatSettings concatSettings = new ConcatSettings ();
  
       concatSettings.ConcatAudioStream = false;
  
       concatSettings.ConcatVideoStream = true;
  
       FFMpegConverter ffMpegConvert = new FFMpegConverter ();
  
       Console.WriteLine ("Converting ... \ r \ n");
  
       ffMpegConvert.ConcatMedia (paths, "3.mp4", Format.mp4, concatSettings);
  
       Console.WriteLine ("Complete!");
  
  }
  
  catch (Exception e)
  
  {
  
  Console.WriteLine (e.Message);
  
  }

  The code produces an error of type

  "ApplicationName = ’/ home / neytchi / Projects / testVE / testVE /
  bin / Debug / ffmpeg.exe’, CommandLine = ’- y -loglevel info -i
  "1.mp4" -i "1.mp4" -i "1. mp4 "-f mp4 -filter_complex" concat = n = 3 :
  v = 1 [v] "-map" [v] "" 3.mp4 "’, CurrentDirectory =’ / home / neytchi
  / Projects / testVE / testVE / bin / Debug ’, Native error = Access
  denied" or so "Unhandled Exception : Systems
  .ComponentModel.Win32Exception"

  I can not understand the cause of problem, but I’m assuming that the library starts the process as 32-bit, when everything else is 64-bit.
  Any ideas ? Perhaps someone met with a similar on Ubuntu.

• utvideoenc : Enable support for multiple slices and use them

  14 février 2014, par Jan Ekström

  utvideoenc : Enable support for multiple slices and use them
  The official Ut Video decoder only threads with slices, thus until
  
  now any files encoded by the libavcodec encoder have only been
  
  decodable with a single thread. The default slice count is now
  
  set to subsampled_height / 120.
  Also sets slices to 1 for the Ut Video encoder tests to keep them
  
  green.
  Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] libavcodec/utvideoenc.c
  • [DH] tests/fate/utvideo.mak

• Header missing in mpg, in spite of using avformat_write_header

  23 novembre 2012, par TheSHEEEP

  I am encoding a live rendered video to mpg and/or mp4 (depends on the later usage of the video) using the ffmpeg C API. When encoding to mp4, everything is well. But when encoding to mpg, the resulting video cannot be played by any player. A quick call to ffprobe on it reveals that the header is missing. But this seems pretty much impossible, as I am explicitly writing it.

  This is how I write the header, before any frame is encoded :

  // ptr->oc is the AVFormatContext
  
  int error = avformat_write_header(ptr->oc, NULL);
  
  if (error < 0)
  
  {
  
      s_logFile << "Could not write header. Error: " << error << endl;
  
      fprintf(stderr, "Could not write header. Error: '%i'\n", error);
  
      return 1;
  
  }

  There never is any error when writing the header.

  For encoding, I am following the official muxing.c example, so I do set the CODEC_FLAG_GLOBAL_HEADER flag. I use CODEC_ID_MPEG2VIDEO (for video) and CODEC_ID_MP2 (for audio).

  The result mpg does work when I "encode" it in an additional step with an external ffmpeg executable like this : "ffmpeg -i ownEncoded.mpg -sameq -y working.mpg".
  So it seems all the data is there, only the header is missing for some reason...

  Here is the only thing ffmpeg is reporting before/when writing the header :

  mpeg -------------------
  
  lvl: 24
  
  msg: VBV buffer size not set, muxing may fail

  Could that be the problem ?

  I wonder what could be wrong here as I encode mp4 with the exact same function, except setting some special values like qmin, qmax, me_method, etc. when encoding to mp4. Do I probably have to set any special values so that ffmpeg really does write the header correctly ?