Hi again, I think you fell for "reply to munging": you did reply only to me instead of the list. I've CCed it on this reply. I'm not using Ubuntu but here are few hints that may apply to it as well: * run 'gstreamer-properties' from a console (it might be available from the gnome-menu as well) to configure the default desktop-audio device. You need to install 'gstreamer-jack' (maybe called 'gstreamer-plugins-bad') package. After starting JACK, Music Playback (rhythmbox, totem, etc) should now go to your Delta Audiophile. mplayer can be configured to use JACK by default with a ~/.mplayer/config * There are some tricks to pipe ALSA applications' audio through JACK: A) http://www.alsa-project.org/main/index.php/Asoundrc#JACK_plugin does not reliably work with all ALSA applications, but gives sound to skype and flash and it is easy to set up. or B) http://alsa.opensrc.org/index.php/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge works very well, but is [still] tricky to setup up and consumes a bit more CPU. Using one of those options, it is certainly possible to also configure Orca to go via JACK, but I see a few problems which may not easily solved by a GNU/Linux Newbie, mostly related to the auto-start procedure during boot: first JACK, (then possibly alsa_in/out for (B) and finally Orca's speech-system. I suggest you start a new thread on the list "Orca Speech Dispatcher and JACK" - other's may have solved this issue. Even though you said you want to do _everything_ with the Delta card, I suggest to re-evaluate that idea for the following reasons: - simplicity and robustness of setup (also during updates) - volume-control: you may want to have different levels for the speech-system and music-production. - no-interference when multi-tasking: I'd be annoyed when quickly reading mail in the middle of a music-production a speech dispatcher pipes into my JACK session and blasts out trough the monitor speakers. just my 2c, robin On 10/01/10 20:14, Edu Camargo wrote: > Guys, > > All I have to say is thank you for all the feedback. I really should be > done a lot of questions in a split form, but I got so anxious about the > new perspective that Linux seems to bring in a few moments that I > wrapped all at once. > > In fact I went in favor of plain Ubuntu because I couldn't figure out a > way to have screen reader assistance during the Ubuntu Studio instalation. > > Actually removing pulseaudio did the trick although I lose some aspects > of the Ubuntu, E.G. sound preferences. But I remember that there should > be a way to use this particular applet without the pulse's presence. I > just can't remember where I found information on how to apply this "patch". > > But Robin pointed me a thing that might make me investigate a bit more, > because my idea was to live only with the Delta, for any purpose, > including listening to music, which of course I prefer doing with Delta, > with my beloved MDR7506 plugged on my console or a pair of Yamaha > monitor speakers. The Speech Dispatcher, (a speech system that is used > by Orca), supports only ALSA, OSS, NAS and pulse for sound output. By > the way, ALSA is recommended by the Speech Dispatcher configuration. > Needless to say that Speech Dispatcher opperates faster with ALSA than > with pulse. Since Jack requires exclusive access to the device, > something tells me that I'll have to use Orca and many other > applications via the on-board sound and use the Audiophile only for > production purposes, right? > > As mentioned, I really wanted to stick fully with the Delta, but if this > ain't possible, what should I configure to make ALSA use the on-board > audio and leave room for Jack in the Audiophile? (I hope I have a way > around because I wouldn't love to sacrifice audio quality on my dayly > computer usage). > > But thanks so much for all the feedback. This is what makes the > diference. The Linux world is really new to me, and I am glad to learn > that there are always people looking forward to offer alternatives that > oppose to expensive and proprietary means of production. I hope to have > a great story to tell to the world. > > And Robin, no problem. Of course top-posting facilitates reading > because you just move the cursor and reads the answer without scrolling, > but this ain't a problem to me. In-line reply doesn't bother me. It > helps to keep threads comprehensive for people who might have lost the > course of the road for a reason. > > Peace and music, > > > Edu Camargo. > > > -------------------------------- > > On 30-09-2010 08:17, Robin Gareus wrote: >> Hi Edu, >> >> I did not know that there's gtk graphical support for screen-readers >> these days. and that thay're good enough to even work wit complex >> applications such as ardour. Wow, That's amazing. >> >> If you like the console: >> http://ltsb.sourceforge.net/ is a "guide is inteded for blind, tuxish >> musicians and all others, who simply like the console." It may be a bit >> outdated though. >> >> As for your sound-issue: It _may_ be pulseaudio blocking the card. >> Edit /etc/pulse/client.conf or $HOME/.pules/client.conf and set >> autospawn = no >> and simply stick to use JACK. >> >> jackd requires exclusive access to the soundcard. So if the system is >> playing sound (I guess your voice-speak accessibility system) JACK can >> not use that card. >> >> If the text-to-voice application supports JACK you could launch jackd >> before that, but you're probably better off using the built-in soundcard >> for that and use jack only for for audio-engineering. >> >> It looks like your main problem boils down to wrong numbering of the >> sound-cards. This has been a long standing issue on Linux and there are >> a few ways around it: >> >> 1) If the numbering is consistent on each boot: you can simply not care >> about the number and configure all audio-software to use whatever ID. >> >> 2) the "modern way" using udev: http://alsa.opensrc.org/index.php/Udev >> >> 3) the "old way" using module load options: >> >> http://www.mail-archive.com/alsa-user@xxxxxxxxxxxxxxxxxxxxx/msg07809.html >> >> >> It may also help to split up your many questions into several emails to >> get better answers. eg. sound-card numbering, jackd startup from the >> console, and last but not least: recommended applications for whatever >> audio task you're up to. >> >> You may also find a lot of answers to those already via google or the >> archive of this list. >> >> best, >> robin >> >> PS. As far as I know, you are not the only Linux-Audio-User on this list >> who needs to rely on a screen-reader. Others may be on holiday or are >> just busy. >> >> PPS. I have top-posted because I assumed that's easier for both >> screen-readers and text-to-speech synths. >> The preferred method on this list is to use inline-replys or >> bottom-posting. I've wondered a few times if this is a problem with >> accessibility in general. Care to enlighten me? >> >> >> On 09/28/10 18:38, Edu Camargo wrote: >> >>> Hello guys, peace and music to all of you. >>> >>> Here's my story: >>> >>> I won a laptop some months ago, and with the Windows 7's arrival I >>> decided to try a Linux distro, more precisely Ubuntu, for its facility >>> and also, for the Gnome's accessibility from the CD boot to the final >>> instalation, which is an enormous advantage for us blind users, when we >>> want to setup a computer independently. I use computer for ten years and >>> it's good to see Linux and Apple's developers going towards facilities >>> to everybody... I've mentioned Apple because seems that Apple's >>> Voiceover can also be accessed even during the instalation according to >>> an article I've read on the web. >>> >>> Anyway, I've tested Ubuntu 9.10 and it wasn't that good because it had >>> some audio issues including with the Orca's usage, so I decided to wait, >>> and soon came Ubuntu 10.04 and, for the moment, it took all the chances >>> of Windows getting wrapped into my laptop. Besides, with a few, very few >>> programs I can do all the things I need to do... Of course things may >>> change in the future, but it's good to work in a system so light, >>> secure, and it's even better to find a supportive comunity. >>> >>> Last saturday I decided to move my desktop computer, an Athlon X2 4000, >>> Asus M2N-SLI, 2GB of RAM with two hard disks, to Ubuntu 10.04.1 64bits >>> version. I really got amazed with the performance, even the Orca screen >>> reader is more responsive with the 64bits version. I'm interested in >>> audio production using Linux, so I need clues. >>> >>> I have two audio cards, the mother board's built-in and the Delta >>> Audiophile 2496, the ladder one detected as card 0, wich according to my >>> understanding is the default card. But I was unable to get output from >>> the Delta, so I had to select the built-in sound card as my default >>> output for the moment. Then, after further reading I could install jackd >>> and Ardour for a test, and with Ardour I get all the feedback I need >>> while playing sounds through Delta. But of course, my goall is to make >>> the system work fully with the Delta. >>> >>> What should I do to build a stable audio set using Ubuntu? And of >>> course, what are the must have programs? Since Orca is GTK-based, I'd >>> prefer to stay far from KDE due to accessibility issues. The thing I've >>> loved about Ardour is that I'm able to control jack without having to >>> access the jack GUI, which is KDE. But of course, if I can adjust >>> settings by editing configuration files it'll be better. >>> >>> Any tips on how to make things work decently will be very appreciated. >>> >>> Sorry for some obvious questions that I might have asked, and sorry for >>> the book. >>> >>> Thanks in advance for all the input. >>> >>> Warm regards from São Paulo, Brazil. >>> >>> Edu Camargo. >>> >>> >>> _______________________________________________ >>> Linux-audio-user mailing list >>> Linux-audio-user@xxxxxxxxxxxxxxxxxxxx >>> http://lists.linuxaudio.org/listinfo/linux-audio-user >>> > _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
