Recherche avancée

Sur d’autres sites (4264)

• FFMpeg with PHP-7.0 on Ubuntu

  25 octobre 2018, par Gabriel Bueno Lemes da Silva

  I have a NGINX server with PHP-7.0 and I would like to install the ffmpeg-php extension. I’ve been trying for a few days now and in many ways.

  The method that worked so far was compiling ffmpeg (https://ffmpeg.org/releases/ffmpeg-4.0.2.tar.bz2) manually, but when trying to compile ffmpeg-php (https: // sourceforge. net / projects / ffmpeg-php / files / ffmpeg-php / 0.6.0 / ffmpeg-php-0.6.0.tbz2 / download) I am encountering the following error message :

  root@zumbiserver-mercury : /php7-ffmpeg# make /bin/bash

  /root/php7-ffmpeg/libtool —mode=compile cc -I. -I/root/php7-ffmpeg
  -DPHP_ATOM_INC -I/root/php7-ffmpeg/include -I/root/php7-ffmpeg/main -I/root/php7-ffmpeg -I/usr/include/php/20151012 -I/usr/include/php/20151012/main -I/usr/include/php/20151012/TSRM -I/usr/include/php/20151012/Zend -I/usr/include/php/20151012/ext -I/usr/include/php/20151012/ext/date/lib -I/usr/local/include/libavcodec/ -I/usr/local/include/libavformat/ -I/usr/local/include/libavutil/ -I/usr/local/include/libswscale/ -I/usr/local/include/libavfilter/ -I/usr/local/include/libavdevice/ -DHAVE_CONFIG_H -g -O2 -Wall -fno-strict-aliasing -c /root/php7-ffmpeg/ffmpeg-php.c -o ffmpeg-php.lo libtool : compile : cc
  -I. -I/root/php7-ffmpeg -DPHP_ATOM_INC -I/root/php7-ffmpeg/include -I/root/php7-ffmpeg/main -I/root/php7-ffmpeg -I/usr/include/php/20151012 -I/usr/include/php/20151012/main -I/usr/include/php/20151012/TSRM -I/usr/include/php/20151012/Zend -I/usr/include/php/20151012/ext -I/usr/include/php/20151012/ext/date/lib -I/usr/local/include/libavcodec/ -I/usr/local/include/libavformat/ -I/usr/local/include/libavutil/ -I/usr/local/include/libswscale/ -I/usr/local/include/libavfilter/ -I/usr/local/include/libavdevice/ -DHAVE_CONFIG_H -g -O2 -Wall -fno-strict-aliasing -c /root/php7-ffmpeg/ffmpeg-php.c -fPIC -DPIC -o .libs/ffmpeg-php.o In
  file included from /usr/include/x86_64-linux-gnu/sys/stat.h:104:0,
  from /usr/include/php/20151012/Zend/zend_stream.h:28,
  from /usr/include/php/20151012/Zend/zend.h:41,
  from /usr/include/php/20151012/main/php.h:36,
  from /root/php7-ffmpeg/ffmpeg-php.c:40 : /usr/include/x86_64-linux-gnu/bits/stat.h:91:21 : error : field
  ‘st_atim’ has incomplete type
  struct timespec st_atim ; /* Time of last access. /
  ^ /usr/include/x86_64-linux-gnu/bits/stat.h:92:21 : error : field
  ‘st_mtim’ has incomplete type
  struct timespec st_mtim ; / Time of last modification. /
  ^ /usr/include/x86_64-linux-gnu/bits/stat.h:93:21 : error : field
  ‘st_ctim’ has incomplete type
  struct timespec st_ctim ; / Time of last status change. /
  ^ /usr/include/x86_64-linux-gnu/bits/stat.h:152:21 : error : field
  ‘st_atim’ has incomplete type
  struct timespec st_atim ; / Time of last access. /
  ^ /usr/include/x86_64-linux-gnu/bits/stat.h:153:21 : error : field
  ‘st_mtim’ has incomplete type
  struct timespec st_mtim ; / Time of last modification. /
  ^ /usr/include/x86_64-linux-gnu/bits/stat.h:154:21 : error : field
  ‘st_ctim’ has incomplete type
  struct timespec st_ctim ; / Time of last status change. /
  ^ In file included from /usr/include/php/20151012/Zend/zend_stream.h:28:0,
  from /usr/include/php/20151012/Zend/zend.h:41,
  from /usr/include/php/20151012/main/php.h:36,
  from /root/php7-ffmpeg/ffmpeg-php.c:40 : /usr/include/x86_64-linux-gnu/sys/stat.h:364:31 : error : array type has
  incomplete element type ‘struct timespec’
  const struct timespec __times[2],
  ^ /usr/include/x86_64-linux-gnu/sys/stat.h:371:54 : error : array type has
  incomplete element type ‘struct timespec’ extern int futimens (int
  __fd, const struct timespec __times[2]) __THROW ;
  ^ In file included from /usr/include/php/20151012/main/php.h:395:0,
  from /root/php7-ffmpeg/ffmpeg-php.c:40 : /usr/include/php/20151012/Zend/zend_virtual_cwd.h:218:2 : error :
  unknown type name ‘time_t’ time_t expires ;
  ^ /usr/include/php/20151012/Zend/zend_virtual_cwd.h:248:86 : error :
  unknown type name ‘time_t’ CWD_API realpath_cache_bucket
  realpath_cache_lookup(const char *path, int path_len, time_t t) ;
  ^ /root/php7-ffmpeg/ffmpeg-php.c : In function ‘zm_startup_ffmpeg’ :
  /root/php7-ffmpeg/ffmpeg-php.c:108:5 : warning : implicit declaration of
  function ‘avcodec_init’ [-Wimplicit-function-declaration]
  avcodec_init() ;
  ^ /root/php7-ffmpeg/ffmpeg-php.c:111:5 : warning : ‘av_register_all’ is deprecated [-Wdeprecated-declarations]
  av_register_all() ;
  ^ In file included from /root/php7-ffmpeg/ffmpeg-php.c:43:0 : /usr/local/include/libavformat/avformat.h:2025:6 : note : declared here
  void av_register_all(void) ;

    ^ Makefile:194: recipe for target 'ffmpeg-php.lo' failed make: *** [ffmpeg-php.lo] Error 1

  Can someone give me a light ? I do not know what else to do !

• ffmpeg get frame time stamp

  19 novembre 2018, par Anshul G.

  I am trying to record a webcam video using ffmpeg. I have a logitech c922 Pro Stream Webcam. This is the command that I use :

  ffmpeg -f v4l2 -framerate 60 -video_size 1280x720 -input_format mjpeg -i /dev/video1 out.mp4

  My application requires me to get the exact timestamp for every frame. While I could use my knowledge of the framerate and frame number to add the required interval to the start time, I am afraid that this might not be completely accurate.

  Firstly, I have noticed that while recording, the console seems to initially display a far higher fps than the one I have set :

  Press [q] to stop, [?] for help
  
  frame=  177 fps= 85 q=-1.0 Lsize=     502kB time=00:00:02.91 bitrate=1410.8kbits/s dup=144 drop=0    

  Also, I think that ffmpeg drops frames in between sometimes.

  However, my videos seem to have the correct number of frames so I think that the fps value displayed could instead be referring to the encoding/ decoding speed. I am not sure about frame dropping.

  I would be happy of you could let me know what you think, or suggest an alternative so that I can timestamp my frames accurately. Thanks !

  Edit :

  I have understood that frame rate is correlated to ambient light which can lead to high duplication in frames. I am currently recording on windows and have set frame rate as the priority in logitech gaming software. However there is still the occasional drop in frame or duplication. Does this affect time stamp of the frames ? Or can I extrapolate from the start time ?

• Projects from behind-the-scenes

  28 septembre 2018, par Jake Thornton

  Kia ora from the marketing team !

  Marketing team ? That’s right ! You haven’t heard from us in the past, but we’ve been working in the background to create a better experience for you, our dedicated Matomo community.

  Kia ora ? Well, that just means “hello” in Maori, we’re based in New Zealand you see.

  The Matomo marketing team has some really exciting projects in the works we wanted to share with you, but first, there’s someone I want to introduce :

  Meet Joselyn from the Matomo Marketing team

  Meet Joselyn, one half of the Matomo marketing team and our Digital Marketing and Communications Specialist. Joselyn has come on board to help us communicate more frequently and effectively as we continue our mission to be the #1 free open source analytics platform in the world. Please take it away, Joselyn !

  “Hi everyone ! The team here at Matomo have been doing an incredible job passionately driving the cause for user privacy and data ownership and uniting that with a love for digital analytics. It’s exciting being a part of a team unafraid to push on with their hearts on their sleeves and their values at the forefront of everything they do. I hope to bring to light all the fantastic things happening in our world of web analytics as well as across the globe.

  

  Our online world is fascinating when we think about what we can achieve with analytics, but there’s room to improve. We see newer technologies, but old ways of working which don’t take into account a person’s safety online. So we hope to champion a new future which looks set to be much more meaningful. Ensuring you get the best experience, but also feel protected with the knowledge that we get it. Your data and privacy isn’t for sale.

  I also hear you guys, the community, have followed Matomo since the beginning, which is wonderful ! I hope you’ll be able to join us as we grow and learn. We’ve got so many thrilling things to share with you. The highs, the lows and everything in between. Cheers !”

  Thanks Joselyn ! On top of working to engage the community and new users, Joselyn will also be keeping the rest of the Matomo team on our toes getting the inside scoop on what’s happening within the Development and Support teams ; as well as giving you behind-the-scenes access to what’s going on here at Matomo. We have a big vision and with so many things happening right now, we want to get you involved as much as possible.

  It may sound a bit clichéd but I’m saying it anyway – without your help, Matomo wouldn’t be here today.

  Help us choose a logo

  So first of all, we want you to say thank you and second we’d be delighted if you could help choose our new logo ! As you may already know, we changed our name from Piwik to Matomo at the start of the year. Though it was fun using a cool font (Aileron Heavy btw) as a quick fix for our name change, it was a temporary solution. The Matomo team has been involved in the direction of creating a new logo, but now we’re stumped ! We have three different concepts to choose from so please help us out !

  Click here to logo poll

  A new website for Matomo.org !

  Other exciting marketing projects include a new website design (yay !) – to everyone gasping nervously…don’t worry, nothing in what we offer is changing. We are and always will be a freely accessible open source analytics platform, just wanted to quickly clear the air on that one !

  We also have some video projects in the works to make the Matomo experience better for everyone and there are even rumours a brand video that tells the Matomo story is on the way ;)

  What next ? With Joselyn on board and loads of exciting projects happening, it won’t be long until you hear from us again, so keep an eye out for our next update as we reveal the winning Matomo logo.

  Be sure to follow us on Facebook, Twitter and Github – we promise to be more active than what we have been !