On Fri, 03 Dec 2004 01:11:15 -0500 Ken Schutte <kschutte(a)MIT.EDU> wrote: Hi, many soundcards offer mirroring the line-in or mic-in directly on the output. Thus hearing them through the speaker does not mean that you are actually capturing from them. It just simply means that the soundcard routes the line-in signal directly back to the output. Read the emu10k1 page in the AlsaDrivers section on alsa.opensrc.org. It should have info on how to use the emu10k1 mixer [which is a beast] correctly.. Good luck, flo -- Palimm Palimm! Sounds/Ware: http://affenbande.org/~tapas/

Hi, the Linux Audio Live CD as published by german Keyboards (www.keyboards.de) is now available at ftp://ftp.suse.com/pub/suse/i386/live-cd-9.2/SUSE-Linux-9.2-LiveCD-Audio.iso International mirrors are found at (some mirrors might not yet be synced) http://www.suse.de/de/private/download/ftp/ausland.html The CD can be switched to english by pressing F4 in the boot menu. Have a lot of fun ! Matthias -- Dr. Matthias Nagorni SuSE Linux GmbH Maxfeldstr. 5 phone: +49 911 74053375 D - 90409 Nuernberg fax : +49 911 74053483

Maybe qamix can help. You can use xml-files to configure its UI. See the readme file included in the source package. Great tool. But warning: qamix cannot offer more controls than the alsa driver supports. Best regards ce

On Sat, 2004-12-04 at 00:50 +0100, Frank Barknecht wrote: Thanks for that reply. The issue of setting the mixer above 50% = silence aside, I've come the conclusion that a sw mixer isn't really important to me (however I guess I could just plug the damn thing into a mac and see what the "official" drivers provide). -ry -- Ryan Gallagher <ruinaudio(a)comcast.net>

Matthias, I immediately did leech the ISO, with reason, of course ;-) . Thanks a lot for your lovely work. This disc really breaks hearts. Great work! Especially I was interested in Fons' Aeolus. I really had a lot of fun with it have a look at the time stamp of this posting (hope Fons reads this list, too ;-). Jack rack is somehow confusing. When starting it from the menu, it complains about jack not running. When trying to start qjackctl, jack cannot start; I removed full duplex to playback only and I also removed realtime support and it did start. I have a notebook with an AC 97 chip. After that, jack started and jackrack also did start. I saw some GUI applications I never saw before; thanks a lot for this work! Best regards and finally: good night :) . ce

On Sun, 12 Dec 2004, Philippe Warichet wrote: We did not add any program to the SUSE Linux 9.2 distro. However we had to recompile the kernel with CONFIG_HPET_RTC_IRQ=n (see below). Also we had to move some config files from the SuperCollider source package to the Emacs directory. This is documented on Keyboards (Linux Download section), in german language (see below). Then we added some PD examples by Frank Barknecht, some SuperCollider demos by Fons Adriaensen and alo some MIDI- and Ogg-files. 1) Configuring the kernel on SUSE 9.2 for use with MusE (/dev/rtc fix): install kernel-source package. cd /usr/src/linux-2.6.8-24 make cloneconfig joe .config // Edit CONFIG_HPET_RTC_IRQ=n make clean make make install make modules_install mkinitrd 2) Configure SuperCollider on SUSE 9.2 (Thanks to Fons Adriaensen for helping me with the SC3 part of the Live-CD and providing the demos): 1) Install emacs and source-RPM of SuperCollider. 2) unpack tarball: cp /usr/src/packages/SOURCES/SuperCollider-3.0_cvs20040823.tar.bz2 ~/ tar xjf SuperCollider-3.0_cvs20040823.tar.bz2 3) Install required data and config files: cd ~/SuperCollider-3.0_cvs20040823/linux/scel su cp el/*.el /usr/share/emacs/site-lisp exit cd ~/SuperCollider-3.0_cvs20040823/build su mkdir /usr/share/SuperCollider/build cp -R Help /usr/share/SuperCollider/build exit 4) Install configuration and examples: Download files from http://www1.keyboards.de/magazine/m0105/501010wp.html Left box, files SuperCollider_Examples.tar.bz2 SuperCollider_homecfg.tar.bz2 cd ~/ tar xjf SuperCollider_homecfg.tar.bz2 tar xjf SuperCollider_Examples.tar.bz2 su SuSEconfig exit Greetings, Matthias -- Dr. Matthias Nagorni SuSE Linux GmbH Maxfeldstr. 5 phone: +49 911 74053375 D - 90409 Nuernberg fax : +49 911 74053483

