Recherche avancée

Sur d’autres sites (7752)

• Intel QuickSync error : Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height

  30 novembre 2018, par Arie Syamsudin

  I want to make IPTV with a topology like this :

  Restream / source -----> IPTV server -----> User

  The problem at the moment is the question of bandwidth that is still large.

  Finally I announced by IPTV software providers to transcode with Intel QuickSync video and FFmpeg.

  I followed the steps given by the software provider at the following link :
  http://www.ezhometech.com/document/intel_ffmpeg.txt

  Which comes from the link below :
  https://www.intel.com/content/dam/www/public/us/en/documents/white-paper...

  I installed IPTV software on a laptop with an Intel processor, chipset and VGA.

  [root@iptv ffmpeg-4.1]# **lspci**
  
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
  
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
  
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
  
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
  
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
  
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
  
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5)
  
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
  
  00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 05)
  
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port Mobile SATA AHCI Controller (rev 05)
  
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
  
  01:00.0 Ethernet controller: Qualcomm Atheros AR8152 v2.0 Fast Ethernet (rev c1)
  
  02:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
  
  
  
  [root@iptv ffmpeg-4.1]# **lspci -nn -s 0:02.0**
  
  00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09)

  but when I do a transcoding test, an error always appears :
  Error initializing output stream 0:0 — Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height.

  Error details :
  https://paste.fedoraproject.org/paste/vp9XIzbeOuyXRuLBlLfSng

  FFmpeg log :

  ./ffmpeg  -hwaccel qsv -i http://premium-play.org:8000/domm0H56Cj/q3ODLP6C16/2826 -vcodec h264_qsv -acodec copy -b:v 1200K -f mpegts udp://127.0.0.1:9011?pkt_size=1316
  
  ffmpeg version 3.2.12 Copyright (c) 2000-2018 the FFmpeg developers
  
    built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-28)
  
    configuration: --enable-libmfx --enable-nonfree
  
    libavutil      55. 34.101 / 55. 34.101
  
    libavcodec     57. 64.101 / 57. 64.101
  
    libavformat    57. 56.101 / 57. 56.101
  
    libavdevice    57.  1.100 / 57.  1.100
  
    libavfilter     6. 65.100 /  6. 65.100
  
    libswscale      4.  2.100 /  4.  2.100
  
    libswresample   2.  3.100 /  2.  3.100
  
  Input #0, mpegts, from 'http://premium-play.org:8000/domm0H56Cj/q3ODLP6C16/2826':
  
    Duration: N/A, start: 30200.274878, bitrate: N/A
  
    Program 1
  
      Metadata:
  
        service_name    : Service01
  
        service_provider: FFmpeg
  
      Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], 50 fps, 50 tbr, 90k tbn, 100 tbc
  
      Stream #0:1[0x101]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 48000 Hz, stereo, fltp, 125 kb/s
  
  libva info: VA-API version 1.0.0
  
  libva info: va_getDriverName() returns 0
  
  libva info: User requested driver 'iHD'
  
  libva info: Trying to open /opt/intel/mediasdk/lib64/iHD_drv_video.so
  
  libva info: Found init function __vaDriverInit_1_0
  
  libva info: va_openDriver() returns 0
  
  [h264_qsv @ 0x2a89500] Selected ratecontrol mode is not supported by the QSV runtime. Choose a different mode.
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 (native) -> h264 (h264_qsv))
  
    Stream #0:1 -> #0:1 (copy)
  
  Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height

