
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 (...) -
Multilang : améliorer l’interface pour les blocs multilingues
18 février 2011, parMultilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela. -
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 (...)
Sur d’autres sites (10331)
-
w32pthreads : move from lavc to compat/
12 mai 2013, par Anton Khirnov -
VP8/WebM : Adobe is the key to open video on the Web
22 mai 2010, par silviaGoogle have today announced the open sourcing of VP8 and the creation of a new media format WebM. Technical Challenges As I predicted earlier, Google had to match VP8 with an audio codec and a container format – their choice was a subpart of the Matroska format and the Vorbis codec. To complete (...)
-
FFMPEG errors with non-English characters
1er avril 2021, par Mingli YangWhen I tried to use the command-line to catch a chrome window with non-English characters such as ¥, or any other 中文页面, an I/O error will occur with the message "Can't find window "¥中文页面。 - Google Chrome", aborting." When the non-English characters are replaced by English ones, the errors will disappear. Environment : Windows 10, ffmpeg version 2021-03-24


This works fine :

ffmpeg -f gdigrab -i title="$ English Page - Google Chrome" -pix_fmt yuv420p grab.mp4


This has errors :

ffmpeg -f gdigrab -i title="¥中文页面。 - Google Chrome" -pix_fmt yuv420p grab.mp4


"Can't find window "¥中文页面。 - Google Chrome", aborting."


Any ideas to solve this ?