Sur d’autres sites (15442)

• Unable to load FFProbe driver for FFmpeg

  4 février 2016, par Kapil Ropalekar

  Hi i am trying to install php-ffmpeg.
  Can someone guide me or correct me in my steps.

  1. I installed the composer on windows and then traversed to my folder i had created to run install ffmpeg cmd

  2. After running this command a composer.json, composer.lock file were created along with a vendor folder.

  3. Later installed the Shared FFMpeg build for 64bit from here

     http://ffmpeg.zeranoe.com/builds/

  and form this folder copied the bin folder to my directory to set the ffmpeg and ffprobe path during create() like this

  $ffmpeg = \FFMpeg\FFMpeg::create([
  
      'ffmpeg.binaries'  => '/vendor/bin/ffmpeg.exe',
  
      'ffprobe.binaries' => '/vendor/bin/ffprobe.exe' 
  
  ]);

  Currently i am getting this error which says :

  "Fatal error: Uncaught exception 'Alchemy\BinaryDriver\Exception\ExecutableNotFoundException' with message 'Executable not found, proposed : /vendor/bin/' in D:\xampp\htdocs\health\vendor\alchemy\binary-driver\src\Alchemy\BinaryDriver\AbstractBinary.php:160 Stack trace: #0 D:\xampp\htdocs\health\vendor\php-ffmpeg\php-ffmpeg\src\FFMpeg\Driver\FFProbeDriver.php(48): Alchemy\BinaryDriver\AbstractBinary::load('/vendor/bin/', NULL, Object(Alchemy\BinaryDriver\Configuration)) #1 D:\xampp\htdocs\health\vendor\php-ffmpeg\php-ffmpeg\src\FFMpeg\FFProbe.php(207): FFMpeg\Driver\FFProbeDriver::create(Array, NULL) #2 D:\xampp\htdocs\health\vendor\php-ffmpeg\php-ffmpeg\src\FFMpeg\FFMpeg.php(117): FFMpeg\FFProbe::create(Array, NULL, NULL) #3 D:\xampp\htdocs\health\ff.php(6): FFMpeg\FFMpeg::create(Array) #4 {main} Next exception 'FFMpeg\Exception\ExecutableNotFoundException' with message 'Unable to load FFProbe' in D:\xampp\htdocs\health\vendor\php-ffmpeg\php-ffmpeg\src\FFMpeg\Driver\FFProbeDriver.php:50 Stack trace: #0 D:\xampp\htdocs\he in D:\xampp\htdocs\health\vendor\php-ffmpeg\php-ffmpeg\src\FFMpeg\Driver\FFProbeDriver.php on line 50".

  So what could i have done wrong or am i missing any steps. Can someone point me to the right direction.

