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 21:13:21 +0100
From John Rigg <[hidden] at jrigg dot co dot uk>
To[hidden] at lists dot jackaudio dot org
In-Reply-ToGabriel Beddingfield [Jack-Devel] [PATCH JACK1 & JACK2] drivers/alsa/memops.c: Error when source is non-native byte-order float
Follow-UpGabriel Beddingfield Re: [Jack-Devel] [PATCH JACK1 & JACK2] drivers/alsa/memops.c: Error when source is non-native byte-order float
On Mon, Aug 08, 2011 at 10:24:25PM -0500, Gabriel Beddingfield wrote:
>
> I stole drivers/alsa/memops.c from jack1 for a project I was working on.  
>  In doing the unit testing, I found that the code fails when the source  
> buffer is float with non-native byte order (i.e. the  
> sample_move_d*_sSs() functions).  The attached patch (against Jack1 SVN)  
> fixes that.  This also affects Jack2.
>
> 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  
> quirk and the *_sSs() functions.

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.

John
PrevNext  Index

1312920608.20164_0.ltw:2,a <20110809201321.GA2997 at localhost0 dot localdomain>