On Fri, Jan 07, 2005 at 06:37:52PM +0100, Michael Schmitz wrote: > Severity: serious
Can you please comment on why you think these bugs make kino unsuitable for release; specifically, which section of policy is violated? I'm not denying that the bugs you reported are nasty and should be fixed, but unless you convince me otherwise, the severity looks inappropriate to me. > kino appears to have multiple issues with data endianness on powerpc. > > Symptoms: > > Video display: fine when using GDK, reverse video (or rather: magenta on > cyan) when using XV for display in the edit and trim menus. Audio in > edit/trim mode is fine BTW (see audio problems below). This sounds a lot like an old Xv bug that first came up in 2002. Can you please supply me with the output of xvinfo? Which system are you testing this on, and what's your graphics adapter? Is DRI turned on, and does it make a difference if you turn it off? For reference, the original discussion should be available from here: http://www.geocrawler.com/mail/thread.php3?subject=%5Blibdv-dev%5D+Re%3A+Should+dv1394+work+on+PPC%3F&list=3147 > I suspect kino declares BE audio data to be LE in the DV export (or indeed > any) pipe. No idea what's the cause of the XV and mpeg2enc endianness > problems though. The audio problems seem to be caused (at least) by big-endian length fields in an otherwise little-endian WAV file. I'm not too familiar with the various video encodings. I'll have another close look on it over the week-end, but might have to pass on the problem to upstream for a fix. Thanks, Daniel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
