Recherche avancée

Sur d’autres sites (8100)

• avformat/movenc : use correct iTunes copyright atom

  3 avril 2018, par Timo Teräs

  avformat/movenc : use correct iTunes copyright atom
  Support for writing copyright metadata was added in commit bed4fc54c9
  
  for 3GP, MOV and iTunes metadata. 3GP and MOV cases are formally
  
  specified. However, iTunes format does not have specification, and
  
  it seems to have been assumed that it would use the same atom as
  
  MOV (both being Apple formats).
  However, Apple uses 'cprt' atom for iTunes metadata (do note that
  
  the iTunes 'cprt' encoding is generic iTunes ItemList atom, not
  
  the 3GP 'cprt' encoding. These are also inside different parent
  
  atoms).
  Most references trying to document iTunes atoms mention only
  
  the 'cprt' tag. See :
  
   - http://atomicparsley.sourceforge.net/mpeg-4files.html
  
   - http://mutagen.readthedocs.io/en/latest/api/mp4.html
  Same applies to other software supporting this tag. Most of them
  
  encode and decode only the 'cprt' atom.
  ffmpeg mov demuxer supports both atoms in this context. There are
  
  few pieces of other software that support similarly both 'cprt' and
  
  the incorrect '\251cpy' atom in this context. I believe they do it in
  
  order to read the ffmpeg encoded incorrect copyright atom.
  In light of the above this changes the copyright atom to 'cprt' as
  
  it seems to be supported univerally and is the correct atom to use.
  Signed-off-by : Timo Teräs <timo.teras@iki.fi>
  
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavformat/movenc.c

• Some Java Process objects finish and close, but some finish and stall

  28 mars 2020, par brendanw36

  My program uses ProcessBuilder to make various calls to ffmpeg. My problem is that with certain commands I can create a Process, have it run, and when it is done it will terminate/exit/close itself and the program will end whereas other commands will run and create a finished output (in my case it will finish encoding a file with no corruption or anything at the end of the video), but won’t close at which point I need to force terminate the program. I have tested the ffmpeg commands that I am running in Windows Command Prompt and they all run fine without need for user input or anything. I will show some examples of commands that do and don’t work, but ultimately what I need is a way to tell why certain Processes do and don’t work. You probably don’t even need to read the rest of this post if you know the inner workings of the Process class better than I do.

  How I create my processes :

  ProcessBuilder pb = new ProcessBuilder(commandGoesHere);
  
  Process p = pb.start();
  
  p.waitFor();

  Works :
  ffmpeg -i test.y4m -f segment -segment_times timecodeList .temp/sgmnt_%d.y4m

  This command takes a y4m(raw video format/large file size/1.7 GB for 53s of 720p video) and cuts it in to chunks.

  Doesn’t work (sometimes) :
  ffmpeg -i chunkname.y4m outputName.mkv

  This command takes the chunked video and encodes it as h.264/AVC video. When I create a process with this command it only works if the chunk is small in which case the Process will start, do its work, and close.

  Doesn’t work ever :
  ffmpeg -i test.mkv -c:v copy -f segment -segment_times timecodeList .temp/sgmnt_%d.mkv

  This command takes and h.264/AVC input video and cut it in to chunks, but this one doesn’t terminate/exit/close when it’s done. I’m forced to terminate the program which I do after seeing the Process’s CPU utilization drop to 0% in Task Manager. When I force terminate the program and check the output folder, all the chunks are there and not corrupted so I know it finished running successfully.

• log : Support for 256color terminals

  26 avril 2013, par Luca Barbato

  log : Support for 256color terminals
  And provide extended coloring capabilities for debugging.
  
  The default colors do not change in 256 more to keep
  
  supporting people using Black on White, White on Black and
  
  Solarized terminals.
  Signed-off-by : Luca Barbato <lu_zero@gentoo.org>
  

  • [DBH] doc/APIchanges
  • [DBH] libavutil/log.c
  • [DBH] libavutil/log.h
  • [DBH] libavutil/version.h