Recherche avancée

Médias (3)

Mot : - Tags -/spip

Autres articles (95)

  • 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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

  • 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 (14228)

  • How to shrink/expand a video file length in UNIX

    26 mars 2015, par Maria Feena

    I need to shrink/expand a video file (mp4, avi) length using command line tools,

    say the original file have 1 min length and output file should have length of 1:10 min or 0:50 min. I would like to keep other aspects of the video as it is.

    I would like to do same thing on mp3 file too. there are many files so I need to do it all in command line only.

    help me please.

  • mov : Fix handling of zero-length metadata values

    15 décembre 2014, par Martin Storsjö
    mov : Fix handling of zero-length metadata values
    

    Since 3cec81f4d4, a zero-length metadata value would try to
    allocate 2*0 bytes, where av_malloc() returns NULL.

    Always add one to the allocated length, to allow space for
    a null terminator in the zero-length case.

    Incidentally, this fixes fate-alac on RVCT 4.0, where a compiler
    bug seems to mess up the mov muxer to the point that it writes
    the wrong sort of metadata. Previously this bug was undetected,
    but since 3cec81f4d4 such mov files started returning
    AVERROR(ENOMEM) in the mov demuxer.

    Signed-off-by : Martin Storsjö <martin@martin.st>

    • [DH] libavformat/mov.c
  • Script doesnt recognize bars / length right for cutting audio , ffmpeg terminal

    14 avril 2024, par totzillarbeats

    This terminal script doesn't recognize bars / length right for cutting audio, maybe somebody knows what's wrong with the calculation ...

    &#xA;

    Would be happy about any help the cutting already works !

    &#xA;

    #!/bin/bash&#xA;&#xA;# Function to extract BPM from filename&#xA;&#xA;get_bpm() {&#xA;    local filename="$1"&#xA;    local bpm=$(echo "$filename" | grep -oE &#x27;[0-9]{1,3}&#x27; | head -n1)&#xA;    echo "$bpm"&#xA;}&#xA;&#xA;# Function to cut audio based on BPM&#xA;cut_audio() {&#xA;    local input_file="$1"&#xA;    local bpm="$2"&#xA;    local output_file="${input_file%.*}_cut.${input_file##*.}" # Appends "_cut" to original filename&#xA;&#xA;    # Define the number of beats per bar (assuming 4 beats per bar)&#xA;    beats_per_bar=4&#xA;&#xA;    # Calculate the duration of each bar in seconds&#xA;    bar_duration=$((60 * beats_per_bar / bpm))&#xA;&#xA;    # Define start and end times for each bar range&#xA;    start_times=(0 21 33 45 57 69 81 93 105 117 129 141)&#xA;    end_times=(20 29 41 53 65 77 89 101 113 125 137 149)&#xA;&#xA;    # Iterate through each bar range&#xA;    for ((i = 0; i &lt; ${#start_times[@]}; i&#x2B;&#x2B;)); do&#xA;        start_time=${start_times[$i]}&#xA;        end_time=${end_times[$i]}&#xA;        echo "Cutting audio file $input_file at $bpm BPM for bar $((i &#x2B; 1)) ($start_time-$end_time) for $bar_duration seconds..."&#xA;&#xA;        # Cut audio for current bar range using ffmpeg&#xA;        ffmpeg -i "$input_file" -ss "$start_time" -to "$end_time" -c copy "$output_file"_"$((i &#x2B; 1)).${input_file##*.}" -y&#xA;    done&#xA;&#xA;    # Check if the output files are empty and delete them if so&#xA;    for output_file in "${output_file}"_*; do&#xA;        if [ ! -s "$output_file" ]; then&#xA;            echo "Output file $output_file is empty. Deleting..."&#xA;            rm "$output_file"&#xA;        fi&#xA;    done&#xA;&#xA;    echo "Audio cut and saved as $output_file"&#xA;}&#xA;&#xA;&#xA;# Main script&#xA;if [ "$#" -eq 0 ]; then&#xA;    echo "Usage: $0 [audio_file1] [audio_file2] ..."&#xA;    exit 1&#xA;fi&#xA;&#xA;for file in "$@"; do&#xA;    bpm=$(get_bpm "$file")&#xA;    if [ -z "$bpm" ]; then&#xA;        echo "Error: No BPM found in filename $file"&#xA;    else&#xA;        cut_audio "$file" "$bpm"&#xA;    fi&#xA;done&#xA;

    &#xA;

    Maybe its only the math calc in the beginning but idk :)

    &#xA;

    If you need more details just lmk

    &#xA;