
Recherche avancée
Médias (1)
-
The Great Big Beautiful Tomorrow
28 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Texte
Autres articles (37)
-
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 -
Support de tous types de médias
10 avril 2011Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)
-
L’utiliser, en parler, le critiquer
10 avril 2011La première attitude à adopter est d’en parler, soit directement avec les personnes impliquées dans son développement, soit autour de vous pour convaincre de nouvelles personnes à l’utiliser.
Plus la communauté sera nombreuse et plus les évolutions seront rapides ...
Une liste de discussion est disponible pour tout échange entre utilisateurs.
Sur d’autres sites (7076)
-
How to dump RTSP to raw data file without encoding
28 juin 2020, par YvesI've read this link : How to dump raw RTSP stream to file ?


In this link, it seems that dumping RTSP stream to some formatted file, such as
mp4
, is normal.

But I want to store the RTSP stream into the raw data files, instead of files like
mp4
,avi
etc. And I should be able to extract data from the raw data files and send it out as RTSP stream too.

In a word, this is what I need :


- 

- receiving RTSP stream ---> 2. store RTSP data into raw data files ---> 3. read raw data files and send data as RTSP stream




Why do I need this ?


Because as my understanding, storing RTSP strema into some formatted file, such as
mp4
, needs to do an action of encoding (encode RTSP to mp4). But for me, I don't need this action, I simply need to store RTSP data and re-send it as RTSP stream. So if I can store RTSP into the raw-data file, instead ofmp4
, I don't need to spend computer resources on the action of encoding.

-
Play audio files on a channel (Ubuntu Server)
16 octobre 2018, par danielperales555I want to make a "soundboard" on my Discord Bot.
The bot is currently running on Ubuntu Server 18.04 in a VPS Hosting.
I installed ffmpeg via aptitude
apt-get install ffmpeg
, and the respective node modules on my project via npm :npm install ffmpeg-binaries --save
andnpm install node-opus --save
I have this provisional code :
//!play (sound)
if (!args[0]) return message.channel.send('noCorrectSyntax'); //args is provided by module.run
let sound = args[0];
let isReady = true;
if (isReady) {
isReady = false;
let voiceChannel = message.member.voiceChannel;
if (!voiceChannel) return message.channel.send('noChannel');
voiceChannel.join().then(connection =>{
const dispatcher = connection.playFile(`../resources/audios/${sound}.mp3`);
if (!dispatcher) return message.channel.send('notFound');
console.log(`${new Date().toUTCString()} 》Playing ${sound} on ${message.member.voiceChannel.name}`);
dispatcher.on("end", end => {
voiceChannel.leave();
console.log(`${new Date().toUTCString()} 》Finished`);
});
}).catch(err => console.log(err));
isReady = true;
} else {
return message.channel.send('notAvailable');
}When my bot joins the voice room, it leaves instantly without playing the sound.
Am I doing something wrong by installing the ffmpeg codec this way ? Is a problem with the VPS ?
(I tried with a new bot, installing ffmpeg on windows and setting the path and it worked fine)
-
How to queue ffmpeg FIFO
29 avril 2013, par Francoiswe build a service similar to youtube. Also converting runs fine with ffmpeg using this script from another post here :
#!/bin/bash
pipe=/tmp/ffmpeg
trap "rm -f $pipe" EXIT
# creating the FIFO
[[ -p $pipe ]] || mkfifo $pipe
while true; do
# can't just use "while read line" if we
# want this script to continue running.
read line < $pipe
# now implementing a bit of security,
# feel free to improve it.
# we ensure that the command is a ffmpeg one.
[[ $line =~ ^ffmpeg ]] && bash <<< "$line"
doneThis works pretty good when i send one by one to the named pipe. When i send more than one at same time the second one queues the terminal to the point the first one finished. if a try more than 2 the third one will not be transcoded.
So i tried to workaround with background sending to get the terminal free (just drop the echo command and close the ssh connection) but this doesn't work, then i played around with screen -X but also no luck. Maybe someone has a good idea to deal this.
What i wanna do is : Every uploaded video which is needed to transcode will send a echo to the named pipe. FIFO should match but not blocking the terminal. So i think i need something to really queue ffmpeg input.
kindest regards
Francois