Recherche avancée

Sur d’autres sites (15071)

• FFMPEG, DrawText Issue in Live Stream

  7 décembre 2022, par Kenneth

  I am using the following command to create an H264 stream with text data from a text file. Example data is fake. I am sending this to an RTSP server that then allows clients to connect. I am connecting from VLC to view the stream.

  


  See update, this only happens for the live stream. If I output to file, it looks correct.

  


  OS : Windows 10

  


  ffmpeg -f lavfi -re -i color=size=1280x720:rate=1:color=black ^
  -vf drawtext="fontsize=16:fontfile=C\\:/Windows/fonts/consola.ttf:fontcolor=white:textfile='livetext.txt':x=50:y=50: reload=1" ^
  -c:v libx264 -preset ultrafast -tune zerolatency -x264-params keyint=10:min-keyint=10 ^
  -f rtsp rtsp://127.0.0.1:60000/sorting


  


  The issue I am having is that the text shown in the video seems to be limited to 10 rows. On a fresh restart, I get even less. I don't see anything mentioned in the documentation about a limitation on length.

  


  I have tried different -preset and -tune options. Nothing improves this issue.

  


  Are there settings I should adjust to help this ?

  


  

  


  Console Output :

  


  ..\ffmpeg\ffmpeg -f lavfi -re -i color=size=1280x720:rate=5:color=black -vf drawtext="fontsize=20:fontfile=C\\:/Windows/fonts/consola.ttf:fontcolor=white:textfile='livetext.txt':x=50:y=50: reload=5"  -c:v libx264 -preset ultrafast -tune zerolatency -x264-params keyint=10:min-keyint=10  -f rtsp rtsp://127.0.0.1:60000/sorting
ffmpeg version 2022-12-04-git-6c814093d8-essentials_build-www.gyan.dev Copyright (c) 2000-2022 the FFmpeg developers
  built with gcc 12.1.0 (Rev2, Built by MSYS2 project)
  configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-bzlib --enable-lzma --enable-zlib --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-sdl2 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-mediafoundation --enable-libass --enable-libfreetype --enable-libfribidi --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-d3d11va --enable-dxva2 --enable-libvpl --enable-libgme --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libtheora --enable-libvo-amrwbenc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-librubberband
  libavutil      57. 43.100 / 57. 43.100
  libavcodec     59. 54.100 / 59. 54.100
  libavformat    59. 34.102 / 59. 34.102
  libavdevice    59.  8.101 / 59.  8.101
  libavfilter     8. 51.100 /  8. 51.100
  libswscale      6.  8.112 /  6.  8.112
  libswresample   4.  9.100 /  4.  9.100
  libpostproc    56.  7.100 / 56.  7.100
Input #0, lavfi, from 'color=size=1280x720:rate=5:color=black':
  Duration: N/A, start: 0.000000, bitrate: N/A
  Stream #0:0: Video: wrapped_avframe, yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 5 fps, 5 tbr, 5 tbn
Stream mapping:
  Stream #0:0 -> #0:0 (wrapped_avframe (native) -> h264 (libx264))
Press [q] to stop, [?] for help
[libx264 @ 000002402dcca140] using SAR=1/1
[libx264 @ 000002402dcca140] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
[libx264 @ 000002402dcca140] profile Constrained Baseline, level 3.1, 4:2:0, 8-bit
[libx264 @ 000002402dcca140] 264 - core 164 r3101 b093bbe - H.264/MPEG-4 AVC codec - Copyleft 2003-2022 - http://www.videolan.org/x264.html - options: cabac=0 ref=1 deblock=0:0:0 analyse=0:0 me=dia subme=0 psy=1 psy_rd=1.00:0.00 mixed_ref=0 me_range=16 chroma_me=1 trellis=0 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=0 threads=11 lookahead_threads=11 sliced_threads=1 slices=11 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=10 keyint_min=6 scenecut=0 intra_refresh=0 rc=crf mbtree=0 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=0
Output #0, rtsp, to 'rtsp://127.0.0.1:60000/sorting':
  Metadata:
    encoder         : Lavf59.34.102
  Stream #0:0: Video: h264, yuv420p(progressive), 1280x720 [SAR 1:1 DAR 16:9], q=2-31, 5 fps, 90k tbn
    Metadata:
      encoder         : Lavc59.54.100 libx264
    Side data:
      cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: N/A
frame=  485 fps=5.0 q=11.0 size=N/A time=00:01:36.80 bitrate=N/A speed=   1x     0x


  


  Update 1 :

  


  If I output to a file, the text is shown correctly (shown below). If I take out the -re argument for the output to match input rate, I get 150fps, so processing power does not seem to be the issue.

  


  

  


