All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Heasman <lists@mythral.org>
To: alsa-devel@lists.sourceforge.net
Subject: MIDI Timer stuck with Alsa 1.0.13, HDSP 9632
Date: Fri, 24 Nov 2006 15:33:15 -0800	[thread overview]
Message-ID: <1164411195.608.29.camel@localhost> (raw)

Hi,

About a year ago I had MIDI working fine on my system (software only to
timidity plus a USB MIDI keyboard), but haven't been using it for the
last year. Having just acquired a MIDI synth module, I decided to set up
an audio workstation again, but can't get it to work.

My problem is that I only hear the MIDI events that are right at the
beginning of a MIDI file. Looking at /proc/asound/seq/queues shows a
"running" timer with a current time that never advances beyond zero.

I have tried different combinations of kernels and alsa-drivers, with no
change in behaviour. I have tried linux 2.6.16-rt29 (Gentoo Proaudio
overlay) and 2.6.18.1 vanilla. I have tried the alsa drivers that came
with those kernels and also alsa-driver 1.0.11 and 1.0.13.

I notice that I can't get software MIDI devices to work either.
aplaymidi will not talk to Timidity, nor will it talk to my external
MIDI synth module. Kmid and Rosegarden behave exactly the same way.

I have a small Windows program that generates MIDI events, and this
works perfectly when I run it under wine.

I have made a package of everything I can think of and put it at
http://www.mythral.org/~ray/public/alsapost/

It contains /proc/asound, dmesg output, kernel configs, etc.

I am happy to provide more information or test new source code if that
helps.

Thanks,
Ray



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

                 reply	other threads:[~2006-11-24 23:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1164411195.608.29.camel@localhost \
    --to=lists@mythral.org \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.