Recherche avancée

Médias (1)

Mot : - Tags -/stallman

Autres articles (98)

  • Gestion des droits de création et d’édition des objets

    8 février 2011, par

    Par défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

  • Dépôt de média et thèmes par FTP

    31 mai 2013, par

    L’outil MédiaSPIP traite aussi les média transférés par la voie FTP. Si vous préférez déposer par cette voie, récupérez les identifiants d’accès vers votre site MédiaSPIP et utilisez votre client FTP favori.
    Vous trouverez dès le départ les dossiers suivants dans votre espace FTP : config/ : dossier de configuration du site IMG/ : dossier des média déjà traités et en ligne sur le site local/ : répertoire cache du site web themes/ : les thèmes ou les feuilles de style personnalisées tmp/ : dossier de travail (...)

Sur d’autres sites (12255)

  • Playback FFmpeg stream through UDP

    11 juillet 2020, par Andrew Raleigh

    I'm using the following command to send ffmpeg data :

    


    ./ffmpeg -i "" -pix_fmt yuv420p -tune zerolatency -preset ultrafast -f mpegts udp://127.0.0.1:23000

    


    I then transmit and receive it to another computer through the srt protocol, and read it back on the end-point.

    


    I play back with .\ffplay.exe -i udp://127.0.0.1:23000 -loglevel 40 and don't see a video. I can see data coming in from WireShark though. This is the log output :

    


    ffplay version N-98438-gc6cdfdf9c3 Copyright (c) 2003-2020 the FFmpeg developers
  built with gcc 10.1.0 (Rev3, Built by MSYS2 project)
  configuration:  --cc='ccache gcc' --cxx='ccache g++' --disable-autodetect --enable-amf --enable-bzlib --enable-cuda --enable-cuvid --enable-d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-nvenc --enable-schannel --enable-zlib --enable-sdl2 --enable-ffnvcodec --enable-nvdec --enable-gmp --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libaom --disable-debug --enable-libsrt --extra-libs=-liconv --enable-version3
  libavutil      56. 55.100 / 56. 55.100
  libavcodec     58. 94.100 / 58. 94.100
  libavformat    58. 48.100 / 58. 48.100
  libavdevice    58. 11.101 / 58. 11.101
  libavfilter     7. 87.100 /  7. 87.100
  libswscale      5.  8.100 /  5.  8.100
  libswresample   3.  8.100 /  3.  8.100
Initialized direct3d renderer.
[mpegts @ 000002130b5eae00] Unable to seek back to the startf=0/0

....

[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
    Last message repeated 1 times
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20791500).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20794500).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
    Last message repeated 1 times
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20800500).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.=0/0
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20805000).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
    Last message repeated 1 times
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20809500).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20812500).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
    Last message repeated 2 times
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20820000).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
    Last message repeated 1 times
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20824500).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.=0/0
    Last message repeated 1 times
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20829000).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
    Last message repeated 1 times
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20838000).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
    Last message repeated 1 times
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20842500).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
    Last message repeated 1 times
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20847000).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20853000).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
    Last message repeated 1 times
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20857500).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.=0/0
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20862000).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
    Last message repeated 1 times
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20866500).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20871000).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
    Last message repeated 1 times
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20875500).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
    Last message repeated 1 times
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20880000).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
    Last message repeated 1 times
[mpegts @ 000002130b5eae00] Packet corrupt (stream = 0, dts = 20884500).
[mpeg2video @ 000002130b612300] Invalid frame dimensions 0x0.
    Last message repeated 1 times
[mpegts @ 000002130b5eae00] changing packet size to 204  0B f=0/0
[mpegts @ 000002130b5eae00] changing packet size to 188
[mpegts @ 000002130b5eae00] changing packet size to 204  0B f=0/0
[mpegts @ 000002130b5eae00] changing packet size to 188  0B f=0/0
[mpegts @ 000002130b5eae00] changing packet size to 204  0B f=0/0
[mpegts @ 000002130b5eae00] changing packet size to 188  0B f=0/0


    


    FFPlay and FFProbe both output the above. Usually FFPlay would show the video playing back, but in this case I get nothing. Any thoughts as to why ?

    


  • ffmpeg livestream by ip camera with a problem of DTS

    7 novembre 2022, par AntoAnto

    I'm a problem with a code of ffmpeg : ffmpeg -rtsp_transport tcp -i "rtsp://admin:passw@xxxxxxxx.ddns.net:554/live/ch0" -deinterlace -vcodec libx264 -pix_fmt yuv420p -preset medium -s 1920x1080 -b:v 5000k -acodec aac -strict -2 -ar 44100 -threads 6 -qscale 3 -b:a 712000 -bufsize 128k -f flv "rtmp://a.rtmp.youtube.com/live2/key"

    


    It's used for a live streaming by a ip camera, but I have this problem

    


    [flv @ 0x558333a41100] Non-monotonous DTS in output stream 0:1; previous: 73709, current: 73220; changing to 73709. This may result in incorrect timestamps in the output file.
[aac @ 0x558333a0f100] Queue input is backward in time14.43 bitrate=1288.8kbits/s dup=0 drop=5 speed=0.486x
[flv @ 0x558333a41100] Non-monotonous DTS in output stream 0:1; previous: 74591, current: 73614; changing to 74591. This may result in incorrect timestamps in the output file.


    


    who can help me ?

    


  • App Crash in libavcodec.so - Likely FFmpeg Related

    19 décembre 2023, par Rathod Vishal

    Hey Stack Overflow community,

    


    I'm facing a persistent crash issue in my Android app, specifically in the libavcodec.so library. The crash is widespread among users, and it's affecting a significant portion of my user base.

    


    Crash Location: #00 pc 0x0000000000b11ccc in /data/app/~~wmcZ3ZPysN9Yl9EYcyRU7g==/com.package.name-lIWCTBFysApQjj2SItcYxg==/split_config.arm64_v8a.apk!libavcodec.so

    


    Hypothesis : I suspect it's related to FFmpeg, as my app heavily relies on it.

    


    Questions :

    


      

    1. Has anyone experienced a similar issue with FFmpeg causing crashes specifically on Android 13 and 12 ?

      2. 


    2. Are there known compatibility issues with these Android versions ?

      3. 


    3. Could it be a memory-related issue, considering the widespread nature of the crash on these specific Android versions ?

      4. 


    


    I appreciate any insights or guidance you can provide to help me tackle this issue, especially in the context of Android 13 and 12. Thank you !

    


Navigation