Recherche avancée

Médias (0)

Mot : - Tags -/navigation

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

Autres articles (79)

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

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

Sur d’autres sites (11366)

  • VOD HTTP Live Streaming in addition to video delivery using (flash) player

    29 mai 2012, par Luuk D. Jansen

    I have created a delivery system for HTTP Live Streaming using the Play ! framework and FFMPEG. Files are encoded on different bandwidths and subsequent segmented for delivery, current, to iOS devices.

    However, I would like to extend to embedded players (cross platform) on websites and in the future Android devices. What would be the best approach, without having too much hard drive space overhead. I could encode the MP4 files for the different bitrates, and leave them as one file.

    Is there a way that the segmented files (using the FFMPEG segment function) could be used in a Flash player and on Android devices ? It would keep the system simple, as FFMPEG seems to do a good job on creating the segments (taking in account keyframes etc.)

    I could use JWPlayer, but I don't have pseudo-live-streaming, so don't think it could switch and searching would prove difficult. It could also mean that I would need to segment on the fly when a request from an iOS device comes, which adds a small delay and also some hard-drive/processor activity. To overcome the pseudo-live-streaming issue I could redact any request to an Apache server with it enabled, but will add further complexity. Not having pseudo-live streaming for the segmented files doesn't seem that much of an issue as they are only 10 minutes each.

    Anybody who has any thoughts on moving forward.

  • Steps to develop Live video chat application for iOS. Please guide [closed]

    3 avril 2013, par Er Amit Sachdeva

    I want to develop a application which enables to user for live video chat between two devices which are connected under LAN. Please guide me a right path to go for learning/implementation of that.

  • Encoding for HTTP Live Streaming with Xuggle

    26 mai 2012, par Luuk D. Jansen

    I have created a server system based on Xuggle to encode an incoming file to H264 and segment it. However, when playing the video back in Quicktime it almost works (with a small hiccup in the audio sometimes) but when changing fro one quality stream to another the image gets lost.

    So I ran the 'mediastreamvalidator'and got the following error :

    ERROR : (-1) Unknown video codec : 1836069494 (program 0, track 0)
    ERROR : (-1) failed to parse segment as either an MPEG-2 TS or an ES

    So I used FFMPEG to get some info on the codex :
    The result of my Xuggler encoding :

    Input #0, mpegts, from 'segment_0.ts':
    
  Duration: 00:00:09.40, start: 0.000000, bitrate: 3618 kb/s
    
  Program 1 
    
    Metadata:
    
      service_name    : Service01
    
      service_provider: FFmpeg
    
    Stream #0.0[0x100]: Video: mpeg2video (Main), yuv420p, 960x540 [PAR 1:1 DAR 16:9], 104857 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc
    
    Stream #0.1[0x101]: Audio: mp2, 48000 Hz, stereo, s16, 128 kb/s

    The result of a file created by Compressor :

    Seems stream 0 codec frame rate differs from container frame rate: 180000.00 (180000/1) -> 25.00 (25/1)
    
Input #0, mpegts, from 'fileSequence1.ts':
    
  Duration: 00:00:09.97, start: 19.984578, bitrate: 5308 kb/s
    
  Program 1 
    
    Stream #0.0[0x101]: Video: h264 (Main), yuv420p, 960x540, 25 tbr, 90k tbn, 180k tbc
    
    Stream #0.1[0x102]: Audio: aac, 22050 Hz, stereo, s16, 32 kb/s

    The main difference seems to me that for the Xuggler encoded file it says Video : mpeg2video instead of h264. However, while encoding I did specifically set the Coder to ICodec.ID.CODEC_ID_H264.

    How can I force it to use h264. The same with audio. I specified AAC and get MP2.

    I subsequent used FFMPEG directly and that results in :

    Input #0, mpegts, from 'encoded.ts':
    
  Duration: 00:00:24.16, start: 1.400000, bitrate: 360 kb/s
    
  Program 1 
    
    Metadata:
    
      service_name    : Service01
    
      service_provider: FFmpeg
    
    Stream #0.0[0x100]: Video: h264 (Main), yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], 25 fps, 25 tbr, 90k tbn, 50 tbc
    
    Stream #0.1[0x101](eng): Audio: aac, 48000 Hz, stereo, s16, 57 kb/s

    That looks better. I could use FFMPEG directly, but by using Xuggler I can segment the file while easier keep track of progress of the process.

Navigation