
Recherche avancée
Autres articles (98)
-
MediaSPIP Core : La Configuration
9 novembre 2010, parMediaSPIP Core fournit par défaut trois pages différentes de configuration (ces pages utilisent le plugin de configuration CFG pour fonctionner) : une page spécifique à la configuration générale du squelettes ; une page spécifique à la configuration de la page d’accueil du site ; une page spécifique à la configuration des secteurs ;
Il fournit également une page supplémentaire qui n’apparait que lorsque certains plugins sont activés permettant de contrôler l’affichage et les fonctionnalités spécifiques (...) -
MediaSPIP Player : problèmes potentiels
22 février 2011, parLe lecteur ne fonctionne pas sur Internet Explorer
Sur Internet Explorer (8 et 7 au moins), le plugin utilise le lecteur Flash flowplayer pour lire vidéos et son. Si le lecteur ne semble pas fonctionner, cela peut venir de la configuration du mod_deflate d’Apache.
Si dans la configuration de ce module Apache vous avez une ligne qui ressemble à la suivante, essayez de la supprimer ou de la commenter pour voir si le lecteur fonctionne correctement : /** * GeSHi (C) 2004 - 2007 Nigel McNie, (...) -
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...)
Sur d’autres sites (9122)
-
Live website to video
25 janvier 2016, par Asaf NevoI have a website which shows a slideshow of pictures using JS.
The pictures objects are coming from a web service and are being updated from time to time.
In few days, I doing a test with a potential client to present the pictures slideshow on his big LED screen.
He’s using BSPlayer for the content on screen, an able to present a website, but it will never be a clean full screen (the X button and such will always be presents).
He’s the most comfort with presenting a video rather than a website.
One of my ideas of solutions was to check if there is a way to stream a content of a website.
Googling it got me to a solution combined
ImageMagic
andFFMPEG
which you can read about hereMy problem is that this solution only creates a slide show out of static pictures - which I can do, but i’m losing the dynamic part of my live slideshow.
Is there a tool for capturing websites and converting them into a stream of videos ?
Or maybe a workaround to achieve the same functionality ?
-
Google Speech to Text on WAV file gives
7 janvier 2021, par Darth.VaderI am using the Google Speech to Text API to convert a WAV file to text. When I play the WAV file, it works fine but when I run the Google Speech To Text API I get this error :


WAV header indicates an unsupported format.



When I try to analyze the file using
ffmpeg
tool, it get the following error :

Output #0, wav, to '/home/shubham/workspace/intent-service/scripts/audio2.tmp.wav':
Metadata:
 ISFT : Lavf57.83.100
 Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 8000 Hz, mono, s16, 128 kb/s
 Metadata:
 encoder : Lavc57.107.100 pcm_s16le
[gsm_ms @ 0x55d4c255cd20] Packet is too small
Error while decoding stream #0:0: Invalid data found when processing input size=7924kB time=00:08:27.16 bitrate= 128.0kbits/s speed=3.72e+03x 
video:0kB audio:7924kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.000961%



What am I missing ?


-
creating a modern nodejs video rendering app (ffmpeg microservice / cloud hosting)
5 avril 2020, par MartinI'm thinking of making a nodejs website like tunestotube.com or audioship.io that will :



- 

-
accept an audio file / image file input
-
render a video using ffmpeg
-
upload that video to youtube









I just have a question on the best way to go about doing this, I want to host over GCP eventually, and am thinking about the best / most efficient way to handle the ffmpeg video rendering, since I want it to be scaleable and have a load balancer (ingress ?) queue to handle getting multiple requests at once.



Would it make sense to containerize my web service ? Have the main website be one docker image ; and have another image / microservice 'video-renderer' that would accept the inputs, render the video, and return the rendered video ?



Does this idea make sense, and would going about it in the way I describe above work ? I'm also trying to find tutorials / example projects with handling microservices / load balancers in node js / gcp if anyone has any ideas / recomendations, thanks


-