On Sun, 12 Dec 2004, Mark Knecht wrote: it certainly (and intentionally) focuses on interactive apps that immediately make a lot of noise ;-) Would be cool to extend it in a way to also offer simple mouse click access e.g. to Ardour, MusE, including the required HowTos. (Live distro designers, are you listening ? ;-) However this might then also require automatic mounting of HDD partitions (which can be done, see e.g. Knoppix). Greetings, Matthias -- Dr. Matthias Nagorni SuSE Linux GmbH Maxfeldstr. 5 phone: +49 911 74053375 D - 90409 Nuernberg fax : +49 911 74053483

I for myself have really enjoyed the live CD, and I immediately did install the latest version of Aeolus on my Gentoo box after I had played the live CD one. Otherwise, the CD somehow also shows that audio on linux is still not that easy to handle. I think that there are so many nice audio apps, but some minor improvements concerning the usability would make it much easier to unexperienced users to get started; I'd simply like to address some of the things that I would find really great: * applications could automatically check during startup if jack is running and autoconnect to it; if not (or ..alsa is given), fall back to ALSA. ams for example does autoconfiguring the audio output really great * applications could remember the last used MIDI interface and autoreconnect to it; most often a computer has only one MIDI interface which is not often changed * applications could automatically reconnect to jack as soon as jack has been restarted or jack has disconnected an application; currently, some applications simply freeze * GUI applications could offer the possibility to set and change the MIDI and audio connections from within the program's interface. * Audio applications could make it possible to choose the desired audio card for input or output from within the GUI (like kamix does, for example) instead of expecting a CLI parameter (which then is different for any application: --ao alsa:3, --device plughhw:1, -c 2, and even the numbering from 0 to n or 1 to n+1 is confusing ;-). There are more things which would be nice to have; we all want to have long required new features instead of some convenience functions, but as soon new users are a destination group, I have to say that it is really great if someone can write a complicated software, but it is also complicated and honourful to have the end user in mind. Meanwhile (and in a very short time), audio applications on linux have seen an evolution which is simply incredible. I guess now it's the right time to add - step by step - some convenience functions to them. And oh yeah, if *I* could only code, I'd immediately start 20 projects concerning the comfort of using linux audio apps. Or I have to win a huge amount of money, so I could pay some developers to do the job for us ;-) . THe next life I live I'll be a programmer for sure! Please note, this is not a complaint, but I thought I should grab the chance to make some suggestions in this great list. Best regards & have phun, ce

On Mon, 2004-12-13 at 20:01 -0500, Paul Winkler wrote: Well, I agree with Christoph. I think all his points were important for the LAD community to hear. Christoph, you may like to send those points to the Developer list as some developers don't subscribe to the users list. The GUI programs should have that functionality IMO, you can always fiddle around as much as you want in qjackconnect if you like. Having the functionality in a program doesn't restrict you from using an external program like qjackconnect. I think the Linux audio apps have come a long way and I'd be excited to see developers take the next step and make their programs easier to use and more polished. IMO anything that makes a program crash (like losing Jack connectivity) is a bug, pure and simple. The program should handle this gracefully, without question. Dan -- Dan Harper http://danharper.org --- Enhancing the Linux desktop for desktop users --- --- http://danharper.org/linuxdesktopblog/ ---

I understand both points of view; but for the common user, having connectivity included in the single programs will make it much more useful. If it would be included, people who do not like it can still use aconnect or even qjackctl. There will also be people out there who argue that there's no need of qjackctl because there are already CLI programs to do the job ;-) . Well, I'm (still) not that deeply involved in the linux audio business, so I cannot tell anything about LASH. Thanks for your thoughts & best regards ce

Yes, I think so too. Furthermore, I'd think about a softsynth which offers the available MIDI-ins via a popup menu (or similar). Does not waste too much space on the screen and is easier to use and understand than the external tools. The same maybe for programs which record audio. These could also offer a popup for available in- and outputs each. Currently, it's a sort of poker because I have two USB cards. Each session the cards will be registrated in a different order. So, a popup would make it easy to directly switch the card from within the the program (OK, I still didn't respect jack ;-). Unfortunately, I'm not a programmer, but maybe the base functionality could be put in common ALSA/Jack headers so the programmer of an application 'only' needs to create a popup and fill it with content. Best regards ce

Thanks for the hint. I'm on Gentoo here, and udev gets discussed in the list from time to time. On the other hand, I'm not a great linux guru; I'm proud to have successfully configured and built my own kernel matching my audio setup; but udev is more difficult because it will cause problems, namely with the NVidia drivers I use (and I shouldn't use because it's not free software, of course ;-). Thanks for the hint anyway. Best regards ce

Thanks for pointing this out. You're right, the nvidia problem has already be solved, but I fear further effects. Best regards ce