[prev in list] [next in list] [prev in thread] [next in thread]
List: gstreamer-devel
Subject: Re: [gst-devel] Mpeg ts mux --missing audio
From: thiagoss <thiagossantos () gmail ! com>
Date: 2009-03-27 12:20:13
Message-ID: de4879e80903270520t41a43364q98026a47f1b5ece4 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Thu, Mar 26, 2009 at 9:40 PM, lyang <oxcsnicho@gmail.com> wrote:
>
> Hi all,
>
> Here is another student intending to apply for Gstreamer in GSoC this year.
> The mpeg2 ts/ps muxer project is my aim, so I've been following the
> interesting discussion here in this topic for quite a while :)
>
> I just want to supplying a bit more information. If we strip off aacparse
> instead of the h264parse, like this:
>
> gst-launch -v --gst-debug-level=2 \
> filesrc location=test.264 \
> ! h264parse ! mux. \
> filesrc location=test.mp2 ! decodebin \
> ! audioconvert ! faac ! mux. \
> mpegtsmux name=mux \
> ! filesink location=test.ts
>
> The product is still having no sound (it's in mplayer; meanwhile VLC
> prefers
> not to show the video instead. This is the same as the product of H.264+AAC
> in my box, an Ubuntu Gutsy.)
> On the other hand if we replace both of H.264 and AAC with something more
> "elementary" like m1v and mp2, mpegtsmux is working perfectly.
>
> I think there must be some mysterious story going on with
> h264+mpegtsmux....
> On the other hand, aacparse looks less susceptible to be the cause of the
> bug.
>
> To Thiago (or someone familiar with qtmux): Does qtmux support h264+aac? I
> just couldn't figure out how to make it (maybe it's totally trivial;
> actually I'm learning hard these days, but not necessarily learning fast:(
> )
> I intended to test if h264+acc is working well in other containers. If yes
> then we can keep our attention in mpegtsmux, I think.
>
Yes, it supports both.
>
>
> Regards,
> Lin
>
>
> yangsb wrote:
> >
> > Hi , Santos,
> > Now I believe bug lies in the plugin " h264parse " , by changing the
> > testing pipeline.
> >
> >
> > At first , my pipeline is like :
> >
> > gst-launch -v --gst-debug-level=$dbg \
> > filesrc location=davincieffect_ntsc.264 \
> > ! h264parse ! mux. \
> > filesrc location=davincieffect.aac ! aacparse ! mux. \
> > mpegtsmux name=mux \
> > ! filesink location=out_264_for_6446.ts
> >
> > Then I changed the testing pipeline :
> >
> > The first one :
> >
> > gst-launch -v --gst-debug-level=$dbg \
> > videotestsrc !
> > video/x-raw-yuv,width=176,height=144,framerate=10/1 ! x264enc \
> > ! mux. \
> > filesrc location=davincieffect.aac ! aacparse ! mux. \
> > mpegtsmux name=mux \
> > ! filesink location=out_264_for_6446.ts
> >
> > The second one :
> >
> > gst-launch -v --gst-debug-level=$dbg \
> > filesrc location=test.mov ! qtdemux name=qtdemux demux.video_00
> !
> > queue \
> > ! mux. \
> > filesrc location=davincieffect.aac ! aacparse ! mux. \
> > mpegtsmux name=mux \
> > ! filesink location=out_264_for_6446.ts
> >
> > Both the pipelines works well .And the ts file can be decoded correctlly
> > by vlc media player.
> > So maybe a bug in h264parse.
> > Hope these to be helpful...
Can't help with that, I have no experience with h264 or mpegts.
Maybe you should try to create a file with video only using two different
pipelines, but from the same source:
1) Decode h264 and reencode with x264enc and then mux it to a mpegts file.
2) Use h264parse and mux it to a mpegts file
After that, inspect the files and look what's different in them. Also, if
h264enc has parameters, you should try to reencode using the same
configuration that h264parse identifies in the stream.
>
> >
> > FYI: you can take a look at this post :
> > http://www.nabble.com/MPEG-2-TS-Muxing-td17485498.html
> >
> >
> > Best regards.
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Mpeg-ts-mux---missing-audio-tp22617660p22734088.html
> Sent from the GStreamer-devel mailing list archive at Nabble.com.
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
>
--
Thiago Sousa Santos
Embedded Systems and Pervasive Computing Lab (Embedded)
Center of Electrical Engineering and Informatics (CEEI)
Federal University of Campina Grande (UFCG)
[Attachment #5 (text/html)]
<br><br><div class="gmail_quote">On Thu, Mar 26, 2009 at 9:40 PM, lyang <span \
dir="ltr"><<a href="mailto:oxcsnicho@gmail.com">oxcsnicho@gmail.com</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;"> <br>
Hi all,<br>
<br>
Here is another student intending to apply for Gstreamer in GSoC this year.<br>
The mpeg2 ts/ps muxer project is my aim, so I've been following the<br>
interesting discussion here in this topic for quite a while :)<br>
<br>
I just want to supplying a bit more information. If we strip off aacparse<br>
instead of the h264parse, like this:<br>
<br>
gst-launch -v --gst-debug-level=2 \<br>
filesrc location=test.264 \<br>
! h264parse ! mux. \<br>
filesrc location=test.mp2 ! decodebin \<br>
! audioconvert ! faac ! mux. \<br>
mpegtsmux name=mux \<br>
! filesink location=test.ts<br>
<br>
The product is still having no sound (it's in mplayer; meanwhile VLC prefers<br>
not to show the video instead. This is the same as the product of H.264+AAC<br>
in my box, an Ubuntu Gutsy.)<br>
On the other hand if we replace both of H.264 and AAC with something more<br>
"elementary" like m1v and mp2, mpegtsmux is working perfectly.<br>
<br>
I think there must be some mysterious story going on with h264+mpegtsmux....<br>
On the other hand, aacparse looks less susceptible to be the cause of the<br>
bug.<br>
<br>
To Thiago (or someone familiar with qtmux): Does qtmux support h264+aac? I<br>
just couldn't figure out how to make it (maybe it's totally trivial;<br>
actually I'm learning hard these days, but not necessarily learning fast:( )<br>
I intended to test if h264+acc is working well in other containers. If yes<br>
then we can keep our attention in mpegtsmux, I think.<br></blockquote><div>Yes, it \
supports both.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex;"> <br>
<br>
Regards,<br>
Lin<br>
<br>
<br>
yangsb wrote:<br>
><br>
> Hi , Santos,<br>
> Now I believe bug lies in the plugin " h264parse " , by changing \
the<br> > testing pipeline.<br>
><br>
><br>
> At first , my pipeline is like :<br>
><br>
> gst-launch -v --gst-debug-level=$dbg \<br>
> filesrc location=davincieffect_ntsc.264 \<br>
> ! h264parse ! mux. \<br>
> filesrc location=davincieffect.aac ! aacparse ! mux. \<br>
> mpegtsmux name=mux \<br>
> ! filesink location=out_264_for_6446.ts<br>
><br>
> Then I changed the testing pipeline :<br>
><br>
> The first one :<br>
><br>
> gst-launch -v --gst-debug-level=$dbg \<br>
> videotestsrc !<br>
> video/x-raw-yuv,width=176,height=144,framerate=10/1 ! x264enc \<br>
> ! mux. \<br>
> filesrc location=davincieffect.aac ! aacparse ! mux. \<br>
> mpegtsmux name=mux \<br>
> ! filesink location=out_264_for_6446.ts<br>
><br>
> The second one :<br>
><br>
> gst-launch -v --gst-debug-level=$dbg \<br>
> filesrc location=test.mov ! qtdemux name=qtdemux demux.video_00 !<br>
> queue \<br>
> ! mux. \<br>
> filesrc location=davincieffect.aac ! aacparse ! mux. \<br>
> mpegtsmux name=mux \<br>
> ! filesink location=out_264_for_6446.ts<br>
><br>
> Both the pipelines works well .And the ts file can be decoded correctlly<br>
> by vlc media player.<br>
> So maybe a bug in h264parse.<br>
> Hope these to be helpful...</blockquote><div><br></div><div>Can't help with \
that, I have no experience with h264 or mpegts.</div><div>Maybe you should try to \
create a file with video only using two different pipelines, but from the same \
source:</div> <div><br></div><div>1) Decode h264 and reencode with x264enc and then \
mux it to a mpegts file.</div><div>2) Use h264parse and mux it to a mpegts \
file</div><div><br></div><div>After that, inspect the files and look what's \
different in them. Also, if h264enc has parameters, you should try to reencode using \
the same configuration that h264parse identifies in the stream.</div> \
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex;"><br> ><br>
> FYI: you can take a look at this post :<br>
> <a href="http://www.nabble.com/MPEG-2-TS-Muxing-td17485498.html" \
target="_blank">http://www.nabble.com/MPEG-2-TS-Muxing-td17485498.html</a><br> \
><br> ><br>
> Best regards.<br>
><br>
><br>
<br>
--<br>
View this message in context: <a \
href="http://www.nabble.com/Mpeg-ts-mux---missing-audio-tp22617660p22734088.html" \
target="_blank">http://www.nabble.com/Mpeg-ts-mux---missing-audio-tp22617660p22734088.html</a><br>
Sent from the GStreamer-devel mailing list archive at Nabble.com.<br>
<br>
<br>
------------------------------------------------------------------------------<br>
_______________________________________________<br>
gstreamer-devel mailing list<br>
<a href="mailto:gstreamer-devel@lists.sourceforge.net">gstreamer-devel@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/gstreamer-devel" \
target="_blank">https://lists.sourceforge.net/lists/listinfo/gstreamer-devel</a><br> \
</blockquote></div><br><br clear="all"><br>-- <br>Thiago Sousa Santos<br><br>Embedded \
Systems and Pervasive Computing Lab (Embedded)<br>Center of Electrical Engineering \
and Informatics (CEEI)<br>Federal University of Campina Grande (UFCG)<br>
------------------------------------------------------------------------------
_______________________________________________
gstreamer-devel mailing list
gstreamer-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic