Recherche avancée

Médias (9)

Mot : - Tags -/soundtrack

Autres articles (50)

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 est la première version de MediaSPIP stable.
    Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Mise à disposition des fichiers

    14 avril 2011, par

    Par défaut, lors de son initialisation, MediaSPIP ne permet pas aux visiteurs de télécharger les fichiers qu’ils soient originaux ou le résultat de leur transformation ou encodage. Il permet uniquement de les visualiser.
    Cependant, il est possible et facile d’autoriser les visiteurs à avoir accès à ces documents et ce sous différentes formes.
    Tout cela se passe dans la page de configuration du squelette. Il vous faut aller dans l’espace d’administration du canal, et choisir dans la navigation (...)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

Sur d’autres sites (8437)

  • FFmpeg - invalid argument on a creation of MP4 with .SRT - Help Needed to Correctly Set Filename of .srt in a FFMPEG Command

    23 mai 2023, par sKunZel

    I have been experiencing a persistent issue while developing a command in FFMPEG to combine a .mp4 file (composed of a static image & audio from a .mp3) with burnt-in subtitles from a stylized .srt file into a new MP4.

    


    This is the command I have been using :

    


    command = f"""ffmpeg -report -i "{input_video_arg_abs}" -vf "subtitles='{input_srt_arg_abs}':original_size=816x1456:force_style='FontName=Open Sans Italic,FontSize=13,MarginR=10,MarginV=149'" -c:v libx264 -crf 18 -c:a copy -movflags +faststart "{output_video}" """ 


    


    My script includes the main variable definitions and function calls as shown below :

    


    input_srt = os.path.normpath(os.path.join(input_directory, srt_file))
print(f"SRT file path: {input_srt}")
reformat_srt(input_srt)
final_video_output=os.path.normpath(os.path.join(output_directory, os.path.splitext(mp3_file)[0] + '.mp4'))
time.sleep(0.5)
create_final_video(temp_video_output, input_srt, final_video_output)


    


    Despite appearing to run successfully, the output file generated is 0 Kb. All logs that I could find suggested an error in the way I've written the .srt, but the input_srt seems to print out correctly.

    


    Here are the log details :
...
[Parsed_subtitles_0 @ 0000028068d97d00] Setting 'filename' to value 'E'
[Parsed_subtitles_0 @ 0000028068d97d00] Unable to open E
...
Error reinitializing filters !
Failed to inject frame into filter network : No such file or directory
Error while processing the decoded data for stream #0:0
Conversion failed !

    


    I am currently speculating that "E :" might be causing the problem. This would be correctly interpreted by Windows, but I'm unsure about FFMPEG's interpretation.
I'm hoping someone might be able to assist me in solving this issue. I'd be delighted if the solution involves an ingenious trick. Otherwise, my apologies for the rookie question. I appreciate your help in advance.

    


    Best,
sKunZel

    


  • Publishing an RTSP stream from my IP camera to a remote MediaMTX / RTSP Simple Server using FFmpeg and Azure [closed]

    28 janvier 2024, par cmd

    Using FFmpeg, I am trying to publish the RTSP stream from my IP camera to an Azure VM running a MediaMTX instance https://github.com/bluenviron/mediamtx. My intention is for the stream to be accessible from other remote connections by connecting to the VM.

    


    I was able to setup a local MediaMTX server on my laptopm, and publish the stream using this FFmpeg command :

    


    ffmpeg -i rtsp://<camera username="username">:<camera password="password">@<camera local="local" ip="ip">:554 -c:v copy -c:a copy -f rtsp rtsp://<laptop local="local" ip="ip">:8554/stream/mystream&#xA;</laptop></camera></camera></camera>

    &#xA;

    This worked fine, as I was able to connect to the MediaMTX server in VLC player to view the stream. However, I have setup an Azure VM running Windows 10, and run the same MediaMTX instance on it. I have attempted to publish the RTSP stream from the IP camera using the same command, but with the Laptop IP replaced with the address of the VM, but this doesn't work.

    &#xA;

    I have disabled the Windows Firewall on my laptop and the VM, but the stream can still not be published. I have also tried the same approach by running the MediaMTX server on my friend's computer on his network, and adding the necessary port forwarding rules to his router. I am unable to edit any rules on the router where I am living however.

    &#xA;

    What else might be causing this issue, and is there any way to publish the IP camera's RTSP to a remote server where it could then be read ?

    &#xA;

  • ffmpeg is failing to load shared libraries after a ./configure with a prefix inside a conda environment

    30 janvier 2024, par user3133806

    I am using conda and building ffmpeg from source within that environment.

    &#xA;

    I ran the following commands :

    &#xA;

    conda create --name my_conda_env&#xA;conda activate my_conda_env&#xA;# Now I am in the conda environment&#xA;# $CONDA_PREFIX is /home/myuser/.conda/envs/my_conda_env/bin/ffmpeg&#xA;&#xA;# Checkout ffmpeg code&#xA;# git checkout ...&#xA;&#xA;./configure --prefix=$CONDA_PREFIX --enable-shared --disable-static &amp;&amp; make distclean &amp;&amp; make -j 100 &amp;&amp; make install&#xA;&#xA;# The above command does install the newly built ffmpeg into:&#xA;# /home/myuser/.conda/envs/my_conda_env/bin/ffmpeg&#xA;&#xA;# However it fails to execute:&#xA;ffmpeg&#xA;ffmpeg: error while loading shared libraries: libavdevice.so.58: cannot open shared object file: No such file or directory&#xA;&#xA;# When I add the conda lib path to LD_LIBRARY_PATH it works:&#xA;LD_LIBRARY_PATH=$CONDA_PREFIX/lib:$LD_LIBRARY_PATH ffmpeg&#xA;ffmpeg version n4.2.9-4-gd7beb0c61f Copyright (c) 2000-2023 the FFmpeg developers&#xA;&#xA;# I thought ./configure with a --prefix will build a binary that will search for libraries relative to itself, but that does not appear to be the case:&#xA;&#xA;strace -o /tmp/strace.out ffmpeg&#xA;tail /tmp/strace.out&#xA;&#xA;openat(AT_FDCWD, "/usr/lib64/haswell/x86_64/libavdevice.so.58", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)&#xA;newfstatat(AT_FDCWD, "/usr/lib64/haswell/x86_64", 0x7fff65f56d90, 0) = -1 ENOENT (No such file or directory)&#xA;openat(AT_FDCWD, "/usr/lib64/haswell/libavdevice.so.58", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)&#xA;newfstatat(AT_FDCWD, "/usr/lib64/haswell", 0x7fff65f56d90, 0) = -1 ENOENT (No such file or directory)&#xA;openat(AT_FDCWD, "/usr/lib64/avx512_1/x86_64/libavdevice.so.58", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)&#xA;newfstatat(AT_FDCWD, "/usr/lib64/avx512_1/x86_64", 0x7fff65f56d90, 0) = -1 ENOENT (No such file or directory)&#xA;openat(AT_FDCWD, "/usr/lib64/avx512_1/libavdevice.so.58", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)&#xA;newfstatat(AT_FDCWD, "/usr/lib64/avx512_1", 0x7fff65f56d90, 0) = -1 ENOENT (No such file or directory)&#xA;openat(AT_FDCWD, "/usr/lib64/x86_64/libavdevice.so.58", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)&#xA;newfstatat(AT_FDCWD, "/usr/lib64/x86_64", 0x7fff65f56d90, 0) = -1 ENOENT (No such file or directory)&#xA;openat(AT_FDCWD, "/usr/lib64/libavdevice.so.58", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)&#xA;newfstatat(AT_FDCWD, "/usr/lib64", {st_mode=S_IFDIR|0555, st_size=49526, ...}, 0) = 0&#xA;writev(2, [{iov_base="ffmpeg", iov_len=6}, {iov_base=": ", iov_len=2}, {iov_base="error while loading shared libra"..., iov_len=36}, {i&#xA;ov_base=": ", iov_len=2}, {iov_base="libavdevice.so.58", iov_len=17}, {iov_base=": ", iov_len=2}, {iov_base="cannot open shared object file", iov_len=30}, {iov_base=": ", iov_len=2}, {iov_base="No such file or directory", iov_len=25}, {iov_base="\n", iov_len=1}], 10) = &#xA;123&#xA;

    &#xA;

    Conda documentation says not to use LD_LIBRARY_PATH here :

    &#xA;

    https://docs.conda.io/projects/conda-build/en/stable/resources/use-shared-libraries.html#shared-libraries-in-macos-and-linux

    &#xA;

    How can I build ffmpeg from source in a conda environment and have the binary find the .so file relative to itself ?

    &#xA;