Recherche avancée

Médias (1)

Mot : - Tags -/censure

Autres articles (60)

  • Le profil des utilisateurs

    12 avril 2011, par

    Chaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
    L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...)

  • Configurer la prise en compte des langues

    15 novembre 2010, par

    Accéder à la configuration et ajouter des langues prises en compte
    Afin de configurer la prise en compte de nouvelles langues, il est nécessaire de se rendre dans la partie "Administrer" du site.
    De là, dans le menu de navigation, vous pouvez accéder à une partie "Gestion des langues" permettant d’activer la prise en compte de nouvelles langues.
    Chaque nouvelle langue ajoutée reste désactivable tant qu’aucun objet n’est créé dans cette langue. Dans ce cas, elle devient grisée dans la configuration et (...)

  • Sélection de projets utilisant MediaSPIP

    29 avril 2011, par

    Les exemples cités ci-dessous sont des éléments représentatifs d’usages spécifiques de MediaSPIP pour certains projets.
    Vous pensez avoir un site "remarquable" réalisé avec MediaSPIP ? Faites le nous savoir ici.
    Ferme MediaSPIP @ Infini
    L’Association Infini développe des activités d’accueil, de point d’accès internet, de formation, de conduite de projets innovants dans le domaine des Technologies de l’Information et de la Communication, et l’hébergement de sites. Elle joue en la matière un rôle unique (...)

Sur d’autres sites (4304)

  • How to solve issue for converting ismv file of h264 video codec and aac audio codec ?

    4 octobre 2013, par Priyal

    I want to convert transmux ismv file to mp4 format. ISMV file is encoded withe the following ffmpeg detail :

       Metadata:
    
   major_brand     : isml
    
   minor_version   : 1
    
   compatible_brands: piffiso2
    
   creation_time   : 2013-10-03 14:10:41
    
   Duration: 15:21:13.16, start: 0.000000, bitrate: 41 kb/s
    
   Stream #0:0(und): Audio: aac (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 64
    
                     kb/s (default)
    
   Metadata:
    
   creation_time   : 2013-10-03 14:10:41
    
   handler_name    : Audio
    
   Stream #0:1(und): Video: h264 (avc1 / 0x31637661), 1280x720, 3217 kb/s, 29.9
    
                     7 tbr, 10000k tbn, 20000k tbc (default)
    
