
Recherche avancée
Autres articles (45)
-
Gestion générale des documents
13 mai 2011, parMédiaSPIP ne modifie jamais le document original mis en ligne.
Pour chaque document mis en ligne il effectue deux opérations successives : la création d’une version supplémentaire qui peut être facilement consultée en ligne tout en laissant l’original téléchargeable dans le cas où le document original ne peut être lu dans un navigateur Internet ; la récupération des métadonnées du document original pour illustrer textuellement le fichier ;
Les tableaux ci-dessous expliquent ce que peut faire MédiaSPIP (...) -
La file d’attente de SPIPmotion
28 novembre 2010, parUne file d’attente stockée dans la base de donnée
Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...) -
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.
Sur d’autres sites (6094)
-
Revision 93a0189936 : Use 8 threads by default for VP9 encodes BUG=https://code.google.com/p/webm/iss
4 mars 2015, par Frank GalliganChanged Paths :
Modify /vp9/vp9_cx_iface.c
Use 8 threads by default for VP9 encodesBUG=https://code.google.com/p/webm/issues/detail?id=964
Change-Id : I70679d0f139b8e0962f7e19eb56b34060953e9b0
-
ffmpeg won't execute properly in google app engine standard nodejs
3 septembre 2019, par tommyc38I have tried for three full days to get GAE (standard - nodejs) to run a simple video transcoder from MOV to MP4 using ffmpeg. I have tried using ffluent-ffmpeg, kicking off a child process (e.g. spawn), and nothing works. As soon as it hits the call to the executable it always errors. I have confirmed ffmpeg is installed and even tried using ffmpeg-static. Moreover, I have it working on my local machine with no problems (using all of the aforementioned ways).
I have also tried logging the errors and nothing is really all that helpful. I can see its working through any installed package including ffmpeg (system package).
Below is the pseudo code...step three is where the problem occurs.
- Send file name to GAE endpoint
- Download the file from google cloud storage to a temp file
- Transcode using ffmpeg
- Upload temp file to google cloud storage
- Remove old google cloud storage file
- Remove temp file
The file I am using to test is 6MB...a 5 second video I took on my iPhone. Thank you in advance.
UPDATE : I successfully deployed the exact same code to Node Flex environment and everything works great. I wasn’t able to get any errors in the standard environment that directed me where to look but my guess is it has something to do with how it stores the file I pipe into FFMPEG on GAE Node Standard. The docs say its a virtual file system that uses RAM. I’d love to hear if anybody managed to get it working in the standard environment.
-
Google Analytics Sampling : Why It Matters and How to Avoid It
21 octobre 2024, par Daniel Crough — Analytics Tips