[Alsa-devel] Re: [Alsa-user] Upgrade problems -addendum
At Thu, 23 Jan 2003 01:35:53 +0100, Tais M. Hansen [EMAIL PROTECTED] wrote: On Wednesday 22 January 2003 17:23, Takashi Iwai wrote: could you test the following two patches? with the first one, the driver will calculate the current pointer like VIA686 does. if this is ok, no messages will appear. The first patch makes artsd freeze the computer for about 10-20 seconds and then aborts with a cpu overload message. ogg123 sometimes plays noise when starting while speeding through the ogg-file, sometimes it plays normally. Only ogg123 generated output in syslog which I've attached in alsa-ogg123-syslog-p1.txt.gz. ok, that's not good... the second one is to force to increase the index. you'll see debug messages, anyway, if POINTER_DEBUG is defined. First, removing first patch and applying the second patch. Ogg123 freezes when started with no sound and a lot of errors. Ctrl-C is caught after about 10 secs. Syslog output is attached in alsa-ogg123-syslog-p2.txt.gz. Artsd starts but keep looping a short random piece of noise. No sound can be played/heard when played. Killing artsd produces the output attached in alsa-artsd-syslog-p2.txt.gz. hmm... Applying both patches. Ogg123 and artsd behaves like when only the first patch was applied. I let ogg123 run a little longer and noticed that sometimes about half a second noise where played. Syslog errors from using ogg123 this time is attached in alsa-ogg123-syslog-p1+p2.txt.gz. ah, applying both has no effect.. Note: POINTER_DEBUG was defined and the initial patch you sent was applied throughout the test. ok, the attached is the third trial. please appply it solely without the preivous patches. hope this works better... ciao, Takashi via-pointer-test3.dif Description: Binary data
Re: [Alsa-devel] Reverb control for emu10k1?
At Tue, 21 Jan 2003 10:37:45 -, Merrony, Stephen (London) [EMAIL PROTECTED] wrote: Sorry if this is a FAQ, but is there any way I can control reverb from my ALSA application? not yet. the emu10k1 dsp code was not implemented fully yet... ciao, Takashi --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Re: [Alsa-user] Upgrade problems -addendum
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 23 January 2003 11:03, Takashi Iwai wrote: ok, the attached is the third trial. please appply it solely without the preivous patches. I'm assuming the very first via8233a-fix.dif is still supposed to be applied. (won't work without it anyway) hope this works better... Well... Ogg123 freezes the same way as with test1. Artsd no longer fails with cpu overload, but it's constantly busy and can't play sound. There's nothing to see in syslog but there's suddenly a bunch of output in the debug log. This is ogg123: Jan 23 12:05:25 proficio kernel: ALSA ../alsa-kernel/core/pcm_lib.c:123: Unexpected hw_pointer value (stream = 0, delta: -1024, max jitter = 4096): wrong interrupt acknowledge? Jan 23 12:05:35 proficio last message repeated 429 times Jan 23 12:05:35 proficio kernel: ALSA ../alsa-kernel/core/pcm_lib.c:2117: playback write error (DMA or IRQ trouble?) And this is artsd: Jan 23 12:06:31 proficio kernel: ALSA ../alsa-kernel/core/pcm_lib.c:123: Unexpected hw_pointer value (stream = 0, delta: -1024, max jitter = 8192): wrong interrupt acknowledge? Jan 23 12:06:41 proficio last message repeated 206 times Aplay is able to play a wav-file though but it also generates errors in the debug log: Jan 23 12:08:16 proficio kernel: ALSA ../alsa-kernel/core/pcm_lib.c:123: Unexpected hw_pointer value (stream = 0, delta: -3386, max jitter = 11025): wrong interrupt acknowledge? Aplay also threw the usual in syslog once: Jan 23 12:08:18 proficio kernel: ALSA ../alsa-kernel/pci/via82xx.c:601: invalid via82xx_cur_ptr, using last valid pointer - -- Regards, Tais M. Hansen OSD -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iQIVAwUBPi/O0IIvLOJqwYc4AQIpHQ//SToDIhB49e/UlJYOqTkTrya/25Vuvqju dYIhobeCn1bm8Lbun3Eb75rBt6pWqf/6g3YhfxdYwVYi5HD9YrX9SaqkOFdEFxiZ KUR0Vop7Nyu7Y379w7BKNZILE6ApvgKoSSsYXiR4EMI3mu5Rst+fAbhvyKuL1+u0 eggkgbZgffmMjZFtm0yyPywBmQxUz1INknIhs+/AXpTpbfHFxIEtaZGwSuEpK2DO is33gNvMIrAGmaXWoC3xNLLcDAOffcWVY3Cjx7KJAi8+UOAiJ15LCORaO41uv3r9 MvycX3KpDvMb5u+/RH00fLutTY8fQKiSwjRCRJWz3QBLOPJw18mIUz55T4i7VSoO x00fy+73xx2IePd9tT8mGZRr+leH19tnXP44+5QeVEj3GuOd85fw4nFkf+01z+9X m0DSS44/+UUG/XDQjl3SBeD0ad3alqOm748Ef0mHnmy058VF+Vh65s6B7bUzq/bf p59x0Ea1Tk9fph8+vyhJfvTLBMzywGhhNrOUuijUwjAkvojsMyB879ay838xkL0c lRW7WmvmB8HSoFCvJmjXHuHCoxP9GrRw0L3V4zj/OmuD8qM+SYUBhkdmLjEjzgsh e9RfEftSNDZSR+bdXE3nChiGWqeDCJXvYdZVcM/kpUfnZbRTZOdKdN2mqZLBvm6D dXEZcr9VgfA= =hpJK -END PGP SIGNATURE- --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Re: [Alsa-user] Upgrade problems -addendum
At Thu, 23 Jan 2003 12:15:26 +0100, Tais M. Hansen [EMAIL PROTECTED] wrote: On Thursday 23 January 2003 11:03, Takashi Iwai wrote: ok, the attached is the third trial. please appply it solely without the preivous patches. I'm assuming the very first via8233a-fix.dif is still supposed to be applied. (won't work without it anyway) yes. the patch had been already applied to cvs. hope this works better... Well... Ogg123 freezes the same way as with test1. Artsd no longer fails with cpu overload, but it's constantly busy and can't play sound. There's nothing to see in syslog but there's suddenly a bunch of output in the debug log. This is ogg123: Jan 23 12:05:25 proficio kernel: ALSA ../alsa-kernel/core/pcm_lib.c:123: Unexpected hw_pointer value (stream = 0, delta: -1024, max jitter = 4096): wrong interrupt acknowledge? Jan 23 12:05:35 proficio last message repeated 429 times Jan 23 12:05:35 proficio kernel: ALSA ../alsa-kernel/core/pcm_lib.c:2117: playback write error (DMA or IRQ trouble?) And this is artsd: Jan 23 12:06:31 proficio kernel: ALSA ../alsa-kernel/core/pcm_lib.c:123: Unexpected hw_pointer value (stream = 0, delta: -1024, max jitter = 8192): wrong interrupt acknowledge? Jan 23 12:06:41 proficio last message repeated 206 times hmm, it'd better to start from the beginning. please try the attached patch (solely). this will generate bunch of debug messages at each interrupt but won't improve any behavior. so, it would be enough to run only once or twice if you got bad playback. from the obtained log, we'll be able to know whether the interrupt is properly generated, or at which condition, the read of register value fails. ciao, Takashi via-pointer-debug.dif Description: Binary data
Re: [Alsa-devel] Re: [Alsa-user] Upgrade problems -addendum
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 23 January 2003 12:46, Takashi Iwai wrote: I'm assuming the very first via8233a-fix.dif is still supposed to be applied. (won't work without it anyway) yes. the patch had been already applied to cvs. Ok, I'll just do a cvs update then. Well... Ogg123 freezes the same way as with test1. Artsd no longer fails with cpu overload, but it's constantly busy and can't play sound. ... hmm, it'd better to start from the beginning. please try the attached patch (solely). this will generate bunch of debug messages at each interrupt but won't improve any behavior. so, it would be enough to run only once or twice if you got bad playback. from the obtained log, we'll be able to know whether the interrupt is properly generated, or at which condition, the read of register value fails. Okay, fresh cvs checkout. Enabled POINTER_DEBUG and applied the via-pointer-debug.dif. Ogg123 freezes/stalls without ever making a sound, like with the previous test and test3 patches. Log output is attached. Aplay plays a wav-file fine. No problems noticed. Log output is attached. When artsd is started a short piece of noise is looped, as described earlier. Can't play any sound through arts. Log output attached. - -- Regards, Tais M. Hansen OSD -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iQIVAwUBPi/h6IIvLOJqwYc4AQI/CBAAoZjVwgiDiERJiN2klyM/eriOO9fezFs6 ZOE1q3fugqhplVXr+CSiOA4P/KG49FUkGFoZYuuaK0xwJcEtneY6zvHcK+29E2zf iiLPaUU19zrnN/Bd11pVqeKKa6zixYuNgG3WLVcXs+dhtCYIGIi930Pdk/5AjXq8 ChB5oTzBXfLZs3pm7wte3mELJSZ1sZQ9q3BUzkjEBUot7AkRW4LEx540MCTvQ6+r d2fYjXswuEeOo/BySuJofCd3Uiv/1tx2jwkDPckjbFZNh0YVZtdp0as1phb/PVOt 05oUj+9nDVFRStqdMaBODSBOiKceewkXR7RwtHa9+OaprjRchGvpyo3x3gJjtfZU HcJqhPQQnt1/xa9JHht2FanHMuY/GJgBJXiNo6bWMkhVWe3d30wcFJpxTL7vzu8h hbbEsH5cAEAP5+KG+lPz07ZF2CZezJovevsE33aAk29Xm7bugDd56yWgLloarulE Ihjk3RLRM3gx6/fdx4JQHt4HTg2cDjKQV2fWkl8XKGhEqDLTIF1D8yGSfVhUbdmh J+F9Ntyhw2GXbaD9JXqDpSFx1QWURvj1BVtwbLZ8aTn7XGzNZiSGK+8UY02jXQ3+ cb5TzUganC9vYrLUfd3lSDiWZobXXs76epyWAAoyh6F00MeGBP3lbAXEdx3eph5D M7RC9gOpl8c= =HyhA -END PGP SIGNATURE- alsa-aplay.txt.gz Description: GNU Zip compressed data alsa-artsd.txt.gz Description: GNU Zip compressed data alsa-ogg123.txt.gz Description: GNU Zip compressed data
[Alsa-devel] Re: [Alsa-user] No sound on Extigy
(moved to alsa-devel up to now...) At Thu, 23 Jan 2003 11:33:50 +0100, I wrote: At Thu, 23 Jan 2003 11:26:02 +0100 (MET), Clemens Ladisch wrote: The default output device used by aplay is hw:0, which doesn't automatically convert sample rates. Try aplay -D plughw:0 something.wav. i'm afraid that it doesn't work, too, because this configuration is not handled well. anyway please try once. it's tough to solve... if the original usb-audio driver doesn't work with plughw like above, please try the attached patch. it will show many debug messages. you can suppress it by undefining HW_CONST_DEBUG at line 1167. Takashi usb-const.dif Description: Binary data
Re: [Alsa-devel] Re: [Alsa-user] Upgrade problems -addendum
At Thu, 23 Jan 2003 13:36:53 +0100, Tais M. Hansen [EMAIL PROTECTED] wrote: Well... Ogg123 freezes the same way as with test1. Artsd no longer fails with cpu overload, but it's constantly busy and can't play sound. ... hmm, it'd better to start from the beginning. please try the attached patch (solely). this will generate bunch of debug messages at each interrupt but won't improve any behavior. so, it would be enough to run only once or twice if you got bad playback. from the obtained log, we'll be able to know whether the interrupt is properly generated, or at which condition, the read of register value fails. Okay, fresh cvs checkout. Enabled POINTER_DEBUG and applied the via-pointer-debug.dif. Ogg123 freezes/stalls without ever making a sound, like with the previous test and test3 patches. Log output is attached. Aplay plays a wav-file fine. No problems noticed. Log output is attached. When artsd is started a short piece of noise is looped, as described earlier. Can't play any sound through arts. Log output attached. thanks. it seems really the index value was not updated correctly by the chip. ok, take 4: please try the new one... Takashi via-pointer-test4.dif Description: Binary data
Re: [Alsa-devel] alsa-lib resamping error
At Wed, 22 Jan 2003 12:38:31 -0500, Paul Davis wrote: if you try to play a 22.05kHz stream on hardware that supports 32kHz and 44.1kHz but not 22.05kHz, alsa-lib's plughw layer chooses to use 32kHz and resamples. this seems like an error to me: it would be much better to choose 44.1kHz and do simple integer resampling. that is: the search for the best rate should first try integer multiples and divisors of the desired rate, not the closest rate. agreed, it would be better. but... errm... changing this in alsa-lib is like going into a big labyrinth for me :) Takashi --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Re: [Alsa-user] Upgrade problems -addendum
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 23 January 2003 16:08, Takashi Iwai wrote: Okay, fresh cvs checkout. Enabled POINTER_DEBUG and applied the via-pointer-debug.dif. Ogg123 freezes/stalls without ever making a sound, like with the previous test and test3 patches. Log output is attached. Aplay plays a wav-file fine. No problems noticed. Log output is attached. thanks. it seems really the index value was not updated correctly by the chip. ok, take 4: please try the new one... Same as before, log output attached. :) - -- Regards, Tais M. Hansen OSD -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iQIVAwUBPjArcYIvLOJqwYc4AQJQyBAAjSgAESxt/dy8dhIaK1XFUAW4fwdnwgFB 8Ydg+Fac5vlsGLpZ2+VnF/wjo4391ZkgdSQIyViCt996csGv1IuVilkd4Nx77dJU /+dbnrHfbP/bATFY3zBMiGahgfDyQQnXb6zrrmQPLRLqN9jYkAoOJRKVJRxme6QT Yc1+S09pxYp9s+wwrf1MQ9k/j5P4KST2jNOfNQsu1nrvpbeHJLxPLps8UJlbz/2O /ZMhyPRUCJJ+8vqTbReaw5fPt4z+vZUzWmiSQkRaH/zmu0mFjEGn0shLwduokKP7 dykv2VOQJT/rzx9bhmj1fXNLf6Fm7JK36VrckOGlmJ/zgXAvI4hmgE210fiIE+Hl 5eX+XQczas7AmdNpwIsfQBnoEidw+14L3mMweMNS4En3mVzaRixzucddlKZP71rN EyV30nlmUhUqDRk5QJnwVZwSXKvILLrYMKSmJ1hmfC6MsD0NNZE97mTVn6L4gPDd SyjElY8q3Ry2OdzaWzIem+fgNK031fzJxVFBNH+zxgNnKocO84wH47vOlweArEkd 4IISZlSMUM78xeCu1DbzFS0BDZkU5vDET0+wQ4sz82Yc1T6nieLOWMMuHrWoztE9 aCj/Hn6KreGdR9jRy+Nt7D+YIQ+NUzFIIohq8nuqvaEOZ3sn5IUV5nSpyUSZsh9F 0nccZ6azGDE= =qJIw -END PGP SIGNATURE- alsa-aplay-test4.txt.gz Description: GNU Zip compressed data alsa-ogg123-test4.txt.gz Description: GNU Zip compressed data
[Alsa-devel] [PATCH] SC-D70 recording support
This finally adds support for capturing.
Contrary to what I've written earlier, the mixer controls (capture
selection etc.) *are* supported, because they're on the device's front
panel, not in software. :-)
--- alsa-kernel/usb/usbquirks.h.orig2003-01-23 18:22:44.78570 +0100
+++ alsa-kernel/usb/usbquirks.h 2003-01-23 18:38:23.808544000 +0100
@@ -398,6 +398,7 @@
}
},
{
+ /* thanks to Emiliano Grilli [EMAIL PROTECTED] for helping researching this
+data */
USB_DEVICE(0x0582, 0x000c),
.driver_info = (unsigned long) (const snd_usb_audio_quirk_t) {
.vendor_name = Roland,
@@ -423,6 +424,23 @@
}
},
{
+ .ifnum = 1,
+ .type = QUIRK_AUDIO_FIXED_ENDPOINT,
+ .data = (const struct audioformat) {
+ .format = SNDRV_PCM_FORMAT_S24_3LE,
+ .channels = 2,
+ .iface = 1,
+ .altsetting = 1,
+ .altset_idx = 1,
+ .attributes = 0,
+ .endpoint = 0x81,
+ .ep_attr = 0x01,
+ .rates = SNDRV_PCM_RATE_CONTINUOUS,
+ .rate_min = 44100,
+ .rate_max = 44100,
+ }
+ },
+ {
.ifnum = 2,
.type = QUIRK_MIDI_FIXED_ENDPOINT,
.data = (const snd_usb_midi_endpoint_info_t) {
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Re: [Alsa-user] Upgrade problems -addendum
At Thu, 23 Jan 2003 18:50:38 +0100, Tais M. Hansen [EMAIL PROTECTED] wrote: On Thursday 23 January 2003 16:08, Takashi Iwai wrote: Okay, fresh cvs checkout. Enabled POINTER_DEBUG and applied the via-pointer-debug.dif. Ogg123 freezes/stalls without ever making a sound, like with the previous test and test3 patches. Log output is attached. Aplay plays a wav-file fine. No problems noticed. Log output is attached. thanks. it seems really the index value was not updated correctly by the chip. ok, take 4: please try the new one... Same as before, log output attached. :) the next one is to put all logs to /var/log/debug. and will show more verbose. Takashi via-pointer-test5.dif Description: Binary data
Re: [linux-audio-user] Re: [Alsa-devel] alsaplayer not working with alsa?
Hi Mark and Jack, regarding to the alsaplayer problem: could you try the attached patch (to cvs version) ? hope this fixes the nasty bug... ciao, Takashi pcm-unlink-fix.dif Description: Binary data
Re: [Alsa-devel] Re: [Alsa-user] Upgrade problems -addendum
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 23 January 2003 19:07, Takashi Iwai wrote: thanks. it seems really the index value was not updated correctly by the chip. ok, take 4: please try the new one... Same as before, log output attached. :) the next one is to put all logs to /var/log/debug. and will show more verbose. Ok, log output attached, 3 files with loads of gibberish ;). Same behavior btw. - -- Regards, Tais M. Hansen OSD -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iQIVAwUBPjA36oIvLOJqwYc4AQKg9w/9E46Tbs7SEdaRFx8OjYLJwDk1QoSQcu7r jE/4B6+1PmqMPIfvmr5C0MjGM5Q+rDiGa1ZRHGfKAvshOcR7RJhCvtTqrJ2G9f36 O1B0+a1lkp/SCWSVkW29eQq37tn1wumn+FrIGNGm99QKlHfkcxXCMRmZMC8LyXmj Rf9ZNKjhz365yZcmnJoX3x3j/O+3q1AmlCCoz0BPhx5GVUPBoic38gj6nS36rWaE wnp+B/BjQ2WQ4lfpSW7KXvYzPpDxxz9XyTHan78O6+6kiaNPiNyTN2haYCL/RJAN 1EVZMqsRwdz3UCWx73A5LyA/SsDQ1bhtJwfcBr194rGM4uDc4BGuSWMg/BYt3KPg O2QkQu0EA0n+i/fTLG67wLCJldslOqTd5nnz6NEa1aaaJT3dSekq4pc7iKBKXKu/ ZJ1K/Mj7w90hGZyyFsXPI53nTrVAkIcwOyaUE88WZ1WEnGEpCoomRJY5+C1gJcnp IQPaaAJVSeqPKJ/ypHUgu4KS5L/QyNlD01hwFbom1C6lz58iyMJdS12Lo1J+64ja exv+OPncxT3vGj/SCotClLS28YAUIStiLhMRcQjQR6AiV0XgTk4XfyqgUa6Qy6IE fAWk7TVekdm+AgKUa+xBWBa+Rs5yykHBGB8foaGJUsZVqOxN2PfQ6lE/8csXOjNB IMrfuUeyraU= =R+NV -END PGP SIGNATURE- alsa-aplay-test5.txt.gz Description: GNU Zip compressed data alsa-artsd-test5.txt.gz Description: GNU Zip compressed data alsa-ogg123-test5.txt.gz Description: GNU Zip compressed data
[Alsa-devel] HDSP 9652 MIDI Timing - Much improved, but no Port 1...
Paul, Takashi-san and Clemens, Hi. A couple of days ago Fernando got a new RPM built for Alsa which includes the recent HDSP 9652 MIDI timing fix that you worked together on and supplied about 10 days ago. I wanted to report back that the timing is now much improved. I haven't used it a lot yet, but I am playing moderately complicated songs now and the timing seems fine. Thanks. There is one problem that has come up new in this release. The HDSP 9652 has two MIDI ports. With this release I can only get MIDI out on Port 2. I cannot get MIDI out at all on Port 1. Both ports used to work on the previous version, albeit with bad timing, so this fix this has changed this aspect of the driver. I also tried using kaconnect to look at the connections between Rosegarden and the alsa_sequencer. It shows that Rosegarden is hooked to 64:32 External MIDI 0 only. A second group, 64:0 External MIDI 0 shows up, but kaconnect will not connect to it. I do not know what that means, but it seems to be part of it. It strikes me that I have not done any recording with this device, so I should do some of that before we make any more driver changes. However, I wanted to report back a big thanks for a step in the right direction, even if we are not quite all the way there yet and allow you to look at what might be causing this problem. If there is any specific testing you'd like me to do, please let me know and I'll try to get to it as soon as possible. I'd like to get this card fully supported (yes, the mixer too Paul!) ;-) as I get 2-3 emails a week from people asking me if they should buy the card and I'd like to tell them yes. Thanks much, Mark --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