Metadata:
    
   creation_time   : 2013-10-03 14:10:41
    
   handler_name    : Video
    
   Stream #0:2(und): Data: none (dfxp / 0x70786664), 32 kb/s (default)
    
   Metadata:
    
   creation_time   : 2013-10-03 14:10:41
    
   handler_name    : Text

    I used the following ffmpeg command to transmux :

     ffmpeg -y -ss 00:00:10 -i Encoder1.ismv -vcodec libx264 -ar 44100 -t 40 -preset slow -qp 0  
    
 Encoder.mp4

    I got output as :

     ffmpeg version N-56010-g54d628a Copyright (c) 2000-2013 the FFmpeg developers
    
 built on Sep  4 2013 00:44:27 with gcc 4.7.3 (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-libvo-aacenc --enable-libvo-
    
 amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxavs --
    
 enable-libxvid --enable-zlib
    
     libavutil      52. 43.100 / 52. 43.100
    
     libavcodec     55. 31.100 / 55. 31.100
    
     libavformat    55. 16.100 / 55. 16.100
    
     libavdevice    55.  3.100 / 55.  3.100
    
     libavfilter     3. 83.102 /  3. 83.102
    
     libswscale      2.  5.100 /  2.  5.100
    
     libswresample   0. 17.103 /  0. 17.103
    
     libpostproc    52.  3.100 / 52.  3.100
    
 [aac @ 040f1ba0] TYPE_FIL: Input buffer exhausted before END element found
    
 [h264 @ 00353120] AVC: nal size -729776398
    
 [h264 @ 00353120] no frame!
    
 [h264 @ 00353120] AVC: nal size -570515285
    
 [h264 @ 00353120] no frame!
    
 [h264 @ 00353120] AVC: nal size -1477874754
    
 [h264 @ 00353120] no frame!
    
 [h264 @ 00353120] AVC: nal size -712314563
    
 [h264 @ 00353120] no frame!
    
 [h264 @ 00353120] AVC: nal size -23151524
    
 [h264 @ 00353120] no frame!
    
 [h264 @ 00353120] AVC: nal size -592499201
    
 [h264 @ 00353120] no frame!
    
 [h264 @ 00353120] AVC: nal size 225768173
    
 [h264 @ 00353120] no frame!
    
 [h264 @ 00353120] AVC: nal size 698187359
    
 [h264 @ 00353120] AVC: nal size 635127544
    
 [h264 @ 00353120] no frame!
    
 [h264 @ 00353120] AVC: nal size -1242688339
    
 [h264 @ 00353120] AVC: nal size 269543071
    
 [h264 @ 00353120] no frame!
    
 [mov,mp4,m4a,3gp,3g2,mj2 @ 0035e840] decoding for stream 1 failed
    
 [mov,mp4,m4a,3gp,3g2,mj2 @ 0035e840] Could not find codec parameters for stream
    
  1 (Video: h264 (avc1 / 0x31637661), 1280x720, 3217 kb/s): unspecified pixel form
    
  at Consider increasing the value for the 'analyzeduration' and 'probesize' options
    
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'C:\inetpub\media\archives\DEFAULT WEB S
    
  ITE\PushToPUblishPoint\Eagan_12034_Soccer_3-10-2013_14_10_19-isml\2013-10-03-14-
    
  10-35-436\Segment001\Encoder1.ismv':
    
   Metadata:
    
   major_brand     : isml
    
   minor_version   : 1
    
   compatible_brands: piffiso2
    
   creation_time   : 2013-10-03 14:10:41
    
   Duration: 15:21:13.16, start: 0.000000, bitrate: 41 kb/s
    
   Stream #0:0(und): Audio: aac (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 64
    
                     kb/s (default)
    
    Metadata:
    
   creation_time   : 2013-10-03 14:10:41
    
   handler_name    : Audio
    
   Stream #0:1(und): Video: h264 (avc1 / 0x31637661), 1280x720, 3217 kb/s, 29.9
    
                     7 tbr, 10000k tbn, 20000k tbc (default)
    
   Metadata:
    
   creation_time   : 2013-10-03 14:10:41
    
   handler_name    : Video
    
   Stream #0:2(und): Data: none (dfxp / 0x70786664), 32 kb/s (default)
    
   Metadata:
    
   creation_time   : 2013-10-03 14:10:41
    
   handler_name    : Text
    

    
 [buffer @ 04679480] Unable to parse option value "-1" as pixel format
    
               Last message repeated 1 times
    
 [buffer @ 04679480] Error setting option pix_fmt to value -1.
    
 [graph 0 input from stream 0:1 @ 040f7380] Error applying options to the filter.
    

    
 Error opening filters!

    Please suggest the solution for Windows OS

  • The First Problem

    19 janvier 2011, par Multimedia Mike — HTML5

    A few years ago, The Linux Hater made the following poignant observation regarding Linux driver support :

    Drivers are only just the beginning... But for some reason y’all like to focus on the drivers. You know why lusers do that ? Because it just happens to be the problem that people notice first.

    And so it is with the HTML5 video codec debate, re-invigorated in the past week by Google’s announcement of dropping native H.264 support in their own HTML5 video tag implementation. As I read up on the fiery debate, I kept wondering why people are so obsessed with this issue. Then I remembered the Linux Hater’s post and realized that the video codec issue is simply the first problem that most people notice regarding HTML5 video.

    I appreciate that the video codec debate has prompted Niedermayer to post on his blog once more. Otherwise, I’m just munching popcorn on the sidelines, amused and mildly relieved that the various factions are vociferously attacking each other rather than that little project I help with at work.

    Getting back to the "first problem" aspect— there’s so much emphasis on the video codec ; I wonder why no one ever, ever mentions word one about an audio codec. AAC is typically the codec that pairs with H.264 in the MPEG stack. Dark Shikari once mentioned that "AAC’s licensing terms are exponentially more onerous than H.264′s. If Google didn’t want to use H.264, they would sure as hell not want to use AAC." Most people are probably using "H.264" to refer to the entire MPEG/H.264/AAC stack, even if they probably don’t understand what all of those pieces mean.

    Anyway, The Linux Hater’s driver piece continues :

    Once y’all have drivers, the fight will move to the next layer up. And like I said, it’s a lot harder at that layer.

    A few months ago, when I wanted to post the WebM output of my new VP8 encoder and thought it would be a nice touch to deliver it via a video tag, I ignored the video codec problem (just encoded a VP8/WebM file) only to immediately discover a problem at a different layer— specifically, embedding a file using a video tag triggers a full file download when the page is loaded, which is unacceptable from end user and web hosting perspectives. This is a known issue but doesn’t get as much attention, I guess because there are bigger problems to solve first (c.f. video codec issue).

    For other issues, check out the YouTube blog’s HTML5 post or Hulu’s post that also commented on HTML5. Issues such as video streaming flexibility, content protection, fullscreen video, webcam/microphone input, and numerous others are rarely mentioned in the debates. Only "video codec" is of paramount importance.

    But I’m lending too much weight to the cacophony of a largely uninformed internet debate. Realistically, I know there are many talented engineers down in the trenches working to solve at least some of these problems. To tie this in with the Linux driver example, I’m consistently stunned these days regarding how simple it is to get Linux working on a new computer— most commodity consumer hardware really does just work right out of the box. Maybe one day, we’ll wake up and find that HTML5 video has advanced to the point that it solves all of the relevant problems to make it the simple and obvious choice for delivering web video in nearly all situations.

    It won’t be this year.

  • Revision 30118 : protéger des erreurs si pas configuré

    23 juillet 2009, par kent1@… — Log

    protéger des erreurs si pas configuré

Navigation