Recherche avancée

Médias (1)

Mot : - Tags -/école

Autres articles (86)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • 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 (...)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    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 (...)

Sur d’autres sites (9675)

  • When creating a Xing or Info tag in an MP3, may I use any MP3 header or does it have to match other frames ?

    13 décembre 2019, par Alexis Wilke

    I have a set of bare MP3 files. Bare as in I removed all tags (no ID3, no Xing, no Info) from those files.

    Just before sending one of these files to the client, I want to add an Info tag. All of my files are CBR so we will use an Info tag (no Xing).

    Right now I get the first 4 bytes of the existing MP3 to get the Version (MPEG-1, Layer III), Bitrate, Frequency, Stereo Mode, etc. and thus determine the size of one frame. I create the tag that way, reusing these 4 bytes for the Info tag and determining the size of the frame.

    For those wondering, these 4 bytes may look like this :

    FF FB 78 04

    To me it felt like you are expected to use the exact same first 4 bytes in the Info tag as found in the other audio frames of the MP3, but when using ffmpeg, they stick an Info tag with a hard coded header (wrong bitrate, wrong frequency, etc.)

    My question is : Is ffmpeg really doing it right ? (LAME doesn’t do that) Could I do the same, skipping the load of the first 4 bytes and still have the greater majority of the players out there play my files as expected ?

    Note : since I read these 4 bytes over the network, it would definitely save a lot of time and some bandwidth to not have to load these 4 bytes on a HEAD request. Resources I could use for the GET requests instead...

  • How to see FFmpeg command MovePY uses ?

    16 novembre 2019, par user319862

    I am trying to figure out why moviepy doesn’t output expected results. How can I log the FFmpeg command that it uses so that I can compare ?

  • What version of FFMPEG should I use on DEBIAN to transcode RTSP to RTMP ?

    20 août 2013, par user300675

    I was using that command :

       ffmpeg -i rtsp://login:password@90.70.42.54:554/axis-media/media.amp -f flv  rtmp://localhost:1935/live/yarek

    WHich worked fine on 1 windows,

    This command gives errors on linux1
    (ffmpeg version 0.8.6-4:0.8.6

    WriteN, RTMP send error 10053 (129 bytes)
    
WriteN, RTMP send error 10053 (45 bytes)
    
WriteN, RTMP send error 10038 (42 bytes)
    
av_interleaved_write_frame(): Operation not permitted

    and gives errors on Linux2 : (ffmpeg version 0.7.15)

    [h264 @ 0x98e2f80] RTP: PT=60: bad cseq c54f expected=b90c
    
[h264 @ 0x98e2f80] RTP: PT=60: bad cseq b90c expected=c551
    
[h264 @ 0x98e2f80] RTP: PT=60: bad cseq c552 expected=b90f
    
[rtsp @ 0x98de5e0] Estimating duration from bitrate, this may be inaccurate
    

    
Seems stream 0 codec frame rate differs from container frame rate: 180000.00 (180000/1) -> 90000.00 (180000/2)
    
Input #0, rtsp, from 'rtsp://login:password@90.70.42.54:554/axis-media/media.amp':
    
  Metadata:
    
    title           : Media Presentation
    
  Duration: N/A, start: -4756.582667, bitrate: N/A
    
    Stream #0.0: Video: h264 (Main), yuvj420p, 1024x768 [PAR 1:1 DAR 4:3], 90k tbr, 90k tbn, 180k tbc

    So I am 100% sure that the command line is GOOD, but FFMPEG is bad.

    My question is : What version of FFMPEG should I use on DEBIAN to transcode RTSP to RTMP ?

    Can someone recommend me a CORRECT version of FFMPEG that works ?

    Regards

Navigation