Recherche avancée

Médias (3)

Mot : - Tags -/pdf

Autres articles (61)

  • Le plugin : Podcasts.

    14 juillet 2010, par

    Le problème du podcasting est à nouveau un problème révélateur de la normalisation des transports de données sur Internet.
    Deux formats intéressants existent : Celui développé par Apple, très axé sur l’utilisation d’iTunes dont la SPEC est ici ; Le format "Media RSS Module" qui est plus "libre" notamment soutenu par Yahoo et le logiciel Miro ;
    Types de fichiers supportés dans les flux
    Le format d’Apple n’autorise que les formats suivants dans ses flux : .mp3 audio/mpeg .m4a audio/x-m4a .mp4 (...)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • Récupération d’informations sur le site maître à l’installation d’une instance

    26 novembre 2010, par

    Utilité
    Sur le site principal, une instance de mutualisation est définie par plusieurs choses : Les données dans la table spip_mutus ; Son logo ; Son auteur principal (id_admin dans la table spip_mutus correspondant à un id_auteur de la table spip_auteurs)qui sera le seul à pouvoir créer définitivement l’instance de mutualisation ;
    Il peut donc être tout à fait judicieux de vouloir récupérer certaines de ces informations afin de compléter l’installation d’une instance pour, par exemple : récupérer le (...)

