Recherche avancée

Sur d’autres sites (5337)

• Qimage : out of memory , returning null image , av_codec_lib

  22 septembre 2022, par Integer75

  here's my code to render the image in FFmpeg format, I am able to render the images but after some time due to memory leakage I got an error, QImage : out of memory, returning null image, and my application crashes.

  


  SwsContext* img_convert_ctx;
img_convert_ctx = sws_getContext(codecCtx->width,
                                 codecCtx->height,
                                 codecCtx->pix_fmt,
                                 codecCtx->width,
                                 codecCtx->height,
                                 AV_PIX_FMT_RGB24,
                                 SWS_BICUBIC, NULL, NULL, NULL);

AVFrame* frameRGB ;

frameRGB = av_frame_alloc();

avpicture_alloc((AVPicture*)frameRGB,
                AV_PIX_FMT_RGB24,
                codecCtx->width,
                codecCtx->height);

sws_scale(img_convert_ctx,
          frame->data,
          frame->linesize, 0,
          codecCtx->height,
          frameRGB->data,
          frameRGB->linesize);

QImage image(frameRGB->data[0],
        codecCtx->width,
        codecCtx->height,
        frameRGB->linesize[0],
        QImage::Format_RGB888);


  


  How can I free the memory ? I tried using av_frame_free, av_frame_unref which are specified to deallocate the memory located

  


• dnxhddec : Decode and use interlace mb flag

  26 septembre 2015, par Christophe Gisquet

  dnxhddec : Decode and use interlace mb flag
  This bit is 1 in some samples, and seems to coincide with interlaced
  
  mbs and CID1260. 2008 specs do not know about it, and maintain qscale
  
  is 11 bits. This looks oversized, but may help larger bitdepths.
  Currently, it leads to an obviously incorrect qscale value, meaning
  
  its syntax is shifted by 1. However, reading 11 bits also leads to
  
  obviously incorrect decoding : qscale seems to be 10 bits.
  However, as most profiles still have 11bits qscale, the feature is
  
  restricted to the CID1260 profile (this flag is dependent on
  
  a higher-level flag located in the header).
  The encoder writes 12 bits of syntax, last and first bits always 0,
  
  which is now somewhat inconsistent with the decoder, but ends up with
  
  the same effect (progressive + reserved bit).
  Signed-off-by : Vittorio Giovara <vittorio.giovara@gmail.com>
  

  • [DH] libavcodec/dnxhddec.c

• How to fix "fatal error : x.264 no such file or directory"

  24 avril 2019, par user11340790

  I wrote a makefile which builds a C program attaching the x.264 header. After trying to execute the makefile in terminal I receive the fatal error :
  "example.c line [line of #include ] x264.h no such file or directory". Below you can find the C code and makefile (located in the same folder, the library - containing the x264.pc file- is in the folder libx264 of the parent folder). I would be very grateful if you could help with the linkage.

  Makefile :

      CC = gcc
  
  
  
      CFLAGS = -c -Wall `export PKG_CONFIG_PATH=../libx264 && pkg-config            --cflags x264`
  
      LDFLAGS = -static `export PKG_CONFIG_PATH=../libx264 && pkg-config --libs --static libx264`
  
  
  
  
  
      all: Release
  
  
  
      Debug: CFLAGS += -g
  
      Debug: example
  
  
  
      Release: example
  
  
  
      test: example.o
  
          $(CC) -o example example.o $(LDFLAGS)
  
  
  
      test.o: example.c
  
          $(CC) $(CFLAGS) example.c -o example.o
  
  
  
      clean:
  
          rm -f example.o example

  example.c code

      #include 
  
      #include 
  
      int main( int argc, char **argv )
  
      {
  
          int width, height;
  
           return 0;
  
      }