Recherche avancée

Sur d’autres sites (4791)

• Pros and cons of installing ffmpeg into the caller's docker container vs. separate container [closed]

  8 mai 2022, par Irina Rapoport

  I have a dockerized app that spawns ffmpeg in a child process. It then communicates with it via standard input/output. The app runs under k3d.

  


  I could install ffmpeg in the parent's Dockerfile, by doing

  


  RUN apt-get install -y ffmpeg


  


  Or I can run it in a container of its own. What are the pros and cons of each approach ?

  


  Container start-up cost, while small, may become an issue, because it's started often.

  


• Stopping Referrer Spam

  13 mai 2015, par Piwik Core Team — Community

  In this blog post we explain what is Referrer spam, this new kind of spam that has recently appeared on the Internet. We also provide solutions to stop it and preserve the quality of your analytics data.

  What is Referrer Spam ?

  Referrer spam (also known as log spam or referrer bombing) is a kind of spamming aimed at web analytics tools. A spammer bot makes repeated web site requests using a fake referrer URL to the site the spammer wishes to advertise.

  Here is an example of referrer spam in action :

  

  Half of those referrers are spams, here are some well know spammers that you may have seen in your logs : buttons-for-you-website.com, best-seo-offer.com, semalt.com…

  The benefit for spammers is that their website will appear in analytics tools like Piwik or Google Analytics :

  • public analytics reports (or logs) will be indexed by search engines : links to the spammer’s website will improve its ranking
  • curious webmasters are likely to visit their referrers, thus bringing traffic to the spammer’s website

  How to deal with Referrer Spam ?

  Referrer spam is still new and analytics tools are all handling it differently.

  Referrer Spam in Piwik

  At Piwik we started working on mitigating Referrer spam more than a year ago. If you use Piwik and keep it up to date, you do not need to do anything.

  Referrer spammers are automatically excluded from your reports to keep your data clean and useful.

  New spammers are continuously detected and added to Piwik’s blacklist on each update. If you find a new spammer in your analytics data, you can even report it so that it is added to the Piwik’s open referrer blacklist and blocked for everyone.

  Referrer Spam in Google Analytics

  Google Analytics doesn’t offer any spam protection by default. It can however be configured manually using a custom Filter.

  To create a filter in Google Analytics go to the Admin section and click on All Filters. Create a new custom filter that excludes based on the Campaign Source field. In the Filter pattern enter the spammers domains you want to exclude (this is a regular expression) :

  

  If new spammers arise you will need to update this list. You can also use Piwik’s referrer blacklist to exclude all the spammers currently detected.

  Other Analytics Tools

  Many web analytics tools do not yet handle Referrer spam and when using these tools, you will often find a lot of spam data in your Referrer Websites analytics reports.

  If you use an analytics tool that does not exclude Referrer spam, we recommend to contact the vendor and ask them to implement a mechanism to remove these referrer spammers. As of today many analytics vendors still have not mitigated this issue.

  Public List of Referrer Spammers

  At Piwik with the help of our large community we have decided to tackle this growing spam issue. We have created a list of up to date referrer spammers that anyone can edit.

  The list is available in a simple text file on Github : github.com/piwik/referrer-spam-blacklist.

  The list is released under the Public Domain and anyone can use it within their applications to exclude referrer spammers.

  Many people have already contributed new spammers to the list. We invite you to use the list in your apps and websites and help us keep the list up to date !

  Let’s unite and fight the spammers together.

  Happy Analytics !

• How to make QProcess stop by button or keyboard in GUI ?

  31 août 2015, par xiaowei

  Here I want to make a recorder by ffmpeg.exe.

  And, I found the commend line, succeed running and generate the video file. And I know press "Esc" or "q" on keyboard can terminal

  Now, I want to use GUI to control the recoder(ffmpeg.exe). I select Qt here, and my work environment is windows 7 sp1.

  I use QProcess to execute it, you will see following.

  But I have no idea for terminal the process.

  The code list :
  main.cpp is simple.

  #include "mainwindow.h"
  
  #include <qapplication>
  
  
  
  int main(int argc, char *argv[])
  
  {
  
      QApplication a(argc, argv);
  
      MainWindow w;
  
      w.show();
  
  
  
      return a.exec();
  
  }
  
  </qapplication>

  mainwindow.h

  #ifndef MAINWINDOW_H
  
  #define MAINWINDOW_H
  
  
  
  #include <qmainwindow>
  
  #include <qprocess>
  
  
  
  namespace Ui {
  
  class MainWindow;
  
  }
  
  
  
  class MainWindow : public QMainWindow
  
  {
  
      Q_OBJECT
  
  
  
  public:
  
      explicit MainWindow(QWidget *parent = 0);
  
      ~MainWindow();
  
  
  
  private:
  
      QProcess *pro;
  
      QString recorder;
  
      QString outputName;
  
      QString options;
  
  
  
  private slots:
  
      void startRecode();
  
      void stopRecode();
  
  };
  
  
  
  #endif // MAINWINDOW_H
  
  </qprocess></qmainwindow>

  mainwindow.cpp

  #include "mainwindow.h"
  
  
  
  #include <qprocess>
  
  #include <qtest>
  
  #include <qpushbutton>
  
  #include <qvboxlayout>
  
  
  
  MainWindow::MainWindow(QWidget *parent) :
  
      QMainWindow(parent),
  
      pro(new QProcess)
  
  {
  
      QDateTime current_date_time = QDateTime::currentDateTime();
  
      QString current_date = current_date_time.toString("yyyy-MM-dd-hh_mm_ss");
  
  
  
      recorder = "E:\\bin\\ffmpeg.exe";
  
      outputName = current_date + ".mp4";
  
      options = "-f gdigrab -framerate 6 -i desktop -vcodec libx264 -preset:v ultrafast -tune:v zerolatency -hide_banner -report";
  
      //-t 00:00:05"; this option can limit the process running time, and work well no GUI, but I don't want to use given time to stop recording.
  
  
  
      QWidget *centerWindow = new QWidget;
  
      setCentralWidget(centerWindow);
  
  
  
      QVBoxLayout *mainLayout = new QVBoxLayout;
  
      QPushButton *startButton = new QPushButton("start recording");
  
      QPushButton *stopButton = new QPushButton("stop recording");
  
      mainLayout->addWidget(startButton);
  
      mainLayout->addWidget(stopButton);
  
  
  
      centerWindow->setLayout(mainLayout);
  
  
  
      connect(startButton, SIGNAL(clicked()), this, SLOT(startRecode()));
  
      connect(stopButton, SIGNAL(clicked()), this, SLOT(stopRecode()));
  
  }
  
  
  
  MainWindow::~MainWindow()
  
  {
  
      delete pro;
  
  }
  
  
  
  void MainWindow::startRecode()
  
  {
  
      pro->execute(QString(recorder + " " +options +" " + outputName));
  
  }
  
  
  
  void MainWindow::stopRecode(){
  
      pro->terminate(); // not work
  
      //pro->close(); // not work, too
  
      //pro->kill(); // not work, T_T
  
  
  
      //how to terminate the process by pushbutton??
  
  }
  
  </qvboxlayout></qpushbutton></qtest></qprocess>

  There have some ideas for me ?

  or, have other solutions for my recorder ?