Recherche avancée

Sur d’autres sites (8211)

• avfilter/palettegen : switch to signed arithmetic

  27 décembre 2022, par Clément Bœsch

  avfilter/palettegen : switch to signed arithmetic
  This prevents mixed sign arithmetic (typically because we have signed
  
  color channel differences), which has nasty side effects in C.
  

  • [DH] libavfilter/vf_palettegen.c

• WordPress Analytics plugin WP-Piwik reaches version 1.0.0 (and 50,000 active users)

  29 mai 2015, par André Bräkling — Plugins

  After six years of development, we are proud to announce the 1.0.0 release of our WP-Piwik WordPress plugin !

  Started as a simple plugin to show a selection of statistics within the WordPress dashboard, WP-Piwik has become a full Piwik integration plugin. The plugin automatically adds the Piwik tracking code to your WordPress sites. The plugin displays your analytics reports directly within the WordPress admin panel. WordPress networks (“multisite”), CDN URLs and the Piwik proxy script are also supported.

  According to WordPress.org the plugin is being used by more than 50,000 WordPress sites !

  

  This article explains how to install WP-Piwik and how to configure it to work with your Piwik instance.
  

  Install WP-Piwik

  You can get WP-Piwik using WordPress’ plugin management. Login to your WordPress admin dashboard and go to « Plugins » → « Add New ». Enter « WP-Piwik » into the search field at the top right, press enter and next to WP-Piwik choose « Install Now ».

  

  If you want to use WP-Piwik in your simple WordPress blog you can just click « Activate Plugin » and WP-Piwik will ask you to configure your Piwik connection.

  Running a WordPress network/multisite you can choose to « Network Activate » the plugin after the installation process. In this case, WP-Piwik will be a fully automated feature of your WordPress network automatically tracking your sites in the same Piwik instance in separate Websites.

  Alternatively you can download WP-Piwik manually from the WordPress website and upload all files to your `wp-content/plugins` directory.

  Configure your Piwik connection

  WP-Piwik lets you choose between three connection modes :

  • Self-hosted (HTTP API) : This is the default option for a self-hosted Piwik and should work for most configurations. You just have to know your Piwik URL, which is the URL you enter to access Piwik, and your auth token (see below). WP-Piwik will connect to Piwik using http(s)-requests.
  • Self-hosted (PHP API) : Choose this, if your self-hosted Piwik and WordPress are running on the same machine and you know the full server path to your Piwik instance. Beside the full server path, you also need to know your auth token (see below).
  • Cloud-hosted (Piwik Pro) : If you are using a cloud-hosted Piwik by Piwik Pro, you just need to know your user name and your auth token (see below).

  Setting up WP-Piwik

  To configure WP-Piwik you will need to specify your Authentication token.

  • If the site you want to track in Piwik is already configured in your Piwik, you only need to specify a token_auth for a user with `view` permission.
  • If you want WP-Piwik to create the website in Piwik (or if you use WP-Piwik in network mode which requires to be able to configure your sites), you should specify a token_auth which has Super User access (after the setting up phase is completed you can set the authentication token back to the token of a `view` user).

  To find your token_auth in Piwik, click on your user name in the right right corner of your Piwik dashboard, then click the « API » in the left menu. The API page displays your auth token in a colored box, just behind the “&token_auth=” string. The screenshot below shows the token_auth anonymous, but your real one will be an alpha numerous random string like a1ec31524a8eabc7a546d71d68b28d17.

  

  That’s it. After you entered your connection data and submitted the form, WP-Piwik will welcome you with some information :

  

  You can now start to configure WP-Piwik and enable the tracking code. Learn about any setting by clicking on the small question mark sign. If you have any problem configuring or using WP-Piwik feel free to use the WordPress support forum related to WP-Piwik.

  Translating WP-Piwik

  We invite you to join our translation community at Transifex and help to translate WP-Piwik in more languages !

  Happy WordPress Analytics !

