Recherche avancée

Sur d’autres sites (9641)

• How to save an SDL bitmap to memory and load it back ?

  19 novembre 2012, par Nav

  I have a bunch of RWops functions :

  static int myseekfunc(SDL_RWops *context, int offset, int whence) { SDL_SetError("Can't seek in this kind of RWops"); return(-1); }
  
  static int myreadfunc(SDL_RWops *context, void *ptr, int size, int maxnum) { memset(ptr,0,size*maxnum); return(maxnum); }
  
  static int mywritefunc(SDL_RWops *context, const void *ptr, int size, int num) { return(num); }
  
  static int myclosefunc(SDL_RWops *context) 
  
  { 
  
    if(context->type != 0xdeadbeef) { SDL_SetError("Wrong kind of RWops for myclosefunc()"); return(-1); }
  
    free(context->hidden.unknown.data1);
  
    SDL_FreeRW(context);
  
    return(0);
  
  }
  
  
  
  // Note that this function is NOT static -- we want it directly callable from other source files 
  
  SDL_RWops *MyCustomRWop()
  
  {
  
    SDL_RWops *c=SDL_AllocRW();
  
    if(c==NULL) return(NULL);
  
  
  
    c->seek =myseekfunc;
  
    c->read =myreadfunc;
  
    c->write=mywritefunc;
  
    c->close=myclosefunc;
  
    c->type =0xdeadbeef;
  
    printf("deadbeef=%d\n",c->type);
  
    c->hidden.unknown.data1=malloc(256);//IS THIS CORRECT?
  
    return(c);
  
  }

  with which I'm trying to write a BMP into memory and then extract it back. The below code is from tutorial02.
  Two problems I'm facing are :
  1. Unless I call SDL_DisplayYUVOverlay, the SDL_SaveBMP function outputs a blank BMP file to the hard disk. How can I output a BMP file without having to call SDL_DisplayYUVOverlay ?
  2. Although I'm able to save the BMP to memory with SDL_SaveBMP_RW and free the memory with filestream->close, I'm unable to load the BMP back from memory with SDL_SaveBMP. The application crashes while trying to load it. Is it because of the c->hidden.unknown.data1=malloc(256); code above ? What would be the right way of allocating this memory ?

    AVFormatContext *pFormatCtx = NULL;
  
    int             i, videoStream;
  
    AVCodecContext  *pCodecCtx = NULL;
  
    AVCodec         *pCodec = NULL;
  
    AVFrame         *pFrame = NULL; 
  
    AVPacket        packet;
  
    SDL_Overlay     *bmp = NULL;
  
    SDL_Surface     *screen = NULL;
  
    SDL_Surface     *screen2 = NULL;
  
    SDL_Rect        rect;
  
  ....
  
  ....    
  
  if(frameFinished) 
  
  
  
  {
  
  SDL_LockYUVOverlay(bmp);//-----------lock
  
  
  
  AVPicture pict;
  
  pict.data[0] = bmp->pixels[0];
  
  pict.data[1] = bmp->pixels[2];
  
  pict.data[2] = bmp->pixels[1];
  
  
  
  pict.linesize[0] = bmp->pitches[0];
  
  pict.linesize[1] = bmp->pitches[2];
  
  pict.linesize[2] = bmp->pitches[1];
  
  
  
  // Convert the image into YUV format that SDL uses
  
  sws_scale( sws_ctx, (uint8_t const * const *)pFrame->data, pFrame->linesize, 0, pCodecCtx->height, pict.data, pict.linesize );
  
  
  
  SDL_UnlockYUVOverlay(bmp);//-----------unlock
  
  
  
  rect.x = 0;
  
  rect.y = 0;
  
  rect.w = pCodecCtx->width;
  
  rect.h = pCodecCtx->height;
  
  SDL_DisplayYUVOverlay(bmp, &rect);
  
  ++i;
  
  
  
  SDL_RWops *filestream = MyCustomRWop();//SDL_AllocRW();
  
  SDL_SaveBMP_RW (screen, filestream, i);
  
  screen2 = SDL_LoadBMP_RW(filestream,1);//LOADING IS THE PROBLEM HERE. DON'T KNOW WHY
  
  filestream->close;
  
  SDL_SaveBMP(screen, filepointer);

• avcodec/evc : Reference to ISO_IEC_23094-1-2020 document section for EVC_MAX_APS_COUNT...

  18 avril 2024, par Dawid Kozinski

  avcodec/evc : Reference to ISO_IEC_23094-1-2020 document section for EVC_MAX_APS_COUNT enum has been fixed
  Signed-off-by : Dawid Kozinski <d.kozinski@samsung.com>
  

  • [DH] libavcodec/evc.h

• Why use sysconf(_SC_NPROCESSORS_CONF) to get the number of CPU cores in x264 ?

  5 novembre 2017, par bknieven

  I find x264 use sysconf(_SC_NPROCESSORS_CONF) instead of sysconf(SC_NPROCESSORS_ONLN) to get the number of CPU cores.

  Here is the code snippet in x264/common/cpu.c :

  ...
  
  #ifdef __ANDROID__
  
      // Android NDK does not expose sched_getaffinity
  
      return sysconf( _SC_NPROCESSORS_CONF );
  
  #else
  
      ...
  
  ....

  And I find the difference between _SC_NPROCESSORS_CONF and _SC_NPROCESSORS_ONLN in this manual :

  sysconf (_SC_NPROCESSORS_CONF) which returns the number of processors
  the operating system configured. But it might be possible for the
  operating system to disable individual processors and so the call
  sysconf (_SC_NPROCESSORS_ONLN) returns the number of processors which
  are currently online (i.e., available).

  I have two questions :

  1. What is the difference between "the number of processors the operating system configured" and "the number of processors which are currently online" ?
  2. Why x264 use _SC_NPROCESSORS_CONF in Android to get the number of CPU cores ?