Recherche avancée

Médias (1)

Mot : - Tags -/bug

Autres articles (104)

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

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

Sur d’autres sites (14952)

  • ffmpeg - generate moov atom

    9 juillet 2021, par mmx

    I am currently recording video with blackmagic's prorecorder. I transcode video on-the-fly to mp4 video container with ffmpeg. Duration is unknown as I'm transcoding .ts that prorecorder is outputting to named pipe.

    


    My goal is to try to play this file with browser, while stream is still being recorded - Playback is great, but problem is that when I open file, duration is defined to current recording time.

    


    So, question is - I would like to generate a "fake" moov atom for duration of fe. 8 hours with ffmpeg, and then start recording mp4 file as I'm already doing. How could I do this ?

    


    Documentation that I checked and I think it's relevant - https://ffmpeg.org/ffmpeg-formats.html#MOV_002fMP4_002fISMV
I also saw this on stack : Is it possible to fake a (mp4) moov atom ?

    


  • Terminal text becomes invisible after terminating subprocess

    22 mai 2022, par wim

    After terminating an ffmpeg subprocess, the terminal gets messed up - typed characters are invisible ! The input still works in that commands can be executed, but keyboard input is not echoed to the terminal.

    



    Issuing shell command reset puts everything back to normal (or !reset from within ipython), so a workaround the issue is calling os.system('reset') inside the script.

    



    Other things I've tried : import curses; curses.initscr() before spawning the subprocess and curses.endwin() after termination, which worked somewhat but broke other stuff. Another possibly related issue is that after spawning the child process, the interactive terminal becomes laggy and sometimes fails to capture typed characters.

    



    The code to spawn the process looks like :

    



    with open('/tmp/stdout.log', 'w') as o:
    with open('/tmp/stderr.log', 'w') as e:
        proc = subprocess.Popen([args], stdout=o, stderr=e)


    



    And later to stop it :

    



    proc.terminate()
proc.communicate()


    



    What could be going wrong here ?

    


  • Terminal text becomes invisible after terminating subprocess

    21 novembre 2016, par wim

    After terminating an ffmpeg subprocess, the terminal gets messed up - typed characters are invisible ! The input still works in that commands can be executed, but keyboard input is not echoed to the terminal.

    Issuing shell command reset puts everything back to normal (or !reset from within ipython), so a workaround the issue is calling os.system('reset') inside the script.

    Other things I’ve tried : import curses; curses.initscr() before spawning the subprocess and curses.endwin() after termination, which worked somewhat but broke other stuff. Another possibly related issue is that after spawning the child process, the interactive terminal becomes laggy and sometimes fails to capture typed characters.

    The code to spawn the process looks like :

    with open('/tmp/stdout.log', 'w') as o:
    
    with open('/tmp/stderr.log', 'w') as e:
    
        proc = subprocess.Popen([args], stdout=o, stderr=e)

    And later to stop it :

    proc.terminate()
    
proc.communicate()

    What could be going wrong here ?

Navigation