Sur d’autres sites (6366)

  • How Media Analytics for Piwik gives you the insights you need to measure how effective your video and audio marketing is – Part 2

    https://piwik.org/media.mp4
    2 février 2017, par InnoCraft — Community

    In Part 1 we have covered some of the Media Analytics features and explained why you cannot afford to not measure the media usage on your website. Chances are, you are wasting or losing money and time by not making the most out of your marketing strategy this very second. In this part, we continue showing you some more insights you can expect to get from Media Analytics and how nicely it is integrated into Piwik.

    Video, Audio and Media Player reports

    Media Analytics adds several new reports around videos, audios and media players. They are all quite similar and give you similar insights so we will mainly focus on the Video Titles report.

    Metrics

    The above mentioned reports give you all the same insights and features so we will mainly focus on the “Video Titles” report. When you open such a report for the first time, you will see a report like this with the following metrics :

    • “Impressions”, the number of times a visitor has viewed a page where this media was included.
    • “Plays”, the number of times a visitor watched or listened to this media.
    • “Play rate”, the percentage of visitors that watched or listened to a media after they have visited a page where this media was included.
    • “Finishes”, the percentage of visitors who played a media and finished it.
    • “Avg. time spent”, the average amount of time a visitor spent watching or listening to this media.
    • “Avg. media length” the average length of a video or audio media file. This number may vary for example if the media is a stream.
    • “Avg completion” the percentage of how much visitors have watched of a video.

    If you are not sure what a certain metric means, simply hover the metric title in the UI and you will get a detailed explanation. By changing the visualization to the “All Columns Table” in the bottom of the report, you get to see even more metrics like “Plays by unique visitors”, “Impressions by unique visitors”, “Finish rate”, “Avg. time to play aka hesitation time”, “Fullscreen rate” and we are always adding more metrics.

    These metrics are available for the following reports :

    • “Video / Audio Titles” shows you all metrics aggregated by video or audio title
    • “Video / Audio Resource URLs” shows you all metrics aggregated by the video or audio resource URL, for example “https://piwik.org/media.mp4”.
    • “Video / Audio Resource URLs grouped” removes some information from the URLs like subdomain, file extensions and other information to get aggregated metrics when you provide the same media in different formats.
    • “Videos per hour in website’s timezone” lets you find out how your media content is consumed depending on the hour of the day. You might realize that your media is consumed very differently in the morning vs at night.
    • “Video Resolutions” lets you discover how your video is consumed depending on the resolution.
    • “Media players” report is useful if you use different media players on your websites or apps and want to see how engagement with your media compares by media player.

    Row evolution

    At InnoCraft, we understand that static numbers are not so useful. When you see for example that yesterday 20 visitors played a certain media, would you know whether this is good or bad ? This is why we always give you the possibility to see the data in relation to the recorded data in the past. To see how a specific media performs over time, simply hover a media title or media resource URL and click on the “Row Evolution” icon.

    Now you can see whether actually more or less visitors played your chosen video for the selected period. Simply click on any metric name and the chosen metrics will be plotted in the big evolution graph.

    This feature is similar to the Media Overall evolution graph introduced in Part 1, but shows you a detailed evolution for an individual media title or resource.

    Media details

    Now that you know some of the most important media metrics, you might want to look a bit deeper into the user behaviour. For example we mentioned before the “Avg time spent on media” metric. Such an average number doesn’t let you know whether most visitors spent about the same time watching the video, or whether there were many more visitors that watched it only for a few seconds and a few that watched it for very long.

    One of the ways to get this insight is by again hovering any media title or resource URL and clicking on the “Media details” icon. It will open a new popup showing you a new set of reports like these :

    The “Time spent watching” and “How far visitors reached in the media” bar charts show you on the X-Axis how much time each visitor spent on watching a video and how far in the video they reached. On the Y-Axis you see the number of visitors. This lets you discover whether your users for example jump often to the middle or end of the video and which parts of your video was seen most often.

    The “How often the media was watched in a certain hour” and “Which resolutions the media was watched” is similar to the reports introduced in Part 1 of the blog post. However, this time instead of showing aggregated video or audio content data, they display data for a specific media title or media resource URL.

    Segmented audience log

    In Part 1 we have already introduced the Audience Log and explained that it is useful to better understand the user behaviour. Just a quick recap : The Audience Log shows you chronologically every action a specific visitor has performed on your website : Which pages they viewed, how they interacted with your media, when they clicked somewhere, and much more.

    By hovering a media title or a media resource and then selecting “Segmented audience log” you get to see the same log, but this time it will show only visitors that have interacted with the selected media. This will be useful for you for example when you notice an unusual value for a metric and then want to better understand why a metric is like that.

    Applying segments

    Media Analytics lets you apply any Piwik segment to the media reports allowing you to dice your visitors or personas multiplying the value that you get out of Media Analytics. For example you may want to apply a segment and analyze the media usage for visitors that have visited your website or mobile app for the first time vs. recurring visitors. Sometimes it may be interesting how visitors that converted a specific goal or purchased something consume your media, the possibilities are endless. We really recommend to take advantage of segments to understand your different target groups even better.

    The plugin also adds a lot of new segments to your Piwik letting you segment any Piwik report by visitors that have viewed or interacted with your media. For example you could go to the “Visitors => Devices” report and apply a media segment to see which devices were used the most to view your media. You can also combine segments to see for example how often your goals were converted when a visitor viewed media for longer than 10 seconds after waiting for at least 20 seconds before playing your media and when they played at least 3 videos during their visit.

    Widgets, Scheduled Reports, and more.

    This is not where the fun ends. Media Analytics defines more than 15 new widgets that you can add to your dashboard or export it into a third party website. You can set up Scheduled Reports to receive the Media reports automatically via email or sms or download the report to share it with your colleagues. It works also very well with Custom Alerts and you can view the Media reports in the Piwik Mobile app for Android and iOS. Via the HTTP Reporting API you can fetch any report in various formats. The plugin is really nicely integrated into Piwik we would need some more blog posts to fully cover all the ways Media Analytics advances your Piwik experience and how you can use and dig into all the data to increase your conversions and sales.

    How to get Media Analytics and related features

    You can get Media Analytics on the Piwik Marketplace. If you want to learn more about this feature, you might be also interested in the Media Analytics User Guide and the Media Analytics FAQ.

  • ffmpeg `avformat_write_header` fail with -22 Invalid arg

    3 février 2017, par user998953

    I am having an error with FFMPEG. Here is my code :

    static int open_output_file(const char *filename) {
    
    AVStream *out_stream;
    
    AVStream *in_stream;
    
    AVCodecContext *dec_ctx, *enc_ctx;
    
    AVCodec *encoder;
    
    int ret;
    
    unsigned int i;
    
    ofmt_ctx = NULL;
    
    avformat_alloc_output_context2(&ofmt_ctx, NULL, NULL, filename);
    
    if (!ofmt_ctx) {
    
        LOGD(NULL, AV_LOG_ERROR, "Could notcreate output context\n");
    
        return AVERROR_UNKNOWN;
    
    }
    
    for (i = 0; i < ifmt_ctx->nb_streams; i++) {
    
        out_stream = avformat_new_stream(ofmt_ctx, NULL);
    
        if (!out_stream) {
    
            LOGD(NULL, AV_LOG_ERROR, "Failed allocating output stream\n");
    
            return AVERROR_UNKNOWN;
    
        }
    
        in_stream = ifmt_ctx->streams[i];
    
        dec_ctx = in_stream->codec;
    
        enc_ctx = out_stream->codec;
    
        if (dec_ctx->codec_type == AVMEDIA_TYPE_VIDEO
    
            || dec_ctx->codec_type == AVMEDIA_TYPE_AUDIO) {
    
            /* in this example, we choose transcoding to same codec */
    

    
            encoder = avcodec_find_encoder(dec_ctx->codec_id);
    
            enc_ctx = avcodec_alloc_context3(encoder);
    
            if (!encoder) {
    
                LOGE("encoder not avalibe ");
    
                return -1;
    
            }
    
            /* In this example, we transcode to same properties(picture size,
    
            * sample rate etc.). These properties can be changed for output
    
            * streams easily using filters */
    
            if (dec_ctx->codec_type == AVMEDIA_TYPE_VIDEO) {
    
                enc_ctx->height = dec_ctx->height;
    
                enc_ctx->width = dec_ctx->width;
    
                enc_ctx->sample_aspect_ratio = dec_ctx->sample_aspect_ratio;
    
                /* take first format from list of supported formats */
    
                enc_ctx->pix_fmt = encoder->pix_fmts[0];
    
                /* video time_base can be set to whatever is handy andsupported by encoder */
    
                enc_ctx->time_base = dec_ctx->time_base;
    
            } else {
    
                enc_ctx->sample_rate = dec_ctx->sample_rate;
    
                enc_ctx->channel_layout = dec_ctx->channel_layout;
    
                enc_ctx->channels = av_get_channel_layout_nb_channels(enc_ctx->channel_layout);
    
                /* take first format from list of supported formats */
    
                enc_ctx->sample_fmt = encoder->sample_fmts[0];
    
                AVRational time_base = {1, enc_ctx->sample_rate};
    
                enc_ctx->time_base = time_base;
    
            }
    
            /* Third parameter can be used to pass settings to encoder*/
    
            ret = avcodec_open2(enc_ctx, encoder, NULL);
    
            if (ret < 0) {
    
                LOGD("Cannot openvideo encoder for stream #%u\n", i);
    
                return ret;
    
            }
    
        } else if (dec_ctx->codec_type == AVMEDIA_TYPE_UNKNOWN) {
    
            LOGE("Elementarystream #%d is of unknown type, cannot proceed\n",
    
                 i);
    
            return AVERROR_INVALIDDATA;
    
        } else {
    
            /* if this stream must be remuxed */
    
            ret = avcodec_copy_context(ofmt_ctx->streams[i]->codec,
    
                                       ifmt_ctx->streams[i]->codec);
    
            if (ret < 0) {
    
                LOGE("Copyingstream context failed\n");
    
                return ret;
    
            }
    
        }
    
        if (ofmt_ctx->oformat->flags & AVFMT_GLOBALHEADER)
    
            enc_ctx->flags |= CODEC_FLAG_GLOBAL_HEADER;
    
    }
    
    av_dump_format(ofmt_ctx, 0, filename, 1);
    
    if (!(ofmt_ctx->oformat->flags & AVFMT_NOFILE)) {
    
        ret = avio_open(&ofmt_ctx->pb, filename, AVIO_FLAG_WRITE);
    
        if (ret < 0) {
    
            LOGE("Could not open output file '%s'", filename);
    
            return ret;
    
        }
    
    }
    
    ret = avformat_write_header(ofmt_ctx, NULL); //wrong here
    
    if (ret < 0) {
    
        char buf[1024] = {0};
    
        av_strerror(ret, buf, 1024);
    
        LOGE("Error occurred when opening output file : %s\n", buf);
    
        return ret;
    
    }
    
    return 0;
    
}

    Here is the ffmpeg log. Pay close attention to the error I am getting which is :

    Error occurred when opening output file : Invalid argument

    Here is the rest of it :

    02-03 18:09:44.120 24571-24571/com.zhenbeiju.avplayer E/videoplayer: [mov,mp4,m4a,3gp,3g2,mj2 @ 0xebf33e00] After avformat_find_stream_info() pos: 680796 bytes read:308417 seeks:1 frames:48
    
