Re: [Jack-Devel] [PATCH JACK1 & JACK2] drivers/alsa/memops.c: Error when source is non-native byte-order float

PrevNext  Index
DateTue, 09 Aug 2011 20:26:27 -0500
From Gabriel Beddingfield <[hidden] at gmail dot com>
To[hidden] at lists dot jackaudio dot org
In-Reply-ToJohn Rigg Re: [Jack-Devel] [PATCH JACK1 & JACK2] drivers/alsa/memops.c: Error when source is non-native byte-order float
Follow-UpJohn Rigg Re: [Jack-Devel] [PATCH JACK1 & JACK2] drivers/alsa/memops.c: Error when source is non-native byte-order float
On 08/09/2011 03:13 PM, John Rigg wrote:
>> As best as I can tell, these functions are only called if
>> driver->quirk_bswap is enabled... and it's not enabled for anything as
>> far as I can tell.  So, another valid option would be to remove this

I stand corrected on this point.  I found the one line of code that 
allows it to be enabled.

> Interesting. I'm wondering if this would explain why I've never been able
> to use my RME HDSPe MADI card in floating point mode with jack clients
> on my x86_64 system. I haven't had time to investigate and have just been
> using it in integer mode to get it working.
>
> I don't actually know what the byte order of the RME card's float output is,
> but if jack has been getting it wrong that might explain why I was getting
> very high level noise instead of a legitimate input signal.

If the RME card is using a big-endian floats, then this is very likely 
the cause.

-gabriel
PrevNext  Index

1312939614.6419_0.ltw:2,a <4E41DE43.5040009 at gmail dot com>