Windows FFmpeg stability and performance

[GoogleCodeExporter]

Having serious problems with FFmpeg under Win32.  Had to hack the h264.c
codec in strange ways to get that codec to initialize versus causing a
segmentation violation.  Audio is choppy, could be VMware.  The program
will randomly crash...  much more work needs to be done on the Windows port.

Original issue reported on code.google.com by dashhacker242 on 15 May 2009 at 3:26

[GoogleCodeExporter]

Original comment by dashhacker242 on 15 May 2009 at 3:27

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Issue 4 has been merged into this issue.

Original comment by dashhacker242 on 16 May 2009 at 3:44

[GoogleCodeExporter]

Added proper packet padding for FFmpeg decoding.  This seems to have completely 
fixed
the seemingly random read access violation crashes under Windows.  I'll leave 
this
issue open until after v1.2 releases and we can confirm that it's fixed.

Original comment by dashhacker242 on 19 May 2009 at 10:08

[GoogleCodeExporter]

Just so you know, setting the issue as "fixed" means that it's fixed but not 
fully 
tested, "verified" means fixed and fully tested to be working. So you should 
still 
set this as fixed. Unless you have other plans...

Original comment by muzeraka...@gmail.com on 20 May 2009 at 5:14

[GoogleCodeExporter]

You're absolutely right! I was going to mark this as fixed but it's a "closed
status", which means it won't be visible on the Issues page unless the user 
changes
the Search to show All Issues.  I wanted this one to remain visible by default 
to
avoid duplicate reports.  Now, the longer I think about it...  I'll change it to
fixed, because it is ;)

Original comment by dashhacker242 on 20 May 2009 at 5:23

• Changed state: Fixed