avimux issue - gst_avi_mux_write_avix_index:<avimux0> No more room in superindex of stream 00db

[madstrum]

Hi,

I am using GStreamer to do raw recording on imx6 using the following pipeline.

gst-launch -e tvsrc fps-n=25 ! queue2 max-size-buffers=1 max-size-bytes=0 max-size-time=0 ! 'video/x-raw-yuv, width=(int)720, height=(int)576, framerate=(fraction)25/1' ! avimux ! queue2 max-size-buffers=1 max-size-bytes=0 max-size-time=0 ! filesink location=output.avi --gst-debug-level=3

It runs fine for some time recording the avi until around the 35min mark gst debug gives me this.

avimux gstavimux.c:c:1540:gst_avi_mux_write_avix_index:<avimux0> No more room in superindex of stream 00db

The video then stops recording effectively even though gstreamer continues.

When I look at the video the frame count ends at the 35min mark.

How can I resolve this? Is this a bug in avimux?

[igorpadykov]

Hi mad

seems board has insufficient memory, in general it may be recommended

to try latest BSP which has gstreamer 1.4 supported

L3.14.28_1.0.0_iMX6QDLS_BUNDLE

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

[madstrum]

I just like to add : When I use vpuenc to encode it to H.264 before sending it to avimux, it runs ok.

ie. vpuenc codec=6 bitrate=1000000 ! avimux

[igorpadykov]

you are right:

https://community.freescale.com/thread/323018

[madstrum]

Hi,

So there isn't any resolution for this?

Does the drop cache method (from your link) really work?

My RAW recording with tvsrc always drops out around 35min - I can't be the only one who's experiencing this.

[igorpadykov]

please try with latest BSP

L3.14.28_1.0.0_iMX6QDLS_BUNDLE : i.MX 6Quad, i.MX 6Dual, i.MX 6DualLite, i.MX 6Solo Linux

[madstrum]

Hi igor,

The board has 1GB of memory, is this not enough?

Is there a memory leak in this particular plugin?