Recherche avancée

Sur d’autres sites (13579)

• ffmpeg rtsp stream to YouTube livestream not doing anything

  29 mai 2018, par felixosth

  I’m using C# to initiate ffmpeg. I’ve a onvif bridge server for a CCTV VMS and I’m building a application to enable the user to livestream any CCTV camera to YouTube.

  The rtsp stream to the camera looks like this :

  rtsp ://onvif:bridge@localhost:554/live/xxxxx-xxxguidtocameraxxx-xxxxx

  I’m new to ffmpeg and I’m using this arg :

  -f lavfi -i anullsrc -rtsp_transport udp -i camerastreamurl -tune zerolatency -vcodec libx264 -pix_fmt + -c:v copy -c:a aac -strict experimental -f flv rtmp ://x.rtmp.youtube.com/live2/streamkey -loglevel debug

  It seems like ffmpeg isn’t finding the camera stream, only the fake audio one. It just freezes.

  This is the result of the debug log :

  ffmpeg version N-91172-gebf85d3190 Copyright (c) 2000-2018 the FFmpeg developers
  
    built with gcc 7.3.0 (GCC)
  
    configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-bzlib --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth
  
    libavutil      56. 18.102 / 56. 18.102
  
    libavcodec     58. 19.104 / 58. 19.104
  
    libavformat    58. 17.100 / 58. 17.100
  
    libavdevice    58.  4.100 / 58.  4.100
  
    libavfilter     7. 24.100 /  7. 24.100
  
    libswscale      5.  2.100 /  5.  2.100
  
    libswresample   3.  2.100 /  3.  2.100
  
    libpostproc    55.  2.100 / 55.  2.100
  
  Splitting the commandline.
  
  Reading option '-f' ... matched as option 'f' (force format) with argument 'lavfi'.
  
  Reading option '-i' ... matched as input url with argument 'anullsrc'.
  
  Reading option '-rtsp_transport' ... matched as AVOption 'rtsp_transport' with argument 'udp'.
  
  Reading option '-i' ... matched as input url with argument 'rtsp://onvif:bridge@localhost:554/live/41cf4f34-e137-4559-8278-47d912c64c5b'.
  
  Reading option '-tune' ... matched as AVOption 'tune' with argument 'zerolatency'.
  
  Reading option '-vcodec' ... matched as option 'vcodec' (force video codec ('copy' to copy stream)) with argument 'libx264'.
  
  Reading option '-pix_fmt' ... matched as option 'pix_fmt' (set pixel format) with argument '+'.
  
  Reading option '-c:v' ... matched as option 'c' (codec name) with argument 'copy'.
  
  Reading option '-c:a' ... matched as option 'c' (codec name) with argument 'aac'.
  
  Reading option '-strict' ...Routing option strict to both codec and muxer layer
  
   matched as AVOption 'strict' with argument 'experimental'.
  
  Reading option '-f' ... matched as option 'f' (force format) with argument 'flv'.
  
  Reading option 'rtmp://x.rtmp.youtube.com/live2/xxxxxxxx' ... matched as output url.
  
  Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument 'debug'.
  
  Finished splitting the commandline.
  
  Parsing a group of options: global .
  
  Applying option loglevel (set logging level) with argument debug.
  
  Successfully parsed a group of options.
  
  Parsing a group of options: input url anullsrc.
  
  Applying option f (force format) with argument lavfi.
  
  Successfully parsed a group of options.
  
  Opening an input file: anullsrc.
  
  detected 8 logical cores
  
  [AVFilterGraph @ 0000027a34bad7c0] query_formats: 2 queried, 3 merged, 0 already done, 0 delayed
  
  [Parsed_anullsrc_0 @ 0000027a34badb80] sample_rate:44100 channel_layout:'stereo' nb_samples:1024
  
  [lavfi @ 0000027a34babc80] All info found
  
  Input #0, lavfi, from 'anullsrc':
  
    Duration: N/A, start: 0.000000, bitrate: 705 kb/s
  
      Stream #0:0, 1, 1/44100: Audio: pcm_u8, 44100 Hz, stereo, u8, 705 kb/s
  
  Successfully opened the file.
  
  Parsing a group of options: input url rtsp://onvif:bridge@localhost:554/live/41cf4f34-e137-4559-8278-47d912c64c5b.
  
  Successfully parsed a group of options.
  
  Opening an input file: rtsp://onvif:bridge@localhost:554/live/41cf4f34-e137-4559-8278-47d912c64c5b.
  
  [tcp @ 0000027a34bb5980] No default whitelist set

  Edit :
  I’m getting this result with minimal args :
  