• Streaming to YouTube using FFmpeg Problems

  9 mai 2016, par jason

  I am trying to stream to a live event I have created inside of YouTube. I am trying to stream a already created video. The command I am using is noted below.

  The problem I have is that YouTube is showing the Streaming status as good (picture attached) and it seems to be receiving the data. But there is no sound and no picture in the live event. I’m not sure what the issue could be.

  ffmpeg -re -y -i input.mp4 -vcodec libx264 -b:v 600k -r 25 -s 640x360 -filter:v yadif -ab 64k -ac 1 -ar 44100 -f flv "rtmp://a.rtmp.youtube.com/live2/KEY"

  Image showing YouTube streaming status :

  

  Console output :

  ffmpeg version N-60321-g4d7d9a5 Copyright (c) 2000-2014 the FFmpeg developers
  
    built on Feb  2 2014 22:01:03 with gcc 4.8.2 (GCC)
  
    configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av
  
  isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab
  
  le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetyp
  
  e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena
  
  ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l
  
  ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp
  
  eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-aa
  
  cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavp
  
  ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib
  
    libavutil      52. 63.100 / 52. 63.100
  
    libavcodec     55. 49.101 / 55. 49.101
  
    libavformat    55. 29.101 / 55. 29.101
  
    libavdevice    55.  7.100 / 55.  7.100
  
    libavfilter     4.  1.102 /  4.  1.102
  
    libswscale      2.  5.101 /  2.  5.101
  
    libswresample   0. 17.104 /  0. 17.104
  
    libpostproc    52.  3.100 / 52.  3.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'input.mp4':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: isommp42
  
      creation_time   : 2013-10-24 05:44:23
  
    Duration: 00:41:52.93, start: 0.000000, bitrate: 187 kb/s
  
      Stream #0:0(und): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yu
  
  v420p, 480x360, 89 kb/s, 15 fps, 15 tbr, 30 tbn, 30 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 96
  
   kb/s (default)
  
      Metadata:
  
        creation_time   : 2013-10-24 05:44:39
  
        handler_name    : IsoMedia File Produced by Google, 5-11-2011
  
  [libx264 @ 040fdc40] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX AVX2
  
   FMA3 LZCNT BMI2
  
  [libx264 @ 040fdc40] profile High, level 3.0
  
  [libx264 @ 040fdc40] 264 - core 142 r2389 956c8d8 - H.264/MPEG-4 AVC codec - Cop
  
  yleft 2003-2014 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deb
  
  lock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 m
  
  e_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chro
  
  ma_qp_offset=-2 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1
  
  interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1
  
   b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=75 keyint_min=38 scenec
  
  ut=0 intra_refresh=0 rc_lookahead=40 rc=abr mbtree=1 bitrate=1200 ratetol=1.0 qc
  
  omp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
  Output #0, flv, to 'rtmp://a.rtmp.youtube.com/live2/keyname':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: isommp42
  
      encoder         : Lavf55.29.101
  
      Stream #0:0(und): Video: h264 (libx264) ([7][0][0][0] / 0x0007), yuv420p, 85
  
  4x480, q=-1--1, 1200 kb/s, 1k tbn, 25 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (libmp3lame) ([2][0][0][0] / 0x0002), 44100 Hz,
  
   mono, fltp, 64 kb/s (default)
  
      Metadata:
  
        creation_time   : 2013-10-24 05:44:39
  
        handler_name    : IsoMedia File Produced by Google, 5-11-2011
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 -> libx264)
  
    Stream #0:1 -> #0:1 (aac -> libmp3lame)
  
  Press [q] to stop, [?] for help
  
  frame=    1 fps=0.0 q=0.0 size=       0kB time=00:00:00.39 bitrate=   9.2kbits/s
  
  ...
  
  frame=  463 fps=7.8 q=0.0 size=    1534kB time=00:00:31.66 bitrate= 396.8kbits/s
  
  [flv @ 040fd6e0] Failed to update header with correct duration.
  
  [flv @ 040fd6e0] Failed to update header with correct filesize.
  
  frame=  463 fps=6.8 q=-1.0 Lsize=    2055kB time=00:00:31.79 bitrate= 529.6kbits
  
  /s
  
  video:1778kB audio:249kB subtitle:0 data:0 global headers:0kB muxing overhead 1.
  
  405947%
  
  [libx264 @ 040fdc40] frame I:7     Avg QP: 2.24  size: 44703
  
  [libx264 @ 040fdc40] frame P:153   Avg QP: 0.65  size:  8418
  
  [libx264 @ 040fdc40] frame B:303   Avg QP: 5.74  size:   724
  
  [libx264 @ 040fdc40] consecutive B-frames: 11.9%  2.6%  0.0% 85.5%
  
  [libx264 @ 040fdc40] mb I  I16..4: 66.0% 12.4% 21.6%
  
  [libx264 @ 040fdc40] mb P  I16..4:  4.7%  0.8%  1.5%  P16..4:  6.6%  1.1%  1.1%
  
   0.0%  0.0%    skip:84.2%
  
  [libx264 @ 040fdc40] mb B  I16..4:  0.2%  0.0%  0.1%  B16..8:  3.0%  0.2%  0.1%
  
   direct: 0.6%  skip:95.8%  L0:47.7% L1:49.2% BI: 3.0%
  
  [libx264 @ 040fdc40] final ratefactor: -9.42
  
  [libx264 @ 040fdc40] 8x8 transform intra:11.8% inter:35.4%
  
  [libx264 @ 040fdc40] coded y,uvDC,uvAC intra: 33.7% 11.2% 11.1% inter: 2.6% 1.6%
  
   1.6%
  
  [libx264 @ 040fdc40] i16 v,h,dc,p: 13% 86%  0%  0%
  
  [libx264 @ 040fdc40] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu:  9% 74% 11%  0%  1%  1%  1%
  
   1%  2%
  
  [libx264 @ 040fdc40] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 17% 61%  6%  1%  3%  2%  4%
  
   2%  4%
  
  [libx264 @ 040fdc40] i8c dc,h,v,p: 88% 10%  2%  0%
  
  [libx264 @ 040fdc40] Weighted P-Frames: Y:0.0% UV:0.0%
  
  [libx264 @ 040fdc40] ref P L0: 81.7%  9.4%  8.0%  0.9%
  
  [libx264 @ 040fdc40] ref B L0: 78.9% 20.9%  0.2%
  
  [libx264 @ 040fdc40] ref B L1: 99.1%  0.9%
  
  [libx264 @ 040fdc40] kb/s:471.59
  
  Received signal 2: terminating.

  Edit -

  I have now tested the following codes but I still dotn get any picture or sound.. but the health status in youtube still shows good

  I ran this command first

  ffmpeg -i input.mp4 -vcodec libx264 -preset medium -maxrate 3000k -bufsize 6000k -vf "scale=1280:-1,format=yuv420p" -g 50 -acodec libmp3lame -b:a 128k -ac 2 -ar 44100 file.flv

  and then I ran this

  ffmpeg -re -i file.flv -codec copy -f flv rtmp://a.rtmp.youtube.com/live2/<key>
  
  </key>

  I still didnt get any picture

  I also tried the full command in 1

  ffmpeg -re -i input.mp4 -vcodec libx264 -preset veryfast -maxrate 3000k -bufsize 6000k -pix_fmt yuv420p -g 50 -c:a aac -b:a 160k -ac 2 -ar 44100 -f flv rtmp://a.rtmp.youtube.com/live2/<key>  
  
  </key>

  still no joy

