
Recherche avancée
Autres articles (52)
-
Participer à sa traduction
10 avril 2011Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
Actuellement MediaSPIP n’est disponible qu’en français et (...) -
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs -
Supporting all media types
13 avril 2011, parUnlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)
Sur d’autres sites (7832)
-
Google Cloud Platform Storage JSON API upload breaks audio files..?! How to fix ?
13 octobre 2017, par ZolaiI did manage to upload files to Google storage with GCP resumable upload (json api) :
https://cloud.google.com/storage/docs/json_api/v1/how-tos/resumable-uploadUsing jQuery and Plupload http://www.plupload.com
But now it seems that audio files loses their codecs in upload and those won’t play or ffmpeg can’t probe those. More testing showed that actually .flac files are ok to ffmpeg, but for example .m4a files are not.
I need to get most of the audio files uploaded to google storage and be able to probe those with ffmpeg. And must be able upload big files over 100Mb. That’s why I believe JSON API is best or only possible way.
I think I have metadata also added correctly, but now I’m confused how to continue..
Any ideas what could be the problem here ?EDIT (more info) :
I had working software :
- Using regular POST > /temp > Google Cloud Storage Client (php).
- GCP Storage Client uploaded files with perfection.
- Even that I named uploaded files with random unique name like "woeiwehf.tmp", those did work and ffmpeg could probe them fine.
THEN something happened, I guess uploading like this was limited (or something) :
-
What meant that my solution couldn’t upload anymore big files, over 32Mb.
-
Well that wasn’t best solution anyway, so that’s okey, that this changed.
NOW :
- I have changed software so it uses GCP JSON API upload resumable, and this mainly works
- But I had to change files to look like "woeiwehf.flac" or what ever type is. ".tmp" didn’t work anymore.
- For example .flac files work nicely, but .m4a will not.
- I’ve tested uploading many different ways, and it seems that JSON API upload loses at least codecs and bit rate.
—
I would be very grateful if I could get help how to resolve this.
I guess one solution may could be to fork ffmpeg client and manually set audio codec, but I’m saving that for the last solution. -
Revision 5260b39e5f : vpxdec : restoring old md5 behavior for y4m files. Fix of https://code.google.co
28 janvier 2014, par Dmitry KovalevChanged Paths :
Modify /vpxdec.c
Modify /y4menc.c
Modify /y4menc.h
vpxdec : restoring old md5 behavior for y4m files.Fix of https://code.google.com/p/webm/issues/detail?id=698 issue.
Change-Id : I7a92d91481dbbae28d8953f146e9faafdcd7a310
-
Revision 55037 : Et Google +1 sous forme de lien sans JS (donc sans tracking ! (cf ...
1er décembre 2011, par real3t@… — LogEt Google +1 sous forme de lien sans JS (donc sans tracking ! (cf http://www.ghacks.net/2011/11/30/embed-facebook-twitter-google-plus-without-javascript/)