Recherche avancée

Sur d’autres sites (11015)

• lavfi : make filter_frame non-recursive.

  3 janvier 2016, par Nicolas George

  lavfi : make filter_frame non-recursive.
  A lot of changes happen at the same time :
   Add a framequeue fifo to AVFilterLink.
   split AVFilterLink.status into status_in and status_out : requires
  
    changes to the few filters and programs that use it directly
  
    (f_interleave, split, filtfmts).
   Add a field ready to AVFilterContext, marking when the filter is ready
  
    and its activation priority.
   Add flags to mark blocked links.
   Change ff_filter_frame() to enqueue the frame.
   Change all filtering functions to update the ready field and the
  
    blocked flags.
   Update ff_filter_graph_run_once() to use the ready field.
   buffersrc : always push the frame immediately.
  

  • [DH] libavfilter/avfilter.c
  • [DH] libavfilter/avfilter.h
  • [DH] libavfilter/avfiltergraph.c
  • [DH] libavfilter/buffersink.c
  • [DH] libavfilter/buffersrc.c
  • [DH] libavfilter/f_interleave.c
  • [DH] libavfilter/internal.h
  • [DH] libavfilter/split.c
  • [DH] libavfilter/tests/filtfmts.c
  • [DH] libavfilter/vf_extractplanes.c

• Data Privacy Day 2021 : Five ways to embrace privacy into your business

  27 janvier 2021, par Matomo Core Team — Community, Privacy

  Welcome to Data Privacy Day 2021 !

  This year we are excited to announce that we are participating as a #PrivacyAware Champion for DPD21 through the National Cyber Security Alliance. This means that on this significant day we are in partnership with hundreds of other organisations and businesses to share a unified message that empowers individuals to “Own Your Privacy” and for organisations to “Respect Privacy.”

  "Last year dawned a new era in the way many businesses operate from a traditional office work setting to a remote working from home environment for employees. This now means it’s more important than ever for your employees to understand how to take ownership of their privacy when working online."

  As a Data Privacy Day #PrivacyAware Champion we would like to provide some practical tips and share examples of how the Matomo team helps employees be privacy aware.

  

  Five ways to embrace privacy into your business

  1. Create a privacy aware culture within your business

  • Get leadership involved.
  • Appoint privacy ambassadors within your team. 
  • Create a privacy awareness campaign where you educate employees on your company privacy policy. 
  • Share messages about privacy around the office/or in meetings online, on internal message boards, in company newsletters, or emails. 
  • Teach new employees their role in your privacy culture and reinforce throughout their career.

  2. Organise privacy awareness training for your employees

  • Invite outside speakers to talk to employees about why privacy matters. 
  • Engage staff by asking them to consider how privacy and data security applies to the work they do on a daily basis.
  • Encourage employees to complete online courses to gain a better understanding of how to avoid privacy risks.

  3. Help employees manage their individual privacy

  • Better security and privacy behaviours at home will translate to better security and privacy practices at work. 
  • Teach employees how to update their privacy and security settings on personal accounts.
  • Use NCSA’s privacy settings page to help them get started

  4. Add privacy to the employee’s toolbox

  • Give your employees actual tools they can use to improve their privacy, such as company-branded camera covers or privacy screens for their devices, or virtual private networks (VPNs) to secure their connections.

  5. Join Matomo and we’ll be your web analytics experts

  • At Matomo, ensuring our users and customers that their privacy is protected is not only a core component of the work we do, it’s why we do what we do ! Find out how.

  Want to find out more about data privacy download your free DPD 2021 Champion Toolkit and read our post on “Why is privacy important”.

  Team Matomo

  2021 Data Privacy Day Toolkit

  Your guide to Data Privacy Day, January 28, 2021

  Free Download

• How can I improve the up-time of my coffee pot live stream ?

  26 avril 2017, par tww0003

  Some Background on the Project :

  Like most software developers I depend on coffee to keep me running, and so do my coworkers. I had an old iPhone sitting around, so I decided to pay homage to the first webcam and live stream my office coffee pot.

  The stream has become popular within my company, so I want to make sure it will stay online with as little effort possible on my part. As of right now, it will occasionally go down, and I have to manually get it up and running again.

  My Setup :

  I have nginx set up on a digital ocean server (my nginx.conf is shown below), and downloaded an rtmp streaming app for my iPhone.

  The phone is set to stream to example.com/live/stream and then I use an ffmpeg command to take that stream, strip the audio (the live stream is public and I don’t want coworkers to feel like they have to be careful about what they say), and then make it accessible at rtmp://example.com/live/coffee and example.com/hls/coffee.m3u8.

  Since I’m not too familiar with ffmpeg, I had to google around and find the appropriate command to strip the coffee stream of the audio and I found this :
  

  ffmpeg -i rtmp://localhost/live/stream -vcodec libx264 -vprofile baseline -acodec aac -strict -2 -f flv -an rtmp://localhost/live/coffee

  Essentially all I know about this command is that the input stream comes from, localhost/live/stream, it strips the audio with -an, and then it outputs to rtmp://localhost/live/coffee.

  I would assume that ffmpeg -i rtmp://localhost/live/stream -an rtmp://localhost/live/coffee would have the same effect, but the page I found the command on was dealing with ffmpeg, and nginx, so I figured the extra parameters were useful.

  What I’ve noticed with this command is that it will error out, taking the live stream down. I wrote a small bash script to rerun the command when it stops, but I don’t think this is the best solution.

  Here is the bash script :

  while true;
  
  do
  
          ffmpeg -i rtmp://localhost/live/stream -vcodec libx264 -vprofile baseline -acodec aac -strict -2 -f flv -an rtmp://localhost/live/coffee
  
          echo 'Something went wrong. Retrying...'
  
          sleep 1
  
  done

  I’m curious about 2 things :

  1. What is the best way to strip audio from an rtmp stream ?
  2. What is the proper configuration for nginx to ensure that my rtmp stream will stay up for as long as possible ?

  Since I have close to 0 experience with nginx, ffmpeg, and rtmp streaming any help, or tips would be appreciated.

  Here is my nginx.conf file :

  worker_processes  1;
  
  
  
  events {
  
      worker_connections  1024;
  
  }
  
  
  
  
  
  http {
  
      include       mime.types;
  
      default_type  application/octet-stream;
  
  
  
      sendfile        on;
  
  
  
      keepalive_timeout  65;
  
  
  
      server {
  
          listen       80;
  
          server_name  localhost;
  
  
  
          location / {
  
              root   html;
  
              index  index.html index.htm;
  
          }
  
  
  
          error_page   500 502 503 504  /50x.html;
  
          location = /50x.html {
  
              root   html;
  
          }
  
  
  
          location /stat {
  
                  rtmp_stat all;
  
                  rtmp_stat_stylesheet stat.xsl;
  
                  allow 127.0.0.1;
  
          }
  
          location /stat.xsl {
  
                  root html;
  
          }
  
          location /hls {
  
                  root /tmp;
  
                  add_header Cache-Control no-cache;
  
          }
  
          location /dash {
  
                  root /tmp;
  
                  add_header Cache-Control no-cache;
  
                  add_header Access-Control-Allow-Origin *;
  
          }
  
      }
  
  }
  
  
  
  rtmp {
  
  
  
      server {
  
  
  
          listen 1935;
  
          chunk_size 4000;
  
  
  
          application live {
  
              live on;
  
  
  
              hls on;
  
              hls_path /tmp/hls;
  
  
  
              dash on;
  
              dash_path /tmp/dash;
  
          }
  
      }
  
  }

  edit :
  I’m also running into this same issue : https://trac.ffmpeg.org/ticket/4401