On Friday 18 October 2002 09:23, Richard Bown wrote:
> it's time that there was a clear distinction between Linux Sound/Audio
> and Linux for Music. The latter has a clearly defined marketplace,
> the former doesn't.
Sorry, that's not quite right. The former does too,
On Friday 18 October 2002 04:25, Patrick Shirkey wrote:
> My opinion is that there is not enough people working on the
> promotional side of ALSA and Linux Audio.
ALSA/LAD is too geeky and too die-hard techno hardcore to appeal to
anyone but geeks. IMHO music geeks are the worst type of geeks a
A question - if you're sending a load of MIDI notes (as opposed to
noteons/noteoffs) with very long duration and to curtail these notes
you're sending notes with shorter (finite if you like) duration to same
channel/pitch should the longer ones clear down from ALSA and get cast
away?
At the m
On Wednesday 18 September 2002 16:18, Paul Davis wrote:
> its part of all distributions at this point. its about as standard as
> autoconf.
While it may be part of the distros it's not always installed as default.
My SuSE 8.0 DVD has it on but I still had to fish it out.
While we're at it - did
On Wednesday 18 September 2002 15:50, Tim Goetze wrote:
> anyway, i agree with paul that pkg-config should be used instead,
> which offers a lot more flexibility.
That's as maybe but it's "non-standard" still isn't it? Another dependency
in a complicated world. I think it's too soon.
However,
On Wednesday 18 September 2002 11:06, Takashi Iwai wrote:
> > Wake me up when it's all over.
>
> please give comments before going to bed.
> (otherwise you will lose the right to whinge ;)
> the decision should not be done self-righteously.
I know that you and Jaroslav will come to a fair an equi
On Wednesday 18 September 2002 10:36, Takashi Iwai wrote:
> using the versioned symbols is a good idea. it should go into
> libasound.so.3 to avoid the further confliction.
I don't know about anyone else but I'm really confused.
All I know is that JACK CVS doesn't build out of the box with ALS
The Rosegarden development team would like to announce the release of
Rosegarden-4 v0.2.0 - a sequencer and music notation editor for Linux.
This is a pre-beta release and while not yet stable enough for end-users it
has many interesting features and is suitable for Audio and MIDI recording,
play
Takashi Iwai wrote:
> well, so the problem doesn't lie on alsa side?
No, it was in our app code. I'm afraid this doesn't help you too much if you
suspect there's a bug in the emu10k synth driver anyway - I'll keep listening
out for one though.
B
--
Taupter wrote:
[ALSA sequencers and that repeating note problem]
> try noteedit.
Of course! Ok so, NoteEdit worked fine and so I reinspected our code and lo
and behold found a little bugette with our note off matrix. Now fixed.
Sorry for the false alarm.
B
Takashi Iwai wrote:
> can you check whether this happens on SB Live only or both on SB Live
> and AWE?
Chris and I are both experiencing it - I've got an SBLive and he's the AWE32.
All of us (including Taupter who's the only other one to report this problem
so far on this list) are using Rosegar
Lazy question - without searching through bug database or getting latest ALSA CVS
(0.9.0 beta12) is there any history or known bug when repeatedly playing the a note
of the same pitch through the SBLive or AWE32 onboard synth?
Given 4 crotchets in a bar playing through the ALSA seq - routing to a
Paul Davis wrote:
> "ppq" stands for "parts per quarter".
Rather boringly I was under the impression it was "pulses per quarter note"
and that's why you sometimes see it as PPQN as well as PPQ.
Sorry.
R
--
http://www.all-day-breakfast.com/rosegarden
http://www.bownie.com
_
[YAMAHA SW1000XG]
Oh wow. I've got one of these too. Great card and I'd _love_ to get
it working with ALSA - I can offer my enthusiasm if nothing else.
R
--
http://www.all-day-breakfast.com/rosegarden
http://www.bownie.com
___
Have
[Excuse the cross-posting. We've added ALSA and KDE3 support
so I thought it was worth shouting about - just this once]
--
The Rosegarden development team would like to announce the release of
Rosegarden-4 v0.1.5 - a sequencer and music notation editor for KDE2
now with KDE3 and ALSA 0.9 suppo
Takashi Iwai wrote:
> no, you shouldn't drop input events. otherwise the input events will
> be really lost.
Oh ok, from your code examples I see that I was implementing a blocking
model for a non-blocking port. Following the second example seems to have
fixed it without the need to drop any e
Hi,
Is it correct that an app should have to snd_seq_drop_input_buffer() every
so often when reading events in via snd_seq_event_input()?
If I don't drop the input buffer periodically then the input buffer appears
eventually to clog up - only allowing a few events through at a time. Whilst
the
Takashi Iwai wrote:
[turning on timestamps]
> err = snd_seq_port_subscribe(handle, subs);
> ...
>
> if you are using snd_seq_connect_to/from, then you need to replace
> it like above.
Excellent, yeah thanks that does the trick. With the minor typo correction that
the last line is
Hi. Another simple one but another one I'm afraid I can't find an example for.
I'm writing and reading events from the same ALSA 0.9.0 port (on the same
duplex handle) - I receive the events correctly through snd_seq_event_input
but the timestamps are coming back as zero even when I've started a
Hi,
Takashi Iwai wrote:
> what do you mean exactly "full polyphony"?
I just meant getting your hands on the full polyphony of the synth.
Now I've realised that the sequencer interface (sensibly) treats the
on-board synth like any other MIDI device.
> it's not difficult at all to reimplement th
Ok, earlier I sent this question to LAD but this is probably a better place
to be asking it. Apologies if you've already seen it.
Basically I'm still confused about synth clients and ports. My SBLive presents
four synth ports as default. I create a port and subscribe or connect_to a specfic
SB
Juan Linietsky wrote:
> I'm interested in extending the api only for retrieval of info about
> bank names/info, patch names/info and controller names. Info would
> default to some midi standard defaults. What do you have in mind for
> an instrument api?
I don't have anything in mind for the in
xibly as we can right from the start.
Cheers,
Richard Bown
--
http://www.all-day-breakfast.com/rosegarden
http://www.bownie.com
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
23 matches
Mail list logo