02-03 18:09:44.120 24571-24571/com.zhenbeiju.avplayer E/videoplayer: [h264 @ 0xea72cc00] nal_unit_type: 7, nal_ref_idc: 3
    
02-03 18:09:44.120 24571-24571/com.zhenbeiju.avplayer E/videoplayer: [h264 @ 0xea72cc00] nal_unit_type: 8, nal_ref_idc: 3
    
02-03 18:09:44.121 24571-24571/com.zhenbeiju.avplayer E/videoplayer: Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/sdcard/test2.mp4':
    
02-03 18:09:44.121 24571-24571/com.zhenbeiju.avplayer E/videoplayer:   Metadata:
    
02-03 18:09:44.121 24571-24571/com.zhenbeiju.avplayer E/videoplayer:     major_brand     : 
    
02-03 18:09:44.121 24571-24571/com.zhenbeiju.avplayer E/videoplayer: mp42
    
02-03 18:09:44.121 24571-24571/com.zhenbeiju.avplayer E/videoplayer:     minor_version   : 
    
02-03 18:09:44.121 24571-24571/com.zhenbeiju.avplayer E/videoplayer: 0
    
02-03 18:09:44.121 24571-24571/com.zhenbeiju.avplayer E/videoplayer:     compatible_brands: 
    
02-03 18:09:44.121 24571-24571/com.zhenbeiju.avplayer E/videoplayer: isommp42
    
