Recherche avancée

Sur d’autres sites (6166)

• how to get 120fps encoded video to play at "normal" speed instead of slow mo

  1er mars 2023, par Patrick Vellia

  I used my GoPro Hero10 to record at 4k 120fps on a green screen. This original video plays slo-mo in QuickTime but "normal" speed in the browser. I want it playing normal speed, and if end user wants to slow it down they have the extra frames for that to maintain clarity, which is why I record at 120.

  


  I then used FFMPEG to create an image sequence of the video.

  


  Then I ran Image Magic to create the transparent frames.

  


  Then I put it back together with the following command for a HEVC mov file :

  


  ffmpeg -r 120 -f image2 -i transparent/image_transparent_%08d.png -vcodec hevc_videotoolbox -crf 28 -alpha_quality 1  -tag:v hvc1 output.mov


  


  I am still on an Intel MacBook Pro running FFMPEG 4.6 (as I've found 5+ was buggy with one of my commands a few months ago but can't remember which one, I think it was the videotoolbox).

  


  The GoPro video has the following stream data as input to the FFMPEG :

  


  Duration: 00:00:08.15, start: 0.000000, bitrate: 60160 kb/s
  Stream #0:0(eng): Video: hevc (Main) (hvc1 / 0x31637668), yuvj420p(pc, bt709), 3840x2160 [SAR 1:1 DAR 16:9], 59891 kb/s, 119.88 fps, 119.88 tbr, 120k tbn, 119.88 tbc (default)
    Metadata:
      creation_time   : 2023-02-28T19:06:41.000000Z
      handler_name    : GoPro H.265
      vendor_id       : [0][0][0][0]
      encoder         : GoPro H.265 encoder
      timecode        : 19:05:32:105
  Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 189 kb/s (default)
    Metadata:
      creation_time   : 2023-02-28T19:06:41.000000Z
      handler_name    : GoPro AAC  
      vendor_id       : [0][0][0][0]
      timecode        : 19:05:32:105
  Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default)
    Metadata:
      creation_time   : 2023-02-28T19:06:41.000000Z
      handler_name    : GoPro TCD  
      timecode        : 19:05:32:105
  Stream #0:3(eng): Data: bin_data (gpmd / 0x646D7067), 76 kb/s (default)
    Metadata:
      creation_time   : 2023-02-28T19:06:41.000000Z
      handler_name    : GoPro MET  


  


  Whereas the re-constructed video has the following data :

  


  Duration: 00:00:08.13, start: 0.000000, bitrate: 763650 kb/s
  Stream #0:0: Video: hevc (Main) (hvc1 / 0x31637668), yuv420p(tv, progressive), 3840x2160 [SAR 1:1 DAR 16:9], 763696 kb/s, 120 fps, 120 tbr, 15360 tbn, 15360 tbc (default)
    Metadata:
      handler_name    : VideoHandler
      vendor_id       : FFMP
      encoder         : Lavc58.134.100 hevc_videotoolbo


  


  When this re-constructed video plays in the browser, it is in slow-mo and I need to set the playbackRate to 4.0 for it to play "normally".

  


  Is there something I need to add to the video for the browser to play it at "normal" speed ?

  


  EDIT

  


  I just compared the two video streams :

  


  original:
Stream #0:0(eng): Video: hevc (Main) (hvc1 / 0x31637668), yuvj420p(pc, bt709), 3840x2160 [SAR 1:1 DAR 16:9], 59891 kb/s, 119.88 fps, 119.88 tbr, 120k tbn, 119.88 tbc (default)

Reconstructed:
 Stream #0:0: Video: hevc (Main) (hvc1 / 0x31637668), yuv420p(tv, progressive), 3840x2160 [SAR 1:1 DAR 16:9], 763696 kb/s, 120 fps, 120 tbr, 15360 tbn, 15360 tbc (default)


  


  I don't quit understand all of this though. so here's what I notice :

  


  original.         reconstructed
--------------------------------
bt709             progressive
89871 kb/s.       763696 kb/s
119.88 fps.       120 fps
119.88 tbr.       120 tbr
120k tbr.         15360 tbr
11960 tbr.        15360 tbc


  


  Hmm. I suspect it has something to do with tbr and tbc whatever those are, or perhaps the progressive vs the bt709 ? the pirates are also vastly different.

  


