Recherche avancée

Médias (0)

Mot : - Tags -/performance

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (47)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (6643)

  • ffmpeg installation undefined reference to

    8 février 2017, par user1683302

    I used this official link to download ffmpeg and compile it. I know it creates a static library and I have to reference the library folder. When i try to compile this tutorial . i get this errors

    tutorial01.c: In function ‘main’:
    tutorial01.c:96:5: warning: ‘codec’ is deprecated [-Wdeprecated- declarations]
    if(pFormatCtx->streams[i]->codec->codec_type==AVMEDIA_TYPE_VIDEO) {
    ^
    In file included from tutorial01.c:27:0:
    /home/osboxes/ffmpeg_build/include/libavformat/avformat.h:893:21: note:  declared here
    AVCodecContext *codec;
                    ^
    tutorial01.c:104:3: warning: ‘codec’ is deprecated [-Wdeprecated-declarations]
    pCodecCtxOrig=pFormatCtx->streams[videoStream]->codec;
    ^
    In file included from tutorial01.c:27:0:
    /home/osboxes/ffmpeg_build/include/libavformat/avformat.h:893:21: note: declared here
    AVCodecContext *codec;
                    ^
    tutorial01.c:113:3: warning: ‘avcodec_copy_context’ is deprecated  [-Wdeprecated-declarations]
    if(avcodec_copy_context(pCodecCtx, pCodecCtxOrig) != 0) {
    ^
    In file included from tutorial01.c:26:0:
    /home/osboxes/ffmpeg_build/include/libavcodec/avcodec.h:4240:5: note: declared here
    int avcodec_copy_context(AVCodecContext *dest, const AVCodecContext *src);
    ^
    tutorial01.c:131:3: warning: ‘avpicture_get_size’ is deprecated   [-Wdeprecated-declarations]
    numBytes=avpicture_get_size(AV_PIX_FMT_RGB24, pCodecCtx->width,
    ^
    In file included from tutorial01.c:26:0:
    /home/osboxes/ffmpeg_build/include/libavcodec/avcodec.h:5467:5: note: declared here
    int avpicture_get_size(enum AVPixelFormat pix_fmt, int width, int height);
    ^
     tutorial01.c:138:3: warning: ‘avpicture_fill’ is deprecated [-Wdeprecated-declarations]
      avpicture_fill((AVPicture *)pFrameRGB, buffer, AV_PIX_FMT_RGB24,
      ^
     In file included from tutorial01.c:26:0:
     /home/osboxes/ffmpeg_build/include/libavcodec/avcodec.h:5452:5: note: declared here
     int avpicture_fill(AVPicture *picture, const uint8_t *ptr,
    ^
      tutorial01.c:160:7: warning: ‘avcodec_decode_video2’ is deprecated [-Wdeprecated-declarations]
          avcodec_decode_video2(pCodecCtx, pFrame, &frameFinished, &packet);
          ^
    In file included from tutorial01.c:26:0:
     /home/osboxes/ffmpeg_build/include/libavcodec/avcodec.h:4811:5: note: declared here
     int avcodec_decode_video2(AVCodecContext *avctx, AVFrame *picture,
    ^
     tutorial01.c:177:5: warning: ‘av_free_packet’ is deprecated [-Wdeprecated-declarations]
     av_free_packet(&packet);
     ^
    In file included from tutorial01.c:26:0:
    /home/osboxes/ffmpeg_build/include/libavcodec/avcodec.h:4472:6: note: declared here
    void av_free_packet(AVPacket *pkt);
     ^
    /tmp/ccHYDd9j.o: In function `main':
    tutorial01.c:(.text+0x178): undefined reference to `av_register_all'
    tutorial01.c:(.text+0x19f): undefined reference to `avformat_open_input'
    tutorial01.c:(.text+0x1c1): undefined reference to `avformat_find_stream_info'
    tutorial01.c:(.text+0x1f6): undefined reference to `av_dump_format'
    tutorial01.c:(.text+0x2ab): undefined reference to `avcodec_find_decoder'
    tutorial01.c:(.text+0x2ea): undefined reference to `avcodec_alloc_context3'
    tutorial01.c:(.text+0x304): undefined reference to `avcodec_copy_context'
    tutorial01.c:(.text+0x348): undefined reference to `avcodec_open2'
    tutorial01.c:(.text+0x35b): undefined reference to `av_frame_alloc'
    tutorial01.c:(.text+0x367): undefined reference to `av_frame_alloc'
    tutorial01.c:(.text+0x3a4): undefined reference to `avpicture_get_size'
    tutorial01.c:(.text+0x3ba): undefined reference to `av_malloc'
    tutorial01.c:(.text+0x3ef): undefined reference to `avpicture_fill'
    tutorial01.c:(.text+0x439): undefined reference to `sws_getContext'
    tutorial01.c:(.text+0x47d): undefined reference to `avcodec_decode_video2'
    tutorial01.c:(.text+0x4de): undefined reference to `sws_scale'
    tutorial01.c:(.text+0x527): undefined reference to `av_free_packet'
    tutorial01.c:(.text+0x53d): undefined reference to `av_read_frame'
    tutorial01.c:(.text+0x551): undefined reference to `av_free'
    tutorial01.c:(.text+0x560): undefined reference to `av_frame_free'
    tutorial01.c:(.text+0x56f): undefined reference to `av_frame_free'
    tutorial01.c:(.text+0x57b): undefined reference to `avcodec_close'
    tutorial01.c:(.text+0x58a): undefined reference to `avcodec_close'
    tutorial01.c:(.text+0x599): undefined reference to `avformat_close_input'
    collect2: error: ld returned 1 exit status

    i used this sudo gcc -I /home/osboxes/ffmpeg_build/include -L /home/osboxes/ffmpeg_build/lib -lavcode -lavformat -lavutil -lswscale -lz -lm tutorial01.c

    my ffmpeg is

    ffmpeg version N-82113-g490c6bd Copyright (c) 2000-2016 the FFmpeg developers
      built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.2) 20160609
      configuration: --prefix=/home/osboxes/ffmpeg_build --pkg-config-flags=--static --extra-cflags=-I/home/osboxes/ffmpeg_build/include --extra-ldflags=- L/home/osboxes/ffmpeg_build/lib --bindir=/home/osboxes/bin --enable-gpl --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libopus --enable-libx264 --enable-nonfree
     libavutil      55. 33.100 / 55. 33.100
     libavcodec     57. 63.103 / 57. 63.103
     libavformat    57. 55.100 / 57. 55.100
     libavdevice    57.  0.103 / 57.  0.103
     libavfilter     6. 64.100 /  6. 64.100
     libswscale      4.  1.100 /  4.  1.100
     libswresample   2.  2.100 /  2.  2.100
     libpostproc    54.  0.100 / 54.  0.100
    Hyper fast Audio and Video encoder
    usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...

    the tutorial code was update to work on new ffmpeg versions.I’m using VM Ubuntu 16.0.4 64 bit fresh install on windows 10 host.

    so why I’m having all of these errors ?

    Update :
    I moved to Ubuntu 12.04 VM and ffmpeg 0.11, I instilled it with opencv 2.4.2 here is the link . This should work yet i don’t why I’m having hard time compiling such small program.

    ffmpeg version 0.11.1 Copyright (c) 2000-2012 the FFmpeg developers
    built on Oct 25 2016 13:39:37 with gcc 4.6.3
     configuration: --enable-gpl --enable-libfaac --enable-libmp3lame    --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-nonfree --enable-postproc --enable-version3 --enable-x11grab --enable-shared --enable-pic
    libavutil      51. 54.100 / 51. 54.100
    libavcodec     54. 23.100 / 54. 23.100
    libavformat    54.  6.100 / 54.  6.100
    libavdevice    54.  0.100 / 54.  0.100
    libavfilter     2. 77.100 /  2. 77.100
    libswscale      2.  1.100 /  2.  1.100
    libswresample   0. 15.100 /  0. 15.100
    libpostproc    52.  0.100 / 52.  0.100
    Hyper fast Audio and Video encoder
    usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...

    yet i still have the problem but it is less sever

    gcc -o tutorial01 tutorial01.c -Wl,--start-group -lavcodec -lavformat  -lswscale -lavutil -lz -lm -Wl,--end-group    
     /tmp/ccnFfu84.o: In function `main':
     tutorial01.c:(.text+0x500): undefined reference to `avcodec_free_frame'
     tutorial01.c:(.text+0x511): undefined reference to `avcodec_free_frame'
     collect2: ld returned 1 exit status

    i tried this ldconfig -p | grep av

     libxklavier.so.16 (libc6,x86-64) => /usr/lib/libxklavier.so.16
     libwavpack.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux gnu/libwavpack.so.1
    libjavascriptcoregtk-3.0.so.0 (libc6,x86-64) => /usr/lib/libjavascriptcoregtk-3.0.so.0
    libdvdnavmini.so.4 (libc6,x86-64) => /usr/lib/libdvdnavmini.so.4
    libdvdnav.so.4 (libc6,x86-64) => /usr/lib/libdvdnav.so.4
    libavutil.so.51 (libc6,x86-64) => /usr/local/lib/libavutil.so.51
    libavutil.so.51 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libavutil.so.51
    libavutil.so (libc6,x86-64) => /usr/local/lib/libavutil.so
    libavformat.so.54 (libc6,x86-64) => /usr/local/lib/libavformat.so.54
    libavformat.so.53 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libavformat.so.53
    libavformat.so (libc6,x86-64) => /usr/local/lib/libavformat.so
    libavfilter.so.2 (libc6,x86-64) => /usr/local/lib/libavfilter.so.2
    libavfilter.so (libc6,x86-64) => /usr/local/lib/libavfilter.so
    libavdevice.so.54 (libc6,x86-64) => /usr/local/lib/libavdevice.so.54
    libavdevice.so (libc6,x86-64) => /usr/local/lib/libavdevice.so
    libavc1394.so.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libavc1394.so.0
    libavcodec.so.54 (libc6,x86-64) => /usr/local/lib/libavcodec.so.54
    libavcodec.so.53 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libavcodec.so.53
    libavcodec.so (libc6,x86-64) => /usr/local/lib/libavcodec.so
    libavahi-ui-gtk3.so.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libavahi-ui-gtk3.so.0
    libavahi-gobject.so.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libavahi-gobject.so.0
    libavahi-glib.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1
    libavahi-core.so.7 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libavahi-core.so.7
    libavahi-common.so.3 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libavahi-common.so.3
    libavahi-common.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libavahi-common.so
    libavahi-client.so.3 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
    libavahi-client.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libavahi-client.so

    Update2

    I changged avcodec_free_frame to av_free and the file complied

    Dranger code is old

    Update 3
    i downloaded ffmpeg 1.0.10 which has the same library version that is the tutorial tested on. Everything complied without any problem now.

  • A *hot* Piwik Community Meetup 2015 !

    10 août 2015 — Community

    Last weekend I arrived in Germany to attend the Piwik Community Meetup 2015 and now I am in Poland. I joined Piwik PRO back in May as enterprise support project coordinator in North America. I am now writing this from the Piwik PRO main office in Wrocław, where I’ll be working from for the next two weeks.

    The meetup was HOT in every sense ! Berlin temperatures reached 35 degrees (celsius), as I finally meet in person several long-time, dedicated Piwik community contributors.

    Meetup preparation in Berlin, photo by M. Zawadziński, licensed under CC-BY-SA 4.0

    Pictures from the meetup preparation sessions

    In the first leg of my trip I was in Berlin to meet Piwik community members and Piwik PRO staff to prepare for the 2015 annual Piwik community meetup. These are my notes taken during the meeting at the request of one of my colleagues. I also relayed live on Framasphère, Twitter and IRC.

    Community discussion at the meetup, photo by D.Czajka, licensed under CC-BY-SA 4.0

    More pictures from the Piwik meetup

    This was harder than I expected, as I took notes with my laptop, pictures with my phone, wrote live to social media (using the Android Diaspora Native Web App), and used my laptop to relay on IRC. Going forward this requires better preparation, I was glad I had a few links and pictures ready before hand but it really requires intense focus to achieve this. I am glad presenters were patient when I requested repeating some of the ideas they shared. I am also a bit disappointed not much happened in IRC.

    Two day preparation sessions

    The discussions and session we had during the two days prior to the meetup are available here.

    We gathered in rented apartments in Berlin, this reminded me very much of similar community gatherings and perhaps of BarCamp and, at a much smaller scale, UDS sessions.

    Piwik Pizza !, photo by F. Rodríguez, licensed under CC-BY-SA 4.0

    A list of ideas of topics was initially submitted, we then proceeded to have scheduled sessions for open discussion. Several people shared their concern there was no possible remote participation which led to making public the Trello boards used/linked here.

    Note : The Trello links below still have action items and notes that are pending bug report / feature requests filing which should happen over the coming weeks. Most importantly, many action items will need identifying leads for different community team including Translations and Documentation, and better coordination of coming community engagement.

    Monday sessions consisted of the following subjects :

    On Tuesday we met again to discuss the following subjects :

    Some more details about individual preparation sessions

    What are Piwik values & how to communicate them ?

    The main subjects in this session were important changes proposed in the project mission and values. This was edited directly on on the wiki page on GitHub, some of the changes can be seen by comparing revisions.

    Piwik mission statement (bug #7376)

    “To create the leading Free and open source analytics platform, and to support global organisations and communities to keep full control over their data.”

    Our values

    • Openness
    • Freedom
    • Transparency
    • Data ownership
    • Privacy
    • Kaizen (改善) : continuous improvement

    This was also presented by Matthieu Aubry at the meetup and is published in the Roadmap page. Bringing more visibility and perhaps having a top page for Mission and Values was also brought up.

    Meetup agenda and notes

    The official agenda is available here.

    Many Piwik PRO employees stayed in Berlin for the meetup, and we had good participation although less than last year in Munich as my colleagues told me. Some were consultants, others staff from public organizations, universities, etc. In retrospect considering the very hot weather and summer holidays the attendance was good. I was very happy to arrive at the beautiful Kulturbrauerei and enter the air-conditioned Soda Club. T-Shirts were waiting for all attendees and free drinks (non-alcohol !) were welcome

  • What is Google Analytics data sampling and what’s so bad about it ?

    16 août 2019, par Joselyn Khor — Analytics Tips, Development

    What is Google Analytics data sampling, and what’s so bad about it ?

    Google (2019) explains what data sampling is :

    “In data analysis, sampling is the practice of analysing a subset of all data in order to uncover the meaningful information in the larger data set.”[1]

    This is basically saying instead of analysing all of the data, there’s a threshold on how much data is analysed and any data after that will be an assumption based on patterns.

    Google’s (2019) data sampling thresholds :

    Ad-hoc queries of your data are subject to the following general thresholds for sampling :
    [Google] Analytics Standard : 500k sessions at the property level for the date range you are using
    [Google] Analytics 360 : 100M sessions at the view level for the date range you are using (para. 3) [2]

    This threshold is limiting because your data in GA may become more inaccurate as the traffic to your website increases.

    Say you’re looking through all your traffic data from the last year and find you have 5 million page views. Only 500K of that 5 million is accurate ! The data for the remaining 4.5 million (90%) is an assumption based on the 500K sample size.

    This is a key weapon Google uses to sell to large businesses. In order to increase that threshold for more accurate reporting, upgrading to premium Google Analytics 360 for approximately US$150,000 per year seems to be the only choice.

    What’s so bad about data sampling ?

    It’s unfair to say sampled data is to be disregarded completely. There is a calculation ensuring it is representative and can allow you to get good enough insights. However, we don’t encourage it as we don’t just want “good enough” data. We want the actual facts.

    In a recent survey sent to Matomo customers, we found a large proportion of users switched from GA to Matomo due to the data sampling issue.

    The two reasons why data sampling isn’t preferable : 

    1. If the selected sample size is too small, you won’t get a good representative of all the data. 
    2. The bigger your website grows, the more inaccurate your reports will become.

    An example of why we don’t fully trust sampled data is, say you have an ecommerce store and see your GA revenue reports aren’t matching the actual sales data, due to data sampling. In GA you may be seeing revenue for the month as $1 million, instead of actual sales of $800K.

    The sampling here has caused an inaccuracy that could have negative financial implications. What you get in the GA report is an estimated dollar figure rather than the actual sales. Making decisions based on inaccurate data can be costly in this case. 

    Another disadvantage to sampled data is that you might be missing out on opportunities you would’ve noticed if you were given a view of the whole. E.g. not being able to see real patterns occurring due to the data already being predicted. 

    By not getting a chance to see things as they are and only being able to jump to the conclusions and assumptions made by GA is risky. The bigger your business grows, the less you can risk making business decisions based on assumptions that could be inaccurate. 

    If you feel you could be missing out on opportunities because your GA data is sampled data, get 100% accurately reported data. 

    The benefits of 100% accurate data

    Matomo doesn’t use data sampling on any of our products or plans. You get to see all of your data and not a sampled data set.

    Data quality is necessary for high impact decision-making. It’s hard to make strategic changes if you don’t have confidence that your data is reliable and accurate.

    Learn about how Matomo is a serious contender to Google Analytics 360. 

    Now you can import your Google Analytics data directly into your Matomo

    If you’re wanting to make the switch to Matomo but worried about losing all your historic Google Analytics data, you can now import this directly into your Matomo with the Google Analytics Importer tool.


    Take the challenge !

    Compare your Google Analytics data (sampled data) against your Matomo data, or if you don’t have Matomo data yet, sign up to our 30-day free trial and start tracking !

    References :

    [1 & 2] About data sampling. (2019). In Analytics Help About data sampling. Retrieved August 14, 2019, from https://support.google.com/analytics/answer/2637192