Recherche avancée
Médias (1)
-
Video d’abeille en portrait
14 mai 2011, par
Mis à jour : Février 2012
Langue : français
Type : Video
Autres articles (83)
-
Amélioration de la version de base
13 septembre 2013Jolie sélection multiple
Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...) -
Participer à sa traduction
10 avril 2011Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
Actuellement MediaSPIP n’est disponible qu’en français et (...) -
Menus personnalisés
14 novembre 2010, parMediaSPIP utilise le plugin Menus pour gérer plusieurs menus configurables pour la navigation.
Cela permet de laisser aux administrateurs de canaux la possibilité de configurer finement ces menus.
Menus créés à l’initialisation du site
Par défaut trois menus sont créés automatiquement à l’initialisation du site : Le menu principal ; Identifiant : barrenav ; Ce menu s’insère en général en haut de la page après le bloc d’entête, son identifiant le rend compatible avec les squelettes basés sur Zpip ; (...)
Sur d’autres sites (8870)
-
Can't obtain information with ffmpeg from Smooth Streaming Manifest file
11 juillet 2020, par albertoiNETI'm trying to get details for a stream of protocol Microsoft Smooth Streaming, with ffmpeg tools (ffprobe and ffplay) but when I run the next command :



ffprobe -i http://b31282.cdn.telefonica.com/31282/Manifest



I obtain this :



http://b31282.cdn.telefonica.com/31282/Manifest: Invalid data found when processing input



I assume that this Manifest file is correct and complies with standards of Smooth Streaming . This is a brief extract of Manifest file :



<smoothstreamingmedia majorversion="2" minorversion="0" duration="0" timescale="10000000" islive="TRUE" lookaheadfragmentcount="2" dvrwindowlength="6000000000" canseek="TRUE" canpause="TRUE">
 <protection>
 <protectionheader systemid="9a04f079-9840-4286-ab92-e65be0885f95">oioAAAIAAQCUAjwAV...</protectionheader>
 </protection>
 <streamindex type="audio" language="esp" subtype="" chunks="0" timescale="10000000" url="QualityLevels({bitrate})/Fragments(audio_esp={start time})"></streamindex>
 <streamindex type="video" language="" subtype="" chunks="0" timescale="10000000" url="QualityLevels({bitrate})/Fragments(video={start time})"></streamindex>
</smoothstreamingmedia>



Is a Fedora 21 and ffmpeg version and configuration is :



ffmpeg version git-2015-02-27-d490b26
configuration: --enable-gpl --enable-nonfree --enable-libfdk_aac --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264
libavutil 54. 19.100 
libavcodec 56. 26.100 
libavformat 56. 23.105 
libavdevice 56. 4.100 
libavfilter 5. 11.102 
libswscale 3. 1.101 
libswresample 1. 1.100 
libpostproc 53. 3.100 



PD : I prefer use only ffmpeg tool



PD2 : Same thing with a Microsoft Smooth Streaming Manifest file :



ffmpeg -i http://mediadl.microsoft.com/mediadl/iisnet/smoothmedia/Experience/BigBuckBunny_720p.ism/Manifest
Invalid data found when processing input



Thanks for all


