Recherche avancée

Médias (1)

Mot : - Tags -/iphone

Autres articles (70)

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

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

  • Amélioration de la version de base

    13 septembre 2013

    Jolie sélection multiple
    Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
    Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)

Sur d’autres sites (9669)

  • ffmpeg youtube live stream settings screen output [closed]

    25 juin 2020, par brainoverflowse
    

    

    Below works but I do get some warnings:

    ffmpeg -rtsp_transport tcp -i rtsp://admin:password@192.168.0.121:5542/Streaming/Channels/1 -tune zerolatency -vcodec libx264 -pix_fmt + -c:v copy -c:a aac -f flv rtmp://a.rtmp.youtube.com/live2/streamcode
ffmpeg version git-2020-06-20-29ea4e1 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 9.3.1 (GCC) 20200523
  configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libsrt --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-libvmaf --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libgsm --disable-w32threads --enable-libmfx --enable-ffnvcodec --enable-cuda-llvm --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt --enable-amf
  libavutil      56. 55.100 / 56. 55.100
  libavcodec     58. 93.100 / 58. 93.100
  libavformat    58. 47.100 / 58. 47.100
  libavdevice    58. 11.100 / 58. 11.100
  libavfilter     7. 86.100 /  7. 86.100
  libswscale      5.  8.100 /  5.  8.100
  libswresample   3.  8.100 /  3.  8.100
  libpostproc    55.  8.100 / 55.  8.100
Guessed Channel Layout for Input Stream #0.1 : mono
Input #0, rtsp, from 'rtsp://admin:password@192.168.0.121:5542/Streaming/Channels/1':
  Metadata:
    title           : Media Presentation
  Duration: N/A, start: 0.000000, bitrate: N/A
    Stream #0:0: Video: h264 (Main), yuv420p(progressive), 1920x1080, 20 fps, 30 tbr, 90k tbn, 40 tbc
    Stream #0:1: Audio: pcm_mulaw, 8000 Hz, mono, s16, 64 kb/s
Multiple -c, -codec, -acodec, -vcodec, -scodec or -dcodec options specified for stream 0, only the last option '-c:v copy' will be used.
Stream mapping:
  Stream #0:0 -> #0:0 (copy)
  Stream #0:1 -> #0:1 (pcm_mulaw (native) -> aac (native))
Press [q] to stop, [?] for help
[aac @ 000002a2862cb900] Too many bits 8832.000000 > 6144 per frame requested, clamping to max
Output #0, flv, to 'rtmp://a.rtmp.youtube.com/live2/streamcode':
  Metadata:
    title           : Media Presentation
    encoder         : Lavf58.47.100
    Stream #0:0: Video: h264 (Main) ([7][0][0][0] / 0x0007), yuv420p(progressive), 1920x1080, q=2-31, 20 fps, 30 tbr, 1k tbn, 90k tbc
    Stream #0:1: Audio: aac (LC) ([10][0][0][0] / 0x000A), 8000 Hz, mono, fltp, 48 kb/s
    Metadata:
      encoder         : Lavc58.93.100 aac
[flv @ 000002a285413200] Non-monotonous DTS in output stream 0:0; previous: 283, current: 33; changing to 283. This may result in incorrect timestamps in the output file.
[flv @ 000002a285413200] Non-monotonous DTS in output stream 0:0; previous: 283, current: 100; changing to 283. This may result in incorrect timestamps in the output file.
[flv @ 000002a285413200] Non-monotonous DTS in output stream 0:0; previous: 283, current: 133; changing to 283. This may result in incorrect timestamps in the output file.
[flv @ 000002a285413200] Non-monotonous DTS in output stream 0:0; previous: 283, current: 200; changing to 283. This may result in incorrect timestamps in the output file.
[flv @ 000002a285413200] Non-monotonous DTS in output stream 0:0; previous: 283, current: 233; changing to 283. This may result in incorrect timestamps in the output file.
frame=22107 fps= 20 q=-1.0 size=  713271kB time=00:18:25.30 bitrate=5286.4kbits/s speed=   1x

-----------------