• Vagrant provision fails to execute the next script without an obvious reason why

  14 juin 2016, par JakeTheSnake

  I’ve created/co-opted several bash scripts to provision my guest Ubuntu 14.04 OS ; the one giving me trouble right now is installing ffmpeg. When the script finishes, vagrant simply does nothing save for sending SSH keep-alives.

  Host OS : Windows 7 x64

  The last output before the infinitely repeating keep-alives is :

  INSTALL libavutil/sha.h
  
  INSTALL libavutil/sha512.h
  
  INSTALL libavutil/stereo3d.h
  
  INSTALL libavutil/threadmessage.h
  
  INSTALL libavutil/time.h
  
  INSTALL libavutil/timecode.h
  
  INSTALL libavutil/timestamp.h
  
  INSTALL libavutil/tree.h
  
  INSTALL libavutil/twofish.h
  
  INSTALL libavutil/version.h
  
  INSTALL libavutil/xtea.h
  
  INSTALL libavutil/tea.h
  
  INSTALL libavutil/lzo.h
  
  INSTALL libavutil/avconfig.h
  
  INSTALL libavutil/ffversion.h
  
  
  
  DEBUG ssh: stdout: INSTALL      libavutil/libavutil.pc
  
  
  
  DEBUG ssh: stdout: Done
  
  
  
  DEBUG ssh: Sending SSH keep-alive...
  
  DEBUG ssh: Sending SSH keep-alive...
  
  DEBUG ssh: Sending SSH keep-alive...

  Here are the relevant scripts :

  Vagrantfile

  # -*- mode: ruby -*-
  
  # vi: set ft=ruby :
  
  
  
  # All Vagrant configuration is done below. The "2" in Vagrant.configure
  
  # configures the configuration version (we support older styles for
  
  # backwards compatibility). Please don't change it unless you know what
  
  # you're doing.
  
  Vagrant.configure(2) do |config|
  
    # The most common configuration options are documented and commented below.
  
    # For a complete reference, please see the online documentation at
  
    # https://docs.vagrantup.com.
  
  
  
    # Every Vagrant development environment requires a box. You can search for
  
    # boxes at https://atlas.hashicorp.com/search.
  
    config.vm.box = 'ubuntu/trusty64'
  
    config.vm.hostname = 'dev'
  
  
  
    config.ssh.forward_agent = true
  
    config.ssh.pty = true
  
  
  
    # Create a private network, which allows host-only access to the machine
  
    # using a specific IP.
  
    config.vm.network :private_network, type: :dhcp, auto_config: false
  
  
  
    # Create a public network, which generally matched to bridged network.
  
    # Bridged networks make the machine appear as another physical device on
  
    # your network.
  
    config.vm.network :public_network,
  
                      ip: '192.168.11.14',
  
                      bridge: 'Realtek PCIe GBE Family Controller'
  
  
  
    # Share an additional folder to the guest VM. The first argument is
  
    # the path on the host to the actual folder. The second argument is
  
    # the path on the guest to mount the folder. And the optional third
  
    # argument is a set of non-required options.
  
    #
  
    # Do not share root directory of vagrant
  
    # config.vm.synced_folder '.', '/vagrant', disabled: true
  
    # Share ruby repository directories
  
    config.vm.synced_folder '.',
  
                            '/home/vagrant/apps',
  
                            nfs: true,
  
                            mount_options: [
  
                              'nfsvers=3',
  
                              'vers=3',
  
                              'actimeo=1',
  
                              'rsize=8192',
  
                              'wsize=8192',
  
                              'timeo=14',
  
                              :nolock,
  
                              :udp,
  
                              :intr,
  
                              :user,
  
                              :auto,
  
                              :exec,
  
                              :rw
  
                            ]
  
  
  
    # Provider-specific configuration so you can fine-tune various
  
    # backing providers for Vagrant. These expose provider-specific options.
  
    # Example for VirtualBox:
  
    #
  
    config.vm.provider :virtualbox do |vb|
  
      # Display the VirtualBox GUI when booting the machine
  
      vb.gui = true
  
  
  
      # Use VBoxManage to customize the VM.
  
      vb.name = 'Ubuntu'
  
      vb.cpus = 4
  
      vb.memory = 2048
  
      vb.customize ['modifyvm', :id, '--vram', 64]
  
      vb.customize ['modifyvm', :id, '--audio', :dsound]
  
      vb.customize ['modifyvm', :id, '--audiocontroller', :ac97]
  
      vb.customize ['modifyvm', :id, '--clipboard', :bidirectional]
  
    end
  
  
  
    # Provisioning
  
    config.vm.provision :shell, path: './provisioning/user/install-apps.sh',
  
                                privileged: false, name: 'Applications'
  
    config.vm.provision :shell, path: './provisioning/user/install-rvm.sh',
  
                                args: 'stable', privileged: false, name: 'RVM'
  
    config.vm.provision :shell, path: './provisioning/user/install-ruby.sh',
  
                                args: '2.3.1', privileged: false, name: 'Ruby'
  
    config.vm.provision :shell, path: './provisioning/user/install-ruby-gems.sh',
  
                                privileged: false, name: 'Ruby Gems'
  
    config.vm.provision :shell, path: './provisioning/root/install-nginx.sh',
  
                                args: '1.9.9', name: 'Nginx'
  
  
  
    config.vm.provision :chef_solo do |chef|
  
      # chef.version = '12.10.40'
  
  
  
      # Paths to your cookbooks (on the host)
  
      chef.cookbooks_path = ['cookbooks']
  
      # Add chef recipes
  
      chef.add_recipe 'apt'
  
      chef.add_recipe 'git' # Is required for NPM
  
      chef.add_recipe 'sqlite'
  
      chef.add_recipe 'mysql'
  
      chef.add_recipe 'nodejs'
  
      chef.add_recipe 'memcached'
  
      chef.add_recipe 'imagemagick'
  
      chef.add_recipe 'optipng'
  
      chef.add_recipe 'sublime-text'
  
      chef.add_recipe 'tomcat'
  
    end
  
  end

  install-apps.sh

  #!/usr/bin/env bash
  
  
  
  echo Turning off console beeps...
  
  grep '^set bell-style none' /etc/inputrc || echo 'set bell-style none' >> /etc/inputrc
  
  
  
  echo Installing languages
  
  sudo apt-get -y update
  
  sudo locale-gen en_US en_US.UTF-8
  
  sudo dpkg-reconfigure locales
  
  
  
  echo Installing essential apps
  
  sudo apt-get -y install build-essential curl yasm
  
  
  
  echo Installing desktop apps
  
  sudo apt-get -y install ubuntu-desktop
  
  
  
  hash ffmpeg 2>/dev/null || {
  
    # Build ffmpeg
  
    echo Installing ffmpeg
  
  
  
    sudo apt-get -y install autoconf automake libass-dev libfreetype6-dev \
  
      libsdl1.2-dev libtheora-dev libtool libva-dev libvdpau-dev libvorbis-dev libxcb1-dev libxcb-shm0-dev \
  
      libxcb-xfixes0-dev pkg-config texinfo zlib1g-dev libx264-dev libmp3lame-dev libopus-dev
  
  
  
    mkdir ~/ffmpeg_sources
  
    cd ~/ffmpeg_sources
  
    wget http://ffmpeg.org/releases/ffmpeg-snapshot.tar.bz2
  
    tar xjvf ffmpeg-snapshot.tar.bz2
  
    cd ffmpeg
  
    PATH="$HOME/bin:$PATH" PKG_CONFIG_PATH="$HOME/ffmpeg_build/lib/pkgconfig" ./configure \
  
      --prefix="$HOME/ffmpeg_build" \
  
      --pkg-config-flags="--static" \
  
      --extra-cflags="-I$HOME/ffmpeg_build/include" \
  
      --extra-ldflags="-L$HOME/ffmpeg_build/lib" \
  
      --bindir="$HOME/bin" \
  
      --enable-gpl \
  
      --enable-libass \
  
      --enable-libfreetype \
  
      --enable-libmp3lame \
  
      --enable-libopus \
  
      --enable-libtheora \
  
      --enable-libvorbis \
  
      --enable-libx264 \
  
      --enable-nonfree
  
  
  
    PATH="$HOME/bin:$PATH" make
  
    make install
  
    make distclean
  
    hash -r
  
  
  
    source ~/.profile
  
  }
  
  
  
  echo Done
  
  exit 0

  install-rvm.sh

  #!/usr/bin/env bash
  
  
  
  echo Installing RVM gpg key
  
  gpg --keyserver hkp://keys.gnupg.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 --trust-model always
  
  
  
  echo Installing RVM
  
  \curl -sSL https://get.rvm.io | bash -s $1
  
  
  
  exit 0

  I won’t include the other scripts for the sake of brevity. When logging into vagrant with the gui nothing seems out of the ordinary, and ffmpeg is available...but nothing else is provisioned. No RVM, no Nginx, nothing.

