On Tue, Mar 14, 2006 at 12:21:40AM +0100, fons adriaensen wrote:
On Mon, Mar 13, 2006 at 11:59:15PM +0100, stefan kersten wrote:
as paul stated, network byte order is defined to be
big-endian, so yes, you have to convert 32 bit floats (and
doubles, for that matter) on intel, because they
On Mon, Mar 13, 2006 at 11:59:15PM +0100, stefan kersten wrote:
On Mon, Mar 13, 2006 at 11:40:04PM +0100, fons adriaensen wrote:
On Mon, Mar 13, 2006 at 05:25:04PM -0500, Paul Davis wrote:
On Mon, 2006-03-13 at 23:10 +0100, fons adriaensen wrote:
Is it true on the common platforms that
On Tue, 2006-03-14 at 19:56 +0100, [EMAIL PROTECTED] wrote:
so you say that i should not htonl the floats i copy from my net
buffer
to the jack-port ?
i doubt, this is a great performance impact.
These were just suggestions... of course the performance impact is
small. But when a code path
On Tue, Mar 14, 2006 at 02:13:59PM -0500, Lee Revell wrote:
On Tue, 2006-03-14 at 19:56 +0100, [EMAIL PROTECTED] wrote:
so you say that i should not htonl the floats i copy from my net
buffer
to the jack-port ?
i doubt, this is a great performance impact.
These were just
On Tue, Mar 14, 2006 at 07:56:47PM +0100, [EMAIL PROTECTED] wrote:
course it would be perfectly valid for netjack
to use little endian `on the wire'; but this would be like
putting my powerbook in little endian mode when playing a
wav file. sort of.
so you say that i should not htonl
On Sun, Mar 12, 2006 at 03:50:26PM -0500, Lee Revell wrote:
On Sun, 2006-03-12 at 14:06 +0100, [EMAIL PROTECTED] wrote:
netjack-0.9rc1 is here...
endianess issues fixed. tests are underway...
but if it works for 2 x86 (double swap) it should work for PPC -
x86
Why do you use
On Mon, 2006-03-13 at 22:21 +0100, [EMAIL PROTECTED] wrote:
On Sun, Mar 12, 2006 at 03:50:26PM -0500, Lee Revell wrote:
On Sun, 2006-03-12 at 14:06 +0100, [EMAIL PROTECTED] wrote:
netjack-0.9rc1 is here...
endianess issues fixed. tests are underway...
but if it works for 2 x86 (double
On Mon, 2006-03-13 at 16:45 -0500, Lee Revell wrote:
On Mon, 2006-03-13 at 22:21 +0100, [EMAIL PROTECTED] wrote:
On Sun, Mar 12, 2006 at 03:50:26PM -0500, Lee Revell wrote:
On Sun, 2006-03-12 at 14:06 +0100, [EMAIL PROTECTED] wrote:
netjack-0.9rc1 is here...
endianess issues fixed.
On Mon, Mar 13, 2006 at 10:21:39PM +0100, [EMAIL PROTECTED] wrote:
On Sun, Mar 12, 2006 at 03:50:26PM -0500, Lee Revell wrote:
Why do you use big-endian on the wire, requiring a double swap for x86
- x86? Wouldn't LE make more sense, especially as PPC Macs become
unavailable?
well i
On Mon, 2006-03-13 at 23:10 +0100, fons adriaensen wrote:
On Mon, Mar 13, 2006 at 10:21:39PM +0100, [EMAIL PROTECTED] wrote:
On Sun, Mar 12, 2006 at 03:50:26PM -0500, Lee Revell wrote:
Why do you use big-endian on the wire, requiring a double swap for x86
- x86? Wouldn't LE make more
On Mon, Mar 13, 2006 at 05:25:04PM -0500, Paul Davis wrote:
On Mon, 2006-03-13 at 23:10 +0100, fons adriaensen wrote:
Is it true on the common platforms that using ntohl and htonl on
floats will always result in compatible data on the wire or in a
file ? In other words, are floats
Can LAU be removed from further replies?
On Mon, 2006-03-13 at 23:40 +0100, fons adriaensen wrote:
On Mon, Mar 13, 2006 at 05:25:04PM -0500, Paul Davis wrote:
On Mon, 2006-03-13 at 23:10 +0100, fons adriaensen wrote:
Is it true on the common platforms that using ntohl and htonl on
floats
On Mon, Mar 13, 2006 at 11:40:04PM +0100, fons adriaensen wrote:
On Mon, Mar 13, 2006 at 05:25:04PM -0500, Paul Davis wrote:
On Mon, 2006-03-13 at 23:10 +0100, fons adriaensen wrote:
Is it true on the common platforms that using ntohl and htonl on
floats will always result in compatible
On Mon, Mar 13, 2006 at 11:59:15PM +0100, stefan kersten wrote:
as paul stated, network byte order is defined to be
big-endian, so yes, you have to convert 32 bit floats (and
doubles, for that matter) on intel, because they are stored
lsb first. of course it would be perfectly valid for
On Tue, 2006-03-14 at 00:21 +0100, fons adriaensen wrote:
On Mon, Mar 13, 2006 at 11:59:15PM +0100, stefan kersten wrote:
as paul stated, network byte order is defined to be
big-endian, so yes, you have to convert 32 bit floats (and
doubles, for that matter) on intel, because they are
On Tue, Mar 14, 2006 at 12:21:40AM +0100, fons adriaensen wrote:
OK, but for floats the situation could be more complex. On
Intel, the exponent/sign byte is the last one. Is it
always the first one on BE platforms ? If it isn't then
using ntohl() or htonl() wich are designed to work on
32-bit
fons adriaensen wrote:
OK, but for floats the situation could be more complex.
In libsndfile I use a 32 bit end swapper on floats and a
64 bit endswapper on doubles.
Will either rule produce consistent results on all
platforms ?
The above does produce consistent results across platforms
On Sun, 2006-03-12 at 14:06 +0100, [EMAIL PROTECTED] wrote:
netjack-0.9rc1 is here...
endianess issues fixed. tests are underway...
but if it works for 2 x86 (double swap) it should work for PPC -
x86
Why do you use big-endian on the wire, requiring a double swap for x86
- x86? Wouldn't LE
18 matches
Mail list logo
