
Recherche avancée
Autres articles (35)
-
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) (...)
-
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 (...)
-
Création définitive du canal
12 mars 2010, parLorsque votre demande est validée, vous pouvez alors procéder à la création proprement dite du canal. Chaque canal est un site à part entière placé sous votre responsabilité. Les administrateurs de la plateforme n’y ont aucun accès.
A la validation, vous recevez un email vous invitant donc à créer votre canal.
Pour ce faire il vous suffit de vous rendre à son adresse, dans notre exemple "http://votre_sous_domaine.mediaspip.net".
A ce moment là un mot de passe vous est demandé, il vous suffit d’y (...)
Sur d’autres sites (7233)
-
Should libavcodec handle non-packed/non-byte-aligned mp3 packets ?
27 août 2015, par Rhythmic FistmanI’m transcoding shoutcast streams using
libavcodec
and I noticed that during the day I get a few 10s’ of packets that it cannot decode without some help :-
Leading zero bytes before a packet sync word, e.g.
0x0000fffa
-
non-byte aligned syncword, e.g
0x82a0fffa
In the first case I have to toss out the zero bytes and in the second I have to shift the data up by an odd number of nibbles.
I don’t have a watertight knowledge of the mp3 spec (is there one ?), but my impression was that the packet format was a bit oriented, not byte, so both types of packets look right to me.
So who is in the wrong here ?
Is it
libavcodec
for not parsing valid packets ?Or the stream encoder for producing non-standard packets ?
-
-
avformat/framecrcenc : List types and checksums for for side data
17 mai, par Michael Niedermayeravformat/framecrcenc : List types and checksums for for side data
This allows detecting changes and regressions in side data related code, same as what
framecrc does for before already for packet data itself.Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
- [DH] libavformat/framecrcenc.c
- [DH] tests/ref/fate/autorotate
- [DH] tests/ref/fate/cover-art-mp3-id3v2-remux
- [DH] tests/ref/fate/ffmpeg-bsf-input
- [DH] tests/ref/fate/ffmpeg-spec-disposition
- [DH] tests/ref/fate/force_key_frames-source
- [DH] tests/ref/fate/force_key_frames-source-drop
- [DH] tests/ref/fate/force_key_frames-source-dup
- [DH] tests/ref/fate/gapless-mp3
- [DH] tests/ref/fate/h264_redundant_pps-side_data
- [DH] tests/ref/fate/id3v2-priv-remux
- [DH] tests/ref/fate/matroska-hdr10-plus-remux
- [DH] tests/ref/fate/matroska-ogg-opus-remux
- [DH] tests/ref/fate/matroska-opus-remux
- [DH] tests/ref/fate/matroska-vp8-alpha-remux
- [DH] tests/ref/fate/mov-cover-image
- [DH] tests/ref/fate/segment-mp4-to-ts
- [DH] tests/ref/fate/shortest
- [DH] tests/ref/fate/webm-hdr10-plus-remux
- [DH] tests/ref/fate/webm-webvtt-remux
-
Convert RTP (OPUS) stream to HLS (AAC) stream using ffmpeg or gstreamer
27 décembre 2020, par Gagan BhatI currently have an RTP protocol stream in OPUS codec playing locally on rtp ://127.0.0.1:5006


I would like to convert this stream into an HLS protocol with AAC codec (or others if easier) so that it is more accessible to devices with just a browser.


I know that ffmpeg and gstreamer are capable of this but I'm just lost among the various arguments/parameters.


Currently, I have an SDP file that describes my stream (unsure if this is correct, I wrote it after just googling/reading the spec)


v=0
t=0 0
m=audio 5006 RTP/AVP 98
c=IN IP4 127.0.0.1
a=recvonly
a=rtpmap:98 opus/48000/2
a=fmtp:98 stereo=0; sprop-stereo=0; useinbandfec=1c



Any ideas ?