Recherche avancée

Médias (91)

Autres articles (87)

  • Les tâches Cron régulières de la ferme

    1er décembre 2010, par

    La gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
    Le super Cron (gestion_mutu_super_cron)
    Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • MediaSPIP Player : problèmes potentiels

    22 février 2011, par

    Le lecteur ne fonctionne pas sur Internet Explorer
    Sur Internet Explorer (8 et 7 au moins), le plugin utilise le lecteur Flash flowplayer pour lire vidéos et son. Si le lecteur ne semble pas fonctionner, cela peut venir de la configuration du mod_deflate d’Apache.
    Si dans la configuration de ce module Apache vous avez une ligne qui ressemble à la suivante, essayez de la supprimer ou de la commenter pour voir si le lecteur fonctionne correctement : /** * GeSHi (C) 2004 - 2007 Nigel McNie, (...)

Sur d’autres sites (12162)

  • Using FFmpeg to Output Audio to Camera Error Issues [closed]

    27 septembre 2024, par crazyday

    I want to send audio to the camera via command, but it fails. Here is my command syntax.

    


    ffmpeg -re -i audio.wav -f lavfi -i anullsrc -c:v copy -c:a aac -strict experimental -f rtsp rtsp://xxxxx:xxxxx@192.168.1.108:554/stream

    


    The error message is as follows :

    


    [af#0:0 @ 0000018ab4046b80] Error sending frames to consumers: Invalid data found when processing input
[af#0:0 @ 0000018ab4046b80] Task finished with error code: -1094995529 (Invalid data found when processing input)
[af#0:0 @ 0000018ab4046b80] Terminating thread with return code -1094995529 (Invalid data found when processing input)
[out#0/rtsp @ 0000018ab406aa00] Nothing was written into output file, because at least one of its streams received no packets.```



    


  • FFMPEG command causing audio issues

    7 août 2018, par alan samuel

    I am converting multiple mp4 video to ts and then stitching it together.

    But this sometimes causes audio issues on my videos where the audio sounds like it was recorded with two mics at the same time causing loud sound.

    I can only reproduce it sometimes and I am still not sure why it’s doing that ? Can anyone help ?

    Here is how I am converting to ts from mp4. I have noticed that the longer the video gets, the audio gets worse and its also off by a couple of seconds.

    ffmpeg -i video1.mp4 -f lavfi -i anullsrc=channel_layout=mono:sample_rate=48000 -shortest -c copy -bsf:v h264_mp4toannexb -c:a aac video1.ts

    ffmpeg -i video2.mp4 -f lavfi -i anullsrc=channel_layout=mono:sample_rate=48000 -shortest -c copy -bsf:v h264_mp4toannexb -c:a aac video2.ts

    ffmpeg -i video3.mp4 -f lavfi -i anullsrc=channel_layout=mono:sample_rate=48000 -shortest -c copy -bsf:v h264_mp4toannexb -c:a aac video3.ts

    and then I save these paths to a txt and call my stitching command like this

    ffmpeg -f concat -safe 0 -i list.txt -c copy -bsf:a aac_adtstoasc finalvideo.mp4

    Here is the complete output of the 4 videos

    C:\Users\Alan\Desktop\videos>ffmpeg -i video1.mp4 -i video2.mp4 -i video3.mp4 -i video4.mp4
    ffmpeg version N-90433-g5b31dd1c6b Copyright (c) 2000-2018 the FFmpeg developers
     built with gcc 7.3.0 (GCC)
     configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-bzlib --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth
     libavutil      56. 12.100 / 56. 12.100
     libavcodec     58. 15.100 / 58. 15.100
     libavformat    58. 10.100 / 58. 10.100
     libavdevice    58.  2.100 / 58.  2.100
     libavfilter     7. 13.100 /  7. 13.100
     libswscale      5.  0.102 /  5.  0.102
     libswresample   3.  0.101 /  3.  0.101
     libpostproc    55.  0.100 / 55.  0.100
    Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'video1.mp4':
     Metadata:
       major_brand     : isom
       minor_version   : 512
       compatible_brands: isomiso2avc1mp41
       encoder         : Lavf57.71.100
     Duration: 00:00:10.80, start: 0.000000, bitrate: 1034 kb/s
       Stream #0:0(eng): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 879 kb/s, 4.17 fps, 4.17 tbr, 12800 tbn, 8.33 tbc (default)
       Metadata:
         handler_name    : VideoHandler
       Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, mono, fltp, 165 kb/s (default)
       Metadata:
         handler_name    : SoundHandler
    Input #1, mov,mp4,m4a,3gp,3g2,mj2, from 'video2.mp4':
     Metadata:
       major_brand     : isom
       minor_version   : 512
       compatible_brands: isomiso2avc1mp41
       encoder         : Lavf57.71.100
     Duration: 00:00:01.62, start: 0.000000, bitrate: 3208 kb/s
       Stream #1:0(eng): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 3203 kb/s, 16.67 fps, 16.67 tbr, 12800 tbn, 33.33 tbc (default)
       Metadata:
         handler_name    : VideoHandler
    Input #2, mov,mp4,m4a,3gp,3g2,mj2, from 'video3.mp4':
     Metadata:
       major_brand     : isom
       minor_version   : 512
       compatible_brands: isomiso2avc1mp41
       encoder         : Lavf57.71.100
     Duration: 00:00:05.58, start: 0.000000, bitrate: 1954 kb/s
       Stream #2:0(eng): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 1805 kb/s, 16.67 fps, 16.67 tbr, 12800 tbn, 33.33 tbc (default)
       Metadata:
         handler_name    : VideoHandler
       Stream #2:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, mono, fltp, 166 kb/s (default)
       Metadata:
         handler_name    : SoundHandler
    Input #3, mov,mp4,m4a,3gp,3g2,mj2, from 'video4.mp4':
     Metadata:
       major_brand     : isom
       minor_version   : 512
       compatible_brands: isomiso2avc1mp41
       encoder         : Lavf57.71.100
     Duration: 00:00:03.90, start: 0.000000, bitrate: 1746 kb/s
       Stream #3:0(eng): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 1744 kb/s, 16.67 fps, 16.67 tbr, 12800 tbn, 33.33 tbc (default)
       Metadata:
         handler_name    : VideoHandler
  • Screen Recording Issues using Python and FFMPEG [closed]

    3 juin, par Kevin McDowell

    I am trying to record a walkthrough of a 3D space contained within a Chrome browser session. The goal is to create deterministic output. If I run this command from a VS Code terminal, it records 30 seconds of video from the window that's about 6MB :

    


    ffmpeg -f gdigrab -framerate 30 -i "title=My3D - Google Chrome" -t 30 "My3D - Google Chrome_screenRecording_v0.mp4"


    


    However, if I call it from Python like so :

    


    subprocess.run("ffmpeg -f gdigrab -framerate 30 -i \"title=My3D - Google Chrome\" -t 15 \"My3D - Google Chrome_screenRecording_v0.mp4\"")


    


    The output video is 30 seconds, but while I can see the mouse moving on the screen, the image is all black and the filesize is only 94KB.

    


    This is on a Windows 11 machine with GPU acceleration disabled in the OS as well as in Chrome. I've also tried it with other web pages and those are also recorded black. Any ideas what is causing this or how to record the screen using Python ?

    


    I've got other alternatives working (using Selenium or PyGet to capture screenshots and then using the VideoWriter class from OpenCV to write them to a video file), but that has a limitation of only about 10 FPS and you can't control the recording time like you can with FFMPEG. If you screen capture for 30 seconds, the actual output may only be 12-18 seconds.