Recherche avancée

Médias (0)

Mot : - Tags -/serveur

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (38)

  • La sauvegarde automatique de canaux SPIP

    1er avril 2010, par

    Dans le cadre de la mise en place d’une plateforme ouverte, il est important pour les hébergeurs de pouvoir disposer de sauvegardes assez régulières pour parer à tout problème éventuel.
    Pour réaliser cette tâche on se base sur deux plugins SPIP : Saveauto qui permet une sauvegarde régulière de la base de donnée sous la forme d’un dump mysql (utilisable dans phpmyadmin) mes_fichiers_2 qui permet de réaliser une archive au format zip des données importantes du site (les documents, les éléments (...)

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

Sur d’autres sites (4093)

  • ffmpeg output separate channel from an input with multiple channels

    16 février 2017, par tiras muturi

    i run this command to be able to stream a udp live stream to a http live stream that is playable using a mobile application that am building.
    its just a stream with audio streams only.

    ffmpeg -i udp ://@localhost:1111 -map 0:a http://localhost:8090/feed1.ffm

    Input #0, mpegts, from 'udp://@localhost:1111':
    
  Duration: N/A, start: 54616.264622, bitrate: 768 kb/s
    
  Program 1
    
    Metadata:
    
  service_name    : Service 1
    
  service_provider: TLK
    
    Stream #0:0[0x101]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 96 kb/s
    
  Program 2
    
Metadata:
    
  service_name    : Service 2
    
  service_provider: TLK
    
Stream #0:1[0x111]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 96 kb/s
    
 Program 3
    
Metadata:
    
  service_name    : Service 3
    
  service_provider: TLK
    
Stream #0:2[0x121]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 96 kb/s
    
 Program 4
    
Metadata:
    
  service_name    : Service 4
    
  service_provider: TLK
    
Stream #0:3[0x131]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 96 kb/s
    
  Program 5
    
Metadata:
    
  service_name    : Service 5
    
  service_provider: TLK
    
Stream #0:4[0x141]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 96 kb/s
    
  Program 6
    
Metadata:
    
  service_name    : Service 6
    
  service_provider: TLK
    
Stream #0:5[0x151]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 96 kb/s
    
  Program 7
    
Metadata:
    
  service_name    : Service 7
    
  service_provider: TLK
    
Stream #0:6[0x161]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 96 kb/s
    
 Program 8
    
Metadata:
    
  service_name    : Service 1
    
  service_provider: TLK
    
Stream #0:7[0x171]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 96 kb/s

    i get this output

    Stream mapping:
    
  Stream #0:0 -> #0:0 (mp2 (native) -> mp2 (native))
    
  Stream #0:0 -> #0:1 (mp2 (native) -> mp2 (native))
    
Press [q] to stop, [?] for help
    
size=     100kB time=00:00:07.19 bitrate= 113.8kbits/s speed=3.01x
    
video:0kB audio:84kB subtitle:0kB other streams:0kB global headers:0kB  muxing overhead: 18.358242%

    i really want a way i can be able to map every input stream to have an output stream that can be accessed separately from the other like maybe if i need the first stream maybe i will just

    ffplay http://localhost:8090/feed1.ffm

    and if i need the 7th stream i will just

    ffplay http://localhost:8090/feed7.ffm

    Please can someone help me crack this issue. FFmpeg dont have complex examples for my current situation.

    this is my header information

    ubuntu@ip-localhost:~$ \ 
    
ffmpeg -i udp://@localhost:4000 \
    
  -map 0:a:0     http://localhost:8090/feed1.ffm 
    
  -map 0:a:1 http://localhost:8090/feed2.ffm 
    
  -map 0:a:2 http://localhost:8090/feed3.ffm 
    
  -map 0:a:3 http://localhost:8090/feed4.ffm 
    
  -map 0:a:4 http://localhost:8090/feed5.ffm 
    
  -map 0:a:5 http://localhost:8090/feed6.ffm 
    
  -map 0:a:6 http://localhost:8090/feed7.ffm 
    
  -map 0:a:7 http://localhost:8090/feed8.ffm

    ffmpeg version 3.2.4-1 16.04.york0 Copyright (c) 2000-2017 the FFmpeg developers built with gcc 5.4.1 (Ubuntu 5.4.1-5ubuntu2 16.04.york1) 20170210
    configuration : —prefix=/usr —extra-version=’1 16.04.york0’ — toolchain=hardened —libdir=/usr/lib/x86_64-linux-gnu —incdir=/usr/include/x86_64-linux-gnu —enable-gpl —disable-stripping —enable-avresample —enable-avisynth —enable-gnutls —enable-ladspa —enable-libass —enable-libbluray —enable-libbs2b —enable-libcaca —enable-libcdio —enable-libebur128 —enable-libflite —enable-libfontconfig —enable-libfreetype —enable-libfribidi —enable-libgme —enable-libgsm —enable-libmp3lame —enable-libopenjpeg —enable-libopenmpt —enable-libopus —enable-libpulse —enable-librubberband —enable-libshine —enable-libsnappy —enable-libsoxr —enable-libspeex —enable-libssh —enable-libtheora —enable-libtwolame —enable-libvorbis —enable-libvpx —enable-libwavpack —enable-libwebp —enable-libx265 —enable-libxvid —enable-libzmq —enable-libzvbi —enable-omx —enable-openal —enable-opengl —enable-sdl2 —enable-libdc1394 —enable-libiec61883 —enable-chromaprint —enable-frei0r —enable-libopencv —enable-libx264 —enable-shared
    libavutil 55. 34.101 / 55. 34.101
    libavcodec 57. 64.101 / 57. 64.101
    libavformat 57. 56.101 / 57. 56.101
    libavdevice 57. 1.100 / 57. 1.100
    libavfilter 6. 65.100 / 6. 65.100
    libavresample 3. 1. 0 / 3. 1. 0
    libswscale 4. 2.100 / 4. 2.100
    libswresample 2. 3.100 / 2. 3.100
    libpostproc 54. 1.100 / 54. 1.100

    Input #0, mpegts, from 'udp://@localhost:1111':
    
  Duration: N/A, start: 60047.944622, bitrate: 768 kb/s
    
  Program 1
    
    Metadata:
    
  service_name    : Service 1
    
  service_provider: TKL
    
Stream #0:0[0x101]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 96 kb/s
    
 Program 2
    
Metadata:
    
  service_name    : Service 2
    
  service_provider: TKL
    
Stream #0:1[0x111]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 96 kb/s
    
 Program 3
    
Metadata:
    
  service_name    : Service 3
    
  service_provider: TKL
    
Stream #0:2[0x121]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 96 kb/s
    
Program 4
    
Metadata:
    
  service_name    : Service 4
    
  service_provider: TKL
    
Stream #0:3[0x131]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 96 kb/s
    
Program 5
    
Metadata:
    
  service_name    : Service 5
    
  service_provider: TKL
    
Stream #0:4[0x141]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 96 kb/s
    
Program 6
    
Metadata:
    
  service_name    : Service 6
    
  service_provider: TKL
    
Stream #0:5[0x151]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 96 kb/s
    
Program 7
    
Metadata:
    
  service_name    : Service 7
    
  service_provider: TKL
    
Stream #0:6[0x161]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 96 kb/s
    
Program 8
    
Metadata:
    
  service_name    : Service 8
    
  service_provider: TKL
    
Stream #0:7[0x171]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 96 kb/s
    
Output #0, ffm, to 'http://localhost:8090/feed1.ffm':
    
Metadata:
    
creation_time   : now
    
encoder         : Lavf57.56.101
    
Stream #0:0: Audio: mp2, 44100 Hz, mono, s16, 32 kb/s
    
Metadata:
    
  encoder         : Lavc57.64.101 mp2
    
Stream #0:1: Audio: mp2, 44100 Hz, stereo, s16, 64 kb/s
    
Metadata:
    
  encoder         : Lavc57.64.101 mp2
    
Output #1, ffm, to 'http://localhost:8090/feed2.ffm':
    
Metadata:
    
creation_time   : now
    
encoder         : Lavf57.56.101
    
Stream #1:0: Audio: mp2, 44100 Hz, stereo, s16, 64 kb/s
    
Metadata:
    
  encoder         : Lavc57.64.101 mp2
    
Output #2, ffm, to 'http://localhost:8090/feed3.ffm':
    
Metadata:
    
creation_time   : now
    
encoder         : Lavf57.56.101
    
Stream #2:0: Audio: mp2, 44100 Hz, stereo, s16, 64 kb/s
    
Metadata:
    
  encoder         : Lavc57.64.101 mp2
    
Output #3, ffm, to 'http://localhost:8090/feed4.ffm':
    
Metadata:
    
creation_time   : now
    
encoder         : Lavf57.56.101
    
Stream #3:0: Audio: mp2, 44100 Hz, stereo, s16, 64 kb/s
    
Metadata:
    
  encoder         : Lavc57.64.101 mp2
    
Output #4, ffm, to 'http://localhost:8090/feed5.ffm':
    
Metadata:
    
creation_time   : now
    
encoder         : Lavf57.56.101
    
Stream #4:0: Audio: mp2, 44100 Hz, stereo, s16, 64 kb/s
    
Metadata:
    
  encoder         : Lavc57.64.101 mp2
    
Output #5, ffm, to 'http://localhost:8090/feed6.ffm':
    
Metadata:
    
creation_time   : now
    
encoder         : Lavf57.56.101
    
Stream #5:0: Audio: mp2, 44100 Hz, stereo, s16, 64 kb/s
    
Metadata:
    
  encoder         : Lavc57.64.101 mp2
    
Output #6, ffm, to 'http://localhost:8090/feed7.ffm':
    
Metadata:
    
creation_time   : now
    
encoder         : Lavf57.56.101
    
Stream #6:0: Audio: mp2, 44100 Hz, stereo, s16, 64 kb/s
    
Metadata:
    
  encoder         : Lavc57.64.101 mp2
    
Output #7, ffm, to 'http://localhost:8090/feed8.ffm':
    
Metadata:
    
creation_time   : now
    
encoder         : Lavf57.56.101
    
Stream #7:0: Audio: mp2, 44100 Hz, stereo, s16, 64 kb/s
    
Metadata:
    
  encoder         : Lavc57.64.101 mp2
    
Stream mapping:
    
Stream #0:0 -> #0:0 (mp2 (native) -> mp2 (native))
    
Stream #0:0 -> #0:1 (mp2 (native) -> mp2 (native))
    
Stream #0:0 -> #1:0 (mp2 (native) -> mp2 (native))
    
Stream #0:0 -> #2:0 (mp2 (native) -> mp2 (native))
    
Stream #0:0 -> #3:0 (mp2 (native) -> mp2 (native))
    
Stream #0:0 -> #4:0 (mp2 (native) -> mp2 (native))
    
Stream #0:0 -> #5:0 (mp2 (native) -> mp2 (native))
    
Stream #0:0 -> #6:0 (mp2 (native) -> mp2 (native))
    
Stream #0:0 -> #7:0 (mp2 (native) -> mp2 (native))
    
Press [q] to stop, [?] for help

    thats my full console.

  • Encode h264 automatically on nginx server

    18 février 2017, par Thinh Pham

    I have installed and configured my own streaming server using Nginx with rtmp module base on this tutorial https://www.vultr.com/docs/setup-nginx-on-ubuntu-to-stream-live-hls-video. I only use live application and record stream into flv file. And now I want to encode any new flv files in my VOD directory automatically to play it on my website. Is it possible to config it in my nginx.conf ? I have tried set record_suffix .mp4; in order to play it without encode but failed.
    Additional, exec ffmpeg -i is not work for me when I want to restream into mobile application.

  • French CNIL recommends Piwik : the only analytics tool that does not require Cookie Consent

    29 octobre 2014, par Matthieu Aubry — Press Releases

    There has been recent and important changes in France regarding data privacy and the use of cookies. This blog post will introduce you to these changes and explain how you make your website compliant.

    Cookie Consent in the data freedom law

    Since the adoption of the EU Directive 2009/136/EC “Telecom Package”, Internet users must be informed and provide their prior consent to the storage of cookies on their computer. The use of cookies for advertising, analytics and social share buttons require the user’s consent :

    It is necessary to inform users of the presence, purpose and duration of the cookies placed in their browsers, and the means at their disposal to oppose it.

    What is a cookie ?

    Cookies are tracers placed on Internet users’ hard drives by the web hosts of the visited website. They allow the website to identify a single user across multiple visits with a unique identifier. Cookies may be used for various purposes : building up a shopping cart, storing a website’s language settings, or targeting advertising by monitoring the user’s web-browsing.

    Which cookies are exempt from the Cookie Consent rule ?

    France has exempted certain cookies from the cookie consent rule : for those cookies that are strictly necessary to offer the service sought after by the user you do not need to ask consent to user. Examples of such cookies are :

    • the shopping cart cookie,
    • authentication cookies,
    • short lived session cookies,
    • load balancer cookies,
    • certain first party analytics (such as Piwik cookies),
    • persistent cookies for interface personalisation.

    Asking users for consent for Analytics (tracking) Cookies

    For all cookies that are not exempted from the Cookie Consent then you will need to :

    • obtain consent from web users before placing or reading cookies and similar technologies,
    • clearly inform web users of the different purposes for which the cookies and similar technologies will be used,
    • propose a real choice to web users between accepting or refusing cookies and similar technologies.

    You don’t need Cookie Consent with Piwik

    The excellent news is that there is a way to bypass the Cookie Consent banner on your website :

    If you are using another analytics solution other than Piwik then you will need to ask users for consent. If you do not want to ask for consent then download and install Piwik or signup to Piwik Cloud to get started.

    If you are already using Piwik you need to do two simple things : (1) anonymise visitor IP addresses (at least two bytes) and (2) include the opt-out iframe solution in your website (learn more).

    Note that these recommendations currently only apply in France, but because the law is European we can expect similar findings in other European countries.

    CNIL recommends Piwik

    We are proud that the CNIL has identified Piwik as the only tool that respects all privacy requirements set by the European Telecom law.

    About the CNIL

    The CNIL is an independent administrative body that operates in accordance with the French data protection legislation. The CNIL has been entrusted with the general duty to inform people of the rights that the data protection legislation allows them.

    The role and responsabilities of the CNIL are :

    • to protect citizens and their data
    • to regulate and control processing of personal data
    • to inspect the security of data processing systems and applications, and impose penalties

    Piwik and Privacy

    At Piwik we love Privacy – our open analytics platform comes with built-in Privacy.

    Future of Privacy at Piwik

    Piwik is already the leader when it comes to respecting user privacy but we plan to continue improving privacy within the open analytics platform. For more information and specific ideas see Privacy enhancing issues in our issue tracker.

    References

    Learn more in these articles in French [fr] or English :

    Contact

    To learn more about Piwik, please visit piwik.org,

    Get in touch with the Piwik team : Contact information,

    For professional support contact Piwik PRO.

Navigation