From: Pedro Lopez-Cabanillas <plcl@telefonica.net>
To: alsa-devel@lists.sourceforge.net
Cc: Ryan Pavlik <rpav@mephle.com>
Subject: Re: ALSA sequencer changes?
Date: Mon, 15 Dec 2003 02:03:53 +0100 [thread overview]
Message-ID: <200312150200.38251.plcl@telefonica.net> (raw)
In-Reply-To: <E1AVNWF-00073D-OC@sc8-sf-list2.sourceforge.net>
Ryan Pavlik wrote:
> Hrm, I've recently updated ALSA after a few weeks of inactivity, and
> suddenly I'm not getting MIDI events from simple code that previously
> worked. I don't see any alsa-devel messages about changes, but I
> apparently missed the PCM API change notice. In addition to the more
> complex library, I tried my test code which you can find here:
>
> http://ogmo.mephle.org/test-alsa.c
>
> The problem isn't getting 0's for time (got that one sorted awhile
> back, but never integrated the fix)---the problem is I'm not getting
> anything.
>
> Anyhow, just wondering what's new or different, or if it's something
> else I missed.
No problems here with 1.0.0rc2. Your test reports events and times like
before. Try using other client/port, check your cables, interfaces, etc...
Regards,
Pedro
--
ALSA Library Bindings for Pascal
http://alsapas.alturl.com
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
next parent reply other threads:[~2003-12-15 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1AVNWF-00073D-OC@sc8-sf-list2.sourceforge.net>
2003-12-15 1:03 ` Pedro Lopez-Cabanillas [this message]
2003-12-15 1:22 ` ALSA sequencer changes? Ryan Pavlik
2003-12-14 2:00 Ryan Pavlik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200312150200.38251.plcl@telefonica.net \
--to=plcl@telefonica.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=rpav@mephle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.