Recherche avancée

Sur d’autres sites (6006)

• Android : How to record the mobile screen without using USB cable ?

  21 juin 2012, par Rajesh

  I want to build an application which would record my screen activities and would store them in a video file.

  1) I need to take the screenshots of my screen movements at periodic intervals and store them on the SD card.

  2) How can I create the video from the images which are already available on my SD card. I have tried with the FFMPEG. But I have encountered a few problems I don't know how to solve. The truth is I don't know the program to convert them.

  3 ) Is it possible to show the picture in my camera ?? That means if a user opens the camera from my app, it should show the pictures which are available on the SD card. If so, please advice me.

  EDIT : I have made a sample which can capable of taking 7 screen shots per second.

  Thanks,
  Rajesh .

• HEVC/H.265 interlaced format support in ffmpeg or VLC

  30 décembre 2020, par Ernestas Gruodis

  "Music Box Russia" channel over satellite transmits in HEVC 1920x1080 25fps interlaced - and after recording VLC recognizes file as 50 fps, and resolution 1920x540 - half a height. But on satellite tuner the player works fine - it plays a file as 1920x1080 25fps... When we can expect support for HEVC/H.265 interlaced ? Here is recorded file (Garry Grey & Eva Miller - wtf). Also - a lot of lost frames in VLC player statistics..

  


  EDIT :

  


  I found some interesting info how in HEVC the interlace video content can be indicated here :

  


  


  Unlike to H.264/AVC, interlace-dedicated coding in HEVC is not exist :

  


  

  • No mixed frame-field interaction (like PAFF in H.264/AVC)

  


  • No interlace scanning of transform coefficients

  


  • No correction MVX[1] (or y-component of MV) if current and reference pictures are in different polarity (top-bottom or
bottom-top).

  


  


  However, in HEVC the interlace video content can be indicated
(signaled in VPS/SPS and pic_timing SEI messages the latter are
transmitted for every picture in the sequence). Interlace-related
setting :

  


  


  • in VPS/SPS set general_interlaced_source_flag=1 and general_progressive_source_flag=0. Indeed, the HEVC standard says :

    


    if general_progressive_source_flag is equal to 0 and
general_interlaced_source_flag is equal to 1, the source scan type of
the pictures in the CVS should be interpreted as interlaced only.

    


  


  • in VPS/SPS set general_frame_only_constraint_flag=0

    


  


  • in SPS VUI set field_seq_flag=1 and frame_field_info_present_flag=1. Notice that if these flags are ON
then picture timing SEIs shall be present for each picture.

    


  


  • transmission of Picture Timing SEI per picture with the following parameters :

    


    source_scan_type = 0 to indicate interlace mode
for top field picture signal pict_struct=1 and for bottom field picture pict_struct=2

    


  


  


  


  Perhaps it is possible to pass these parameters to ffmpeg/vlc before playing a file ?

  


• fate/gif : Remove nonsense requirement

  28 avril 2022, par Andreas Rheinhardt

  fate/gif : Remove nonsense requirement
  It seems as if it was intended to declare fate-gif-color as prerequisite
  
  of the fate-gifenc% tests. Yet the latter do not need anything from
  
  the former, so this would be unnecessary. Furthermore, given that this
  
  line has no associated recipe, it actually cancels implicit rules for
  
  fate-gifenc% instead of adding a prerequisite.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] tests/fate/gif.mak