Recherche avancée

Médias (1)

Mot : - Tags -/artwork

Autres articles (23)

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

  • D’autres logiciels intéressants

    12 avril 2011, par

    On ne revendique pas d’être les seuls à faire ce que l’on fait ... et on ne revendique surtout pas d’être les meilleurs non plus ... Ce que l’on fait, on essaie juste de le faire bien, et de mieux en mieux...
    La liste suivante correspond à des logiciels qui tendent peu ou prou à faire comme MediaSPIP ou que MediaSPIP tente peu ou prou à faire pareil, peu importe ...
    On ne les connais pas, on ne les a pas essayé, mais vous pouvez peut être y jeter un coup d’oeil.
    Videopress
    Site Internet : (...)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

Sur d’autres sites (4425)

  • Warning in pepeline of stream audio + Video gstreamer

    18 avril 2014, par user3212448

    i use this pepline for stream audio and video from RPI to Windows8
    But i have 2 warning in client and Server ,

    pepeline for client :

    gst-launch-1.0 udpsrc port=5000 ! "application/x-rtp, media=(string)video, \
    clock-rate=(int)90000, encoding-name=(string)MP2T, payload=(int)33, ssrc=(uint)4251539348, \
    timestamp-offset=(uint)2033210929, seqnum-offset=(uint)34671" ! rtpmp2tdepay \
    ! tsparse ! tsdemux  ! "video/x-h264" ! avdec_h264 ! autovideosink

    Server (RPI)

    gst-launch-1.0 rpicamsrc bitrate=1000000 ! "video/x-h264,width=640,height=480" !\
    queue ! h264parse ! queue ! mux.  alsasrc device=hw:1,0 ! audioconvert ! \
    lamemp3enc ! "audio/mpeg"! queue !   mux. mpegtsmux name=mux ! queue ! \
    udpsink host=192.168.1.9 port=5000 -v

    Warning client :

    Additional debug info :
    gstrtpbasedepayload.c(381) : gst_rtp_base_depayload_chain () : /GstPipeline:pipeli
    ne0/GstRtpMP2TDepay:rtpmp2tdepay0 :
    Received invalid RTP payload, dropping
    WARNING : from element /GstPipeline:pipeline0/GstRtpMP2TDepay:rtpmp2tdepay0 : Coul
    d not decode stream.

    Warning in RPI

    WARNING : from element /GstPipeline:pipeline0/GstAlsaSrc:alsasrc0 : Can't record audio fast enough
    Additional debug info :
    gstaudiobasesrc.c(848) : gst_audio_base_src_create () : /GstPipeline:pipeline0/GstAlsaSrc:alsasrc0 :
    Dropped 8820 samples. This is most likely because downstream can't keep up and is consuming samples too slowly.

    any one can help me ?
    best regards

  • Display formatted date and time over frames using ffmpeg

    28 août 2020, par marcman

    I've gone through a handful of questions on here (this, this, this, etc) concerning overlaying the date and time on videos using ffmpeg, but I haven't been able to figure out the solution.

    


    I personally have found the ffmpeg documentation difficult to parse as well regarding drawing text that updates every (N) frame(s).

    


    I have the exif data from a movie specifying when it was created. I'd like to be able to emblazen that over the movie (as though it were a home video from some old VHS tape). For example, let's say I have a video from January 2, 2012 at 10:33:53. I'd like to be able to show "Jan 2, 2012 10:33:53am" on the lower right in white text. The spatial positioning and color are clear to me, but just how to go from the timestamp information I have to the formatted expansion is proving to be quite difficult for me. I have succeeded in getting a clock starting from 00:00:00.00 and counting up (using timecode and timecode_rate), but unfortunately I can't get much more than that.

    


    My question is : what is the proper datetext command that will allow me to both (a) provide the start time, and (b) format it with the proper expansion.

    



    


    As a bonus, if you can also point me to how to do this using the wonderful ffmpeg-python library, it would be even better. That library is quite good, but it does not appear to be actively maintained anymore.

    


  • ffmpeg's segment_atclocktime cuts at inaccurate times for audio

    3 mai 2023, par Ross Richardson

    I am using ffmpeg's segment format to save files of an AAC stream to disk in hourly segments.
The segmenting works well, but the files are segmented/cut at different times in the clock each hour using segment_atclocktime

    


    I would like each to be exactly on the hour, e.g. 12:00:00, 13:00:00 etc. Or at least, beginning after the hour and not before, e.g. 12:00:00, 13:00:01, 14:00:00 etc.

    


    I am using ffmpeg-python to process the AAC stream and send to two outputs : stdout and these segments.
Here's the code :

    


    out1 = ffmpeg.input(stream, loglevel="panic").output("pipe:",
                                                     format="s16le", 
                                                     acodec="pcm_s16le", 
                                                     ac="1", 
                                                     ar="16000")

out2 = ffmpeg.input(stream, loglevel="info").output("rec/%Y-%m-%d-%H%M%S.aac",
                                                     acodec="copy",
                                                     format="segment",
                                                     segment_time="3600",
                                                     segment_atclocktime="1",
                                                     reset_timestamps="1",
                                                     strftime="1")
            
ffmpeg.merge_outputs(out1, out2)
      .run_async(pipe_stdout=True, overwrite_output=True)


    


    Most files are produced at the desired time : 05:00:00, 06:00:00, 07:00:00, but one or two each day start at 08:59:59 (where 09:00:00 would be desired), or even 16:00:24.

    


    I understand the segment needs to begin on a audio sample so it can't be perfect to the hour, but wondering how I can make it more consistent. Ideally, each hour's recording would begin at 00:00 or later, and not begin before the hour.

    


    I have tried using min_seg_duration 3600, reset_timestamps 1
I am not sure how exactly to use segment_clocktime_wrap_duration for audio, or whether segment_time_delta applies to audio.

    


    I'd appreciate any advice or understanding of how segment_atclocktime works with audio, as much on the internet seems video-focused.