02-03 18:09:44.121 24571-24571/com.zhenbeiju.avplayer E/videoplayer:     creation_time   : 
    
02-03 18:09:44.121 24571-24571/com.zhenbeiju.avplayer E/videoplayer: 2017-01-23T08:22:57.000000Z
    
02-03 18:09:44.121 24571-24571/com.zhenbeiju.avplayer E/videoplayer:     com.android.version: 
    
02-03 18:09:44.121 24571-24571/com.zhenbeiju.avplayer E/videoplayer: 6.0.1
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer:   Duration: 
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer: 00:00:07.74
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer: , start: 
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer: 0.000000
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer: , bitrate: 
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer: 14377 kb/s
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer:     Stream #0:0
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer: (eng)
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer: , 1, 1/90000
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer: : Video: h264 (avc1 / 0x31637661), yuv420p, 1280x720, 13892 kb/s
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer: , SAR 1:1 DAR 16:9
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer: , 
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer: 30.02 fps, 
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer: 30 tbr, 
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer: 90k tbn, 
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer: 60.04 tbc
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer:  (default)
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer:     Metadata:
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer:       rotate          : 
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer: 90
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer:       creation_time   : 
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer: 2017-01-23T08:22:57.000000Z
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer:       handler_name    : 
    
02-03 18:09:44.122 24571-24571/com.zhenbeiju.avplayer E/videoplayer: VideoHandle
    
02-03 18:09:44.123 24571-24571/com.zhenbeiju.avplayer E/videoplayer:     Side data:
    
02-03 18:09:44.123 24571-24571/com.zhenbeiju.avplayer E/videoplayer:       
    
