Recherche avancée

Sur d’autres sites (8186)

• pyInstaller : Pack binary executable inside project's executable to run

  18 décembre 2023, par zur

  TLDR ;

  


  I would like to pack the ffmpeg executable inside my own executable. Currently I am getting

  


  FileNotFoundError: [Errno 2] No such file or directory: 'ffmpeg'
Skipping ./testFile202312061352.mp4 due to FileNotFoundError: [Errno 2] No such file or directory: 'ffmpeg'


  


  Details :

  


  I am creating executable file using following command :

  


  pyinstaller cli.py \&#xA;  --onefile \&#xA;  --add-binary /Users/<machineuser>/anaconda3/envs/my_env/bin/ffmpeg:bin&#xA;</machineuser>

  


  The code that uses ffmpeg is not authored by me. And I would like to keep that part the same.

  


  When I run from command line while conda environment is active I can successfully run it as python (or perhaps anaconda) knows where the binaries are. I have a pretty empty cli.py. That seems to be the entry point and I hope if it is possible I can set the bin directory's path there ...

  


  I am able to successfully run the application like following :

  


  (my_env) machineUser folder % "dist/cli_mac_001202312051431" ./testFile202312061352.mp4


  


  I would like to run like following :

  


  (base) machineUser folder % "dist/cli_mac_001202312051431" ./testFile202312061352.mp4


  


  I would like to keep the world out side my executable's tmp folder the same. I would not want to change something that will be "left behind" after the exec is terminated.

  


  Question :

  


  Can some one please mention how to modify the pyinstaller command or what to change in cli.py to achieve it successfully ?

  


• FFMPEG : Explain parameters of any codecs fuction pointers

  3 décembre 2013, par Zax

  I'm going through the article, How to integrate a codec in FFMPEG multimedia framework.
  According to it, every codec needs to have 3 basic functions to be defined and these functions are assigned to function pointers of the structure AVCodec.

  The 3 function pointers specified in the above article are :

  .init -> takes care of allocations and other initializations
  
  
  
  .close -> freeing the allocated memory and de-initializations
  
  
  
  .decode -> frame by frame decoding.

  For the function pointer .decode, the funtion assigned is :

  static int cook_decode_frame(AVCodecContext *avctx,
  
              void *data, int *data_size,
  
              uint8_t *buf, int buf_size) {
  
  ...

  The details of these parameters are specified in the above article. However, in the latest code, when the same function is taken as an example, its declaration is as shown below :

  static int cook_decode_frame(AVCodecContext *avctx, void *data,
  
                               int *got_frame_ptr, AVPacket *avpkt)

  I need to perform some mapping operations on the memory. So, i request if anyone could kindly explain the above parameters in the function declarations. Also, which parameter has the input buffer for decoding the frame ? And after decoding a frame, to which parameter is the decoded frame mapped ?

  Thanks in advance.

  -Regards.

• lavc/rawdec : Use AV_PIX_FMT_PAL8 for 1-bit raw QuickTime video

  17 janvier 2016, par Mats Peterson

  lavc/rawdec : Use AV_PIX_FMT_PAL8 for 1-bit raw QuickTime video
  Match the use of AV_PIX_FMT_PAL8 for 1-bit QuickTime Animation in
  
  lavc/qtrle. To reiterate, 1-bit video is not necessary black & white in
  
  QuickTime, merely bi-level. The two colors can be any color. The palette,
  
  either included in the sample description, or the default Macintosh
  
  palette (black & white for 1-bit video) will be set in lavf/qtpalette.
  
  See the QuickTime File Format Specification for details.
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavcodec/raw.c
  • [DH] libavcodec/rawdec.c