
Recherche avancée
Autres articles (98)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 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 (...) -
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...) -
ANNEXE : Les plugins utilisés spécifiquement pour la ferme
5 mars 2010, parLe site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)
Sur d’autres sites (10615)
-
How to get your Piwik plugin translated in many languages ?
About a year ago we introduced the Piwik Marketplace to make it easy for developers to share their plugins with all Piwik users.
As Piwik is currently available in 54 languages we would love to have as many plugins as possible available in at least a few of those languages.
Currently most plugins on the Marketplace are only available in English and sometimes some other languages. To improve this situation, we offer plugin developers the possibility to use the power of our translators community to get their plugins translated.
Some plugin developers are already using this service and some very popular plugins like BotTracker or CustomOptOut have already been translated in more than 10 languages !
Getting translations for your plugin
As long as you are developing an open source plugin hosted on Github, you may get in touch with us (translations@piwik.org) in order to get your plugin translated by the Piwik translators community.
You will need an account on Transifex.com. If you use Transifex with a social login, please ensure to set a password in your account settings. This will be required for fetching new translations into your plugin repository.
Importing your plugin’s strings in the translation platform
While doing the initial setup for your plugin, we will import your english translation file (
en.json
) in your Github plugin repository and we will configure an auto-update for this file. Source strings on Transifex will automatically synchronise with your plugin repository. When you change any string in youren.json
translation file, the updated English strings will automatically be imported in Transifex.How to fetch your plugins translations into your repository
As soon as we have set up your plugin within our project Piwik on Transifex and there are new translations available, you will be able to update your plugin translations using the Piwik console. You will need a locally installed Piwik with development mode enabled, and your plugin installed. To update the translations go to the Piwik directory on your development box and execute the following command :
./console translations:update -u {YourTransifexUserName} -p {YourTransifexPassword} -P {YourPluginName}
We are looking forward to seeing your Piwik plugins available in more languages ! For more information, check out our Translations plugin developer guide.
Happy hacking,
-
The video is very long when I pair them
14 août 2019, par Ngo Van PhucFirst of all, I’m sorry for not being good at English.
I want to ask about Ffmpeg :Video A (time : 00:31:51 - 1280x720) connect with Video B (time : 00:00:22 - 1270x720) output video : (time : 01:20:38)
The code I use(Ffmpeg) : "ffmpeg -f concat -i file-list.txt -c copy outputfile.mp4"
Please help me, thank you.
-
H.264 (MP4) video not play in IE9, but will play in Safari [closed]
27 septembre 2011, par Austin SI have encoded a video using FFMPEG into three formats : WebM, MP4, and FLV. Chrome, Mozilla, and theoretically Opera (although I haven't tested it) should all use the WebM version. IE9, iOS devices, and Adriod should use the MP4 container. While all legacy browsers should default back to the flash version of the file. I'm using video-js to help serve the content. The content is set to preload and autoplay.
I have found that everything is working as intended except for IE9, where all I get is the poster image and a white dot that typically spins indicating that the file is loading however it is not spinning in this scenario. The MP4 file opens in Safari, an iPad, an iPhone, and an Andriod - verifying that the file is infact legit.
The following is the specs for the MP4 file when I stream it using VLC. I don't know if this is particularly useful, I'm just trying to provide as much detail as possible.
VLC Codec Details
-
Stream 0
Type : Video
Codec : MPEG-4 Video (mp4v)
Language : English
Resolution : 480x270
Frame rate : 2997
-
Stream 1
Type : Audio
Codec : MPEG AAC Audio (mp4a)
Language : English
Channels : Stereo
Sample rate : 48000 Hz
When accessing videojs.com from my coworkers computer, the video on their main page wouldn't play the video correctly in IE9, but we could hear the audio. When I went to another coworkers computer it played just fine. I'm wondering if IE9, or video-js, is tempermental depending on how updated your OS is.
The fact that I'm working on XP with IE7 is making this all the more difficult to fix, so if you have any suggestions on what could point me in the right direction, I would greatly appreciate it !
Thanks,
Austin S
-