Recherche avancée

Médias (0)

Mot : - Tags -/navigation

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

Autres articles (54)

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

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

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

Sur d’autres sites (4094)

  • configure : support msvc build inside WSL

    25 avril 2024, par Timo Rothenpieler
    configure : support msvc build inside WSL
    • [DH] configure

  • Revision c4d1ab573a : Removing memset calls inside idct/iht functions. Making appropriate memset insi

    2 octobre 2013, par Dmitry Kovalev

    Changed Paths :
     Modify /vp9/decoder/vp9_decodframe.c


     Modify /vp9/decoder/vp9_idct_blk.c



    Removing memset calls inside idct/iht functions.

    Making appropriate memset inside decode_block now.

    Change-Id : I8e944194668c830de08271c8fb6e413251c201d8

  • How do I enable ffmpeg python inside a docker ?

    4 mars 2024, par Noam Zadok

    I have a problem with enabling ffmpeg streaming inside my Docker container, and specifically, inside a Python service running inside the Docker.
I need to stream my screen view, and I'm using the 'x11grab' source, and the destination is an RTSP server (AWS IVS). This is my code for the stream :

    


    bit_rate = f"{self.config_service.thermal_stream_bit_rate}k" # 150k
vsync_param = self.config_service.stream_vsync_param # 'cfr'
frame_rate = self.config_service.stream_frame_rate # 5
stream_command = ffmpeg.input(
                os.getenv('DISPLAY'), # env var passed into the container
                s=f"{self.config_service.display_width}x{self.config_service.display_height}",
                f="x11grab",
                r=frame_rate,
                fflags="nobuffer+discardcorrupt+shortest",
                loglevel="level+debug",
            )..output(
                self.dest_path, # My rstp url
                vcodec='nvenc_h264',
                preset='hp',
                pix_fmt=pix_format_param,
                tune="zerolatency",
                b=bit_rate,
                g=keyframe_interval_seconds,
                r=frame_rate,
                format="flv",
            )
streaming_process = await stream_command.run_asyncio(pipe_stderr=True)


    


    When I run the code, I receive this error : x11grab: No such file or directory.

    


    When I enter the Docker container, and run Python, and then the script :

    


    import ffmpeg

>>> x11_display = ':0'
>>> format = "x11grab"
>>> screen_width = f"1920x1080"
>>> bit_rate = "150k"
>>> pix_format_param = "yuv420p"
>>> keyframe_interval_seconds = 2
>>> frame_rate = 5
>>> dest_path = 'rtmps://XXXX.global-contribute.live-video.net:443/app/YYYY'
>>> command = ffmpeg.input(x11_display, s=screen_width, f="x11grab", r=frame_rate, fflags="nobuffer+discardcorrupt+shortest", loglevel="level+debug",).output(dest_path, vcodec='nvenc_h264', preset='hp', pix_fmt=pix_format_param, tune="zerolatency", b=bit_rate, g=keyframe_interval_seconds, r=frame_rate, format="flv",)
>>> command.run()


    


    The stream is starting. I took the exact command by printing inside my service script (print the ffmpeg.input, and the ffmpeg.output).
Also, when I tried async running the command (as in my script) inside the Python console, it also succeeded, so it's not related to that. Basically there are no functional differences between the commands.
I've tried comparing the Python version, the ffmpeg version, the file system permissions - they are the same in the script run and in the python console.
I don't understand what configuration am I missing.
Thank you in advance.

    


Navigation