Recherche avancée

Médias (0)

Mot : - Tags -/médias

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

Autres articles (93)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

  • Gestion de la ferme

    2 mars 2010, par

    La ferme est gérée dans son ensemble par des "super admins".
    Certains réglages peuvent être fais afin de réguler les besoins des différents canaux.
    Dans un premier temps il utilise le plugin "Gestion de mutualisation"

Sur d’autres sites (14276)

  • Chromecast HLS : Unable to derive timescale

    31 juillet 2020, par Scott

    I'm trying to get fmp4 HLS playing back on a new Chromecast (3rd gen I believe, not Ultra).

    


    I've tried encoding the content with ffmpeg using both x264 and h264 libraries.
The main profile initially gives me a codec not supported error, remove the codec list from the hls manifest fixes this issue.

    


    Switching to baseline (which is not ideal) doesn't give the codec error.

    


    Both then (after removing the codec definitions or using baseline) give the following error :

    


    Uncaught Error: Unable to derive timescale
    at Xl (www.gstatic.com/cast/sdk/libs/mediaplayer/1.0.0/media_player.js:344)
    at Y.$e (www.gstatic.com/cast/sdk/libs/mediaplayer/1.0.0/media_player.js:337)
    at Y.k.processSegment (www.gstatic.com/cast/sdk/libs/mediaplayer/1.0.0/media_player.js:340)
    at Am.k.processSegment (www.gstatic.com/cast/sdk/libs/mediaplayer/1.0.0/media_player.js:384)
    at Mj.$e (www.gstatic.com/cast/sdk/libs/mediaplayer/1.0.0/media_player.js:238)
    at Wj (www.gstatic.com/cast/sdk/libs/mediaplayer/1.0.0/media_player.js:236)
    at Oj (www.gstatic.com/cast/sdk/libs/mediaplayer/1.0.0/media_player.js:240)
    at Mj.fd (www.gstatic.com/cast/sdk/libs/mediaplayer/1.0.0/media_player.js:239)
    at Nc (www.gstatic.com/cast/sdk/libs/mediaplayer/1.0.0/media_player.js:39)
    at wi.Mc.dispatchEvent (www.gstatic.com/cast/sdk/libs/mediaplayer/1.0.0/media_player.js:38)


    


  • How to create an encoding ladder for any aspect ratio ?

    18 avril 2024, par volume one

    For a given video uploaded by a user, I need to create three versions of it to cover standard definition (SD), high definition (HD), full high definition (FHD), and ultra high definition (UHD e.g. 4K). "resolution/encoding ladders" for standard aspect ratios like 16:9 and 4:3.

    


    For 4:3 we might have :

    


    640 x 480
960 x 720
1440 x 1080
2880 x 2160


    


    For 16:9 we might have :

    


    854 x 480
1280 x 720
1920 x 1080
3840 x 2160


    


    If a user uploads a file in either of those aspect ratios, we can create the four different versions because the resolution standards are known.

    


    However if a user uploads a video with an unforseen aspect ratio, say 23:19, then how would you go about formatting that video into SD, HD, FHD, and UHD versions ?

    


    If a 23:19 video is indeed uploaded then I am not looking to resize it to fit a different 'standard' aspect ratio. It must remain the same aspect ratio, but have four quality versions. The problem is what height and width sizes to create for non-standard resolutions ?

    


    I have already come accross many aspect ratios like 16:10, 21:9, 1.85:1, 2.39:1. How could I take care of making quality variations of those ?

    


    I am using Node.js and FFMpeg for video processing.

    


  • Compiling FFMPEG on CentOS DigitalOcean

    29 juillet 2015, par coder_uk

    I set up a DigitalOcean instance running CentOS 6.5 and successfully followed the guide to compile FFMPEG (https://trac.ffmpeg.org/wiki/CompilationGuide/Centos). Hurrah !

    But of course I realised that by default, DigitalOcean creates a root user and so ffmpeg now lives in /root/bin/ffmpeg. Which isn’t ideal because when I want to exec the ffmpeg bin from nginx, I would have to run nginx as root for it to have permission.

    Questions ...

    1) Long-shot, but presumably if I change the owner of the ffmpeg binary to nginx, it still won’t work, because nginx won’t be able to access the /root folder it is in. Correct ?

    2) I could run nginx as root (’user root’). But this seems like a very bad idea. Correct ?

    3) Which leaves me with the option of creating a new user, and then compiling ffmpeg into its home folder. But : which user ? EC2 creates ’ec2-user’, so should I make my own equivalent for DO ? But then won’t I have to run nginx as that user, else I’ll run into the same problem ?

    Or should I compile ffmpeg into the ’nginx’ home folder, if indeed it has one ? Is that how it is supposed to be done ?

    Since compiling ffmpeg takes ages, I don’t want to keep doing it, and the static files all seem very out of date. Thanks

Navigation