Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 170771
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Denis Dupeyron <calchan@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Artiom Molchanov <artiom@hotbox.ru>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 170771 depends on: Show dependency tree
Bug 170771 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   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.

------- Comment #1 From Denis Dupeyron 2007-03-13 20:36:39 0000 -------
(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.

------- Comment #2 From hvjunk@gmail.com 2007-03-17 07:11:59 0000 -------
(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?

------- Comment #3 From Denis Dupeyron 2007-03-28 17:11:36 0000 -------
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.

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug