Recherche avancée

Sur d’autres sites (9132)

• avcodec/proresenc_anatoliy : do not write into chroma reserved bitfields

  7 janvier 2024, par Clément Bœsch

  avcodec/proresenc_anatoliy : do not write into chroma reserved bitfields
  The layout for the frame flags is as follow :
     chroma_format  u(2)
  
     reserved       u(2)
  
     interlace_mode u(2)
  
     reserved       u(2)
  chroma_format has 2 allowed values :
  
     0 : reserved
  
     1 : reserved
  
     2 : 4:2:2
  
     3 : 4:4:4
  interlace_mode has 3 allowed values :
  
     0 : progressive
  
     1 : tff
  
     2 : bff
  
     3 : reserved
  0x80 is what we expect for "422 not interlaced", and the extra 0x2 from
  
  0x82 is actually writing into the reserved bits.
  

  • [DH] libavcodec/proresenc_anatoliy.c
  • [DH] tests/ref/vsynth/vsynth1-prores
  • [DH] tests/ref/vsynth/vsynth1-prores_444
  • [DH] tests/ref/vsynth/vsynth1-prores_444_int
  • [DH] tests/ref/vsynth/vsynth1-prores_int
  • [DH] tests/ref/vsynth/vsynth2-prores
  • [DH] tests/ref/vsynth/vsynth2-prores_444
  • [DH] tests/ref/vsynth/vsynth2-prores_444_int
  • [DH] tests/ref/vsynth/vsynth2-prores_int
  • [DH] tests/ref/vsynth/vsynth3-prores
  • [DH] tests/ref/vsynth/vsynth3-prores_444
  • [DH] tests/ref/vsynth/vsynth3-prores_444_int
  • [DH] tests/ref/vsynth/vsynth3-prores_int
  • [DH] tests/ref/vsynth/vsynth_lena-prores
  • [DH] tests/ref/vsynth/vsynth_lena-prores_444
  • [DH] tests/ref/vsynth/vsynth_lena-prores_444_int
  • [DH] tests/ref/vsynth/vsynth_lena-prores_int

• avformat/webmdashenc : Remove possibility of infinite loop

  18 mai 2020, par Andreas Rheinhardt

  avformat/webmdashenc : Remove possibility of infinite loop
  The WebM DASH manifest muxer uses a loop to parse the adaptation_sets
  
  string (which is given by the user and governs which AVStreams are
  
  mapped to what adaptation set) and the very beginning of this loop is
  
  "if (*p == ' ') continue ;". This of course leads to an infinite loop if
  
  the condition is true. It is true if e.g. the string begins with ' ' or
  
  if there are more than one ' ' between different adaptation set groups.
  To fix this, the parsing process has been modified to consume the space
  
  if it is at a place where it can legitimately occur, i.e. when a new
  
  adaptation set group is expected. The latter restriction implies that an
  
  error is returned if a space exists where none is allowed to exist.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  

  • [DH] libavformat/webmdashenc.c

• How can I create a c++ console application which makes use of an open source c project

  2 octobre 2018, par Bogdan Daniel

  I’ve been playing around with a compiled version of https://github.com/FFmpeg/FFmpeg. But it has some problems, during the closing of an opened stream using avio_close(it takes a really long time to close it).

  I’ve been trying to understand what could go wrong by reading through the implementation, but couldn’t find anything.

  What I would like to do, is to actually have a C++ console application which uses the c files and to debug them while running the code(using breakpoints and so on).

  Unfortunately I cannot find any information on how to set it up. Simply copying the files in a new console application is not enough.

  Thanks in advance for any suggestions.

  Edit : I can already see a closing vote. If this question is not appropriate for this website, I will delete it. But please point me in the right direction of where to post it.Although it is quite a general question, I believe that it is clear and enough information has been provided.

  Edit2 : Yes, I was a bit unclear about what I’m using.

  I’m using Visual Studio Community 2017 on Windows 10 for creating the C++ console application.

  Edit3 :

  Steps that I’ve taken into using the source files into my console application which was using the DLLs.

  1. Copy all of the contents of the FFmpeg-master to my console application
  2. Include all of them in the c++ console application project
  3. Run a build - takes forever and has infinite build errors( > 1000) - probably compiler related

  Edit4 :

  I have no actual errors with avio_close, it just takes too long to close the stream. What I found out when playing around with the settings is that when the fifo_size parameter is set, closing the stream is a lot faster depending on how small the set value is. And it sort of makes sense since fifo_size is related to the packet size, but I haven’t found out where in the code this size has an impact.

  fifo_size=units
  Set the UDP receiving circular buffer size, expressed as a number of packets with size of 188 bytes. If not specified defaults to 7*4096.

  Edit5 : I still haven’t found a way to compile the open source ffmpeg project into libs, dlls and pdbs. Am I the first one needing such files(seems unrealistic) ?
  The only tool capable of delivering those so far is vcpkg. The only problem is that it compiles the 3.3.3 version and the latest is 4.0.2 .

  I tried to modify the vcpkg\ports\ffmpeg\portfile.cmake file to include the latest version of ffmpeg, but it doesn’t build it.

  Are there any other suggestions ?