Recherche avancée

Sur d’autres sites (7874)

• how to use x264 dll in another project

  5 août 2014, par Hadi Rasekh

  enter code here I want to use x264 in my project. There is some line in the code said :

  /* Application developers planning to link against a shared library version of
* libx264 from a Microsoft Visual Studio or similar development environment
* will need to define X264_API_IMPORTS before including this header.
* This clause does not apply to MinGW, similar development environments, or non
* Windows platforms. */

  But I don’t get this line :
  define X264_API_IMPORTS before including this header

  We can create x264 dll by its configuration and make

      ./configure --enable-shared
  
      make

  but I can not use the dll in my Qt Project.

  I can make my own dll (in another code) and use it in the project.
  But when I start to use x264 dll in my project I get the following error :

      C:\DataHiding\SourceCode2\GUI\DataHiding\mainwindow.cpp:10: error:
  
      'pulldown_frame_duration' was not declared in this scope
  
      qDebug() << pulldown_frame_duration[1];
  
               ^

• Live stream prerecorded video to YouTube using FFMPEG with 4500 kbps bitrate

  9 avril 2023, par Rsan

  I tried various ways to make a live streaming script with a bit rate according to YouTube's recommendation of 4500 Kbps bit rate.
The code :

  


  ffmpeg -re -stream_loop -1 -i live1.mp4 -c copy -preset veryfast -b:v 7000k -maxrate 3000k -bufsize 6000k -pix_fmt yuv420p -g 50 -c:a aac -b:a 160k -ac 2 -ar 44100 -f flv -flvflags no_duration_filesize rtmp://a.rtmp.youtube.com/live2/(streamkey)

  


  and in my current code, there is an error when live : Use a keyframe frequency of four seconds or less. Currently, keyframes are sent infrequently which can cause buffering. The current keyframe frequency is 5.0 seconds. Please note that errors in the transfer process can cause the size of the GOP (group of images) to be incorrect.

  


  How to fix my code ?

  


  I've tried several ways, but the bit rate is still high, and the error is in YouTube Studio

  


• Revision e890c2579b : add a context tree structure to encoder This patch sets up a quad_tree structur

  17 avril 2014, par Jim Bankoski

  Changed Paths :
   Modify /vp9/encoder/vp9_block.h

  
   Add /vp9/encoder/vp9_context_tree.c

  
   Add /vp9/encoder/vp9_context_tree.h

  
   Modify /vp9/encoder/vp9_encodeframe.c

  
   Modify /vp9/encoder/vp9_firstpass.c

  
   Modify /vp9/encoder/vp9_onyx_if.c

  
   Modify /vp9/vp9cx.mk

  
  
  add a context tree structure to encoder

  This patch sets up a quad_tree structure (pc_tree) for holding all of
  pick_mode_context data we use at any square block size during encoding
  or picking modes. That includes contexts for 2 horizontal and 2 vertical
  splits, one none, and pointers to 4 sub pc_tree nodes corresponding
  to split. It also includes a pointer to the current chosen partitioning.

  This replaces code that held an index for every level in the pick
  modes array including : sb_index, mb_index,
  b_index, ab_index.

  These were used as stateful indexes that pointed to the current pick mode
  contexts you had at each level stored in the following arrays

  array ab4x4_context[][][],
  sb8x4_context[][][], sb4x8_context[][][], sb8x8_context[][][],
  sb8x16_context[][][], sb16x8_context[][][], mb_context[][], sb32x16[][],
  sb16x32[], sb32_context[], sb32x64_context[], sb64x32_context[],
  sb64_context

  and the partitioning that had been stored in the following :
  b_partitioning, mb_partitioning, sb_partitioning, and sb64_partitioning.

  Prior to this patch before doing an encode you had to set the appropriate
  index for your block size ( switch statement), update it ( up to 3
  lookups for the index array value) and then make your call into a recursive
  function at which point you'd have to call get_context which then
  had to do a switch statement based on the blocksize, and then up to 3
  lookups based upon the block size to find the context to use.

  With the new code the context for the block size is passed around directly
  avoiding the extraneous switch statements and multi dimensional array
  look ups that were listed above. At any level in the search all of the
  contexts are local to the pc_tree you are working on (in ?).

  In addition in most places code that used to call sub functions and
  then check if the block size was 4x4 and index was > 0 and return
  now don't preferring instead to call the right none function on the inside.

  Change-Id : I06e39318269d9af2ce37961b3f95e181b57f5ed9