
Recherche avancée
Autres articles (112)
-
Personnaliser en ajoutant son logo, sa bannière ou son image de fond
5 septembre 2013, parCertains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;
-
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...) -
Script d’installation automatique de MediaSPIP
25 avril 2011, parAfin de palier aux difficultés d’installation dues principalement aux dépendances logicielles coté serveur, un script d’installation "tout en un" en bash a été créé afin de faciliter cette étape sur un serveur doté d’une distribution Linux compatible.
Vous devez bénéficier d’un accès SSH à votre serveur et d’un compte "root" afin de l’utiliser, ce qui permettra d’installer les dépendances. Contactez votre hébergeur si vous ne disposez pas de cela.
La documentation de l’utilisation du script d’installation (...)
Sur d’autres sites (9931)
-
ffmpeg 4.1.4 wav to mp3 error of "deprecated pixel format used" [on hold]
26 août 2019, par yang jia[swscaler @ 0xc946d000] deprecated pixel format used, make sure you did set range correctly
[mp3 @ 0xc9621600] Frame rate very high for a muxer not efficiently supporting it.
Please consider specifying a lower framerate, a different muxer or -vsync 2
[auto_resampler_0 @ 0xd8e73be0] [SWR @ 0xc8058000] Output channel layout '6 channels (FLC+BC+SL+SR+TC+TFL)' is not supported
[auto_resampler_0 @ 0xd8e73be0] Failed to configure output pad on auto_resampler_0
Error reinitializing filters!
Failed to inject frame into filter network: Invalid argument
Error while processing the decoded data for stream #0:0
--------- beginning of crash
2019-02-26 16:04:58.368 27737-27737/com.blplayer.jbl.blplayer A/libc: Fatal signal 7 (SIGBUS), code 1, fault addr 0xc5ca in tid 27737 (er.jbl.blplayer)cmd
ffmpeg -i test.wav -acodec libmp3lame -ar 8000 -ac 2 -y wav2mp3.mp3
This is the log :
then on Mac it success egg
ffmpeg -i input.wav -vn -ar 44100 -ac 2 -b:a 192k output.mp3Guessed Channel Layout for Input Stream #0.0 : stereo
Input #0, wav, from ’input.wav’ :
Metadata :
encoder : Lavf58.20.100
Duration : 00:02:08.29, bitrate : 256 kb/s
Stream #0:0 : Audio : pcm_s16le (1[0][0][0] / 0x0001), 8000 Hz, stereo, s16, 256 kb/s
Stream mapping :
Stream #0:0 -> #0:0 (pcm_s16le (native) -> mp3 (libmp3lame))Output #0, mp3, to ’output.mp3’ :
Metadata :
TSSE : Lavf58.31.104
Stream #0:0 : Audio : mp3 (libmp3lame), 44100 Hz, stereo, s16p, 192 kb/s
Metadata :
encoder : Lavc58.55.101 libmp3lamebut on android it gets error
-
Connection timed out RTSP stream exited with error"
30 septembre 2019, par fw08I am building an web application on AWS Cloud that requires to stream a recorded/live video over the global network. I purchased an IP camera(GV-AVD4710) and NVR(GV-SNVR0811) for our application. In future I need to stream no. of cameras on my application.
While Camera in use With NVR, I have connected the NVR in our local network and the camera at channel_1 of NVR. Now the lets assume NVR is getting an IP of 192.168.1.203. So for rtsp streaming URL for channel_1 will be
"rtsp://id:password@192.168.1.203:554/ch1"
as per manufacturer’s specification. For camera streaming I am using "ffmpeg" multimedia framework (https://github.com/xpcrts/Steaming-IP-Camera-Nodejs ). So it is working fine. I tested it and working well in local network. Code that is running on the serverStream = require('node-rtsp-stream')
stream = new Stream({
name: 'name',
streamUrl: 'rtsp://ID:PASSWORD@abcxyz.com:554/ch1',
wsPort:3000,
ffmpegOptions: {
'-stats': '',
'-r': 30
}
})and Code running at client side which is independent of any plug-ins
<div>
<canvas width="auto" height="auto"></canvas>
<code class="echappe-js"><script type="text/javascript" src='http://stackoverflow.com/feeds/tag/jsmpeg.min.js'></script><script type="text/javascript"><br />
var canvas = document.getElementById('chanel1');<br />
var websocket = new WebSocket("ws://34.202.222.188:3000");<br />
var player= new jsmpeg(websocket, {canvas:canvas, autoplay:true, loop:true})<br />
</script>When I made this IP address available for public, and then the problem begins. It is not working and giving an error :
"[tcp @ 0x563911f0a340] Connection to tcp://192.168.1.205:554?timeout=0 failed: Connection timed out
rtsp://admin:admin@192.168.1.205: Connection timed out RTSP stream exited with error"In Camera Without NVR, I connected camera directly to our local network and so got an rtsp url like rtsp ://id:password@192.168.1.205/media/video1. Same happens again. Works well in local, but not working when I am making this available on public network.
How can stream video over global network ? Is it possible to implement these logic using ffmpeg multimedia framework ? Does VLC can help in these cases ?
I would like to reiterate that, In future there are no. of cameras needs to be stream.
RTSP stream exited with error" : Connection timed out
I am building an web application on AWS Cloud that requires to stream a recorded/live video over the global network. I purchased an IP camera(GV-AVD4710) and NVR(GV-SNVR0811) for our application. In future I need to stream no. of cameras on my application.
While Camera in use With NVR, I have connected the NVR in our local network and the camera at channel_1 of NVR. Now the lets assume NVR is getting an IP of 192.168.1.203. So for rtsp streaming URL for channel_1 will be "rtsp://id:password@192.168.1.203:554/ch1"
as per manufacturer’s specification. For camera streaming I am using "ffmpeg" multimedia framework (https://github.com/xpcrts/Steaming-IP-Camera-Nodejs ). So it is working fine. I tested it and working well in local network. Code that is running on the server
Stream = require('node-rtsp-stream')
stream = new Stream({
name: 'name',
streamUrl: 'rtsp://ID:PASSWORD@abcxyz.com:554/ch1',
wsPort:3000,
ffmpegOptions: {
'-stats': '',
'-r': 30
}
})
and Code running at client side which is independent of any plug-ins
<div>
<canvas width="auto" height="auto"></canvas>
<code class="echappe-js"><script type="text/javascript" src='http://stackoverflow.com/feeds/tag/jsmpeg.min.js'></script><script type="text/javascript"><br />
var canvas = document.getElementById('chanel1');<br />
var websocket = new WebSocket("ws://34.202.222.188:3000");<br />
var player= new jsmpeg(websocket, {canvas:canvas, autoplay:true, loop:true})<br />
</script>
When I made this IP address available for public, and then the problem begins. It is not working and giving an error :
"[tcp @ 0x563911f0a340] Connection to tcp://192.168.1.205:554?timeout=0 failed: Connection timed out
rtsp://admin:admin@192.168.1.205: Connection timed out RTSP stream exited with error"
In Camera Without NVR, I connected camera directly to our local network and so got an rtsp url like rtsp ://id:password@192.168.1.205/media/video1. Same happens again. Works well in local, but not working when I am making this available on public network.
How can stream video over global network ? Is it possible to implement these logic using ffmpeg multimedia framework ? Does VLC can help in these cases ?
I would like to reiterate that, In future there are no. of cameras needs to be stream.