Recherche avancée

Médias (3)

Mot : - Tags -/Valkaama

Autres articles (58)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • 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

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

Sur d’autres sites (15397)

  • Google - Shaka | Deleting SegmentTimeline in manifest.mpd after restart container

    27 juin 2022, par burakkiymaz

    Shaka is running inside docker container. When I restarted container, SegmentTimeline part in manifest.mpd file deleting. Is possible appending old SegmentTimeline to new manifest.mpd file or recover it when I restarted ?

    


    Operating System :

    


    NAME="CentOS Linux"
VERSION="7 (Core)"


    


    Shaka Packager Version :

    


    google/shaka-packager:v2.5.1


    


    You can find out my configuration file below :

    


    CH_PATH=/some/path/$CH_NAME

/usr/bin/packager \
        'in=udp://127.0.0.1:'$PORT',stream=audio,init_segment='$CH_PATH'/audio_init.m4s,segment_template='$CH_PATH'/audio_$Time$.m4s' \
        'in=udp://127.0.0.1:'$PORT',stream=video,init_segment='$CH_PATH'/h264_360p_init.m4s,segment_template='$CH_PATH'/h264_360p_$Time$.m4s' \
        'in=udp://127.0.0.1:'$(($PORT + 1))',stream=video,init_segment='$CH_PATH'/h264_540p_init.m4s,segment_template='$CH_PATH'/h264_540p_$Time$.m4s' \
        'in=udp://127.0.0.1:'$(($PORT + 2))',stream=video,init_segment='$CH_PATH'/h264_720p_init.m4s,segment_template='$CH_PATH'/h264_720p_$Time$.m4s' \
        'in=udp://127.0.0.1:'$(($PORT + 3))',stream=video,init_segment='$CH_PATH'/h264_1080p_init.m4s,segment_template='$CH_PATH'/h264_1080p_$Time$.m4s' \
        --enable_widevine_encryption \
        --key_server_url ************ \
        --content_id ********** \
        --signer ********** \
        --aes_signing_key ************ \
        --aes_signing_iv ************* \
        --mpd_output $CH_PATH/manifest.mpd \
        --hls_playlist_type LIVE \
        --hls_master_playlist_output $CH_PATH/mn.m3u8 \
        --time_shift_buffer_depth 43200 \
        --preserved_segments_outside_live_window 43200


    


  • How to Adjust Google TTS SSML to Match Original SRT Timing ?

    2 avril, par Alexandre Silkin

    I have an .srt file where each speech segment is supposed to last a specific duration (e.g., 4 seconds). However, when I generate the speech using Google Text-to-Speech (TTS) with SSML, the resulting audio plays the same segment in a shorter time (e.g., 3 seconds).

    


    I want to adjust the speech rate dynamically in SSML so that each segment matches its original timing. My idea is to use ffmpeg to extract the actual duration of each generated speech segment, then calculate the speech rate percentage as :
generated duration
speech rate = --------------------
original duration

    


    This percentage would then be applied in SSML using the tag, like :
Text to be spoken

    


    How can I accurately measure the duration of each segment using ffmpeg, and what is the best way to apply the correct speech rate in SSML to match the original .srt timing ?

    


    I tried duration and my SSML should look like this :

    


            f.write(f&#x27;\t<p>{break_until_start}{text}<break time="{value["></break></p>\n&#x27;)&#xA;

    &#xA;

    Code writing the SSML :

    &#xA;

    text = value['text']&#xA;start_time_ms = int(value['start_ms']) # Start time in milliseconds&#xA;previous_end_ms = int(subsDict.get(str(int(key) - 1), {}).get('end_ms', 0)) # Get the previous end time&#xA;gap_to_fill = max(0, start_time_ms - previous_end_ms)

    &#xA;

            text = text.replace("&amp;", "&amp;amp;").replace(&#x27;"&#x27;, "&amp;quot;").replace("&#x27;", "&amp;apos;").replace("&lt;", "&amp;lt;").replace(&#xA;            ">", "&amp;gt;")&#xA;&#xA;        break_until_start = f&#x27;<break time="{gap_to_fill}ms"></break>&#x27; if gap_to_fill > 0 else &#x27;&#x27;&#xA;&#xA;        f.write(f&#x27;\t<p>{break_until_start}{text}<break time="{value["></break></p>\n&#x27;)&#xA;&#xA;    f.write(&#x27;\n&#x27;)&#xA;

    &#xA;

  • Anomalie #2866 (Fermé) : SPIP sous estime les visites de 30 à 50% par rapport à Google Analytics

    2 août 2014, par cedric -

    Tout et son contraire dans les fils de discussion, ticket inexploitable.

Navigation