Recherche avancée

Médias (1)

Mot : - Tags -/ticket

Autres articles (47)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

Sur d’autres sites (8679)

  • Revision 5260b39e5f : vpxdec : restoring old md5 behavior for y4m files. Fix of https://code.google.co

    28 janvier 2014, par Dmitry Kovalev

    Changed 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

  • how can I set a specific duration for my speech using Google Text to Speech

    2 avril, par Alexandre Silkin

    I went through the documentation of Google Text to Speech SSML. https://developers.google.com/assistant/actions/reference/ssml#prosody

    


    So there is a tag called which as per the documentation of W3 Specification can accept an attribute called duration which is a value in seconds or milliseconds for the desired time to take to read the contained text.

    


    So <speak><prosody duration="&#x27;6s&#x27;">Hello, How are you?</prosody></speak> should take 3 seconds for google text to speech to speak this ! But when i try it here https://cloud.google.com/text-to-speech/ , its not working and also I tried it in rest API.

    &#xA;

    How can I get the time of each speech segment generated by the Google Text to Speech SSML that´s a little different from the original .srt from witch it was generated from, I was looking for a way to do so with ffmpeg so then I could divide the (tts_generated_speech/original_duration) in order to get the speech_rate_percentage witch I could use for each speech segment, so it would match the original_duration time.

    &#xA;

    Original post : Is there a way to make Google Text to Speech, speak text for a desired duration ?

    &#xA;

  • Google Cloud Platform Storage JSON API upload breaks audio files..?! How to fix ?

    13 octobre 2017, par Zolai

    I 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-upload

    Using 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.