
Recherche avancée
Médias (1)
-
Rennes Emotion Map 2010-11
19 octobre 2011, par
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (67)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Possibilité de déploiement en ferme
12 avril 2011, parMediaSPIP peut être installé comme une ferme, avec un seul "noyau" hébergé sur un serveur dédié et utilisé par une multitude de sites différents.
Cela permet, par exemple : de pouvoir partager les frais de mise en œuvre entre plusieurs projets / individus ; de pouvoir déployer rapidement une multitude de sites uniques ; d’éviter d’avoir à mettre l’ensemble des créations dans un fourre-tout numérique comme c’est le cas pour les grandes plate-formes tout public disséminées sur le (...) -
Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs
12 avril 2011, parLa manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras.
Sur d’autres sites (9004)
-
Anomalie #4006 : "Fullscreen" demande la validation des champs obligatoires d’un formulaire
28 septembre 2017, par b bLe mode plein écran affiche le même bloc de prévisu que l’onglet prévisualisation, le problème me semble donc bien être le même. De plus, le ticket que je citais en référence signale le même problème aussi lors de l’utilisation du plein écran (cf mail de jean marie), c’est pourquoi je pense que le ticket ici présent est un doublon :)
Le seul truc qui m’étonne est que tu signales que ton site n’utilise pas HTML5, mais peut-être que saisies force aussi la validation des champs obligatoires en js si HTML5 n’est pas actif, à vérifier et discuter dans le premier ticket donc.
-
Selecting GPU with ffmpeg hwaccel
19 octobre 2017, par Nick ErokhinIn my project I need to make many edits of the same video
ffmpeg -hwaccel cuvid -c:v h264_cuvid -i [input video] -ss [start time] -to [end time] -vcodec h264_nvenc [output video]
This command gave me a significant performance increase from using software decoding. However, I only used one GPU for this.
I’m trying to scale up to a p2.8x with 8 GPUs. I want to be able to create 8 sets of edits and map each set to a GPU to be processed in parallel.
How can I specify a GPU for FFmpeg to use ?
-
Presentation of Piwik’s collaborative translations platform : oTrance [Interview]
19 avril 2013, par matt — Community, translationPiwik enables domain administrators, hobbyists, power users, personal website builders and everyone in between to access enormous amounts of data for website analytics. To support all those users, Piwik needs to be available in a number of different languages. From the start, we made internationalization (i18n) part of Piwik’s DNA. There are now dozens active volunteers who help make sure each language is well represented in the latest official release of Piwik. As of now, Piwik is available in 48 languages.
Recently a new tool became available that makes the translation of Piwik much easier. The software we are using is an open source platform called oTrance. It has made our translation architecture more robust, and it allows us to expedite the timely delivery of high quality and up-to-date translations to the thousands of people who rely on Piwik every day.
We’ve met with oTrance creator and lead developer Daniel Schlichtholz who answered a few questions for us.
What is oTrance ?
oTranCe is the short form of “Online Translation Center”. It was born because I needed a translation platform for my project MySQLDumper.
Many languages have been added by the community and manual maintenance became more and more time consuming. I wanted to change that. So I searched for an existing platform I could use and tested a lot of approaches. To put a long story short : none of the given solutions satisfied my needs.
From the view of a translator maintaining a language should be as easy as possible. In most cases they have to install a program on their local machine or the workflow was too difficult. A translator doesn’t want to struggle with technical things ; he just wants to translate the phrases and wants to know the progress.
That’s the main goal we want to reach : to make the translation process as easy as possible.
What sets oTrance apart from the other ways to manage translations ?
Ease of use is one advantage of oTranCe compared to other solutions. Another advantage is that project administrators can install oTranCe on their own server – so nobody is dependant of a third party provider.
We love to get feedback from other users. User feedback influences the way oTranCe is developed. We believe that this way oTranCe satisfies the requirements of the real world.
We also have extensive user documentation, in our “Working with oTranCe” wiki. We try to document use cases in an understandable way. We don’t write down marketing buzz words, but try to explain the use from the view of the user/administrator.
Now that oTranCe 1.0 is out, what will you be working on next ?
The language files can be exported to version control and oTranCe can commit changes to the target repository. Currently we support export to Subversion, and we are working on a Git export adapter, which will be released soon.
Another issue we are trying to solve is the context problem. When your project uses many different phrases the translator often doesn’t know in which context the current phrase is used. Version 1.1.0 (not released yet, but you can grab the latest developer version from GitHub) introduces the oTranCe-connector. The idea behind it : a small plug in grabs the used phrases/keys on the current page, and on click this list is submitted to oTranCe, where the translator can edit the words. This way the translator knows in which context these phrases are used. I wrote a small plug in for OXID eShop. Since it is really easy to implement, my hope is that other plug ins for other applications will be added by the community.
Matthieu : Congratulations Daniel for having created such an awesome Translation Platform. At Piwik we are really thankful for oTranCe, which has resulted in much better translation process, and happier translators. Keep up the good work !
If you are a Piwik user, and if you want to participate in translating Piwik, please sign up for an account on oTrance and become part of the team making Piwik available in more languages across the world.