Attempt to render a mpg 2 file creates a zero length file

[GoogleCodeExporter]

What steps will reproduce the problem?

Created a new project profile CVD NTSC

Added a 18MB mpg file with the same resolution 352x480

Added file to time line

Rendered output with the default project profile

Application says it is rendering file movie.mpg. Shows rendering time and 
updating progress bar.

End results is a file of zero length

Also tried this with DV/DVD NTSC profile with same results

Using fresh install of Linux Mint 13

Video file originally came from a cannon camcorder 

Here is a dump from the command line when the file is being rendered.

[mpeg @ 0x7f8a9802ce00] max_analyze_duration reached
[mpeg @ 0x7f8a9802f6e0] max_analyze_duration reached
[mpeg @ 0x7f8a98032620] max_analyze_duration reached
[mpeg @ 0x7f8a803947c0] max_analyze_duration reached
[mpeg @ 0x7f8a80396d20] max_analyze_duration reached
[mpeg @ 0x7f8a80398680] max_analyze_duration reached
[mpeg2video @ 0x7f8a803977e0] warning: first frame is no keyframe

[mpeg @ 0x3f33420] max_analyze_duration reached
[mpeg @ 0x3e98660] max_analyze_duration reached
[mpeg @ 0x3f43000] max_analyze_duration reached
[mpeg @ 0x7f8a900b0960] max_analyze_duration reached
[mpeg @ 0x7f8a90035d40] max_analyze_duration reached
[mpeg @ 0x7f8a9006a4c0] max_analyze_duration reached
[mp2 @ 0x7f8a68325080] bitrate 3000 is not allowed in mp2
consumer_avformat.c: Unable to encode audio - disabling audio output.
[mpeg @ 0x7f8a68001980] VBV buffer size not set, muxing may fail

[mpeg @ 0x7f8a90056440] max_analyze_duration reached
[mpeg @ 0x7f8a9005ff60] max_analyze_duration reached
[mp2 @ 0x7f8a90041b80] Header missing
[producer avformat] /home/brent/fl_1/test.mpg
    audio decoding error -1094995529

Thanks

Brent

Original issue reported on code.google.com by brent.si...@gmail.com on 6 Jul 2012 at 5:52

[GoogleCodeExporter]

Looks like the problem is the file does not get closed when the render 
finishes. As soon as you exit the program it changes from 0 to the file size.

Original comment by brent.si...@gmail.com on 9 Jul 2012 at 9:20

[GoogleCodeExporter]

Yes I've seen this happen too. The problem is that I have not been able to 
reliably reproduce it.

If anyone else sees this, please provide a similar command line dump like 
brent.sima did.

Original comment by janne.li...@gmail.com on 16 Aug 2012 at 7:28

• Changed state: Accepted

[GoogleCodeExporter]

Did a little more experimenting. When you specify a marked range then the save 
works. When you specify program length as the render range then the file is not 
closed correctly. I added some debug statements to the code and had it print 
out the value of start_frame and end_frame in the _do_rendering function. When 
you do the full program length you get a value of 0 for the start_frame and a 
value of -1 for the end_frame. When you do the marked range you get two 
positive values. In my experiment the values were 0 for the start_frame and 778 
for the end_frame. Could the problem be due to the file being a streamed MPEG ?

Hope this helps.

Original comment by brent.si...@gmail.com on 20 Aug 2012 at 10:01

[GoogleCodeExporter]

When you do the following command after flowblade has finished the rendering

lsof | grep -i movie
flowblade 29116      brent   12w      REG                8,3        0  2098587 
/home/brent/movie.mpg

It will show that flowblade still has the file opened even though the rendering 
is complete. Also if do a second rendering to the same file it opens the file a 
second time and this time it closes it and the file contains the encoded video. 
Two points to note during the second rendering lsof show the file as being 
opened twice by Flowblade and after the rendering is complete the original 
first opened file handle is still active and the second handle is gone. 

Original comment by brent.si...@gmail.com on 20 Aug 2012 at 10:48

[GoogleCodeExporter]

Marking this invalid.

Rendering code has been updated many times since this report and I'm not sure 
this still happens. At least on dev system this has stopped happening.

Original comment by janne.li...@gmail.com on 2 Dec 2013 at 6:15

• Changed state: Invalid

[GoogleCodeExporter]

Hello, I can reproduce kind of similar issue with 0.16. The rendered file grows 
_very_ slowly and if I let the rendering finish without interrupting, it 
contains only half a second. But if I cancel the rendering, then it starts to 
fill up the file.

I got the same when trying to export to 1080p and PAL DVD, so I think it is not 
directly related to the destination format.

Original comment by twuimo...@gmail.com on 6 Dec 2014 at 7:04