• Piwik is now Matomo – Announcement

  
  9 janvier 2018, par Matomo Core Team

  You may be surprised to read this announcement, but no stress, take a deep breath, nothing big is going to happen, it is just our name that is changing and here are the reasons why.

  

  Why are we changing from Piwik to Matomo ?

  “After an epic 10 year journey creating and perfecting the best open digital analytics solution, we felt it was a good time to refresh our brand to reflect how far we have come and to reaffirm our vision :
  To create, as a community, the leading international open source digital analytics platform, that gives every user full control of their data.”

  Matthieu Aubry, creator of Piwik

  As projects evolve, so do names. After 10 years of Piwik and the amazing achievement of building the top open source analytics software that gives every user full control of their data, we are now looking forward to the next chapter. Thus, Piwik, the community project, will now become Matomo. The only change is our name, everything else stays the same.

  This will allow users to take a fresh look at what we’ve become today and acknowledging all of the community’s hard work over the past 10 years. In addition, we also want our name to be unique, ensuring that it is not shared with any other company to remove any possible confusion or affiliations. Piwik is already used on over 1 million websites and with Matomo, we hope to reach our maximum potential.

  With the strong focus on privacy worldwide and the upcoming privacy regulations about to be legislated in Europe, it is clear that we were on the right mission from the very beginning. With the upcoming big release Matomo 4.0 planned for this year, new privacy protections will bring users the tools to be compliant with the GDPR privacy laws. And Matomo will grow in line with these regulations, with a very clear and focused vision.

  Changing our name is an exciting opportunity for us, and we hope you love the name Matomo as much as we do.

  Matomo FAQs

  So what is going to change for me ?

  Well, basically nothing, the name will change but the values stay the same : Matomo (Piwik) will continue to be free and always will be.

  Also the same people stay behind the project. We are motivated more than ever to take this project to the next level.

  Why not keep the name Piwik ?

  For a few reasons, one of which is to ensure that Matomo does not/will not share its name with any other businesses unlike Piwik. We also want to protect the Matomo brand and for it to remain the open source community project name forever.

  Where does the name Matomo come from ?

  We loved the name Piwik and were looking for something that sounded just as good ! Initially we wanted to have an acronym based on key terms, such as Free, Open Source and Privacy, but none really fit us perfectly.

  Until we found Matomo ! Easily pronounced in all languages. Short enough to remember. Concise. And best of all… Matomo means honesty in Japanese. Which aligns with one of our key values – transparency.

  We love the name Matomo and hope you do too.

  What is the vision of Matomo ?

  

  We have come a long way in those 10 years ! However, our mission statement remains the same :

  “To create, as a community, the leading international open source digital analytics platform, that gives every user full control of their data.”

  Matomo provides a range of amazing and innovative features, allowing you to get a 360 view of your visitors. These insights are invaluable to help understand behavior, keep track of goals, and increase conversion rates and revenue.

  Who will deliver Matomo professional services ?

  Any company who wishes to. The only exception is that no companies will be allowed to have the name Matomo.

  Our company providing professional services is and will remain InnoCraft.

  Where can I follow the Matomo project ?

  Our new website will be matomo.org (automatically redirected from Piwik.org)

  Follow our new Twitter : twitter.com/matomo_org

  Github : github.com/matomo-org

  Facebook : facebook.com/Matomo.org

  Linkedin : linkedin.com/company/matomo/

  If you are already following us on social media, you will be kept up to date with Matomo automatically as all social media accounts will be redirected.

  How should I pronounce Matomo ?

  If you’re wondering how to say ‘Matomo’, you can find out by clicking play :

  Where can I see a demo of Matomo ?

  On demo.matomo.org

  Where can I download Matomo first release ?

  On matomo.org/download

  (Matomo 3.3.0 will be released in the next few days)

  What is the new logo ?

  Check it out below.

  

  Matomo trademark Policy

  Matomo is an internationally registered trademark of Matthieu Aubry, Founder of Piwik (now Matomo).

  Information about how to use the name Matomo (and logo) can be found here : matomo.org/trademark/

  What are the next big steps ?

  We will keep it simple for our valued users. As it is just a name change, the only thing you will notice is that the Piwik brand will gradually be replaced on the websites you are used to seeing the name on. The first version of Matomo will be available in just a few days for download. The software version numbers stay the same : the next release after Piwik 3.2.1 will be Matomo 3.3.0.

  All our public HTTP APIs and Tracking SDKs will continue working normally. As you can imagine, there is a lot of work and complexity behind slowly updating all the SDKs and keeping backwards compatibility, so our renaming project will take a few weeks to complete.

  The Matomo trademark will later be transferred into the Matomo foundation, a non-profit that will be dedicated to promoting and ensuring access to Matomo and our related open source projects in perpetuity.

  ---

  Thank you

  Thank you for continuing to support our project, alongside our 20+ Matomo core team members and more than 500 contributors.

  Please help to spread the word about this announcement by sharing it with friends or or colleagues who may benefit from using Matomo Analytics !

  The post Piwik is now Matomo – Announcement appeared first on Analytics Platform - Matomo.