• Data Privacy Day 2020

  27 janvier 2020, par Matthieu Aubry — Privacy
  It’s January 28th which means it’s Data Privacy Day !

  Today is an important day for the Matomo team as we reflect on our mission and our goals for 2020. This year I wanted to send a video message to all Matomo users, community members and customers. 

  Check it out (full transcript below)

  

  A video message from Matomo founder, Matthieu Aubry

  Privacy-friendly alternatives

  • NoMoreGoogle :
    a comprehensive list giving you options for other privacy-friendly alternatives.
  • Switching.Software :
    Ethical alternatives to popular sites and apps.
  • Web browser :
    Firefox
    Brave
    Vivaldi
  • Search engine :
    DuckDuckGo
    Qwant
  • File sharing :
    Nextcloud
  • Email provider :
    ProtonMail
    Mailfence
    Tutanota

  Video transcript

  Hey everyone,

  Matthieu here, Founder of Matomo.

  Today is one of the most significant days of the year for the Matomo team – it’s Data Privacy Day. And so I wanted to quickly reflect on our mission and the significance of this day. 

  In today’s busy online world where data is king, this day is an important reminder of being vigilant in protecting our personal information online.

  Matomo began 12 years ago as an open-source alternative to Google Analytics – the goal was, and still is to give full control of data back to users. 

  In 2020, we are determined to see through this commitment. We will keep building a powerful and ethical web analytics platform that focuses on privacy protection, data ownership, and provides value to all Matomo users and customers.

  And what’s fantastic is to see the rise of other quality software companies offering privacy-friendly alternatives for web browsers, search engines, file sharing, email providers, all with a similar mission. And with these products now widely available, we encourage you to take back control of all your online activities and begin this new decade with a resolution to stay safe online.

  I’ll provide you with some links below the video to check out these privacy-friendly alternatives. If you have a website and want to gain valuable insights on the visitors while owning your data, join us ! 

  Matomo Analytics On-Premise is and always will be free to download and install on your own servers and on your own terms.

  Also feel free to join our active community or spread the word to your friends and network about the importance of data privacy.

  Thank you all and wishing you a great 2020 !

  For more information on how Matomo protects the privacy of your users, visit : https://matomo.org/privacy/

  Do you have privacy concerns ?

  What better day than today to speak up ! What privacy concerns have you experienced ?

  Contact Support