Recherche avancée

Sur d’autres sites (6551)

• hwcontext_vaapi : Try to support the VDPAU wrapper

  30 janvier 2017, par Mark Thompson

  hwcontext_vaapi : Try to support the VDPAU wrapper
  The driver is somewhat bitrotten (not updated for years) but is still
  
  usable for decoding with this change.  To support it, this adds a new
  
  driver quirk to indicate no support at all for surface attributes.
  Based on a patch by wm4 <nfxjfg@googlemail.com>.
  

  • [DBH] libavutil/hwcontext_vaapi.c
  • [DBH] libavutil/hwcontext_vaapi.h

• How to install a Matomo premium feature

  31 janvier 2018, par InnoCraft

  You may have noticed over the last few months that many fantastic new features have been launched on the Matomo Marketplace. As some of them are paid premium features, you may wonder if the process to install them is straightforward, if you can test them before, and whether there is any support behind it. No worries – we’ve got you covered ! This blog post will answer some questions you may have about getting your first premium plugin.

  So why are there some premium features ?

  Researching, building, documenting, testing and maintaining quality products take years of experience and months of hard work by the team behind the scenes. When you purchase a premium plugin, you get a fully working product and you directly help the Matomo core engineers to grow and fund the new Free Matomo versions and cool features.

  However, it is important for us to mention that Matomo will always be free, it is a Free software under GPLv3 license and it will always be the same.
  Want to know more about this ? Check out our FAQ about why there are premium features.

  Can I test a premium feature before a purchase ?

  Absolutely. There are two ways in order to do that :

  1. InnoCraft Matomo Cloud
  2. Matomo Marketplace

  1. InnoCraft Matomo Cloud

  The easiest way is to create a free trial account (one minute of your time) on our Matomo cloud service. You will then have the possibility to test all the premium features during a 30-day trial period. No credit card is required.

  

  Every premium feature can be trialled for free on the Matomo Cloud

  2. Matomo Marketplace

  The second way is to get the premium feature from the Matomo Marketplace. We have an easy and hassle-free 30-day money back guarantee period on each feature. This means that if you are not happy with a premium feature and you are within the 30-day period, then you will get a full refund for it. Guaranteed !

  How to purchase and install a premium feature ?

  Step 1 : Purchasing the feature

  In order to get a premium feature, just add it to the cart :

  

  Once done, go to your cart and complete the checkout process to confirm the order.

  When the order is confirmed, you immediately get your license key on the order confirmation page. You also receive the license key by email.

  Step 2 : Activating the feature in your Matomo

  Now that you have received the license key, it is time to activate the plugin in your Matomo :

  • Log in to your Matomo and go to “Administration => Marketplace
  • Copy / paste the license key into the license field at the top of the page and click “Activate”

  

  • The key will now be activated and you will see a couple of new buttons.

  

  • To install the premium feature(s) you just purchased in one click, simply click on “Install purchased plugins”. Alternatively, you can scroll down in the Marketplace to the premium feature you purchased and click on “Install”. You can also download the ZIP file on https://shop.matomo.org/my-account/downloads

  And that’s it. The installation of a premium feature is as easy as copy/pasting the license key and clicking a button. Because one license key is linked to all purchased premium features, you only need to enter the license key once. The next time you purchase a premium feature, you simply click on “Install” to have it up and running.

  Updating a premium feature

  Updates for premium features work just like regular plugin updates. When there is a new update available, you will see a notification in the Matomo UI and also receive an email (if enabled under “General Settings”). To upgrade the feature simply click on “Update” and you’re done.

  Which support is provided for each of those premium features ?

  Premium features represent most of our day to day activity, so you can be 100% sure that we will do our maximum in order to answer any of your questions regarding them. To be 100% transparent, we often receive answers from our customers telling us how impressed they are by the quality of the service we are offering.

  Have any questions ?

  We are happy to answer any questions you may have so feel free to get in touch with us.

  Thanks !

  The post How to install a Matomo premium feature appeared first on Analytics Platform - Matomo.

