Re: [linux-audio-dev] more on XAP Virtual Voice ID system

2003-01-06 Thread robbins jacob
My understanding of VVID's is that the sequencer puts one complete, continuous note on a particular VVID. The sequencer only reuses a VVID once it has ended any previous notes on that VVID. The sequencer can allocate a large number of VVIDs so that it never has to make a voice stealing decision

Re: [linux-audio-dev] more on XAP Virtual Voice ID system

2003-01-06 Thread Tim Hockin
> Two problems solved! (Well, almost... Still need temporary space for > the "parameters", unless voice allocation is non-conditional.) I think if you get an allocate voice event, you MUST get a voice on event. > That doesn't really work for normal polyphonic instruments, unless > the host *ful

Re: [linux-audio-dev] more on XAP Virtual Voice ID system

2003-01-06 Thread David Olofson
On Tuesday 07 January 2003 01.55, Tim Hockin wrote: > > > 1. Recv VOICE_ON, allocate a voice struct > > > 2. Recv VELOCITY, set velocity in voice struct > > > 3. No more events for timestamp X, next is timestamp Y > > > 4. Process audio until stamp Y > > > 4.a. Start playing the voice with given ve

Re: [linux-audio-dev] more on XAP Virtual Voice ID system

2003-01-06 Thread Tim Hockin
> > 1. Recv VOICE_ON, allocate a voice struct > > 2. Recv VELOCITY, set velocity in voice struct > > 3. No more events for timestamp X, next is timestamp Y > > 4. Process audio until stamp Y > > 4.a. Start playing the voice with given velocity > > Problem is step 1. If the voice allocator looks at

Re: [linux-audio-dev] more on XAP Virtual Voice ID system

2003-01-06 Thread David Olofson
On Tuesday 07 January 2003 00.31, Tim Hockin wrote: > > Problem is that that requires special case event processing in > > synths. You'll need an inner event decoding loop just to get the > > parameters, before you can go on with voice intantiation. > > You always process all events for timestamp X

Re: [linux-audio-dev] more on XAP Virtual Voice ID system

2003-01-06 Thread Tim Hockin
> Problem is that that requires special case event processing in > synths. You'll need an inner event decoding loop just to get the > parameters, before you can go on with voice intantiation. You always process all events for timestamp X before you generate X's audio right? 1. Recv VOICE_ON, al

Re: [linux-audio-dev] MIDI Software Sampler

2003-01-06 Thread David Gerard Matthews
STEFFL, ERIK (SBCSI) wrote: also, alsa is linux only, isn't it? erik There was a QNX port, iirc, but I don't know what its status is. Seriously, though, anything as advanced as a sampler should be using JACK. JACK currently exists for Linux and (I believe) Solaris, but it's not far off f

Re: [linux-audio-dev] more on XAP Virtual Voice ID system

2003-01-06 Thread David Olofson
On Monday 06 January 2003 23.04, Tim Hockin wrote: > > The main difficulty I see with the VVID system is how to > > initialize parameters on a new voice before the voice is > > activated with a VoiceOn event. > > After, or rather - at the same time. The host just has to make > sure the VoiceOn arr

Re: [linux-audio-dev] more on XAP Virtual Voice ID system

2003-01-06 Thread David Olofson
On Monday 06 January 2003 22.03, Steve Harris wrote: > On Mon, Jan 06, 2003 at 12:04:23 -0800, robbins jacob wrote: > > Alternately, we could require that event ordering has 2 > > criterion: -first- order on timestamps > > -second- put voice-on ahead of all other event types. > > This is what I was

Re: [linux-audio-dev] more on XAP Virtual Voice ID system

2003-01-06 Thread Tim Hockin
> The main difficulty I see with the VVID system is how to initialize > parameters on a new voice before the voice is activated with a VoiceOn > event. After, or rather - at the same time. The host just has to make sure the VoiceOn arrives first. This is what is currently in the header in my w

Re: [linux-audio-dev] more on XAP Virtual Voice ID system

2003-01-06 Thread robbins jacob
On Mon, Jan 06, 2003 at 12:04:23 -0800, robbins jacob wrote: Alternately, we could require that event ordering has 2 criterion: -first- order on timestamps -second- put voice-on ahead of all other event types. This is what I was assuming was meant orignally. However you dont have to think

Re: [linux-audio-dev] more on XAP Virtual Voice ID system

2003-01-06 Thread Steve Harris
On Mon, Jan 06, 2003 at 12:04:23 -0800, robbins jacob wrote: > Alternately, we could require that event ordering has 2 criterion: > -first- order on timestamps > -second- put voice-on ahead of all other event types. This is what I was assuming was meant orignally. However you dont have to think o

RE: [linux-audio-dev] MIDI Software Sampler

2003-01-06 Thread STEFFL, ERIK (SBCSI)
> -Original Message- > From: Pascal Haakmat [mailto:[EMAIL PROTECTED]] > 05/01/03 18:14, CK wrote: > > > if this is OSS forget about it, it will be outdated as soon > an 2.6 kernel > > is out > > Well, ALSA has OSS compatibility, and 4front-tech.com will still be > selling their for-mone

[linux-audio-dev] more on XAP Virtual Voice ID system

2003-01-06 Thread robbins jacob
The main difficulty I see with the VVID system is how to initialize parameters on a new voice before the voice is activated with a VoiceOn event. The MIDI standard deals with this by allowing 2 particular parameters, pitch and velocity, to be privileged as voice-on initializers. These parameter

[linux-audio-dev] XAP status - brief

2003-01-06 Thread Tim Hockin
I am not dead, I am moving house. :) I have not lost interest. I have a new draft of the header and I am incorporating many discussed items. I will be very busy this month, but I will try to post a new version soon. I move next week, and am out for one week this month. Just so no one wonders w

[linux-audio-dev] [ANN] Cow 0.1.0

2003-01-06 Thread Kay Pruefer
Hi, Cow Outputs Waves is a waveform editor. You draw graphs for amplitude and frequency, cow synthesizes a wavfile. The GUI uses Qt. The package includes also a program to play the cow-sounds and also wavfiles with a midi-keyboard (or any other thing that can output note on/off commands) and sev