
Recherche avancée
Autres articles (74)
-
Soumettre bugs et patchs
10 avril 2011Un logiciel n’est malheureusement jamais parfait...
Si vous pensez avoir mis la main sur un bug, reportez le dans notre système de tickets en prenant bien soin de nous remonter certaines informations pertinentes : le type de navigateur et sa version exacte avec lequel vous avez l’anomalie ; une explication la plus précise possible du problème rencontré ; si possibles les étapes pour reproduire le problème ; un lien vers le site / la page en question ;
Si vous pensez avoir résolu vous même le bug (...) -
Contribute to a better visual interface
13 avril 2011MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community. -
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) (...)
Sur d’autres sites (3706)
-
AS3 AIR Detecting video play completion with FFMPEG
21 août 2015, par AntBirchI’m using FFMPEG with AS3 as I need to be able to allow the use of multiple video formats. The problem I’m having is that whilst using FFMPEG the following netStatus will never get triggered -
NetStream.Play.Stop
I’ve tried adding onPlayStatus and onStatus to the client but it seems that FFMPEG doesn’t work with these either. The only way I currently have of knowing if the video is finished is by using
"NetStream.Buffer.Empty"
but this really isn’t practical and may cause issues in the long run.I previously had an issue with being unable to trace out the netStream duration with FFMPEG which resulted in the use of ProgressEvent. Is this function the way forward for my current issue ?
Thanks in advance.
EDIT 1 : It may be possible that because NetStream is a sealed class that I have to use an internal class to add the onPlayStatus function to it ? I’ve added
netStream.client = new Client();
EDIT 2 : Can’t seem to find a way to call onPlayStatus.
EDIT 3 : Not sure if it’s worth noting but
netStream.time
never seems to matchnetStream.bufferlength
when the video has finished. -
Raspberry Pi Camera Module - Stream to LAN
20 août 2015, par user3096434have a little problem with the setup of my RasPi camera infrastructure. Basically I have a RPi 2 which shall act as a MontionEye server from now on and 2 Pi B+ with camera modules.
Previously, when I had only one camera in my network, I used the following command to stream the output from RPi B+ camera module to Youtube in full HD. So far, this command works flawless :
raspivid -n -vf -hf -t 0 -w 1920 -h 1080 -fps 30 -b 3750000 -g 50 -o - | b ffmpeg -ar 8000 -ac 2 -acodec pcm_s16le -f s16le -ac 2 -i /dev/zero -f h264 -i - -vcodec copy -acodec aac -ab 64k -g 50 -strict experimental -f flv $RTMP_URL/$STREAM_KEY
Now I have a 2nd RPi with a camera module and figured it might be the time for a change towards motioneye, as I then can view both/all camera’s in my network within the same software. I have motioneye installed on my RPi 2 and the software is running correctly.
I have a little problem when it comes to access the data stream from the RPi B+ camera on my local network.
Basically I cannot seem to figure out how to change the ffmpeg portion of the above mentioned command, in a way so it will stream the data to localhost (Or the RPi2 IP where motioneye runs - which one to use ?) instead of Youtube or any other videohoster.
I wonder, if changing the following part is a correct assumption :
Instead of using variables to define Youtube URL and key
-f flv $RTMP_URL/$STREAM_KEY
And change this to
-f flv 10.1.1.11:8080
Will I then be able to add this RPi B+ video stream to my RPi 2 motioneye server, by using motioneye ’add network camera’ function ?
From my understanding I should be able to enter the following details into motioneye ’add network camera’wizard :
Camera type: network camera
RTSP-URL: 10.1.1.11:8080
User: Pi
Pass: [my pwd]
Camera: [my ffmpeg stream shall show here]Thanks in advance !
Uhm, and then... How do I forwarded the video stream from a given camera connected to motioneye ? Like from motioneye to youtube (or similar), without re-encoding the stream ?
Like the command shown above streams directly to youtube. But I want to have it in a way, that video is streamed to local network/motioneye server, and from there I can decide which camera’s stream and when I want to send the videostream to youtube ?
How would a RPi professional realize this ?
The command above explained : Takes full HD video with 30 fps from Pi camera module and hardware encodes it on GPU with 3.75mbit/s. Then I streamcopy the video (no re-encoding) and add some audio, so that the stream complies with youtube rules (yes, no live stream without audio). Audio is taken from virtual SB16 /dev/zero at low sampling rate then encoded to 32k AAC and sent to youtube. Works fine xD.
Just when I have like 3 or more of these RPi cams the youtube stream approach ain’t feasible anymore, as my DSL upstream is limited (10 mbit/s=. Thus I need motioneye server and some magic, so I can watch f.e. all 3 camera’s videostream and then motioneye server can select and streamcopy the video from the Pi’s cam I choose and send it to youtube, as the original command did.
Any help, tips, links to similar projects highly appreciated.
Again, many thanks in advance, and even more thanks just cause you read until here.
—mx
-
vaapi : fix usage of invalid buffer ids.
28 juillet 2015, par Gwenole Beauchesnevaapi : fix usage of invalid buffer ids.
Invalid buffer ids are defined by VA_INVALID_ID. Use that through out
vaapi_*.c support files now that we have private data initialized and
managed by libavcodec. Previously, the only requirement for the public
vaapi_context struct was to be zero-initialized.This fixes support for 3rdparty VA drivers that strictly conform to
the API whereby an invalid buffer id is VA_INVALID_ID and the first
valid buffer id can actually be zero.Signed-off-by : Gwenole Beauchesne <gwenole.beauchesne@intel.com>