
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 (82)
-
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 (...) -
MediaSPIP Player : problèmes potentiels
22 février 2011, parLe lecteur ne fonctionne pas sur Internet Explorer
Sur Internet Explorer (8 et 7 au moins), le plugin utilise le lecteur Flash flowplayer pour lire vidéos et son. Si le lecteur ne semble pas fonctionner, cela peut venir de la configuration du mod_deflate d’Apache.
Si dans la configuration de ce module Apache vous avez une ligne qui ressemble à la suivante, essayez de la supprimer ou de la commenter pour voir si le lecteur fonctionne correctement : /** * GeSHi (C) 2004 - 2007 Nigel McNie, (...) -
Supporting all media types
13 avril 2011, parUnlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)
Sur d’autres sites (5496)
-
FFmpeg can't run in some device Android
30 mars 2016, par tqni’m working in a video processing project and now i’m using ffmpeg library in Android. I’m facing with a strange problem with asus zenphone 4 t00l (or all x86 device, I’ve just test in this x86 phone). When start command in project, app always crash :
03-30 15:08:18.461 21068-21068/com.paditech.videa I/FFmpeg: Loading FFmpeg for armv7-neon CPU
03-30 15:08:18.781 21068-21068/com.paditech.videa I/System.out: Success........
03-30 15:26:12.933 21068-21068/com.paditech.videa E/IMGSRV: :0: PVRDRMOpen: TP3, ret = 59
03-30 15:26:12.933 21068-21068/com.paditech.videa E/IMGSRV: :0: PVRDRMOpen: TP3, ret = 63
03-30 15:26:15.913 21068-21068/com.paditech.videa D/VideoActivity: onDestroy
03-30 15:26:18.993 21068-21068/com.paditech.videa I/FFmpeg: Loading FFmpeg for armv7-neon CPU
03-30 15:26:19.263 21068-21068/com.paditech.videa I/System.out: Success........
03-30 15:26:42.583 21068-21184/com.paditech.videa D/FFmpeg: Running publishing updates method
03-30 15:26:42.583 21068-21068/com.paditech.videa E/IMGSRV: :0: PVRDRMOpen: TP3, ret = 59
03-30 15:26:42.583 21068-21068/com.paditech.videa E/IMGSRV: :0: PVRDRMOpen: TP3, ret = 85
03-30 15:26:42.683 21068-21068/com.paditech.videa D/VideoActivity: /data/data/com.paditech.videa/files/ffmpeg[1]: syntax error: '-�-4�' unexpected
03-30 15:26:42.683 21068-21068/com.paditech.videa D/VideoActivity: /data/data/com.paditech.videa/files/ffmpeg[1]: syntax error: '-�-4�' unexpectedFirst, I think the problem is ffmpeg library. So I created a test module with simple activity just load and run command and there’re no problem.
Second, I’m afraid that app cannot load version ffmpeg, because in my log, it’s armv7-neon althought it’s x86 (In my test module, it display x86). And according my search result, may be a external library make app to use abi arm (Build.CPU_API="armv7"). So I try remove all library in gradle in module Test and detected a library. But check in aar file of library, it support all x86 and arm. But after remove it, app still crash with same log. And strangely, althogh Test module register as arm but it’still run success (External question : Why add library jp.wasabeef:picasso-transformations make system register as armv7 although it’s x86)
Finally, i think problem is command. But after debug, I use same command for Test module but it still success. Now i’m still stuck with it. Could anyone help me to solve it. Thanks. Here my demo code :
String input = "/storage/emulated/0/Videa/Video/VIDEO_20160122_160020.mp4";
String output = "/storage/emulated/0/Videa/Audio/AUDIO_20160330_142501.wav";
String[] command = {
"-y",
"-i",
input,
"-vn",
"-f",
"wav",
output
};
FFmpeg ffmpeg = FFmpeg.getInstance(getApplicationContext());
try {
ffmpeg.execute(command, new ExecuteBinaryResponseHandler() {
@Override
public void onSuccess(String message) {
super.onSuccess(message);
System.out.println("Success " + message);
}
@Override
public void onFailure(String message) {
super.onFailure(message);
System.out.println("Failure " + message);
}
});
} catch (Exception e) {
e.printStackTrace();
}And here is Failed command :
ArrayList<string> cmd = new ArrayList<string>();
cmd.add("-y");
cmd.add("-i");
cmd.add(input);
cmd.add("-vn");
cmd.add("-f");
cmd.add("wav");
cmd.add(output);
String[] result = new String[cmd.size()];
return cmd.toArray(result);
</string></string> -
Webcam - Publishing and Archiving on line video files
11 novembre 2014, par Emmanuel BrunetI want to publish an ASF live video stream over the internet and also copy the backup to disk (without sound to spare disk space)
I’m running debian 7.7 wheezy / ffmpeg 2.2 and ffserver 1.2.9.
The IP camera video streams specifications are
Input #0, asf, from 'http://account:password@webcam/videostream.asf':
Duration: N/A, start: 0.000000, bitrate: 32 kb/s
Stream #0:0: Video: mjpeg (MJPG / 0x47504A4D), yuvj422p(pc), 640x480, 50 tbr, 1k tbn, 1k tbc
Stream #0:1: Audio: adpcm_ima_wav ([17][0][0][0] / 0x0011), 8000 Hz, 1 channels, s16p, 32 kb/sTo achieve this I have set up a /etc/ffserver.conf configuration
Port 11000
BindAddress 0.0.0.0
MaxClients 1000
MaxBandwidth 40000
CustomLog -
<feed>
File /tmp/feed1.ffm
FileMaxSize 200K
ACL allow localhost
ACL allow 192.168.1.1 192.168.255.255
</feed>
# --------------------------- ASF ----------------------
<stream>
Feed feed1.ffm
Format asf
AVOptionVideo flags +global_header
VideoFrameRate 25
VideoSize 640x480
VideoBitRate 1024
VideoBufferSize 1024
StartSendOnKey
NoAudio
</stream>
# ------------ Server status -------------------
<stream>
Format status
# Only allow local people to get the status
ACL allow localhost
ACL allow 192.168.0.0 192.168.255.255
#FaviconURL http://pond1.gladstonefamily.net:8080/favicon.ico
</stream>
# ---------- Redirect --------------------
<redirect>
URL http://www.ffmpeg.org/
</redirect>To connect the feed I run
to start the ffserver
ffserver -f /etc/ffserver.conf
to collect the stream from the camera
ffmpeg -i http://account:password@webcam/videostream.asf -c:v libx264 -an http://localhost:11000/feed1.ffm
and all works like a charm.
My questions are :
- How in the same time having the stream saved to disk ?
(as done by the command)
ffmpeg -i http://account:password@webcam/videostream.asf -preset veryfast -t 00:60:00 -b:v 512K -c:v libx264 -pix_fmt yuv420p -an /var/backup/videos/YYY-MM-DD.mp4
Note that the output .mp4 file names should rotate to get multiple timestamped output archives
- How can I published video over RTSP ?
I’ve found examples on the internet but none worked for me
Thanks in advance
regards
-
avdevice/xcbgrab : don't assume xserver endianness
31 janvier 2021, par Andriy Gelmanavdevice/xcbgrab : don't assume xserver endianness
xserver defines the endianness of the grabbed images. Use this information
to set the correct pixel format.This also fixes format selection in configuration depth=32/bpp=32 with
xserver on a little endian machine. Before the patch, the big endian
layout 0RGB was always selected which is incorrect because BGR0 should
be used. RGB24 was also incorrectly assumed (but this format was removed
in xserver 1.20).The big-endian settings can be tested using docker+qemu from a little-endian
machine :$ docker run —rm —privileged multiarch/qemu-user-static —reset -p yes
$ docker run —rm -it -v /tmp :/tmp powerpc64/debian /bin/bashIn docker container
$ apt-get update
$ apt-get install xvfb
$ apt-get install x11-appsTo test AV_PIX_FMT_0RGB32
$ Xvfb :2 -screen 0 720x480x24 &
$ export DISPLAY=:2
$ xclock -geometry 720x480 -bg green #test different colorsOn your host machine grab the frames using the following
command. View output to check that colors are rendered correctly
$ ./ffmpeg -y -f x11grab -i :2.0 -codec:v mpeg2video out.mp4Other pixel formats can be tested by modifying how Xvfb is started in the docker
container :AV_PIX_FMT_RGB565
$ Xvfb :2 -screen 0 720x480x16AV_PIX_FMT_RGB555
$ Xvfb :2 -screen 0 720x480x15AV_PIX_FMT_BGR24 / AV_PIX_FMT_RGB24
This is difficult to test because bpp=24 support was removed in xserver 1.20
https://lists.x.org/archives/xorg-devel/2018-February/056175.html?hmsr=joyk.com&utm_source=joyk.com&utm_medium=referral
However, I was able to run previous version of Xvfb (with some
modifications to force 24bpp) to check that images are rendered correctly.Reviewed-by : Carl Eugen Hoyos <ceffmpeg@gmail.com>
Signed-off-by : Andriy Gelman <andriy.gelman@gmail.com>