• Matomo SSO options and why is it useful ?

  8 novembre 2017, par Matomo Core Team — Plugins

  Bored with typing again and again different logins and passwords for each service you have access to ? Would you like to add hundreds or thousands of users with different roles to your Matomo (Piwik) at once ? Would you like to save time and effort of managing your users while increasing the security in your business ? Guess what, Matomo has come up with great features to do just that.

  But what is a SSO ?

  Before introducing you to new Matomo (Piwik) features, let me explain what a SSO is.
  SSO is the acronym for Single Sign On. As its name suggests this authentication process allows a user to access multiple applications with one set of login credentials.

  Advantages of using a SSO are numerous :

  • improving security, for example when an employee is leaving your company, how can you check that all his credentials have been removed ?
  • reducing employees time-wasters such as having to enter logins/passwords each time.
  • providing a centralized database for administrators. They can then easily manage permissions of all employees saving them heaps of time.
  • reduces support costs related to authentication / accounts management.

  In order to provide SSO options, two Matomo (Piwik) plugins have been developed and are available on the marketplace :

  • SAML
  • LDAP

  SAML

  

  SAML stands for “Security Assertion Markup Language”, it is a standard in order to exchange authentication and authorization between an identity provider (OneLogin, Okta, Ping Identity, ADFS, Google, Salesforce, SharePoint…) and a service provider.
  An identity provider is an online service that authenticates users on the Internet by using security tokens.

  Are you wondering if your business or organization is using any of these providers ? We recommend to ask your operations team or sysadmin.

  At InnoCraft, we developed a plugin in order to allow SSO with SAML for Matomo (Piwik). It can ensure consistent access control across the enterprise and external providers, potentially reducing support costs related to authentication and accounts management.

  The installation process is straightforward. All you need is to get the SAML premium feature from the marketplace. Once installed, you will access the SAML configuration interface through the admin where you can configure various settings :

  • SAML Status
  • Identity Provider (Entity ID, SSO endpoint info, Public x509 certificate)
  • Just-in-time provisioning and Mapping attributes
  • Access Synchronization
  • Advanced settings

  

  From there you will need to follow our detailed documentation to have it up and running :
  https://matomo.org/docs/login-saml/.
  Once finished, you will then be able to use SAML to authenticate to your Matomo (Piwik) account :

  

  As all premium features, SAML is eligible to a 30-day period money back guarantee, so do not hesitate to have it a try.

  LDAP

  

  LDAP stands for Lightweight Directory Access Protocol. As its names implies LDAP is a directory, hosted on a server, which organizes the data about people in your company.
  Thanks to the LDAP plugin, Matomo (Piwik) can be connected to your LDAP infrastructure and then use all its power in order to give each individual an access with different rights according to their needs.

  Let’s say that you have 1,000 employees within a company and they all need right now an access to the analytics reports in Matomo (Piwik) with different roles. This is what LDAP can do.

  Moreover if your business or organization is already using LDAP, we recommend using the LDAP connector for Matomo (Piwik) for better security, to stop wasting time of your users and sysadmins, and to reduce the costs related to account management.

  You understood it well. LDAP is a plugin which saves a LOT of time within an organization. Here is a preview of the settings part :

  

  LDAP has been developed by the Matomo (Piwik) core team and is available as a Free plugin on the marketplace.

  Try it now within the marketplace

  If you are surprised by the possibilities that Matomo (Piwik) is offering in terms of plugins, the good news is that many other plugins are waiting for you on the marketplace. Check out our premium marketplace which offers state-of-the-art plugins to get the most out of Matomo.

  And if you are a developer feel free to create your own plugin, a detailed documentation is available at : https://developer.matomo.org/guides/getting-started-part-1.

• Progress with rtc.io

  12 août 2014, par silvia

  At the end of July, I gave a presentation about WebRTC and rtc.io at the WDCNZ Web Dev Conference in beautiful Wellington, NZ.

  

  Putting that talk together reminded me about how far we have come in the last year both with the progress of WebRTC, its standards and browser implementations, as well as with our own small team at NICTA and our rtc.io WebRTC toolbox.

  

  One of the most exciting opportunities is still under-exploited : the data channel. When I talked about the above slide and pointed out Bananabread, PeerCDN, Copay, PubNub and also later WebTorrent, that’s where I really started to get Web Developers excited about WebRTC. They can totally see the shift in paradigm to peer-to-peer applications away from the Server-based architecture of the current Web.

  Many were also excited to learn more about rtc.io, our own npm nodules based approach to a JavaScript API for WebRTC.

  

  We believe that the World of JavaScript has reached a critical stage where we can no longer code by copy-and-paste of JavaScript snippets from all over the Web universe. We need a more structured module reuse approach to JavaScript. Node with JavaScript on the back end really only motivated this development. However, we’ve needed it for a long time on the front end, too. One big library (jquery anyone ?) that does everything that anyone could ever need on the front-end isn’t going to work any longer with the amount of functionality that we now expect Web applications to support. Just look at the insane growth of npm compared to other module collections :

  

  For those that – like myself – found it difficult to understand how to tap into the sheer power of npm modules as a font end developer, simply use browserify. npm modules are prepared following the CommonJS module definition spec. Browserify works natively with that and “compiles” all the dependencies of a npm modules into a single bundle.js file that you can use on the front end through a script tag as you would in plain HTML. You can learn more about browserify and module definitions and how to use browserify.

  For those of you not quite ready to dive in with browserify we have prepared prepared the rtc module, which exposes the most commonly used packages of rtc.io through an “RTC” object from a browserified JavaScript file. You can also directly download the JavaScript file from GitHub.

  

  So, I hope you enjoy rtc.io and I hope you enjoy my slides and large collection of interesting links inside the deck, and of course : enjoy WebRTC ! Thanks to Damon, JEeff, Cathy, Pete and Nathan – you’re an awesome team !

  On a side note, I was really excited to meet the author of browserify, James Halliday (@substack) at WDCNZ, whose talk on “building your own tools” seemed to take me back to the times where everything was done on the command-line. I think James is using Node and the Web in a way that would appeal to a Linux Kernel developer. Fascinating !!