Recherche avancée

Médias (1)

Mot : - Tags -/MediaSPIP

Autres articles (35)

  • Configuration spécifique d’Apache

    4 février 2011, par

    Modules spécifiques
    Pour la configuration d’Apache, il est conseillé d’activer certains modules non spécifiques à MediaSPIP, mais permettant d’améliorer les performances : mod_deflate et mod_headers pour compresser automatiquement via Apache les pages. Cf ce tutoriel ; mode_expires pour gérer correctement l’expiration des hits. Cf ce tutoriel ;
    Il est également conseillé d’ajouter la prise en charge par apache du mime-type pour les fichiers WebM comme indiqué dans ce tutoriel.
    Création d’un (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

Sur d’autres sites (5550)

  • CANNOT get FFserver stream going

    18 septembre 2016, par Euroclydon37

    I want to preface this question with the fact that I am very very new to ffmpeg and even newer to ffserver.

    I cannot, for the life of me, get this thing going.
    I get :

    "Too large number of skipped frames 882933314374 > 60000"

    Also, ffplay gives me first frame is no keyframe

    Here is my ffserver.conf file

    HTTPPort 8090
    HTTPBindAddress 0.0.0.0
    MaxHTTPConnections 1000
    MaxClients 10
    MaxBandwidth 2000000
    NoDefaults

    ###############################################################################################

    <feed>
       File /tmp/test.ffm
       FileMaxSize 10000M
       ACL ALLOW localhost
    </feed>

    <stream>
    Format status

    # Only allow local people to get the status
       ACL allow localhost
    </stream>

    <stream>
       Feed test.ffm
       Format avi
       ACL ALLOW localhost
       ACL ALLOW 192.168.1.0
       NoAudio
       VideoSize 3840x2160
       VideoFrameRate 30
       Preroll 10
    </stream>

    ###############################################################################################

    And here is my ffmpeg command

    ffmpeg -i smaller.avi http://localhost:8090/test.ffm

    I’ve been fighting with this thing all day, googling like a madman the entire time. What am I doing wrong ? Any help will be welcomed enthusiastically.

  • Initializing hwaccel_context in libavcodec

    3 janvier 2018, par dloman

    I am trying to get hardware accelerated video working using libavcodec. I am using the hw_decode.c example as a starting point and am unable to get it to work. both AVCodecContext->hwaccel and AVCodecContext->hwaccel_context are NULL

    I belive some part of the hwaccel is working as I see the output

    libva info: VA-API version 0.39.0
    libva info: va_getDriverName() returns 0
    libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
    libva info: Found init function __vaDriverInit_0_39
    libva info: va_openDriver() returns 0

    Which is the same as when I run

    ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format vaapi -i input.mpg -f null -

    but immediately after that I get the following error message

    [h264 @ 0x1df2cc0] Hardware acceleration context (hwaccel_context) does not exist.
    Failed to get HW surface format.
    [h264 @ 0x1df2cc0] decode_slice_header error
    [h264 @ 0x1df2cc0] no frame!

    I looked at the similar question and the answer to this shows how to get a AVCodecContext->hwaccel. But even with the AVCodecContext->hwaccel being a valid VAApih264 decoder I still get the same error message.

    How do I initialize a AVCodecContext->hwaccel_context and after that what else do I need to do to get hardware accelerated video working in ffmpeg ?

  • 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