• Developers and vendors : Want a Matomo Hoodie ? Add a tag to the Matomo Open Source Tag Manager and this could be yours !

  7 juin 2018, par Matomo Core Team — Community, Development

  The Free Open Source Tag Manager is now available as a public beta on the Matomo Marketplace. Don’t know what a Tag Manager is ? Learn more here. In Short : It lets you easily manage all your third party JavaScript and HTML snippets (analytics, ads, social media, remarketing, affiliates, etc) through a single interface.

  Over the last few months we have worked on building the core for the Matomo Tag Manager which comes with a great set of features and a large set of pre-configured triggers and variables. However, we currently lack tags.

  This is where we need your help ! Together we can build a complete and industry leading open source tag manager.

  Tag examples include Google AdWords Conversion Tracking, Facebook Buttons, Facebook Pixels, Twitter Universal Website Tags, LinkedIn Insights.

  Are you a developer who is familiar with JavaScript and keen on adding a tag ? Or are you a vendor ? Don’t be shy, we appreciate any tags, even analytics related :) We have documented how to develop a new tag here, which is quite easy and straightforward. You may also need to understand a tiny bit of PHP but you’ll likely be fine even if you don’t (here is an example PHP file and the related JS file).

  As we want to ship the Matomo Tag Manager with as many tags as possible out of the box, we appreciate any new tag additions as a pull request on https://github.com/matomo-org/tag-manager.

  We will send out “Matomo Contributor” stickers that cannot be purchased anywhere for every contributor who contributes a tag within the next 3 months. As for the top 3 contributors… you’ll receive a Matomo hoodie ! Simply send us an email at hello@matomo.org after your tag has been merged. If needed, a draw will decide who gets the hoodies.

  FYI : The Matomo Tag Manager is already prepared to be handled in different contexts and we may possibly generate containers for Android and iOS. If you are keen on building the official Matomo SDKs for any of these mobile platforms, please get in touch.

  

• Thinking about switching to GeoIP2 for better location detection ? Here’s what you should know

  5 juin 2018, par Matomo Core Team

  In Matomo 3.5.0 we added a new feature to improve the location detection (country, region, city) of your visitors. Especially when it comes to IPv6 addresses, you will see less “Unknown” locations and more accurate results in general. This feature is now enabled for all new installations but needs to be manually enabled for existing Matomo self-hosted users.

  

  Why is the Matomo plugin not enabled for existing users ?

  When you enable the GeoIP2 plugin, a database update will need to be executed on two datatable tables (“log_visit” and “log_conversion”) which stores some of the raw data. Please be aware that this update could take several hours depending on the size of your database.

  If you store many visits in your database, it is recommended to execute the update through the command line by executing the command ./console core:update to avoid the update from timing out. You may also have to put your Matomo into maintenance mode during this time and replay the missed traffic from logs afterwards as explained in the FAQ article.

  GeoIP2 may slow down your tracking

  In the past we have seen that a few Matomo databases with high traffic volumes struggle to handle all the tracking requests after enabling GeoIP2. The reason for this is the location database now contains many more entries because it has to store all the IPv6 addresses and the database itself has a different format. Hence, the location lookup takes longer.

  It is hard to say how much slower the location lookup gets, but we found GeoIP2-PHP is about 20 times slower than GeoIP1-PHP. On a fast CPU the lookup time for an IP with GeoIP2 takes about 1ms, but can also take much longer depending on the server.

  Making location lookups fast again

  There is a PHP extension available that makes lookups very fast, even faster than the old GeoIP1-PHP provider. If you can install additional PHP extensions on your server and have a high traffic website, you may want to install the GeoIP2 extension.

  There is also an Nginx module and an Apache module. Unfortunately, we don’t have any performance metrics for these providers.

  How do I activate the GeoIP2 location provider ?

  As a Super User, log in to your Matomo and go to “Administration => Plugins”. There you can activate the “GeoIP2” plugin. As mentioned, this will trigger a database update which can take a while and you may want to perform this update through the command line.

  Now you can go to “Administration => Geolocation”. Here you will first need to install the GeoIP2 databases at the bottom of the page before you can activate the GeoIP2-PHP provider. To activate any of the other GeoIP2 providers, you will need to install the required modules.

  You will be able to check if the detection works on the right next to location provider. Once you selected one of the available providers, you’re all good to go.

  The post Thinking about switching to GeoIP2 for better location detection ? Here’s what you should know appeared first on Analytics Platform - Matomo.