
Recherche avancée
Autres articles (111)
-
Script d’installation automatique de MediaSPIP
25 avril 2011, parAfin de palier aux difficultés d’installation dues principalement aux dépendances logicielles coté serveur, un script d’installation "tout en un" en bash a été créé afin de faciliter cette étape sur un serveur doté d’une distribution Linux compatible.
Vous devez bénéficier d’un accès SSH à votre serveur et d’un compte "root" afin de l’utiliser, ce qui permettra d’installer les dépendances. Contactez votre hébergeur si vous ne disposez pas de cela.
La documentation de l’utilisation du script d’installation (...) -
Automated installation script of MediaSPIP
25 avril 2011, parTo overcome the difficulties mainly due to the installation of server side software dependencies, an "all-in-one" installation script written in bash was created to facilitate this step on a server with a compatible Linux distribution.
You must have access to your server via SSH and a root account to use it, which will install the dependencies. Contact your provider if you do not have that.
The documentation of the use of this installation script is available here.
The code of this (...) -
Que fait exactement ce script ?
18 janvier 2011, parCe script est écrit en bash. Il est donc facilement utilisable sur n’importe quel serveur.
Il n’est compatible qu’avec une liste de distributions précises (voir Liste des distributions compatibles).
Installation de dépendances de MediaSPIP
Son rôle principal est d’installer l’ensemble des dépendances logicielles nécessaires coté serveur à savoir :
Les outils de base pour pouvoir installer le reste des dépendances Les outils de développements : build-essential (via APT depuis les dépôts officiels) ; (...)
Sur d’autres sites (11388)
-
FFMPEG - speed up/slow down video, add jitter etc
27 septembre 2019, par DarrellI’m trying to put together a Windows script that will process short videos in a folder.
The videos will be shot at a high frame rate 60+ fps and be about 4-5 secs long.Basically I am looking to make various style clips, using fast/slow effects, back and forth etc.
So, the script might process a video, make it start normal speed, then slow motion. Next video might be normal speed, slomo, normal speed slomo. Next video might be forwards,back, forwards back, slomo.See example : (this is a compliation, I’m looking at processing individual videos in a folder.)
http://www.youtube.com/watch?v=K03IBQZu8SQ
I’m guessing there is no way to do this, other than splitting a clip using FFMPEG, processing the bits, then merging back together ? I can’t seem to find a way to do it as one clip.
-
ffprobe : IGMP membership packet doesn't include source when localaddr is set to the non-default GW interface [closed]
28 août 2023, par Chu NOn a Ubuntu 18.04.6 LTS box with 2 interfaces e.g. eno1 (10.1.1.1/24), eno2 (10.2.2.2/24). The default route goes out eno1, however I need to send SSM membership reports via eno2 to join a multicast S,G stream on 232.0.0.5 sourced from 10.5.5.5.


ffprobe version 3.4.11-0ubuntu0.1


When I input the command :
ffprobe udp ://232.0.0.5:8000 ?localaddr=10.2.2.2&sources=10.5.5.5


The outgoing IGMPv3 packet leaves via eno2 but it does NOT include the Source Address in the membership report group record field as observed on Wireshark.


When I input the command to go out via eno1 :
ffprobe udp ://232.0.0.5:8000 ?sources=10.5.5.5
or
ffprobe udp ://232.0.0.5:8000 ?localaddr=10.1.1.1&sources=10.5.5.5


The outgoing IGMPv3 packet leaves via the default GW eno1 and includes the Source Address in the IGMPv3 membership report group record field as observed on Wireshark.


How do I make ffprobe include the Source Address in the IGMPv3 packet when using an interface that's not the default gateway ?


I tried different formats of the UDP URL.
When I put the sources before localaddr(10.2.2.2), the IGMPv3 packet goes out via the default gateway (10.1.1.1).
I tried using a routing-policy on netplan to do some source routing under the eno2 stanza but it didn't work.


-
Announcing Long Term Support in Piwik 2 – The analytics platform for your mission critical projects
11 janvier 2016, par Matthieu Aubry — About, DevelopmentWe are proud to announce our Long Term Support (LTS) for Piwik 2.X !
Why Long Term Support (LTS) ?
Part of our mission is to ready Piwik for the enterprise — and ready the enterprise for Piwik. Our fast release cycle and our ability to quickly innovate has served us well for the past seven years and has lead Piwik to being one of the most popular open source projects, used by over one million websites worldwide. But Piwik’s success today has also shown us that this fast release cycle is not suited for all users and customers. Like most large open source projects (such as Ubuntu, Firefox, Debian, Symfony, Node.js, etc.) at Piwik we now also offer a Long Term Support release which gives users the confidence that Piwik can be used for mission critical projects for months to come.
What does LTS mean for Piwik ?
For the duration of the LTS period, Piwik 2.X will continue to receive the following fixes :
- Critical bugs causing data loss or data corruption.
- Major and Critical security issues.
Our goal is to offer you a Piwik LTS release that you can trust for all your mission critical projects.
How long will Piwik 2.X be supported ?
Piwik 2.X will be supported for at least 12 months after the initial release of Piwik 3.0.0.
Piwik 3.0.0 is expected to be released in the second half of 2016.
This means that Piwik 2.X will be supported at least until the second half of 2017.Which Piwik version is LTS ?
The latest Piwik 2.16.X release is our Long Term Support version.
How do I benefit from the LTS version ?
To get the full benefits of Piwik LTS, please make sure you are using the latest LTS version. First, update to the latest Piwik 2.X version, then Configure Piwik to use the LTS release channel and then update to the latest LTS version.
How do I configure Piwik to use the LTS version ?
By default, Piwik will not use the LTS version. When you use the one-click update your Piwik instance will be updated to the very latest release : when Piwik 3.0.0 will be released, the one click update will update your instance to 3.0.0. It is however possible to configure your Piwik so that you will stay on Piwik 2.X and keep using the LTS Long Term Support version :
- Login Piwik as the Super User,
- Go to Settings > General > Update settings,
- Under “Release channel” click “Latest stable 2.X Long Term Support version”, and click “Save”.
How do I get professional Piwik Support ?
If you need professional support for your Piwik service get in touch with the Piwik PRO experts.
For other questions, feedback or discussion, feel free to join our forums and comment on this LTS forum post.
We wish you all a fantastic year 2016 !