• FFMPEG Without Headers is Causing Video To Be Height 0X0

  21 novembre 2022, par Devin Dixon

  I am grabbing a stream from X11 and streaming it to other sources like Node Media Server and Twitch. Except, I get audio only with no video and the resolution size says 0X0.

  


  My ffmpeg is command is this :

  


   /usr/bin/ffmpeg -hide_banner -hwaccel vaapi -hwaccel_output_format vaapi -vaapi_device /dev/dri/renderD128 -video_size 1920x1080 -y -v info -f x11grab -draw_mouse 0 -r 60 -s 1920x1080 -thread_queue_size 14000 -i :0.0+0,0 -f alsa -thread_queue_size 14000 -i plug:bsnoop -acodec aac -strict -2 -ar 44100 -b:a 128k -af aresample=async=1 -c:v h264_vaapi -vf format=nv12,hwupload,scale_vaapi=w=1920:h=1080 -attempt_recovery 1 -max_recovery_attempts 2 -drop_pkts_on_overflow 1 -video_size 1920x1080 -crf 19 -preset medium -maxrate 14000k -bufsize 14000k -r 60 -crf 25 -g 120 -tune zerolatency -f flv rtmp://[some_other_source]


  


  The ffmpeg output is as follows :

  


  2022-11-21 13:42:45.527 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: Codec AVOption crf (Select the quality for constant quality mode) specified for output file #0 (rtmp://[some_other_sorce]) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some encoder which was not actually used for any stream.
2022-11-21 13:42:45.527 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: Codec AVOption tune (The metric that the encoder tunes for. Automatically chosen by the encoder by default) specified for output file #0 (rtmp://[some_other_source]) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some encoder which was not actually used for any stream.
2022-11-21 13:42:45.527 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: Codec AVOption preset (Encoding preset) specified for output file #0 (rtmp://relay.bingewave.com/live/e3057272-271d-40d5-90d1-f9065c5dfa37-broadcast?sign=1669642928-17aa73baeaedaad786140b5b2cca9d2b) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some encoder which was not actually used for any stream.
2022-11-21 13:42:45.527 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: Codec AVOption preset (Encoding preset) specified for output file #1 (rtmp://127.0.0.1:1935/live/e3057272-271d-40d5-90d1-f9065c5dfa37-broadcast?sign=1669642928-17aa73baeaedaad786140b5b2cca9d2b) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some encoder which was not actually used for any stream.
2022-11-21 13:42:45.527 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: Codec AVOption tune (The metric that the encoder tunes for. Automatically chosen by the encoder by default) specified for output file #1 (rtmp://127.0.0.1:1935/live/['for_reording']) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some encoder which was not actually used for any stream.
2022-11-21 13:42:45.550 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: Codec AVOption crf (Select the quality for constant quality mode) specified for output file #1 (rtmp://127.0.0.1:1935/live/e3057272-271d-40d5-90d1-f9065c5dfa37-broadcast?sign=1669642928-17aa73baeaedaad786140b5b2cca9d2b) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some encoder which was not actually used for any stream.
2022-11-21 13:42:45.550 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: Stream mapping:
2022-11-21 13:42:45.550 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:   Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (h264_vaapi))
2022-11-21 13:42:45.550 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:   Stream #1:0 -> #0:1 (pcm_s16le (native) -> aac (native))
2022-11-21 13:42:45.550 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:   Stream #0:0 -> #1:0 (rawvideo (native) -> h264 (h264_vaapi))
2022-11-21 13:42:45.550 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:   Stream #1:0 -> #1:1 (pcm_s16le (native) -> mp3 (libmp3lame))
2022-11-21 13:42:45.550 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: Press [q] to stop, [?] for help
2022-11-21 13:42:45.550 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: [h264_vaapi @ 0x55a02df06980] No quality level set; using default (20).
2022-11-21 13:42:45.550 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: [h264_vaapi @ 0x55a02df06980] Buffering settings are ignored in CQP RC mode.
2022-11-21 13:42:45.550 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: [h264_vaapi @ 0x55a02df06980] Driver does not support some wanted packed headers (wanted 0xd, found 0).
2022-11-21 13:42:45.550 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: [h264_vaapi @ 0x55a02df06980] Driver does not support packed sequence headers, but a global header is requested.
2022-11-21 13:42:45.583 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: [h264_vaapi @ 0x55a02df06980] No global header will be written: this may result in a stream which is not usable for some purposes (e.g. not muxable to some containers).
2022-11-21 13:42:45.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: [h264_vaapi @ 0x55a02df0a700] Driver does not support some wanted packed headers (wanted 0xd, found 0).
2022-11-21 13:42:45.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: [h264_vaapi @ 0x55a02df0a700] Driver does not support packed sequence headers, but a global header is requested.
2022-11-21 13:42:45.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: [h264_vaapi @ 0x55a02df0a700] No global header will be written: this may result in a stream which is not usable for some purposes (e.g. not muxable to some containers).
2022-11-21 13:42:45.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: Output #0, flv, to 'rtmp://relay.bingewave.com/live/[some_other_source]':
2022-11-21 13:42:45.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:   Metadata:
2022-11-21 13:42:45.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:     encoder         : Lavf59.27.100
2022-11-21 13:42:45.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:   Stream #0:0: Video: h264 (High) ([7][0][0][0] / 0x0007), vaapi(tv, progressive), 1920x1080, q=2-31, 60 fps, 1k tbn
2022-11-21 13:42:45.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:     Metadata:
2022-11-21 13:42:45.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:       encoder         : Lavc59.37.100 h264_vaapi
2022-11-21 13:42:45.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:   Stream #0:1: Audio: aac (LC) ([10][0][0][0] / 0x000A), 44100 Hz, stereo, fltp, 128 kb/s
2022-11-21 13:42:45.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:     Metadata:
2022-11-21 13:42:45.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:       encoder         : Lavc59.37.100 aac
2022-11-21 13:42:46.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: Output #1, flv, to 'rtmp://127.0.0.1:1935/live/e3057272-271d-40d5-90d1-f9065c5dfa37-broadcast?sign=1669642928-17aa73baeaedaad786140b5b2cca9d2b':
2022-11-21 13:42:46.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:   Metadata:
2022-11-21 13:42:46.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:     encoder         : Lavf59.27.100
2022-11-21 13:42:46.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:   Stream #1:0: Video: h264 (High) ([7][0][0][0] / 0x0007), vaapi(tv, progressive), 1920x1080, q=2-31, 15000 kb/s, 60 fps, 1k tbn
2022-11-21 13:42:46.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:     Metadata:
2022-11-21 13:42:46.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:       encoder         : Lavc59.37.100 h264_vaapi
2022-11-21 13:42:46.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:   Stream #1:1: Audio: mp3 ([2][0][0][0] / 0x0002), 48000 Hz, stereo, s16p
2022-11-21 13:42:46.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:     Metadata:
2022-11-21 13:42:46.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42:       encoder         : Lavc59.37.100 libmp3lame
2022-11-21 13:42:46.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: frame=    1 fps=0.0 q=-0.0 q=-0.0 size=       7kB time=00:00:00.06 bitrate= 875.5kbits/s speed=1.31x    
2022-11-21 13:42:46.584 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: frame=   31 fps=0.0 q=-0.0 q=-0.0 size=     281kB time=00:00:00.55 bitrate=4133.2kbits/s speed=1.01x    
2022-11-21 13:42:47.325 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: frame=   60 fps= 57 q=-0.0 q=-0.0 size=     546kB time=00:00:01.18 bitrate=3774.7kbits/s speed=1.12x    
2022-11-21 13:42:47.325 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: frame=   91 fps= 58 q=-0.0 q=-0.0 size=     828kB time=00:00:01.69 bitrate=4003.3kbits/s speed=1.08x    
2022-11-21 13:42:47.325 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: [flv @ 0x55a02df10e00] Failed to update header with correct duration.
2022-11-21 13:42:47.325 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: [flv @ 0x55a02df10e00] Failed to update header with correct filesize.
2022-11-21 13:42:47.325 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: [flv @ 0x55a02df15500] Failed to update header with correct duration.
2022-11-21 13:42:47.325 INFO: [658] LoggingUtils$Companion$OutputLogger$1.invoke$lambda-0#42: [flv @ 0x55a02df15500] Failed to update header with correct filesize.


  


  I've noticed there are several errors the headers going out. For VAAPI, how do I set resolution header ?