• FFMPEG concat videos

  10 juin 2015, par Maverick

  I am unable to concat two videos using FFMPEG. The command fails on the two special videos.

  Video 1 :
  First video is generated from the image using the following command :

  ffmpeg -loop 1 -i 20150608_162807.jpg -c:v libx264 -t 3 -pix_fmt yuv420p out.mp4

  I tried to concat the above video but it did not work so, I thought to add an audio to check if it will work.

  ffmpeg -f lavfi -i aevalsrc=0 -i out.mp4 -shortest -c:v copy -c:a aac -strict experimental silent.mp4

  but even with that it did not work.

  Video 2 :
  Second video is captured from the device camera.

  Both of these videos can be downloaded from here.

  06-09 11:05:56.238  29771-30715/﹕ ffmpeg -i concat:/storage/emulated/0/DCIM/Camera/20150603_142209.mp4|/storage/emulated/0/DCIM/Camera/silent.mp4 -c copy /storage/emulated/0/DCIM/test/MIU-2015-06-09 11-05-56.mp4
  
  06-09 11:05:56.268  29771-30739/﹕ WARNING: linker: ffmpeg has text relocations. This is wasting memory and prevents security hardening. Please fix.
  
  06-09 11:05:56.278  29771-30739/﹕ ffmpeg version n2.4.2 Copyright (c) 2000-2014 the FFmpeg developers
  
  06-09 11:05:56.278  29771-30739/﹕ built on Apr  8 2015 11:29:21 with gcc 4.8 (GCC)
  
  06-09 11:05:56.278  29771-30739/﹕ configuration: --target-os=linux --cross-prefix=/ilovevideo/jobs/ffmpeg-android-build-publisher/workspace/ffmpeg-android/toolchain-android/bin/arm-linux-androideabi- --arch=arm --cpu=cortex-a8 --enable-runtime-cpudetect --sysroot=/ilovevideo/jobs/ffmpeg-android-build-publisher/workspace/ffmpeg-android/toolchain-android/sysroot --enable-pic --enable-libx264 --enable-libass --enable-libfreetype --enable-libfribidi --enable-fontconfig --enable-pthreads --disable-debug --disable-ffserver --enable-version3 --enable-hardcoded-tables --disable-ffplay --disable-ffprobe --enable-gpl --enable-yasm --disable-doc --disable-shared --enable-static --pkg-config=/ilovevideo/jobs/ffmpeg-android-build-publisher/workspace/ffmpeg-android/ffmpeg-pkg-config --prefix=/ilovevideo/jobs/ffmpeg-android-build-publisher/workspace/ffmpeg-android/build/armeabi-v7a --extra-cflags='-I/ilovevideo/jobs/ffmpeg-android-build-publisher/workspace/ffmpeg-android/toolchain-android/include -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-strict-overflow -fstack-protector-all' --extra-ldflags='-L/ilovevideo/jobs/ffmpeg-android-build-publisher/workspace/ffmpeg-android/toolchain-android/lib -Wl,-z,relro -Wl,-z,now -pie' --extra-libs='-lpng -lexpat -lm' --extra-cxxflags=
  
  06-09 11:05:56.278  29771-30739/﹕ libavutil      54.  7.100 / 54.  7.100
  
  06-09 11:05:56.278  29771-30739/﹕ libavcodec     56.  1.100 / 56.  1.100
  
  06-09 11:05:56.288  29771-30739/﹕ libavformat    56.  4.101 / 56.  4.101
  
  06-09 11:05:56.288  29771-30739/﹕ libavdevice    56.  0.100 / 56.  0.100
  
  06-09 11:05:56.288  29771-30739/﹕ libavfilter     5.  1.100 /  5.  1.100
  
  06-09 11:05:56.288  29771-30739/﹕ libswscale      3.  0.100 /  3.  0.100
  
  06-09 11:05:56.288  29771-30739/﹕ libswresample   1.  1.100 /  1.  1.100
  
  06-09 11:05:56.288  29771-30739/﹕ libpostproc    53.  0.100 / 53.  0.100
  
  06-09 11:05:56.308  29771-30739/﹕ [mov,mp4,m4a,3gp,3g2,mj2 @ 0xb5e5a400] Found duplicated MOOV Atom. Skipped it
  
  06-09 11:05:56.398  29771-30739/﹕ Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'concat:/storage/emulated/0/DCIM/Camera/20150603_142209.mp4|/storage/emulated/0/DCIM/Camera/silent.mp4':
  
  06-09 11:05:56.398  29771-30739/﹕ Metadata:
  
  06-09 11:05:56.398  29771-30739/﹕ creation_time   : 2015-06-03 12:22:15
  
  06-09 11:05:56.398  29771-30739/﹕ major_brand     : isom
  
  06-09 11:05:56.398  29771-30739/﹕ minor_version   : 512
  
  06-09 11:05:56.398  29771-30739/﹕ compatible_brands: isomiso2avc1mp41
  
  06-09 11:05:56.398  29771-30739/﹕ Duration: 00:00:04.80, start: 0.000000, bitrate: 13040 kb/s
  
  06-09 11:05:56.398  29771-30739/﹕ Stream #0:0(eng): Video: h264 (Baseline) (avc1 / 0x31637661), yuv420p, 1280x720, 12008 kb/s, 29.88 fps, 29.92 tbr, 90k tbn, 180k tbc (default)
  
  06-09 11:05:56.398  29771-30739/﹕ Metadata:
  
  06-09 11:05:56.398  29771-30739/﹕ creation_time   : 2015-06-03 12:22:15
  
  06-09 11:05:56.398  29771-30739/﹕ handler_name    : VideoHandle
  
  06-09 11:05:56.408  29771-30739/﹕ Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 256 kb/s (default)
  
  06-09 11:05:56.408  29771-30739/﹕ Metadata:
  
  06-09 11:05:56.408  29771-30739/﹕ creation_time   : 2015-06-03 12:22:15
  
  06-09 11:05:56.408  29771-30739/﹕ handler_name    : SoundHandle
  
  06-09 11:05:56.408  29771-30739/﹕ Output #0, mp4, to '/storage/emulated/0/DCIM/iLoveVideo/MIU-2015-06-09 11-05-56.mp4':
  
  06-09 11:05:56.408  29771-30739/﹕ Metadata:
  
  06-09 11:05:56.408  29771-30739/﹕ compatible_brands: isomiso2avc1mp41
  
  06-09 11:05:56.408  29771-30739/﹕ major_brand     : isom
  
  06-09 11:05:56.408  29771-30739/﹕ minor_version   : 512
  
  06-09 11:05:56.408  29771-30739/﹕ encoder         : Lavf56.4.101
  
  06-09 11:05:56.418  29771-30739/﹕ Stream #0:0(eng): Video: h264 ([33][0][0][0] / 0x0021), yuv420p, 1280x720, q=2-31, 12008 kb/s, 29.88 fps, 90k tbn, 90k tbc (default)
  
  06-09 11:05:56.418  29771-30739/﹕ Metadata:
  
  06-09 11:05:56.418  29771-30739/﹕ creation_time   : 2015-06-03 12:22:15
  
  06-09 11:05:56.418  29771-30739/﹕ handler_name    : VideoHandle
  
  06-09 11:05:56.418  29771-30739/﹕ Stream #0:1(eng): Audio: aac ([64][0][0][0] / 0x0040), 48000 Hz, stereo, 256 kb/s (default)
  
  06-09 11:05:56.418  29771-30739/﹕ Metadata:
  
  06-09 11:05:56.418  29771-30739/﹕ creation_time   : 2015-06-03 12:22:15
  
  06-09 11:05:56.418  29771-30739/﹕ handler_name    : SoundHandle
  
  06-09 11:05:56.418  29771-30739/﹕ Stream mapping:
  
  06-09 11:05:56.418  29771-30739/﹕ Stream #0:0 -> #0:0 (copy)
  
  06-09 11:05:56.418  29771-30739/﹕ Stream #0:1 -> #0:1 (copy)
  
  06-09 11:05:56.418  29771-30739/﹕ Press [q] to stop, [?] for help
  
  06-09 11:05:56.548  29771-30739/﹕ frame=  142 fps=0.0 q=-1.0 Lsize=    7121kB time=00:00:04.80 bitrate=12153.1kbits/s
  
  06-09 11:05:56.558  29771-30739/﹕ video:6965kB audio:150kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.078725%

  Update 1 :
  The concat protocol doesn’t work with mp4s. So, I tried the other approaches.

  ffmpeg -i input1.mp4 -c copy -bsf:v h264_mp4toannexb -f mpegts intermediate1.ts
  
  ffmpeg -i input2.mp4 -c copy -bsf:v h264_mp4toannexb -f mpegts intermediate2.ts 
  
  ffmpeg -i "concat:intermediate1.ts|intermediate2.ts" -c copy -bsf:a aac_adtstoasc output.mp4

  but still it didn’t work.

  Update 2 :
  I have also used concat demuxer approach but it did not work as well.