Recherche avancée

Sur d’autres sites (8498)

• Ffmpeg : Scale+crop video then overlay image ?

  8 juillet 2019, par skitzo

  This is my first SO question. Help me help you help me : does this question need any clarification ?

  Goal : A script that makes Instagram-ready videos with audio, and a logo overlay. The script takes in an audio and video source and combines them. Important : the logo should have a consistent position and size for each video. This probably means that all output videos should have the same width x height.

  Any alternate approaches are welcome !

  The ffmpeg command I’m calling from python is below. I try to scale the video to 720 :-2 (so auto-height), then crop a 500x500 square from the center. The choices of 720 and 500 are arbitrary ; better approaches are welcome.

  ffmpeg -i video.mp4 -i logo.png -i audio.mp3 -filter_complex "[0:v]scale=720:-2,crop=500:500[bg];[bg][1:v] overlay=(W-w)/2:(H-h)/2" -pix_fmt yuv420p -map 0:v -map 2:a -shortest + output.mp4

  This script errors on some videos.

  [Parsed_crop_1 @ 0x7fcf96401f00] Invalid too big or non positive size for width '500' or height '500'
  
  [Parsed_crop_1 @ 0x7fcf96401f00] Failed to configure input pad on Parsed_crop_1

  I’m new to ffmpeg so please guide me to correct usage of filter_complex. Thank you !

• 'arecord' works but FFMPEG 'cannot open audio device'

  16 mai 2020, par kwithnail

  On my Linux-based QNAP NAS, I can successfully record my Loopback audio device using :

  



  # arecord -D default:CARD=Loopback test.wav


  



  However, FFMPEG cannot use this same audio device. It returns :

  



      [alsa @ 0x5a45880] cannot open audio device hw:default:CARD=Loopback (No such file or directory)
hw:default:CARD=Loopback: Input/output error


  



  I've also tried any number of hw: options in FFMPEG. For what it's worth, the arecord -l command returns :

  



  **** List of CAPTURE Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC262 Analog [ALC262 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM]
  Subdevices: 1/1
  Subdevice #0: subdevice #0


  



  arecord -L returns :

  



  [~] # arecord -L
null
    Discard all samples (playback) or generate zero samples (capture)
sysdefault:CARD=PCH
    HDA Intel PCH, ALC262 Analog
    Default Audio Device
front:CARD=PCH,DEV=0
    HDA Intel PCH, ALC262 Analog
    Front speakers
sysdefault:CARD=Loopback
    Loopback, Loopback PCM
    Default Audio Device
front:CARD=Loopback,DEV=0
    Loopback, Loopback PCM
    Front speakers
surround21:CARD=Loopback,DEV=0
    Loopback, Loopback PCM
    2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=Loopback,DEV=0
    Loopback, Loopback PCM
    4.0 Surround output to Front and Rear speakers
surround41:CARD=Loopback,DEV=0
    Loopback, Loopback PCM
    4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=Loopback,DEV=0
    Loopback, Loopback PCM
    5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=Loopback,DEV=0
    Loopback, Loopback PCM
    5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=Loopback,DEV=0
    Loopback, Loopback PCM
    7.1 Surround output to Front, Center, Side, Rear and Woofer speakers


  



  FFMPEG command and response is :

  



  [~] # /share/CACHEDEV1_DATA/.qpkg/ffmpeg/ffmpeg -f alsa -i hw:default:CARD=Loopback test.mp3
ffmpeg version 4.2.1-static https://johnvansickle.com/ffmpeg/  Copyright (c) 2000-2019 the FFmpeg developers
  built with gcc 6.3.0 (Debian 6.3.0-18+deb9u1) 20170516
  configuration: --enable-gpl --enable-version3 --enable-static --disable-debug --disable-ffplay --disable-indev=sndio --disable-outdev=sndio --cc=gcc-6 --enable-fontconfig --enable-frei0r --enable-gnutls --enable-gmp --enable-libgme --enable-gray --enable-libaom --enable-libfribidi --enable-libass --enable-libvmaf --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librubberband --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libvorbis --enable-libopus --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libdav1d --enable-libxvid --enable-libzvbi --enable-libzimg
  libavutil      56. 31.100 / 56. 31.100
  libavcodec     58. 54.100 / 58. 54.100
  libavformat    58. 29.100 / 58. 29.100
  libavdevice    58.  8.100 / 58.  8.100
  libavfilter     7. 57.100 /  7. 57.100
  libswscale      5.  5.100 /  5.  5.100
  libswresample   3.  5.100 /  3.  5.100
  libpostproc    55.  5.100 / 55.  5.100
