
Recherche avancée
Médias (1)
-
Carte de Schillerkiez
13 mai 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Texte
Autres articles (99)
-
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 (...) -
Les statuts des instances de mutualisation
13 mars 2010, parPour des raisons de compatibilité générale du plugin de gestion de mutualisations avec les fonctions originales de SPIP, les statuts des instances sont les mêmes que pour tout autre objets (articles...), seuls leurs noms dans l’interface change quelque peu.
Les différents statuts possibles sont : prepa (demandé) qui correspond à une instance demandée par un utilisateur. Si le site a déjà été créé par le passé, il est passé en mode désactivé. publie (validé) qui correspond à une instance validée par un (...) -
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 (11384)
-
Piwik Developer Guides : helping you make the most of the Piwik platform
At Piwik we are creating the leading open analytics platform that gives every user full control over their data. Today we are excited to announce the official launch of the Piwik Developer Guides at developer.piwik.org. The Developer Guides complement existing User Guides and more than 250 FAQs.
Piwik Developer Guides
The Developer guides will help you whenever you need to :
- Integrate Piwik analytics in your website or application — Integration guides explain (1) how to track users of your apps (with JavaScript Tracking or other Tracking API Clients) and (2) how to query Piwik’s reporting data to integrate it into your application (Accessing Piwik data).
- Develop a new Plugin for Piwik — Plugin development guides introduce the Piwik Platform and explain how to get started with creating a new plugin to extend and customise Piwik.
- Piwik API references — API References include the references for Tracking API, Analytics API, JavaScript Tracking API and the Database schema.
- See what’s changed in the platform — Changelog for Piwik platform developers lists all changes to our HTTP API’s, Plugins, Themes, etc.
Helping Developers innovate with Piwik
Piwik is an open platform – it is open because users control their data, users control the Piwik software (it is Free/libre software) and also because users can extend the platform via the powerful plugins architecture. Piwik users can already choose from 49 plugins available on the Marketplace ! (as of 2015 April 16th)
Now that developer guides are officially released, we are hopeful that even more talented developers will be able to create Plugins and distribute them on the Marketplace.
Share your feedback
We are committed to providing excellent Developer Guides and to achieve this, we need to hear your feedback and suggestions. To send us a message, click on the “Give Feedback” link in the footer of pages (we are listening !).
What’s coming next ?
- Platform Developer Changelog will continue to list all changes to the Piwik Platform and APIs.
- We will regularly update the guides when there are changes in the platform.
- We will improve existing guides based on users’ feedback and suggestions (tasks are tracked in this issue tracker on Github.)
We hope you find the guides useful, and thank you for being part of the Piwik community !
-
How do you compile Winff ?
3 mai 2015, par RichardI downloaded the WinFF source code in the hopes the new version would solve a segfault.
It’s sitting, extracted, in its folder. But I see no
./configure
, nothingmake
would know what to do with, no binaries, and no compilation instructions :$ ls
AUTHORS COPYING README-Presets.txt unit2.lfm unit4.pas winff.1 winff.rc
changelog.txt docs README.txt unit2.pas unit5.lfm winff.ico
clean.bat languages RESOURCES.RC unit3.lfm unit5.pas winff-icons
clean.sh potranslator.pas unit1.lfm unit3.pas unit6.lfm winff.lpi
COMPILE.TXT presets.xml unit1.pas unit4.lfm unit6.pas winff.lprDoes anyone know how I can try to actually compile the code ?
All we get is a README.txt :
Winff - graphical video and audio batch converter using ffmpeg or
avconv Copyright © 2006-2012 Matthew Weatherford
http://www.winff.orgThis program is free software : you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or (at
your option) any later version.This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY ; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.You should have received a copy of the GNU General Public License
along with this program. If not, see http://www.gnu.org/licenses/.WinFF is a GUI for the command line video converter FFmpeg or avconv.
Get the latest ffmpeg builds and source from http://ffmpeg.org/
-
Cut video in chunks at nearest keyframe to the nearest scene change (ffmpeg)
11 janvier 2024, par ToxiroI want to cut a video in let’s say approximately 30 minute chunks. I first want to find the nearest scene change each 30 minutes and then cut at the nearest keyframe to that scene changes (without reencoding).


I guess I can’t do that in a single ffmpeg command, but I maybe here are some pros with very helpful tips. Is it possible for example to just output the nearest scene change (or maybe just the next scene change) at a timecode, so that ffmpeg does not need to analyze the whole video ?


I hope someone can help. If I have a solution, probably a bash script, I will post it here.