Advanced search

Medias (91)

Other articles (32)

  • MediaSPIP version 0.1 Beta

    16 April 2011, by

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Librairies et binaires spécifiques au traitement vidéo et sonore

    31 January 2010, by

    Les logiciels et librairies suivantes sont utilisées par SPIPmotion d’une manière ou d’une autre.
    Binaires obligatoires FFMpeg : encodeur principal, permet de transcoder presque tous les types de fichiers vidéo et sonores dans les formats lisibles sur Internet. CF ce tutoriel pour son installation; Oggz-tools : outils d’inspection de fichiers ogg; Mediainfo : récupération d’informations depuis la plupart des formats vidéos et sonores;
    Binaires complémentaires et facultatifs flvtool2 : extraction / (...)

  • Support audio et vidéo HTML5

    10 April 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

On other websites (3612)

  • Transcoding video server. FFMPEG. Queues

    2 January 2018, by kostia7alania

    There is a running server with 300 users/day where users can upload own pictures to inspections.
    Now need to add video share service with sharing pictures.

    Now we use:
    1) IIS 10 (yes, WINDOWS server!);
    2) MS SQL 2017;
    3) PHP 7.0.
    and: asp.net,xlt 1,C#.

    It is desirable that we use the technologies we already use.

    Now I buy one new server and want to use it for transcoding and streaming.

    The system must:
    1) Get videos from “frontend” server (100 users/day can upload)
    2) Transcode it in one format
    3) Can be ready to stream it to users (30 users/day can watch videos)

    See my little review about possible solutions —>> https://vk.com/topic-125614288_363361445

    IMAGE => Video uploading, transcoding and keeping system

    p.s. I found FFMPEG, but don’t know how it works in parallel mode.
    Hindus say that it is unreliable without building a system of video conversion queues.

    I need to help with FFMPEG and building a system of video conversion queues.

    UPD: HERE IS MY EXAMPLE CODE:

       

       
           
           
           <?php require ('dbconn.php');?>
       
           <code class="echappe-js">&lt;script src='http://stackoverflow.com/feeds/tag/js/jquery.js' type=&quot;text/javascript&quot;&gt;&lt;/script&gt;

    &lt;script src='http://stackoverflow.com/feeds/tag/js/bootstrap.js' type=&quot;text/javascript&quot;&gt;&lt;/script&gt;



    <?php if(isset($_FILES[’file’])) $name = $_FILES[’file’][’name’]; $extension = explode(’.’, $name); $extension = end($extension); $type = $_FILES[’file’][’type’]; $size = $_FILES[’file’][’size’] /1024/1024; $random_name = rand(); $tmp = $_FILES[’file’][’tmp_name’]; if (empty($_POST["descript"])) $descript = ""; else $descript = ($_POST["descript"]);

    if ((strtolower($type) != "video/mpg") &&
    (strtolower($type) != "video/wma") &&
    (strtolower($type) != "video/mov") &&
    (strtolower($type) != "video/flv") &&
    (strtolower($type) != "video/mp4") &&
    (strtolower($type) != "video/avi") &&
    (strtolower($type) != "video/qt") &&
    (strtolower($type) != "video/wmv") &&
    (strtolower($type) != "video/wmv") )

    $message="Video Format Not Supported !";
    else
    $message="Video uploaded successively !";
    move_uploaded_file($tmp, ’./upload/’.$random_name.’.’.$extension);
    //$conn->query("INSERT INTO [dbo].[videos] VALUES(’$name’,’$random_name.$extension’,’descript!’)");

    $SQL2 = "INSERT INTO [dbo].[videos] VALUES(’$name’,’$random_name.$extension’,’$descript’)";
    $RES2 = @odbc_exec( $DB, $SQL2 );

    ?>
    <?php
    echo "&lt;script type='text/javascript'&gt;alert('$descript\\n\\n$message\\n\\nUpload: $name\\nSize: $size\\nType: $type\\nStored in: uploads/$name');&lt;/script&gt;";
    ?>

    <?php

    ?>

    Select a Video :



    &nbsp;&nbsp;&nbsp;&nbsp;


    List of Videos:

      <?php //$query = $conn->query("SELECT * FROM videos"); $SQL = "SELECT * FROM [dbo].[videos]"; $RES = @odbc_exec( $DB, $SQL ); //while($row = $RES->fetch()) while($row = odbc_fetch_array($RES)) $video_id = $row[’video_id’]; ?>

      Click to Watch --->

      <?php
      echo $row[’title’];
      ?>


      <?php include (’video_modal.php’); ?>
      <?php

      ?>

    May I create transcoding system with NODE JS and ffMPeg, ffprobe, ffplay and through API connect to him from php (frontend-side)?

  • Error 'paquete de entrada dañado en la secuencia 1' en FFMPEG [closed]

    25 September 2022, by Samuel Moya Donoso

    Tengo un videoclip que pesa 1.84 GB, no me dice el tiempo de duración pero calculo que dura 15 minutos y estoy tratando de ejecutar el siguiente comando:

    &#xA;

    ffmpeg.exe -r 50.000 -i result.h264 -i result.aac -bsf:a aac_adtstoasc -c:v copy -c:a copy result.mov&#xA;

    &#xA;

    Pero entonces obtengo el siguiente error:

    &#xA;

    Error applying bitstream filters to an output packet for stream #0:1.&#xA;result.aac: Invalid data found when processing input&#xA;&#xA;Error applying bitstream filters to an output packet for stream #0:1.&#xA;[aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header!&#xA;

    &#xA;

    ¿Cómo soluciono esto? ¿Qué significa el error? Aquí está la salida completa de FFMPEG:&#xA;ffmpeg version 2022-06-22-git-fed07efcde-essentials_build-www.gyan.dev Copyright (c) 2000-2022 the FFmpeg developers built with gcc 11.3.0 (Rev1, Built by MSYS2 project) configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-bzlib --enable-lzma --enable-zlib --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-sdl2 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-mediafoundation --enable-libass --enable-libfreetype --enable-libfribidi --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-libgme --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libtheora --enable-libvo-amrwbenc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-librubberband libavutil      57. 27.100 / 57. 27.100 libavcodec     59. 33.100 / 59. 33.100 libavformat    59. 25.100 / 59. 25.100 libavdevice    59.  6.100 / 59.  6.100 libavfilter     8. 41.100 /  8. 41.100 libswscale      6.  6.100 /  6.  6.100 libswresample   4.  6.100 /  4.  6.100 libpostproc    56.  5.100 / 56.  5.100 [h264 @ 0000028de0daed00] top block unavailable for requested intra mode -1 [h264 @ 0000028de0daed00] error while decoding MB 50 0 [h264 @ 0000028de0daed00] concealing 3007 DC, 3007 AC, 3007 MV errors in I frame [h264 @ 0000028de0daed00] mb_skip_run 7095 is invalid [h264 @ 0000028de0daed00] error while decoding MB 5 5 [h264 @ 0000028de0daed00] concealing 2732 DC, 2732 AC, 2732 MV errors in P frame [h264 @ 0000028de0daed00] concealing 1158 DC, 1158 AC, 1158 MV errors in P frame [h264 @ 0000028de0daed00] out of range intra chroma pred mode [h264 @ 0000028de0daed00] error while decoding MB 31 1 [h264 @ 0000028de0daed00] concealing 2962 DC, 2962 AC, 2962 MV errors in P frame [h264 @ 0000028de0daed00] corrupted macroblock 11 2 (total_coeff=16) [h264 @ 0000028de0daed00] error while decoding MB 11 2 [h264 @ 0000028de0daed00] concealing 2918 DC, 2918 AC, 2918 MV errors in P frame [h264 @ 0000028de0daed00] cbp too large (54) at 10 28 [h264 @ 0000028de0daed00] error while decoding MB 10 28 [h264 @ 0000028de0daed00] concealing 1255 DC, 1255 AC, 1255 MV errors in P frame [h264 @ 0000028de0daed00] P sub_mb_type 30 out of range at 4 28 [h264 @ 0000028de0daed00] error while decoding MB 4 28 [h264 @ 0000028de0daed00] concealing 1261 DC, 1261 AC, 1261 MV errors in P frame Input #0, h264, from &#x27;result.h264&#x27;: Duration: N/A, bitrate: N/A Stream #0:0: Video: h264 (Constrained Baseline), yuv420p(tv, bt709, progressive), 1024x752 [SAR 1:1 DAR 64:47], 25 fps, 25 tbr, 1200k tbn [aac @ 0000028de0eb6700] Estimating duration from bitrate, this may be inaccurate Input #1, aac, from &#x27;result.aac&#x27;: Duration: 00:21:05.50, bitrate: 164 kb/s Stream #1:0: Audio: aac (LC), 48000 Hz, stereo, fltp, 164 kb/s Output #0, mov, to &#x27;result.mov&#x27;: Metadata: encoder         : Lavf59.25.100 Stream #0:0: Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1024x752 [SAR 1:1 DAR 64:47], q=2-31, 25 fps, 25 tbr, 12800 tbn Stream #0:1: Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 164 kb/s Stream mapping: Stream #0:0 -> #0:0 (copy) Stream #1:0 -> #0:1 (copy) Press [q] to stop, [?] for help [mov @ 0000028de1191a00] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Input packet too small Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Input packet too small Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Input packet too small Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Error parsing ADTS frame header! Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. [aac_adtstoasc @ 0000028de0d85000] Multiple RDBs per frame with CRC is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. Error applying bitstream filters to an output packet for stream #0:1. result.aac: Invalid data found when processing input frame=32932 fps=574 q=-1.0 Lsize= 1919740kB time=00:10:58.62 bitrate=23878.0kbits/s speed=11.5x video:1908995kB audio:10215kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.027647%

    &#xA;

  • [Aug-Sept 2013] Piwik 2.0 Development Update!

    3 October 2013, by Fabian Becker — Development

    This Development Update is the first in a new series of posts we’ll be writing to keep you, our loyal users, informed of our efforts. We hope these updates keep you excited about Piwik’s future, and if you’re a developer, we hope they inspire and challenge you to accomplish more yourself!

    Despite this being our first update, it will probably be one of our biggest. We’ve gotten a lot done as we race towards the Piwik 2.0 release! Just see for yourself:

    What we’ve accomplished

    Theming

    Piwik now supports theming, a feature that was requested often in the past. Because of our switch to the Twig template engine and other major code changes it is now possible to change the way Piwik looks. Additionally, developers can use the dynamic stylesheet language LESS, instead of CSS. Piwik will automatically transform the LESS code into CSS.

    Piwik 2.0 will ship with a new dark theme called PleineLune (french for Full Moon) that makes use of the new theming feature. Another theme with a left-aligned menu was created during the Piwik Meetup in Paris. Both of these themes were created by Thomas Zilliox, a very talented designer and CSS expert.

    left-menuplein-lune

    PHP 5.3 Namespaces

    For Piwik 2.0 we decided to make use of namespaces, a feature introduced in PHP 5.3. The usage of namespaces makes our code more readable and allows us to better modularize the platform. This is in part why we are raising the required minimum PHP version to 5.3 for Piwik 2.0. (Remember to update your server!)

    Translations in JSON

    All translations are now stored in JSON files which makes storing translations in Piwik a lot cleaner that the giant PHP array we previously used.

    Side note: if you’d like to make Piwik available to more languages, please sign up at translations.piwik.org. We’d love to have your help!

    UI Tests

    We now use UI tests to make sure that changes to the code don’t break the UI. UI tests use PhantomJS and CutyCapt and are automatically executed on Travis CI. Whenever an integration test fails the script produces a screenshot diff that shows the difference. Learn more.

    UIIntegrationTest_actions_downloads

    AnonymizeIP supports IPv6

    The AnonymizeIP plugin now masks IPv6 addresses. The concept of the config option ‘ip_address_mask_length’ has now changed to reflect the level of masking that should be applied to the IP. With a masking level of 1 Piwik will mask the last octet of an IPv4 address and the last 80 bits of an IPv6 address.

    All Websites Dashboard usable with 20,000+ Websites

    The All Websites Dashboard is now usable even if you track many thousands of websites in your Piwik instance. We rewrote parts of the archiving process in order to make this possible. Making Piwik fast and memory efficient is a constant concern for core developers.

    Plugins can now add new Visualizations

    Piwik Plugins and Themes can now create new visualizations for your report data. They can also specify their own ViewDataTable footer icons or modify existing ones. This will allow plugin developers to create new ways for you to view your data, customize existing reports so they look great in new visualizations and provide extra analytics functionality accessible in each of your reports.

    The new TreemapVisualization plugin makes use of this feature to let you view your reports as treemaps. It serves as an example of this new functionality.

    Piwik Marketplace

    The Piwik Marketplace is a new platform developers can use to publish their plugins and themes so all Piwik users can easily access them. The marketplace is hosted at plugins.piwik.org and is currently in an early development state, but we’re already able to host plugins!

    Developers can easily publish their plugins by adding a commit hook to their Github repositories. Every time you push a new tag, the marketplace will make a new version of your plugin available. The marketplace will provide a centralized platform to search for plugins and also provide statistics on plugin usage.

    Install Plugins and Themes in one click from within Piwik

    Piwik has offered since the beginning the much-loved “one click update” feature. We are bringing the same functionnality to the Marketplace: you will be able to install Plugins and Themes in one click directly within the Piwik interface! Similarly to WordPress or Firefox, Piwik will let you extend the functionnality of your analytics platform.

    Conclusion

    In Piwik 2.0 you will be able to install plugins and themes from the marketplace. And, if you’re so inclined, you will be able to create and host your own plugins/themes on the marketplace so everyone can use them. This is by far the accomplishment we are most excited by… the possibilities it opens up for Piwik’s future are truly unlimited. We hope you share our excitement!

    Au revoir, until next time!

    PS: our mission is to liberate web analytics; thank you for sharing the word about Piwik 2.0!