This is what I receive this repeating in yellow when something happens to the stream connection:

    [flv @ 0000026847b60040] Non-monotonous DTS in output stream 0:1; previous: 47046874, current: 7601881; changing to 47046874. This may result in incorrect timestamps in the output file.

    


    


    



    Great site for info and I have learned quite a bit so far in my quest to learn programming. There are a bunch of us who live stream to youtube and use ffmpeg. All we want to do is with the least amount of flags in our command line and make it simple to send a live rtsp connection from our cameras to youtube. I know we have some command line interpretations that we have wrong or need to be taken out or added. Could any of you assist with what we would need to resolve our yellow warnings and when it appears the rtsp stream crashes. I apologize with the learning curve for entering code into the post.

    


  • ffmpeg : create .mp4 from .mp3 and .jpg

    28 juin 2021, par user292344

    I've searched for the best way to do this and nothing seems to work. I'm using Ubuntu 20.04.

    


    ffmpeg -version :

    


    


    ffmpeg version 4.2.4-1ubuntu0.1 Copyright (c) 2000-2020 the FFmpeg developers
built with gcc 9 (Ubuntu 9.3.0-10ubuntu2)
configuration : —prefix=/usr —extra-version=1ubuntu0.1 —toolchain=hardened —libdir=/usr/lib/x86_64-linux-gnu —incdir=/usr/include/x86_64-linux-gnu —arch=amd64 —enable-gpl —disable-stripping —enable-avresample —disable-filter=resample —enable-avisynth —enable-gnutls —enable-ladspa —enable-libaom —enable-libass —enable-libbluray —enable-libbs2b —enable-libcaca —enable-libcdio —enable-libcodec2 —enable-libflite —enable-libfontconfig —enable-libfreetype —enable-libfribidi —enable-libgme —enable-libgsm —enable-libjack —enable-libmp3lame —enable-libmysofa —enable-libopenjpeg —enable-libopenmpt —enable-libopus —enable-libpulse —enable-librsvg —enable-librubberband —enable-libshine —enable-libsnappy —enable-libsoxr —enable-libspeex —enable-libssh —enable-libtheora —enable-libtwolame —enable-libvidstab —enable-libvorbis —enable-libvpx —enable-libwavpack —enable-libwebp —enable-libx265 —enable-libxml2 —enable-libxvid —enable-libzmq —enable-libzvbi —enable-lv2 —enable-omx —enable-openal —enable-opencl —enable-opengl —enable-sdl2 —enable-libdc1394 —enable-libdrm —enable-libiec61883 —enable-nvenc —enable-chromaprint —enable-frei0r —enable-libx264 —enable-shared
libavutil 56. 31.100 / 56. 31.100
libavcodec 58. 54.100 / 58. 54.100
libavformat 58. 29.100 / 58. 29.100
libavdevice 58. 8.100 / 58. 8.100
libavfilter 7. 57.100 / 7. 57.100
libavresample 4. 0. 0 / 4. 0. 0
libswscale 5. 5.100 / 5. 5.100
libswresample 3. 5.100 / 3. 5.100
libpostproc 55. 5.100 / 55. 5.100

    


    


    This is the command that I'm using :

    


    ffmpeg -y -hide_banner -loop 1 -i test.jpg -i test.mp3 -c:v libx264 -tune stillimage -c:a aac -b:a 192k -pix_fmt yuv420p -shortest out.mp4

    


    The result won't play in VLC. And it takes a very long time for the command to finish. Also the test.jpg image had an odd number y dimension, so I made it even with imagick by reducing that size by 1.

    


    How do you do this 'correctly' ?

    


  • Introducing Improvements to the Opt-Out Form Feature

    18 septembre 2022, par Ben — About

    Matomo includes a built-in opt-out form that you can add to your website so you can provide your visitors with the choice to opt-out of Matomo tracking. Up until Matomo 4.12.0 the built-in opt-out form relied on iFrame technology which has become increasingly problematic due to browser changes and restrictions on setting third-party cookies.

    With our privacy-first approach, we’ve known for some time that we would eventually need a new way to provide this important opt-out functionality that would work most reliably in the myriad of contexts our users rely on it for.

    Embedding the opt-out form

    Matomo 4.12.0 introduces an improved opt-out. This provides two new options for embedding the opt-out on your website, either using the Matomo tracker code or as self-contained code.

    As with the iFrame method, the built-in opt-out code can be styled in Matomo to match your website, and provides a snippet which you can add to your website to show the opt-out feature to your users.

    Find out how to customise the opt-out form.

    Customising the opt-out form

    What does this mean for existing opt-out forms ?

    Although it is no longer possible to generate new iFrame embed code using the Matomo UI, the underlying opt-out feature is still fully supported and any existing iFrame opt-out form code embedded in websites will still work as before. It is recommended to migrate to one of the new opt-out form options as browser support for the iFrame opt-out will continue to decrease.

    To read more in depth information about the new opt-out functionality please refer to our new developer documentation for tracking opt-out.