• Playing 120fps in browser between original and re-made video, original is normal speed, new video is slo-mo

  1er mars 2023, par Patrick Vellia

  I used my GoPro Hero10 to record at 4k 120fps on a green screen. This original video plays slo-mo in QuickTime but "normal" speed in the browser. I want it playing normal speed, and if end user wants to slow it down they have the extra frames for that to maintain clarity, which is why I record at 120.

  


  I then used FFMPEG to create an image sequence of the video.

  


  Then I ran Image Magic to create the transparent frames.

  


  Then I put it back together with the following command for a HEVC mov file :

  


  ffmpeg -r 120 -f image2 -i transparent/image_transparent_%08d.png -vcodec hevc_videotoolbox -crf 28 -alpha_quality 1  -tag:v hvc1 output.mov


  


  I am still on an Intel MacBook Pro running FFMPEG 4.6 (as I've found 5+ was buggy with one of my commands a few months ago but can't remember which one, I think it was the videotoolbox).

  


  The GoPro video has the following stream data as input to the FFMPEG :

  


  Duration: 00:00:08.15, start: 0.000000, bitrate: 60160 kb/s
  Stream #0:0(eng): Video: hevc (Main) (hvc1 / 0x31637668), yuvj420p(pc, bt709), 3840x2160 [SAR 1:1 DAR 16:9], 59891 kb/s, 119.88 fps, 119.88 tbr, 120k tbn, 119.88 tbc (default)
    Metadata:
      creation_time   : 2023-02-28T19:06:41.000000Z
      handler_name    : GoPro H.265
      vendor_id       : [0][0][0][0]
      encoder         : GoPro H.265 encoder
      timecode        : 19:05:32:105
  Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 189 kb/s (default)
    Metadata:
      creation_time   : 2023-02-28T19:06:41.000000Z
      handler_name    : GoPro AAC  
      vendor_id       : [0][0][0][0]
      timecode        : 19:05:32:105
  Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default)
    Metadata:
      creation_time   : 2023-02-28T19:06:41.000000Z
      handler_name    : GoPro TCD  
      timecode        : 19:05:32:105
  Stream #0:3(eng): Data: bin_data (gpmd / 0x646D7067), 76 kb/s (default)
    Metadata:
      creation_time   : 2023-02-28T19:06:41.000000Z
      handler_name    : GoPro MET  


  


  Whereas the re-constructed video has the following data :

  


  Duration: 00:00:08.13, start: 0.000000, bitrate: 763650 kb/s
  Stream #0:0: Video: hevc (Main) (hvc1 / 0x31637668), yuv420p(tv, progressive), 3840x2160 [SAR 1:1 DAR 16:9], 763696 kb/s, 120 fps, 120 tbr, 15360 tbn, 15360 tbc (default)
    Metadata:
      handler_name    : VideoHandler
      vendor_id       : FFMP
      encoder         : Lavc58.134.100 hevc_videotoolbo


  


  When this re-constructed video plays in the browser, it is in slow-mo and I need to set the playbackRate to 4.0 for it to play "normally".

  


  Is there something I need to add to the video for the browser to play it at "normal" speed ?

  


• Power-Up your Piwik installation with Custom Reports

  13 novembre 2017, par InnoCraft — Plugins

  Would you like to create a report in Piwik with just the data you want and nothing else ? Would you like to be free to decide the shape of it ? Are you struggling with the Piwik database and wish you could have an easy interface to create the report you want ? Are you tired of exporting your data in a spreadsheet ? Since last October, there’s a solution and it’s called Custom Reports.

  With custom reports you will :

  1. get a user-friendly interface to create the report you wish
  2. see all the possible combinations to create the report you desire
  3. reveal new data combinations which were not directly available in Piwik

  User friendly interface

  The time when you created your reports from MySQL database is over. Now with custom reports you can create the report you want and get the data you need in just a few seconds.
  Custom reports are part of the main user interface. You can access them in just one click :

  

  As you can see from above the interface is straightforward, just indicate the name of your report and start to select the dimensions and metrics you would like to see.

  See all the possible combinations to create the report you desire

  As a user the big question has always been, how much data does Piwik collect and where can I find a list of all those data points ? Here you have the solution. Piwik is gathering in custom reports all the possible combinations so you can select only the data you want :

  

  Creating such a report is going to take you no more than a minute. As with any reports within Piwik, you can easily get information regarding the specific data you are using by hovering your mouse on the question mark next to each dimension and metric :

  

  Make new combinations which were not directly available in Piwik

  By default, not all combinations are possible within the Piwik user interface. Now thanks to Custom Reports, you can easily design the report you want. Here is for example a report crossing page titles and page url :

  

  You can then identify if there are any duplicate titles within your content and see the associated URL in a single report.

  You could also identify easily what are your most viewed entry page from Google :

  

  Custom reports can also be used with segments and filters in order to get even more specific data.
  Here we have an example of a custom report designed to take into consideration only the visits coming from Wikipedia :

  

  What is the next step ?

  As you understood it, Piwik custom reports is the must-have plugin in order to take your Piwik to the next level. Why wait ? Piwik custom reports are available through the marketplace.

  Get Custom Reports

  If you are not sure yet, you can always give it a try within our Piwik Cloud infrastructure.