Re: [linux-audio-dev] libsndfile breakage

2004-02-12 Thread Erik de Castro Lopo
On Wed, 11 Feb 2004 21:32:03 + [EMAIL PROTECTED] wrote: Well, I've stopped the crashing. It was my bad, but still a bit confusing. Here's what I was doing samples=info-frames*info-channels; sound=(sample_t *) malloc (samples * sizeof(sample_t));

Re: [linux-audio-dev] hdsp+latency questions

2004-02-12 Thread d
thank you thomas an paul! after a night of configuring an testing i can safely go down to 512 frames. 256 is a bit xruny. the whole issue seems to be related to my specific laptop. everything (e.g. 128 frames) works fine on a new centrino laptop with the same software. things i noticed (in

[linux-audio-dev] [i686] xmm regs + gcc inline assembly

2004-02-12 Thread Tim Goetze
can anybody help out with gcc inline assembly syntax applied to sse registers/memory locations? for a simplified example, i'm using float t[4]; ... asm (movaps %%xmm1, %0 : : m (t[0])); to move 4 packed floats from xmm1 into 't'. my suspicion is that gcc concludes from the expression

Re: [linux-audio-dev] DRI + Jack conflict?

2004-02-12 Thread martin rumori
On Tue, Feb 10, 2004 at 12:14:24PM +0100, Vincent Touquet wrote: On Mon, Feb 09, 2004 at 07:32:35PM -0500, Paul Davis wrote: the implementation of DRI by certain video interface drivers means I was just thinking of getting an IBM thinkpad and I might want to change the model I want based on

[linux-audio-dev] MIDI interface latency

2004-02-12 Thread jrobbins
Anybody know what's the minimum latency that can be achieved passing MIDI notes from one computer to another? I'm wondering if it's possible in theory to set up an audio generation cluster to be used as a realtime instrument. Basically, have a network aware synthesis app running on all machines,

Re: [linux-audio-dev] libsndfile breakage

2004-02-12 Thread Erik de Castro Lopo
On Thu, 12 Feb 2004 19:36:19 + [EMAIL PROTECTED] wrote: Heh! I didn't realise I was talking to the author. Thats the internet. Sometimes you're talking to some 12 year old and sometimes you're not :-). Sorry if that last line sounded whiney and/or ungrateful - It didn't and I get even

Re: [linux-audio-dev] [i686] xmm regs + gcc inline assembly

2004-02-12 Thread Simon Jenkins
Tim Goetze wrote: can anybody help out with gcc inline assembly syntax applied to sse registers/memory locations? for a simplified example, i'm using float t[4]; ... asm (movaps %%xmm1, %0 : : m (t[0])); to move 4 packed floats from xmm1 into 't'. I couldn't get this to fail in practice -

Re: [linux-audio-dev] [i686] xmm regs + gcc inline assembly

2004-02-12 Thread Tim Goetze
Simon Jenkins wrote: for a simplified example, i'm using float t[4]; ... asm (movaps %%xmm1, %0 : : m (t[0])); to move 4 packed floats from xmm1 into 't'. I couldn't get this to fail in practice - though I didn't try all that hard - unless t isn't on a 16 byte boundary in which case it

Re: [linux-audio-dev] MIDI interface latency

2004-02-12 Thread David Olofson
On Thursday 12 February 2004 20.30, [EMAIL PROTECTED] wrote: Anybody know what's the minimum latency that can be achieved passing MIDI notes from one computer to another? Depends on the wire. For standard 31250 bps MIDI cables, the minimum latency for a NoteOn message (status, pitch, velocity

Re: [linux-audio-dev] [i686] xmm regs + gcc inline assembly

2004-02-12 Thread Simon Jenkins
Tim Goetze wrote: Simon Jenkins wrote: for a simplified example, i'm using float t[4]; ... asm (movaps %%xmm1, %0 : : m (t[0])); to move 4 packed floats from xmm1 into 't'. I couldn't get this to fail in practice - though I didn't try all that hard - unless t isn't on a 16 byte boundary in

Re: [linux-audio-dev] MIDI interface latency

2004-02-12 Thread Tim Goetze
David Olofson wrote: Depends on the wire. For standard 31250 bps MIDI cables, the minimum latency for a NoteOn message (status, pitch, velocity - three bytes) is 0.96 ms. (It is one start bit and one stop bit, right...?) yes, but you forgot there's only two bytes for the message in running

Re: [linux-audio-dev] MIDI interface latency

2004-02-12 Thread David Olofson
On Friday 13 February 2004 00.53, Tim Goetze wrote: David Olofson wrote: Depends on the wire. For standard 31250 bps MIDI cables, the minimum latency for a NoteOn message (status, pitch, velocity - three bytes) is 0.96 ms. (It is one start bit and one stop bit, right...?) yes, but you

Re: [linux-audio-dev] [i686] xmm regs + gcc inline assembly

2004-02-12 Thread Tim Goetze
Simon Jenkins wrote: I can definitely get asm (movaps %%xmm1 %0 : =m (t[0])); to exhibit the optimisation problem (the one I couldn't get your original line to show) and then fix it again by removing the [0]. I was getting a segfault on about 50% of compiles, as I modified the code,

Re: [linux-audio-dev] MIDI interface latency

2004-02-12 Thread jrobbins
One way to use NICs would be to drop the protocol stack and just use the NICs as high speed serial interfaces. You could use cross-over cables and point-point connections only, to completely avoid the risk of collisions and the related random latencies that may cause. right, i remember