
Recherche avancée
Médias (1)
-
Rennes Emotion Map 2010-11
19 octobre 2011, par
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (62)
-
Publier sur MédiaSpip
13 juin 2013Puis-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 -
XMP PHP
13 mai 2011, parDixit Wikipedia, XMP signifie :
Extensible Metadata Platform ou XMP est un format de métadonnées basé sur XML utilisé dans les applications PDF, de photographie et de graphisme. Il a été lancé par Adobe Systems en avril 2001 en étant intégré à la version 5.0 d’Adobe Acrobat.
Étant basé sur XML, il gère un ensemble de tags dynamiques pour l’utilisation dans le cadre du Web sémantique.
XMP permet d’enregistrer sous forme d’un document XML des informations relatives à un fichier : titre, auteur, historique (...) -
ANNEXE : Les plugins utilisés spécifiquement pour la ferme
5 mars 2010, parLe site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)
Sur d’autres sites (10861)
-
avformat/movenc : Fix stack overflow when remuxing timecode tracks
30 septembre 2020, par Andreas Rheinhardtavformat/movenc : Fix stack overflow when remuxing timecode tracks
There are two possible kinds of timecode tracks (with tag "tmcd") in the
mov muxer : Tracks created internally by the muxer and timecode tracks
sent by the user. If any of the latter exists, the former are
deactivated. The former all belong to another track, the source
track ; the latter don't have a source track set, but the index of the
source track is initially zeroed by av_mallocz_array(). This is a
problem since 3d894db700cc1e360a7a75ab9ac8bf67ac6670a3 : Said commit added
a function that calculates the duration of tracks and the duration of
timecode tracks is calculated by rescaling the duration (calculated by
the very same function) of the source track. This gives an infinite
recursion if the first track (the one that will be treated as source
track for all timecode tracks) is a timecode track itself, leading to a
stack overflow.This commit fixes this by not using the nonexistent source track
when calculating the duration of timecode tracks not created internally
by the mov muxer.Reviewed-by : Martin Storsjö <martin@martin.st>
Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com> -
avformat/smacker : Avoid potential inifinite loop on error
23 juin 2020, par Andreas Rheinhardtavformat/smacker : Avoid potential inifinite loop on error
When reading a new frame, the Smacker demuxer seeks to the next frame
position where it excepts the next frame ; then it (potentially) reads
the palette, the audio packets associated with the frame and finally the
actual video frame. It is only at the end that the frame counter as well
as the position where the next frame is expected get updated.This has a downside : If e.g. invalid data is encountered when reading
the palette, the demuxer returns immediately (with an error) and if the
caller calls av_read_frame again, the demuxer seeks to the position where
it already was, reads the very same palette data again and therefore will
return an error again. If the caller calls av_read_frame repeatedly
(say, until a packet is received or until EOF), this meight become an
infinite loop.This could also happen if e.g. the size of one of the audio frames was
invalid or if the frame size was gigantic.This commit changes this by skipping a frame if it turns out to be
invalid or an error happens otherwise. This ensures that EOF will be
returned eventually in the above scenario.Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
-
ffmpeg doesn't stop the playing track even after ending
17 novembre 2024, par BlyZeI'm trying to run a 24/7 music stream on my Raspberry Pi 4. The .sh script works perfectly until the first track ends. After the track ends the script still sends empty data infinitely and so the stream is basically dead.


Script.sh


#!/bin/bash
MUSIC_DIR="/home/pi/Desktop/24-7-Music"
BACKGROUND_VIDEO="$MUSIC_DIR/bgvid.mp4"
KEY="myKey"

# Infinite loop to play random files
while true; do
 # Pick a random file from the folder (only including mp3)
 file=$(find "$MUSIC_DIR" -type f -name "*.mp3" | shuf -n 1)
 
 # Check if a file was found
 if [ -n "$file" ]; then
 # Extract the filename without path
 title=$(basename "$file" .mp3 | sed 's/_/ /g')
 echo "Now playing: $title"

 # Stream the file with the background video, looping the video
 # Using ffmpeg to stream video and audio together
 ffmpeg -re -stream_loop -1 -i "$BACKGROUND_VIDEO" -i "$file" \
 -filter_complex "[0:v]scale=1920x1080[v]; [1:a]anull[a]" \
 -map "[v]" -map "[a]" \
 -c:v h264_v4l2m2m -b:v 4000k -r 30 \
 -c:a aac -b:a 192k -ac 2 -bufsize 10000k -f flv "rtmp://a.rtmp.youtube.com/live2/$KEY"

 # Check if ffmpeg exited cleanly
 if [ $? -ne 0 ]; then
 echo "Error during playback. Retrying..."
 sleep 2 # Wait before retrying
 fi

 echo "Track ended, picking the next track..."

 else
 echo "No MP3 files found in $MUSIC_DIR."
 sleep 5 # Wait before checking again
 fi
done



I tried removing the stream_loop but then the stream is stuck because the background video ended.