
Recherche avancée
Autres articles (69)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 0.2 est la première version de MediaSPIP stable.
Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...) -
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)
Sur d’autres sites (12961)
-
why did google create the webm format ?
18 octobre 2019, par hgoldfishI known the WebM format is derived from Matroska format. And WebM is a subset of Matroska. But why Google didn’t use Matroska directly ?
What advantages does WebM have over Matroska ?
-
why google create webm format ?
17 octobre 2019, par hgoldfishI known the WebM format is derived from Matroska format. And WebM is a subset of Matroska. But why Google didn’t use Matroska directly ?
What advantages does WebM have over Matroska ?
-
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 ?