02-03 18:09:44.123 24571-24571/com.zhenbeiju.avplayer E/videoplayer: displaymatrix: rotation of -90.00 degrees
    
02-03 18:09:44.123 24571-24571/com.zhenbeiju.avplayer E/videoplayer:     Stream #0:1
    
02-03 18:09:44.123 24571-24571/com.zhenbeiju.avplayer E/videoplayer: (eng)
    
02-03 18:09:44.123 24571-24571/com.zhenbeiju.avplayer E/videoplayer: , 47, 1/48000
    
02-03 18:09:44.123 24571-24571/com.zhenbeiju.avplayer E/videoplayer: : Audio: aac (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 96 kb/s
    
02-03 18:09:44.123 24571-24571/com.zhenbeiju.avplayer E/videoplayer:  (default)
    
02-03 18:09:44.123 24571-24571/com.zhenbeiju.avplayer E/videoplayer:     Metadata:
    
02-03 18:09:44.123 24571-24571/com.zhenbeiju.avplayer E/videoplayer:       creation_time   : 
    
02-03 18:09:44.123 24571-24571/com.zhenbeiju.avplayer E/videoplayer: 2017-01-23T08:22:57.000000Z
    
02-03 18:09:44.123 24571-24571/com.zhenbeiju.avplayer E/videoplayer:       handler_name    : 
    
02-03 18:09:44.123 24571-24571/com.zhenbeiju.avplayer E/videoplayer: SoundHandle
    
02-03 18:09:44.124 24571-24571/com.zhenbeiju.avplayer E/videoplayer: [libx264 @ 0xdbf3dc00] using mv_range_thread = 56
    
02-03 18:09:44.126 24571-24571/com.zhenbeiju.avplayer E/videoplayer: [libx264 @ 0xdbf3dc00] using cpu capabilities: none!
    
02-03 18:09:44.197 24571-24571/com.zhenbeiju.avplayer E/videoplayer: [libx264 @ 0xdbf3dc00] profile High, level 4.0
    
02-03 18:09:44.199 24571-24571/com.zhenbeiju.avplayer E/videoplayer: Output #0, mp4, to '/sdcard/test3.mp4':
    
02-03 18:09:44.199 24571-24571/com.zhenbeiju.avplayer E/videoplayer:     Stream #0:0
    
02-03 18:09:44.199 24571-24571/com.zhenbeiju.avplayer E/videoplayer: , 0, 0/0
    
02-03 18:09:44.199 24571-24571/com.zhenbeiju.avplayer E/videoplayer: : Unknown: none
    
02-03 18:09:44.200 24571-24571/com.zhenbeiju.avplayer E/videoplayer:     Stream #0:1
    
02-03 18:09:44.200 24571-24571/com.zhenbeiju.avplayer E/videoplayer: , 0, 0/0
    
02-03 18:09:44.200 24571-24571/com.zhenbeiju.avplayer E/videoplayer: : Unknown: none
    
02-03 18:09:44.200 24571-24571/com.zhenbeiju.avplayer E/videoplayer: [file @ 0xdbdc71e0] Setting default whitelist 'file,crypto'
    
02-03 18:09:44.201 24571-24571/com.zhenbeiju.avplayer E/videoplayer: [mp4 @ 0xebf3a800] Could not find tag for codec none in stream #0, codec not currently supported in container
    
02-03 18:09:44.201 24571-24571/com.zhenbeiju.avplayer E/videoplayer: Error occurred when opening output file : Invalid argument

  • Anomalie #3875 : Impossible de voir les sous-rubriques

    9 février 2017, par denis -

    Juste pour préciser /158 donne en fait l’url complète /prog/2017/158/ qui pointe bien vers une rubrique.

    Et ça ne semble pas lié aux chiffres, si je crée une rubrique qui donne comme url coucou-coucou, j’ai bien accès à un article prog/2017/coucou-coucou/bonjour, si je la renomme en coucou l’url prog/2017/coucou/bonjour donne une erreur.

    C’est sans doute très marginal de se retrouver avec 2 urls /xxx et /xxx-xxx

Navigation