Bug 170771 - media-video/kino-1.0.0 version bump - fix audio corruption w/ avi files larger than 2G
|
Bug#:
170771
|
Product: Gentoo Linux
|
Version: 2006.1
|
Platform: x86
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: calchan@gentoo.org
|
Reported By: artiom@hotbox.ru
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: media-video/kino-1.0.0 version bump - fix audio corruption w/ avi files larger than 2G
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2007-03-13 18:44 0000
|
I have a DV .avi file captured by Kino which size is 8G. When I go to the edit
tab the sound is corrupted (digital noise instead of sound) on the scenes
different from the first.
Reproducible: Always
Steps to Reproduce:
1.Open a DV .avi type 2 size > 2G
2.Export a movie
3.Look in a player
Actual Results:
Noise at the second part of the file (after 2G)
Expected Results:
Normal sound
This bug was fixed just after 0.9.5 release.
https://sourceforge.net/tracker/?func=detail&atid=114103&aid=1657388&group_id=14103
And now there is 1.0 release.
(In reply to comment #0)
> This bug was fixed just after 0.9.5 release.
Great news. However, the fix comes in the form of a local ffmpeg which creates
a kino-specific and statically-linked transcode. So I'll need to think of how
we can manage this, portage-wise.
Denis.
(In reply to comment #1)
> (In reply to comment #0)
> > This bug was fixed just after 0.9.5 release.
>
> Great news. However, the fix comes in the form of a local ffmpeg which creates
> a kino-specific and statically-linked transcode. So I'll need to think of how
> we can manage this, portage-wise.
AS in there is a "second" transcode that now needs to be placed somewhere in
the
filesystem that's not the "normal" transcode?
Is there a patch in that local ffmpeg that could perhaps be applied to the
gentoo ffmpeg ebuild?
Thanks to both of you for your input. I have just committed kino-1.0.0, so you
should be able to get the ebuild from your preferred mirror in a few hours.
The DV .avi bugfix will come in a new snapshot of ffmpeg, which is already in
Portage but masked (ffmpeg-0.4.9_p20070325). You can go ahead and unmask it on
your machine, it should work (but may break something else and comes with no
warranty as usual...).
Denis.