Recherche avancée

Médias (91)

Autres articles (99)

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

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

Sur d’autres sites (10184)

  • ffmpeg-normalize exits with OSError : [WinError 193] %1 is not a valid Win32 application

    1er septembre 2021, par Moldy1

    I have a large number of files I want to normalize the volume with a simple method using a basic loop.

    


    When trying to use ffmpeg-normalize the application exits with the error. I searched the error on-line but I can't find any issue similar to mine. I thought it may be a 'path' or file type association problem but they look ok.

    


    Can anyone give me an explanation for this error and a possible fix for it please ?

    


    D:\Test>ffmpeg-normalize.exe in.mkv -o out.mkv&#xA;Traceback (most recent call last):&#xA;  File "c:\users\les\appdata\local\programs\python\python39\lib\runpy.py", line 197, in _run_module_as_main&#xA;    return _run_code(code, main_globals, None,&#xA;  File "c:\users\les\appdata\local\programs\python\python39\lib\runpy.py", line 87, in _run_code&#xA;    exec(code, run_globals)&#xA;  File "C:\Users\Les\AppData\Local\Programs\Python\Python39\Scripts\ffmpeg-normalize.exe\__main__.py", line 7, in <module>&#xA;  File "c:\users\les\appdata\local\programs\python\python39\lib\site-packages\ffmpeg_normalize\__main__.py", line 409, in main&#xA;    ffmpeg_normalize = FFmpegNormalize(&#xA;  File "c:\users\les\appdata\local\programs\python\python39\lib\site-packages\ffmpeg_normalize\_ffmpeg_normalize.py", line 68, in __init__&#xA;    self.has_loudnorm_capabilities = ffmpeg_has_loudnorm()&#xA;  File "c:\users\les\appdata\local\programs\python\python39\lib\site-packages\ffmpeg_normalize\_cmd_utils.py", line 185, in ffmpeg_has_loudnorm&#xA;    cmd_runner.run_command()&#xA;  File "c:\users\les\appdata\local\programs\python\python39\lib\site-packages\ffmpeg_normalize\_cmd_utils.py", line 101, in run_command&#xA;    p = subprocess.Popen(&#xA;  File "c:\users\les\appdata\local\programs\python\python39\lib\subprocess.py", line 947, in __init__&#xA;    self._execute_child(args, executable, preexec_fn, close_fds,&#xA;  File "c:\users\les\appdata\local\programs\python\python39\lib\subprocess.py", line 1416, in _execute_child&#xA;    hp, ht, pid, tid = _winapi.CreateProcess(executable, args,&#xA;OSError: [WinError 193] %1 is not a valid Win32 application&#xA;&#xA;D:\Test>path&#xA;PATH=C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\Calibre2\;C:\Program Files (x86)\Calibre2\;C:\Users\Les\AppData\Local\Programs\Python\Python39\Scripts\;C:\Users\Les\AppData\Local\Programs\Python\Python39\;C:\Users\Les\AppData\Local\Microsoft\WindowsApps;D:\MABS\local64\bin-video;C:\Program Files (x86)\sox-14-4-2&#xA;&#xA;D:\Test>ftype python.file&#xA;python.file="C:\Users\Les\AppData\Local\Programs\Python\Python39\python.exe" "%1"&#xA;&#xA;D:\Test>python.exe&#xA;Python 3.9.1 (tags/v3.9.1:1e5d33e, Dec  7 2020, 17:08:21) [MSC v.1927 64 bit (AMD64)] on win32&#xA;&#xA;ffmpeg -version&#xA;ffmpeg version N-100483-g728b83a7c4-gd67c6c7f6f&#x2B;4 Copyright (c) 2000-2020 the FFmpeg developers&#xA;built with gcc 10.2.0 (Rev6, Built by MSYS2 project)&#xA;&#xA;&#xA;&#xA; D:\Test>ffmpeg-normalize --version&#xA;        ffmpeg-normalize v1.22.1&#xA;</module>

    &#xA;

  • strange artifacts in image - where does a frame start ?

    26 mai 2017, par user3387542

    We are live broadcasting a webcam stream. No audio, video only. The current command that works great :

    # Direct replay works well:
    
ffmpeg -f video4linux2 -r 10 -s 1280x720 -i /dev/video0 -c:v rawvideo -f rawvideo -pix_fmt yuv420p - | \
    
 ffplay -f rawvideo -pixel_format yuv420p -video_size 1280x720 -framerate 10 -

    but as soon as we try to send this data over the network (udp broadcast / gigabit lan) we are getting strange artefacts into the image.

    # server command:
    
ffmpeg -f video4linux2 -r 10 -s 1280x720 -i /dev/video0 -c:v rawvideo -f rawvideo -pix_fmt yuv420p - | \
    
socat - UDP-DATAGRAM:10.0.0.255:12345,broadcast
    

    
# client command:
    
socat -u udp-recv:12345,reuseaddr - | \
    
