
Recherche avancée
Médias (1)
-
Carte de Schillerkiez
13 mai 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Texte
Autres articles (70)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
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 ;
-
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)
Sur d’autres sites (8660)
-
Which lib is better Transcoder for live camera ? ffmpeg vs intel media sdk
4 janvier 2017, par ParkAtStreetI would like to do a performance comparison between Ffmpeg and Intel Media SDK in transcoding.
I have to write a new application that will do the following.
-
Receive frames from MJPEG, MPEG4 and H264 cameras.
-
Transcode the frames. Output will be h264. Here I have to either use Ffmpeg or Intel Media SDK.
-
Multicast transcoded frames as RTSP streaming.
I have noticed that both these libs are CPU intensive. Is there any settings in Ffmpeg can reduce the CPU usage ?
Thanks in advance,
-
-
Media type not supported after FFMpeg compression
9 décembre 2017, par amit srivastavaI am compressing a video(mp4) in android using FFMpeg it is getting compressed successfully, but when I am trying to open compressed file in mobile device it says "Media type not supported", though I can play that media in my computer’s VLC player.
My purpose is to compress and post it to server as Multipart but it is also failing because server can’t read media Metadata.
I am using EpMedia android library to rum FFMpeg command which is :
String[] command = {"-y", "-i", sourceFile.getAbsolutePath(), "-s", "160x120", "-r", "25", "-vcodec", "mp4", "-b:v", "150k", "-b:a", "48000", "-ac", "2", "-ar", "22050", destFile.getAbsolutePath()};
EpEditor epEditor = new EpEditor(context);
epEditor.execCmd(cmd, 0, new OnEditorListener(){
@Override
public void onSuccess(){
Log.d("Compress", "Success");}
@Override
public void onFailure(){
Log.d("Compress", "Failed");
}
@Override
public void onProgress(float progress){
Log.d("Compress", "Running");
}
});I have also tried using SiliCompressor android library but same thing happened Media type not supported resulting issue in uploading to server.
What can be done in this scenario, even if I upload the media to server what if I want to play that media on mobile device.
-
avformat/rtsp : correctly set media control uri with mpegts
11 octobre 2020, par tpolavformat/rtsp : correctly set media control uri with mpegts
Fixes #1941
Currently the media control uri is not correctly assigned when mpegts is
signalled in the media description.The code checks whether at least one AVStream has been setup before
assigning to the media's uri. With mpegts the AVStreams are setup when
parsing packets and so the media's uri is skipped. This is fixed by
using rt->nb_rtsp_streams in the check which counts all medias in the
sdp.Reviewed-by : Andriy Gelman <andriy.gelman@gmail.com>
Signed-off-by : Andriy Gelman <andriy.gelman@gmail.com>