<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 40: Endianess problem in audio encoding </title><link>https://sourceforge.net/p/libdv/bugs/40/</link><description>Recent changes to 40: Endianess problem in audio encoding </description><atom:link href="https://sourceforge.net/p/libdv/bugs/40/feed.rss" rel="self"/><language>en</language><lastBuildDate>Thu, 07 Oct 2004 20:59:48 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/libdv/bugs/40/feed.rss" rel="self" type="application/rss+xml"/><item><title>Endianess problem in audio encoding </title><link>https://sourceforge.net/p/libdv/bugs/40/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I found a nasty bug related to audio encoding, when used &lt;br /&gt;
on big-endian (PowerPC) machine. &lt;/p&gt;
&lt;p&gt;dv_decode_full_audio() function fill audio buffer in cpu &lt;br /&gt;
native byte order, however dv_encode_full_audio() &lt;br /&gt;
requires audio buffer to be in little-endian byte-order. &lt;/p&gt;
&lt;p&gt;This is the real problem, because such construction as: &lt;br /&gt;
dv_decode_full_audio() &lt;br /&gt;
do something with audio &lt;br /&gt;
dv_encode_full_audio() &lt;br /&gt;
is often used in tools for processing DV files (like Kino for &lt;br /&gt;
example). In my opinion both functions should work on &lt;br /&gt;
buffers in same byte-order. &lt;/p&gt;
&lt;p&gt;Regards, Marek Szyprowski &amp;lt;march@staszic.waw.pl&amp;gt; &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Marek Szyprowski</dc:creator><pubDate>Thu, 07 Oct 2004 20:59:48 -0000</pubDate><guid>https://sourceforge.net668f30d65d7b635e9e4cfc3e3afd3f771ed194ab</guid></item></channel></rss>