ffplay -f rawvideo -pixel_format yuv420p -video_size 1280x720 -framerate 10 -

    Where do these artifacts come from and how to get rid of them ? Does this has something to do with the client not knowing where a certain video frame starts ?

    We have chosen to stream raw video to reduce latency. The final goal would be to apply opencv tools to the video and react live depending on the situation. Which works great, as long as the camera is plugged in directly into this computer. But we need to set it apart and need multiple clients.

    enter image description here

    The camera used is a Microsoft® LifeCam Studio(TM).

    $ v4l2-ctl -d 0 --list-formats
    
ioctl: VIDIOC_ENUM_FMT
    
Index       : 0
    
Type        : Video Capture
    
Pixel Format: 'YUYV'
    
Name        : YUYV 4:2:2
    

    
Index       : 1
    
Type        : Video Capture
    
Pixel Format: 'MJPG' (compressed)
    
Name        : Motion-JPEG
    

    
Index       : 2
    
Type        : Video Capture
    
Pixel Format: 'M420'
    
Name        : YUV 4:2:0 (M420)

    Update

    To narrow down the issue, I tried to split it up into different tasks :

    1.0. Writing the stream to a file :

    ffmpeg -f video4linux2 -r 10 -s 1280x720 -i /dev/video0 -c:v rawvideo -f rawvideo -pix_fmt yuv420p - > ~/deltemp/rawout

    1.1. Reading the file : The result looks great, no artefacts :

    cat ~/deltemp/rawout | ffplay -f rawvideo -pixel_format yuv420p -video_size 1280x720 -framerate 10 -

    2.0 Starting the stream and broadcasting the stream as mentioned in the server command above

    2.1 Writing the UDP stream to a file. And watching the file (artifacts are back again)

    socat -u udp-recv:12345,reuseaddr - > ~/deltemp/rawout
    
cat ~/deltemp/rawout | ffplay -f rawvideo -pixel_format yuv420p -video_size 1280x720 -framerate 10 -

    As test 1 showed no artifacts and test 2 did, it must be something with udp packet loss.

    Test 3 : Reducing quality to 640x480 did not help either.

  • How do I configure ffmpeg & openh264 so that the video file can be opened in Windows Media Player 12

    10 mars 2017, par Sacha Guyer

    I have successfully created h264/mp4 movie files with ffmpeg and the x264 library.

    Now I would like to change the h264 library from x264 to openH264. I could replace the x264 library with openH264, recompile ffmpeg and produce movie files, without changing my sources that produce the movie. The resulting movie opens fine in Quicktime on Mac, but on Windows, Windows Media Player 12 cannot play it.

    The documentation about Windows Media Player support for h264 is unclear. File types supported by Windows Media Player states in the table that Windows Media Player 12 supports mp4, but the text below says :

    Windows Media Player does not support the playback of the .mp4 file format.

    From what I have observed, Windows Media Player 12 IS capable of playing h264/mp4 files, but only when created with x264.

    Does anyone know how I need to adjust the configuration of the codec/context so that the movie plays in Windows Media Player ? Does Windows Media Player only support certain h264 profiles ?

    I noticed the warning :

    [libopenh264 @ 0x...] [OpenH264] this = 0x..., Warning:bEnableFrameSkip = 0,bitrate can’t be controlled for RC_QUALITY_MODE,RC_BITRATE_MODE and RC_TIMESTAMP_MODE without enabling skip frame

    With the configuration :

    av_dict_set(&amp;options, "allow_skip_frames", "1", 0);

    I could get rid of this warning, but the movie still does not play. Are there other options that need to be set so that the movie plays in Windows Media Player ?

    Thank you for your help

    ffprobe output of the file that does play fine in Windows Media Player :

    Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'test_x264.mp4':
    
  Metadata:
    
    major_brand     : isom
    
    minor_version   : 512
    
    compatible_brands: isomiso2avc1mp41
    
    title           : retina
    
    encoder         : Lavf57.56.100
    
    comment         : Creation Date: 2017-03-10 07:47:39.601
    
  Duration: 00:00:04.17, start: 0.000000, bitrate: 17497 kb/s
    
    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661),
    
      yuv420p, 852x754, 17495 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
    
    Metadata:
    
      handler_name    : VideoHandler

    ffprobe output of the file that does not play in Windows Media Player :

    Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'test_openh264.mp4':
    
  Metadata:
    
    major_brand     : isom
    
    minor_version   : 512
    
    compatible_brands: isomiso2avc1mp41
    
    title           : retina
    
    encoder         : Lavf57.56.100
    
    comment         : Creation Date: 2017-03-10 07:49:27.024
    
  Duration: 00:00:04.17, start: 0.000000, bitrate: 17781 kb/s
    
    Stream #0:0(und): Video: h264 (Constrained Baseline) (avc1 / 0x31637661),
    
      yuv420p, 852x754, 17779 kb/s, 24 fps, 24 tbr, 24k tbn, 48k tbc (default)
    
    Metadata:
    
      handler_name    : VideoHandler

Navigation