-
Can't obtain information with ffmpeg from Smooth Streaming Manifest file
5 mars 2015, par AlbertoI’m trying to get details for a stream of protocol Microsoft Smooth Streaming, with ffmpeg tools (ffprobe and ffplay) but when I run the next command :
ffprobe -i http://b31282.cdn.telefonica.com/31282/ManifestI obtain this :
http://b31282.cdn.telefonica.com/31282/Manifest: Invalid data found when processing inputI assume that this Manifest file is correct and complies with standards of Smooth Streaming . This is a brief extract of Manifest file :
<smoothstreamingmedia majorversion="2" minorversion="0" duration="0" timescale="10000000" islive="TRUE" lookaheadfragmentcount="2" dvrwindowlength="6000000000" canseek="TRUE" canpause="TRUE">
<protection>
<protectionheader systemid="9a04f079-9840-4286-ab92-e65be0885f95">oioAAAIAAQCUAjwAV...</protectionheader>
</protection>
<streamindex type="audio" language="esp" subtype="" chunks="0" timescale="10000000" url="QualityLevels({bitrate})/Fragments(audio_esp={start time})"></streamindex>
<streamindex type="video" language="" subtype="" chunks="0" timescale="10000000" url="QualityLevels({bitrate})/Fragments(video={start time})"></streamindex>
</smoothstreamingmedia>Is a Fedora 21 and ffmpeg version and configuration is :
ffmpeg version git-2015-02-27-d490b26
configuration: --enable-gpl --enable-nonfree --enable-libfdk_aac --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264
libavutil 54. 19.100
libavcodec 56. 26.100
libavformat 56. 23.105
libavdevice 56. 4.100
libavfilter 5. 11.102
libswscale 3. 1.101
libswresample 1. 1.100
libpostproc 53. 3.100PD : I prefer use only ffmpeg tool
PD2 : Same thing with a Microsoft Smooth Streaming Manifest file :
ffmpeg -i http://mediadl.microsoft.com/mediadl/iisnet/smoothmedia/Experience/BigBuckBunny_720p.ism/Manifest
Invalid data found when processing inputThanks for all
-
DTS and PTS are different, despite not having B-frames (ffmpeg)
7 août 2018, par DamianJust a quick question in regards to video encoding/muxing a video file with ffmpeg. Basically, I have my muxer functioning and I’m trying to have my packets output the correct PTS/DTS.
This is a portion of my code that encodes my AVFrame, muxing it to an output file :
int ret;
int got_packet = 0;
AVPacket pkt = { 0 };
av_init_packet(&pkt);
pkt.data = NULL;
pkt.size = 0;
/* encode the image */
ret = avcodec_encode_video2(cc, &pkt, frame, &got_packet);
if (ret < 0)
{
fprintf(stderr, "error encoding video frame: %s\n", av_err2str(ret));
exit(EXIT_FAILURE);
}
if (got_packet)
{
av_packet_rescale_ts(&pkt, cc->time_base, st->time_base);
fprintf(stderr, "\npkt.pts = %ld\n", pkt.pts);
fprintf(stderr, "pkt.dts = %ld\n", pkt.dts);
fprintf(stderr, "writing frame\n");
ret = av_interleaved_write_frame(fmt_ctx, &pkt);
av_packet_unref(&pkt);
}
else
{
ret = 0;
}
...I’m then getting an output of the following :
pkt.pts = 0
pkt.dts = 0
writing frame
pkt.pts = 1502
pkt.dts = 0
writing frame
pkt.pts = 3003
pkt.dts = 1502
writing frame
pkt.pts = 4505
pkt.dts = 3003
writing frame
...My goal is to have my PST and DST both with the pattern : 1502, 3003, 4505, 6006, 7508, ...
But it seems that the first DTS value is repeating once, and thus being off-sync with it’s corresponding PTS value. It’s also worth mentioning that the codec context was configured to have no b-frames, so only i- and p- frames are present here.
Does anyone with more experience have some insight on this ?
Addition :
I ran the following command in terminal to check if my DTS and PTS values were consistent to my print statements :
sudo ./ffprobe -show_packets -print_format json mux_test.ts | lessAnd I got the following :
{
"packets": [
{
"codec_type": "video",
"stream_index": 0,
"pts": 0,
"pts_time": "0.000000",
"dts": -1501,
"dts_time": "-0.016678",
"duration": 1501,
"duration_time": "0.016678",
"convergence_duration": "N/A",
"convergence_duration_time": "N/A",
"size": "55409",
"pos": "564",
"flags": "K"
},
{
"codec_type": "video",
"stream_index": 0,
"pts": 1502,
"pts_time": "0.016689",
"dts": 0,
"dts_time": "0.000000",
"duration": 1501,
"duration_time": "0.016678",
"convergence_duration": "N/A",
"convergence_duration_time": "N/A",
"size": "46574",
"pos": "60160",
"flags": "_"
},
{
"codec_type": "video",
"stream_index": 0,
"pts": 3003,
"pts_time": "0.033367",
"dts": 1502,
"dts_time": "0.016689",
"duration": 1501,
"duration_time": "0.016678",
"convergence_duration": "N/A",
"convergence_duration_time": "N/A",
"size": "2544",
"pos": "110356",
"flags": "_"
},
...Which doesn’t show my first DTS value repeated, but continues to show my DTS one cycle behind my PTS.
Syndiquer tout le site
