<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 04/14/2015 11:42 AM, KPAXIT wrote:<br>
</div>
<blockquote
cite="mid:CAKANpvR7dFaY60bQ0ZfxfUxttOkAvaaizPuFCTnWUBdOcuWjNQ@mail.gmail.com"
type="cite">
<div dir="ltr">Hello Thiago Santos-3,
<div><br>
I just tested last git master (1.5.0.1) and it is working!
Thank you so much. <br>
I almost cracked my head over this issue while doing numerous
of test for last two weeks... thanks.<br>
<br>
Can I ask you follow up question!? <br>
<br>
My streaming application (written in python) will be put in
production on short term. I understood that Gstreamer advises
to use stable releases for production. At the moment of
writing 1.4.5 is the last stable release but with broken
mp4/qtmux in it(at least for my usecase).<br>
<br>
</div>
<div>What is usual in such cases like mine? <br>
Just use last git master version in production and hope for
the best? or<br>
Try to use last stable and manually apply needed patches (like
qtmux in my case)? or</div>
<div>Just wait until git master becomes stable?<br>
</div>
</div>
</blockquote>
In all cases you should re-test your application scenarios to make
sure they work for you.<br>
It is a trade-off, while git master will give you more bugfixes,
improvements and features, it has a higher risk of regressions.
Using patched 1.4.5. will give you something you already have
working + fixes for issues you identified and patched. The later
also implies more work for backporting while master is easier to
upgrade and interact with the community for fixes.<br>
<br>
There is no right answer here. Assuming you have a well tested
application both can work for you.<br>
<br>
Regards,<br>
<blockquote
cite="mid:CAKANpvR7dFaY60bQ0ZfxfUxttOkAvaaizPuFCTnWUBdOcuWjNQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
Thanks in advance.<br>
Best regards,<br>
<br>
Roman S./KPAXIT</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 14 April 2015 at 05:16, Thiago
Santos-3 [via GStreamer-devel] <span dir="ltr"><<a
moz-do-not-send="true"
href="/user/SendEmail.jtp?type=node&node=4671559&i=0"
target="_top" rel="nofollow" link="external">[hidden
email]</a>></span> wrote:<br>
<blockquote style="border-left:2px solid #CCCCCC;padding:0
1em" class="gmail_quote"> On 04/13/2015 12:54 PM, KPAXIT
wrote:
<div>
<div class="shrinkable-quote"><br>
> Hi list,
<br>
>
<br>
> I'm using following pipeline to record in file:
<br>
>
<br>
> gst-launch-1.0 -e --gst-debug=**:4 videotestsrc
is-live=true \
<br>
> ! queue ! videoconvert \
<br>
> ! videorate silent=false \
<br>
> ! videoscale \
<br>
> ! "video/x-raw, width=1280, height=720,
framerate=25/1" \
<br>
> ! queue ! x264enc speed-preset=3 tune=zerolatency
bitrate=3800 key-int-max=0
<br>
> \
<br>
> ! queue ! muxer.video_0 \
<br>
> audiotestsrc is-live=true \
<br>
> ! audioconvert ! audioresample ! audiorate !
"audio/x-raw, rate=48000,
<br>
> channels=2" \
<br>
> ! queue ! faac bitrate=128000 rate-control=2 \
<br>
> ! queue ! muxer.audio_0 \
<br>
> mp4mux name=muxer streamable=true \
<br>
> ! queue ! filesink
location="/home/myenc/mystream.mp4" sync=false
<br>
>
<br>
> *Q/Problem:*
<br>
> It seems that there are no problems with given
pipeline if we run it for
<br>
> short session e.a. ~1-2 hour(s) or so.
<br>
> But when we run it a bit longer (4-10h), recording
file get broken somewhere
<br>
> around ~4GB in file (equals to physical RAM!?)
<br>
> For example: if we capture 360p 1Mbit then file is
playable until 4 hours
<br>
> and if we capture in 720p 4Mbit then file is
playable until 1 hour in file.
<br>
>
<br>
> Did anyone experienced same issue or maybe somebody
can reproduce it?
<br>
> Is this a normal behavior of qt/mp4mux like
'ensonic' mentioned here for
<br>
> example?
<br>
> Is there a workaround for it?
<br>
>
<br>
> After a lot of testing I made a hypothesis that it
has something to do with
<br>
> physical memory and how mp4mux works.
<br>
> However putting and/or removing extra RAM from
machine did not had any
<br>
> affect on broken files(still only playable until
4GB)
<br>
>
<br>
> Any suggestion, example, point to right direction
would be very much
<br>
> appreciated.
<br>
>
<br>
>
<br>
> *Please note:*
<br>
> * the only playable recording file after 4GB I was
able to generate, is when
<br>
> we DO NOT use any muxer at all (aka
byte-stream=true filename.h264)
<br>
> * or we use mpegtsmux, which doesn't make use of
index tables in memory (?)
<br>
> * Because theora+vorbis+oggmux produced same broken
result as h264+mp4 did,
<br>
> it sounds like a general muxer issue and not only
mp4mux/qtmux, but that is
<br>
> only a guess.
<br>
>
<br>
>
<br>
> OS: Ubuntu 14.04
<br>
> Gstreamer: 1.4.5 (also tested with 1.3.90)
<br>
> Proc: i5-3570 @ 3.4Ghz
<br>
> Ram: 4GB (also tested with 2GB, 8GB)
</div>
Could you try with git master? There were some fixes
regarding 32/64 bit </div>
variables in some places in qtmux/mp4mux. I just recorded a
3h / 5.2gb <br>
file and it seems to play fine here.
<br>
<br>
I think this bug was already fixed.
<br>
<div>
<div class="shrinkable-quote"><br>
>
<br>
>
<br>
>
<br>
> --
<br>
> View this message in context: <a
moz-do-not-send="true"
href="http://gstreamer-devel.966125.n4.nabble.com/Record-to-file-h264-aac-in-mp4-produce-only-partially-playable-file-tp4671554.html"
rel="nofollow" link="external" target="_blank">http://gstreamer-devel.966125.n4.nabble.com/Record-to-file-h264-aac-in-mp4-produce-only-partially-playable-file-tp4671554.html</a><br>
> Sent from the GStreamer-devel mailing list archive
at Nabble.com.
<br>
> _______________________________________________
<br>
> gstreamer-devel mailing list
<br>
> <a moz-do-not-send="true"
href="http:///user/SendEmail.jtp?type=node&node=4671558&i=0"
rel="nofollow" link="external" target="_blank">[hidden
email]</a>
<br>
> <a moz-do-not-send="true"
href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel"
rel="nofollow" link="external" target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a></div>
</div>
<br>
-- <br>
Thiago Sousa Santos
<br>
Senior Multimedia Engineer, Open Source Group
<br>
Samsung Research America - Silicon Valley
<br>
<br>
_______________________________________________
<br>
gstreamer-devel mailing list
<br>
<a moz-do-not-send="true"
href="http:///user/SendEmail.jtp?type=node&node=4671558&i=1"
rel="nofollow" link="external" target="_blank">[hidden
email]</a>
<br>
<a moz-do-not-send="true"
href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel"
rel="nofollow" link="external" target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><br>
<br>
<br>
<hr noshade="noshade" size="1" color="#cccccc">
<div style="color:#444;font:12px
tahoma,geneva,helvetica,arial,sans-serif">
<div style="font-weight:bold">If you reply to this email,
your message will be added to the discussion below:</div>
<a moz-do-not-send="true"
href="http://gstreamer-devel.966125.n4.nabble.com/Record-to-file-h264-aac-in-mp4-produce-only-partially-playable-file-tp4671554p4671558.html"
target="_blank" rel="nofollow" link="external">http://gstreamer-devel.966125.n4.nabble.com/Record-to-file-h264-aac-in-mp4-produce-only-partially-playable-file-tp4671554p4671558.html</a>
</div>
<div style="color:#666;font:11px
tahoma,geneva,helvetica,arial,sans-serif;margin-top:.4em;line-height:1.5em">
To unsubscribe from Record to file h264 + aac in mp4
produce only partially playable file., <a
moz-do-not-send="true" href="" target="_blank"
rel="nofollow" link="external">click here</a>.<br>
<a moz-do-not-send="true"
href="http://gstreamer-devel.966125.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml"
rel="nofollow" style="font:9px serif" target="_blank"
link="external">NAML</a> </div>
</blockquote>
</div>
<br>
</div>
<br>
<hr align="left" width="300">
View this message in context: <a moz-do-not-send="true"
href="http://gstreamer-devel.966125.n4.nabble.com/Record-to-file-h264-aac-in-mp4-produce-only-partially-playable-file-tp4671554p4671559.html">Re:
Record to file h264 + aac in mp4 produce only partially playable
file.</a><br>
Sent from the <a moz-do-not-send="true"
href="http://gstreamer-devel.966125.n4.nabble.com/">GStreamer-devel
mailing list archive</a> at Nabble.com.<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gstreamer-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Thiago Sousa Santos
Senior Multimedia Engineer, Open Source Group
Samsung Research America - Silicon Valley</pre>
</body>
</html>