From: Romain Bossart <romain.bossart@free.fr>
To: alsa-devel@alsa-project.org
Subject: Re: Audiophile Delta 24/96 Midi Out continuously sends zeroes (alsa 1.0.14)
Date: Wed, 19 Sep 2007 06:59:29 +0200 [thread overview]
Message-ID: <fcqabi$cj7$2@sea.gmane.org> (raw)
In-Reply-To: <46DC3BF4.9010204@free.fr>
Hi all, Hi Clemens,
just for your information, the midi out was broken.
I grabbed a bought an old layla and everything works now.
Thank you again for your help.
Cheers,
Romain
Romain Bossart wrote:
>
> Clemens Ladisch wrote:
>> Romain Bossart wrote:
>>> Selon Clemens Ladisch <cladisch@fastmail.net>:
>>>> That is, the zeroes are _not_ sent when you're not using jack? When
>>>> nothing is connected, or when you use aplaymidi or amidi to send
>>>> something, everything is OK?
>>> Here is a summary of the various tests I did. I have just one card: Audiophile
>>> Delta 24/96. My kernel is now 2.6.22.1 RT patched & alsa 1.0.14,
>>> Audio works perfectly. I don't think jack is the problem.
>>>
>>> Config #2 = Delta Midi Out -> (Midi In) Instrument (Midi Out/Thru) -> Delta Midi
>>> In and 'amidi -p hw:0,0 -d'. Jack being started or not.
>>>
>>> Symptoms: tons of zeroes are shown by amidi as soon as I launch it. The stream
>>> is so intense I can actually hear it in my speakers/monitors (need to switch to
>>> better MIDI cables, I know!). amidi and /proc/asound/card0/midi0 give the same number
>>> of transmitted bytes.
>> With "transmitted", you meant "received"?
>> When Jack is not running, there is no software to send anything. If the number
>> of _transmitted_ bytes changes anyway, this would be a bug in ALSA.
> Oops, 'reveived' is correct. Thank you.
>
>
>>> Config #2b = Delta Midi Out -> Delta Midi In
>>> and 'amidi -p hw:0,0 -d', Jack being started or not.
>>>
>>> Symptoms: identical to config#2. Moreover, if meanwhile I send some Midi commands
>>> with amidi ('amidi -p hw:0,0 -S C01C'), I don't find this data in my dump.
>> Apparently, the output port is broken. While it is theoretically
>> possible that the driver doesn't initialize the card correctly, I cannot
>> imagine a bug that would cause the port to presume that there is data to
>> send.
> You're right the output port seems to be broken.
>
>> Could you test if the port sends data even before the driver (or Linux)
>> is loaded, or in Windows?
>>
>
> I am not sure I can try this. I will change my card.
>
>> Regards,
>> Clemens
>>
> Thank you very much for your help.
>
> Regards,
> Romain
prev parent reply other threads:[~2007-09-19 5:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46D4A1D6.7010604@free.fr>
2007-08-29 6:34 ` Audiophile Delta 24/96 Midi Out continuously sends zeroes (alsa 1.0.14) Clemens Ladisch
2007-08-29 9:00 ` Romain Bossart
2007-08-29 22:22 ` Romain Bossart
2007-09-02 12:03 ` Romain Bossart
2007-09-03 6:52 ` Clemens Ladisch
[not found] ` <1188826536.46dc0da8097bc@imp.free.fr>
2007-09-03 15:29 ` Clemens Ladisch
2007-09-03 16:53 ` Romain Bossart
2007-09-19 4:59 ` Romain Bossart [this message]
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='fcqabi$cj7$2@sea.gmane.org' \
--to=romain.bossart@free.fr \
--cc=alsa-devel@alsa-project.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox