Recherche avancée

Sur d’autres sites (5327)

• random_seed : Reorder if clauses for gathering entropy

  5 février, par Martin Storsjö

  random_seed : Reorder if clauses for gathering entropy
  Make it easier to add more cases.
  This should be a pure refactoring, with no functional changes.
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] libavutil/random_seed.c

• swscale/internal : group user-facing options together

  10 octobre 2024, par Niklas Haas

  swscale/internal : group user-facing options together
  This is a preliminary step to separating these into a new struct. This
  
  commit contains no functional changes, it is a pure search-and-replace.
  Sponsored-by : Sovereign Tech Fund
  
  Signed-off-by : Niklas Haas <git@haasn.dev>
  

  • [DH] libswscale/aarch64/swscale.c
  • [DH] libswscale/aarch64/swscale_unscaled.c
  • [DH] libswscale/alphablend.c
  • [DH] libswscale/arm/swscale_unscaled.c
  • [DH] libswscale/input.c
  • [DH] libswscale/loongarch/input_lasx.c
  • [DH] libswscale/loongarch/input_lsx.c
  • [DH] libswscale/loongarch/output_lasx.c
  • [DH] libswscale/loongarch/output_lsx.c
  • [DH] libswscale/loongarch/swscale_init_loongarch.c
  • [DH] libswscale/loongarch/swscale_lasx.c
  • [DH] libswscale/loongarch/swscale_lsx.c
  • [DH] libswscale/loongarch/yuv2rgb_lasx.c
  • [DH] libswscale/loongarch/yuv2rgb_lsx.c
  • [DH] libswscale/options.c
  • [DH] libswscale/output.c
  • [DH] libswscale/ppc/swscale_altivec.c
  • [DH] libswscale/ppc/swscale_vsx.c
  • [DH] libswscale/ppc/yuv2rgb_altivec.c
  • [DH] libswscale/ppc/yuv2yuv_altivec.c
  • [DH] libswscale/riscv/swscale.c
  • [DH] libswscale/slice.c
  • [DH] libswscale/swscale.c
  • [DH] libswscale/swscale_internal.h
  • [DH] libswscale/swscale_unscaled.c
  • [DH] libswscale/utils.c
  • [DH] libswscale/vscale.c
  • [DH] libswscale/x86/output.asm
  • [DH] libswscale/x86/swscale.c
  • [DH] libswscale/x86/swscale_template.c
  • [DH] libswscale/x86/yuv2rgb.c
  • [DH] libswscale/yuv2rgb.c
  • [DH] tests/checkasm/sw_gbrp.c
  • [DH] tests/checkasm/sw_range_convert.c
  • [DH] tests/checkasm/sw_rgb.c
  • [DH] tests/checkasm/sw_scale.c

• How can I quantitatively measure gstreamer H264 latency between source and display ?

  16 décembre 2014, par KevinM

  I have a project where we are using gstreamer , x264, etc, to multicast a video stream over a local network to multiple receivers (dedicated computers attached to monitors). We’re using gstreamer on both the video source (camera) systems and the display monitors.

  We’re using RTP, payload 96, and libx264 to encode the video stream (no audio).

  But now I need to quantify the latency between (as close as possible to) frame acquisition and display.

  Does anyone have suggestions that use the existing software ?

  Ideally I’d like to be able to run the testing software for a few hours to generate enough statistics to quantify the system. Meaning that I can’t do one-off tests like point the source camera at the receiving display monitor displaying a high resolution and manually calculate the difference...

  I do realise that using a pure software-only solution, I will not be able to quantify the video acquisition delay (i.e. CCD to framebuffer).

  I can arrange that the system clocks on the source and display systems are synchronised to a high accuracy (using PTP), so I will be able to trust the system clocks (else I will use some software to track the difference between the system clocks and remove this from the test results).

  In case it helps, the project applications are written in C++, so I can use C event callbacks, if they’re available, to consider embedding system time in a custom header (e.g. frame xyz, encoded at time TTT - and use the same information on the receiver to calculate a difference).