
Recherche avancée
Autres articles (84)
-
Use, discuss, criticize
13 avril 2011, parTalk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
A discussion list is available for all exchanges between users. -
Le profil des utilisateurs
12 avril 2011, parChaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...) -
Configurer la prise en compte des langues
15 novembre 2010, parAccéder à la configuration et ajouter des langues prises en compte
Afin de configurer la prise en compte de nouvelles langues, il est nécessaire de se rendre dans la partie "Administrer" du site.
De là, dans le menu de navigation, vous pouvez accéder à une partie "Gestion des langues" permettant d’activer la prise en compte de nouvelles langues.
Chaque nouvelle langue ajoutée reste désactivable tant qu’aucun objet n’est créé dans cette langue. Dans ce cas, elle devient grisée dans la configuration et (...)
Sur d’autres sites (9250)
-
How to build a daemon to encode video files on S3 ?
4 avril 2013, par Yuval CohenI am interested in running a daemon to go over user uploaded video files and encode them in an optimal format (and add some watermarks).
I was considering services such as Zencoder, Encoding.com, Amazon's encoding service but some lack overlaying capabilities and some are just too expensive for our (big) volumes.
I want to build a daemon that encodes videos that are located on S3 once users upload them.
The solution I thought of would be Python Heroku servers using Celery for a task queue to keep track of the encoded files and ffmpeg to do the actual work. However, I ran into troubles compiling ffmpeg for Heroku (with libass support, so the basic ffmpeg bins aren't enough).
What approach/technology stack would you consider for this mini-project ?
Thanks !
Yuval -
Encoding videos locally or through a third party ?
7 septembre 2015, par JordanDevelopWe’re in the process on building a view uploading and sharing community right now and we’re currently developing with idea of using a third-party like Zencoder, but what makes Zencoder a better option ?
I’m sorry if i butcher up what is involved with supporting a local encoding system, so I’ll try to be vague. We plan on releasing with AWS, so why not setup an instance running ffmpeg ? I understand it’s a lot more then simply that, but if is it that difficult to find someone who can put together an instance for encoding ?
Am I right to assume most third party encoding services seem very unrealistic, price wise, for a web application who specifically focus on encoding large amounts of media ? I did notice Amazon offers an encoding features and would definitely feel more comfortable using them, but even that seems seems redundant.
I completely understand the cost behind encoding is very real, but I just can’t understand why third-party encoders are so widely accepted.
-
Yes or no, will ffmpeg api do hardware decoding on iOS ?
15 janvier 2019, par FattieThere seems to be conflicting information on this.
https://trac.ffmpeg.org/wiki/HWAccelIntro
notice the first diagram, it firmly marks iOS as “Y” on VideoToolbox
however in the comments down the bottom it says
VideoToolbox. VideoToolbox, only supported on macOS. H.264 decoding is available in FFmpeg/libavcodec.
And in the confusing second diagram it says "Standalone" is not done for VideoToolbox.
We have found that using ffmpeg compiled in to iOS .... it seems to not use hardware decoding, which is really a pain.
-
With
avcodec_get_hw_config()
we getAV_PIX_FMT_VIDEOTOOLBOX
,AV_HWDEVICE_TYPE_VIDEOTOOLBOX
which is seemingly correct. -
But usage and framerates clearly shows everything is being done in CPU. The code is in
ff_hevc_hls_residual_coding
all the time. (That’s fffmpeg’s software decoder.) -
This very diff very long git.videolan.org URL here seems to suggest again it should all be working.
-
Have tried every iPhone etc. of course
-