ALSA lib ../../../src/pcm/pcm.c:2564:(snd_pcm_open_noupdate) Unknown PCM hw:default:CARD=Loopback
[alsa @ 0x5f64800] cannot open audio device hw:default:CARD=Loopback (No such file or directory)
hw:default:CARD=Loopback: Input/output error


  



  FFMPEG -sources alsa gives :

  



  [~] # /share/CACHEDEV1_DATA/.qpkg/ffmpeg/ffmpeg -sources alsa
ffmpeg version 4.2.1-static https://johnvansickle.com/ffmpeg/  Copyright (c) 2000-2019 the FFmpeg developers
  built with gcc 6.3.0 (Debian 6.3.0-18+deb9u1) 20170516
  configuration: --enable-gpl --enable-version3 --enable-static --disable-debug --disable-ffplay --disable-indev=sndio --disable-outdev=sndio --cc=gcc-6 --enable-fontconfig --enable-frei0r --enable-gnutls --enable-gmp --enable-libgme --enable-gray --enable-libaom --enable-libfribidi --enable-libass --enable-libvmaf --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librubberband --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libvorbis --enable-libopus --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libdav1d --enable-libxvid --enable-libzvbi --enable-libzimg
  libavutil      56. 31.100 / 56. 31.100
  libavcodec     58. 54.100 / 58. 54.100
  libavformat    58. 29.100 / 58. 29.100
  libavdevice    58.  8.100 / 58.  8.100
  libavfilter     7. 57.100 /  7. 57.100
  libswscale      5.  5.100 /  5.  5.100
  libswresample   3.  5.100 /  3.  5.100
  libpostproc    55.  5.100 / 55.  5.100
Auto-detected sources for alsa:
ALSA lib ../../../src/control/control.c:1375:(snd_ctl_open_noupdate) Invalid CTL hw:0
Cannot list sources.


  



  Can anyone shed some light on why this is impossible in FFMPEG and suggest what I'm doing wrong here ? FFMPEG includes the ALSA module, and is version 4.2.1. Thanks !

  


• How to sell Piwik services without any confusion ?

  10 octobre 2017, par InnoCraft — Plugins

  As you may know, Piwik is a Free software under the GPL license which guarantees you :

  • The freedom to run the program for any purpose.
  • The freedom to study how it works and change it.
  • The freedom to improve the program, and release your changes.
  • The freedom to redistribute it under the GPL license, and to sell it if you wish.

  In this article we will focus on the Free aspect of Piwik, which is how to rebrand Piwik, how to offer your clients a better experience, and possibly how to make a profit from it ?

  How to sell Piwik services as an agency ?

  As a web analytics software, Piwik is often installed by web agencies when it comes to designing a brand new website for a given customer.
  Most of the time agencies are using Piwik for the following reasons :

  • free of charge
  • data ownership
  • user privacy compliance
  • feature rich while easy to use
  • open source

  Most of the agencies are charging their customers for the installation process, tracking code implementation, analysing reports to get insights about users… but do you know that you could also sell the software as your own brand ? This is where the “White Label” plugin, developed by the InnoCraft company, comes into play.

  White labelling for Piwik

  Creating a “white label” plugin came into the mind of InnoCraft founders when they realized that on any modern Piwik installation, the following components were visible :

  • Piwik branded widgets within the dashboards
  • Piwik marketplace plugin teasers on the admin page
  • Piwik help and support pages
  • the “Piwik” word in general
  • Piwik Mobile app banners

  

  Example of Piwik branded widgets

  In order to remove all those mentions of Piwik and to start selling this web analytics under your own name, you can either hack Piwik on your own (it is going to take you some precious time and money) or have a look at the White Label plugin on the marketplace where InnoCraft has solved all the challenges already for you.

  The White Label plugin is straightforward. Once downloaded and installed, you will have access to a dedicated interface where you will be able to change the Piwik name by a new custom brand of your choice :

  

  Piwik White Label settings

  Once you click Save, all “Piwik” mentions will be substituted by your company name/service :

  

  Here the Piwik version is changed by the name of the company

  How to make your installation even more customized ?

  Few Piwik users know about this trick, but since 2014 the Piwik templates can be customized through Themes. You are free to design your own template, installing existing ones, or even monetize them through the marketplace :

  

  A simple example of how Piwik can be easily customized, here fonts and colours are changed

  If you want to know how you can tweak your existing template and make it match your brand and image, just follow our theme documentation. A simple theme with your colors can be built in a few minutes simply by defining different color codes. You can also browse the public themes on the Marketplace.

  Get White Label for Piwik

  Tell us your story

  If you are an agency or any business related in selling Piwik services, we recommend having a look at our FAQ for rebranding, selling, reusing, re-licensing, and including Piwik in my offering. Are you interested or already re-selling Piwik services ? We would love to hear your story and write a blog post about it.

  Write for Piwik

  Do not hesitate to contact the Piwik core team, we’re looking forward to hearing from you.