From birger at birger.sh Wed Dec 23 10:08:19 2009 From: birger at birger.sh (birger) Date: Wed, 23 Dec 2009 11:08:19 +0100 Subject: [Fedora-music-list] Better information needed for noobs like me Message-ID: <1261562899.19844.16.camel@localhost.localdomain> Thank you all for a very nice initiative, getting all the great audio software working on a great linux distro. :-) I have browsed archives a few months back, and I have looked at the 'obvious' places. As a complete noob regarding studio work, mixers, effects and the whole 'audio workstation' thing I would love to see a little documentation holding my hand through the first configuration steps. Something that tells me how to do it for the latest Fedora release so I know I am not following incompatible howtos for different applications and different distros. I think something like this would work: - Basic setup (something like the articles at http://www.passback.org.uk/music/ updated for latest Fedora) - Simple special purpose workstations. Simple separate howtos building on the basic one but setting up simple environments for various purposes. Examples would be 'guitar utilities and effects processor', 'connecting a MIDI keyboard', and so on. Making sure everything gets done in a coherent fashion so bits and pieces can be mixed without running into problems later on. Some of the problems I have run into trying to master this are: guitarix not starting without qjackctl and arts installed. No messages until I ran from command line. Correct user configuration for jack (audio group membership). Choppy sound in tuxguitar, and no matter what I do I cannot seem to get completely rid of it. Probably because I don't quite understand what I am doing to fix it. There are so many options... I cannot find my USB headset in Jack audio. Is it possible to use it? It works fine in pulseaudio. These are issues that don't work out of the box yet, and I hope someone can write a little documentation on how to do it all the correct fedora way. :-) With kind regards birger From m.tarenskeen at zonnet.nl Wed Dec 23 10:46:36 2009 From: m.tarenskeen at zonnet.nl (Martin Tarenskeen) Date: Wed, 23 Dec 2009 11:46:36 +0100 (CET) Subject: [Fedora-music-list] Better information needed for noobs like me In-Reply-To: <1261562899.19844.16.camel@localhost.localdomain> References: <1261562899.19844.16.camel@localhost.localdomain> Message-ID: On Wed, 23 Dec 2009, birger wrote: > As a complete noob regarding studio work, mixers, effects and the whole > 'audio workstation' thing I would love to see a little documentation > holding my hand through the first configuration steps. Something that > tells me how to do it for the latest Fedora release so I know I am not > following incompatible howtos for different applications and different > distros. Even if this mailing list is a good initiative, there is not much traffic (yet). Hopefully this will change in the future ? My advice: also take a look at PlanetCCRMA. 1. Do a google search for "Planet CCRMA Fedora" or something like that and do some reading. 2. Install the Planet CCRMA yum repo. The Planet CCRMA website will tell you why and how. 3. Join also the planet-ccrma mailinglist. There are a lot of friendly and helpful people there, both experienced people and newbies sharing one passion: using Fedora to make music. Read and learn more about the real time kernel, about (not) using pulseaudio, alsa, jack, configurations, and things like that. For serious music making many Fedora musicians use a combination of the Fedora repositories, planet-ccrma, and rpmfusion-free/nonfree repositories. -- MT From birger at birger.sh Wed Dec 23 11:27:57 2009 From: birger at birger.sh (birger) Date: Wed, 23 Dec 2009 12:27:57 +0100 Subject: [Fedora-music-list] Better information needed for noobs like me In-Reply-To: References: <1261562899.19844.16.camel@localhost.localdomain> Message-ID: <1261567677.27398.15.camel@localhost.localdomain> On Wed, 2009-12-23 at 11:46 +0100, Martin Tarenskeen wrote: > > Even if this mailing list is a good initiative, there is not much traffic > (yet). Hopefully this will change in the future ? I really hope so. Get as many packages as possible properly orchestrated and create a good scene where both developers and musicians can find what they need. :-) I can fully understand the need for getting apps over to the more well-known fedora repos before anything else, but at least to me it looks like there are so many packages now that it may be time to look at the rest. Create a 'home' for something that may grow into a separate spin some day. Forums/wiki? At least some informational pages that are current with respect to supported fedora releases. > > My advice: also take a look at PlanetCCRMA. > 1. Do a google search for "Planet CCRMA Fedora" or something like that and > do some reading. I did, and there were lots of talk about installing ccrma low-tatency kernels and other mods to fedora 7 to 10. Nothing about 11 or 12. > 2. Install the Planet CCRMA yum repo. The Planet CCRMA website will tell > you why and how. Again, no links to repos for 11 and 12. I feel pretty safe installing packages from rpmfusion. Not so sure about installing packages from a ccrma F10 repo on my work laptop... > 3. Join also the planet-ccrma mailinglist. There are a lot of friendly and > helpful people there, both experienced people and newbies sharing one > passion: using Fedora to make music. I'll have a look at the lists. When I didn't find any info for Fedora 12 on the web pages I kind of stumbled on to look elsewhere. Perhaps that was a mistake. > Read and learn more about the real time kernel, about (not) using > pulseaudio, alsa, jack, configurations, and things like that. Pulseaudio has changed a bit since F10 hasn't it? Again, I would like to see how bits fit together in the supported Fedora releases. That would make it less likely for newcomers to [beep] up ther config completely trying to follow outdated guides... > For serious music making many Fedora musicians use a combination of the > Fedora repositories, planet-ccrma, and rpmfusion-free/nonfree > repositories. I have 3 kids with guitars. I have a keyboard somewhere. I need to learn how to set up the software for them :-D Move over Jonas Brothers... The future is getting ready. birger From oget.fedora at gmail.com Wed Dec 23 12:46:40 2009 From: oget.fedora at gmail.com (Orcan Ogetbil) Date: Wed, 23 Dec 2009 07:46:40 -0500 Subject: [Fedora-music-list] Better information needed for noobs like me In-Reply-To: <1261562899.19844.16.camel@localhost.localdomain> References: <1261562899.19844.16.camel@localhost.localdomain> Message-ID: On Wed, Dec 23, 2009 at 5:08 AM, birger wrote: > Thank you all for a very nice initiative, getting all the great audio > software working on a great linux distro. :-) > > I have browsed archives a few months back, and I have looked at the > 'obvious' places. > > As a complete noob regarding studio work, mixers, effects and the whole > 'audio workstation' thing I would love to see a little documentation > holding my hand through the first configuration steps. Something that > tells me how to do it for the latest Fedora release so I know I am not > following incompatible howtos for different applications and different > distros. > > I think something like this would work: > ?- Basic setup (something like the articles at > http://www.passback.org.uk/music/ updated for latest Fedora) > > ?- Simple special purpose workstations. Simple separate howtos building > on the basic one but setting up simple environments for various > purposes. Examples would be 'guitar utilities and effects processor', > 'connecting a MIDI keyboard', and so on. Making sure everything gets > done in a coherent fashion so bits and pieces can be mixed without > running into problems later on. > > > Some of the problems I have run into trying to master this are: > guitarix not starting without qjackctl and arts installed. No messages > until I ran from command line. > Correct user configuration for jack (audio group membership). > Choppy sound in tuxguitar, and no matter what I do I cannot seem to get > completely rid of it. Probably because I don't quite understand what I > am doing to fix it. There are so many options... > I cannot find my USB headset in Jack audio. Is it possible to use it? It > works fine in pulseaudio. > > These are issues that don't work out of the box yet, and I hope someone > can write a little documentation on how to do it all the correct fedora > way. :-) > > > With kind regards > birger > Hi, Martin gave a good summary. Let me add my 2 cents into the subject. (Well it will be more like 10 cents :)) * The documentation is possibly what we lack most for the time being. Feel free to help us out if you have time and will to do so. We have started a page in the Fedora wiki a while ago https://fedoraproject.org/wiki/AudioCreation for listing our audio creation type software (Fedora only) but yet it needs a lot more work. * PlanetCCRMA is ready for F-11 and F-12. See for instance: http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/12/i386/ http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/12/x86_64/ You probably need the planetccrma-repo package from that repo. (Be careful about the architecture) * Install the multimedia-menus package yum install multimedia-menus This is new for Fedora 12. It will create submenus in your Multimedia (Sound&Video in Gnome) menu and sort audio/video related applications so you can find things easier. * For guitarix, after you filed the bug, I saw that the application looks for qjackctl and if it is missing it looks for a ~/.jackdrc file in your home directory. If it cannot find either of them, it fails. The ~/.jackdrc is always there when you have a working jack setup. I didn't think about the case where someone would start guitarix on a fresh installation, which hasn't run jackd yet. I will let upstream developer know about the issue. Normally, guitarix shouldn't need qjackctl. But I'll add that dependency today. * Check out the updates-testing repository frequently. New updates usually go there first. Typically they stay there for 2 weeks and if no bugs are reported they go to stable. For example, Martin is a very good tester and I appreciate his contributions. But of course, having more testers won't hurt :) * Pulseaudio is pain. As a Fedora developer, normally I shouldn't recommend anything about not using it. But it is pain, at least for me. It blew up my harddrive at some point and I stopped using it since. Although pulseaudio is supposed to play nice with jack these days, I am not planning to support it myself. As audio creation people, we want control over our sound hardware. Hiding many of the sound card's controls is a "feature" of pulseaudio for the sake of simplicity. And this is against my use case. At the end of the day, it is your choice what sound servers you want to use. I just want you to know that one of the primary audio creation packagers of Fedora does not have time and will to support pulseaudio. * Look at /usr/share/doc/jack-audio-connection-kit-0.118.0/README.Fedora Part of it is obsolete information by now. But it will get you started. Make sure you add your user to the correct groups * For tuxguitar, please try the version from updates-testing. It should sort things out. There are many independent ways to get good sound out of it. In the version in updates-testing, I made it default to fluidsynth/fluid soundfont combination. It is supposed to work out of the box now. (Alternatively, you can use gervill (java sound API), or forward the midi output of tuxguitar to qjackctl, and connect it to qsynth... There are still more ways to do it.) * qjackctl and qsynth are your friends. * For recording&mixing, ardour is still the best in my opinion. And we have a bunch of lv2 and ladspa plugins for sound effects. For drumming, I primarily use hydrogen. And with jack, you can hook up every application that uses jack to each other rather easily. Push the Connect button on qjackctl. * As Martin said, PlanetCCRMA list is a good list to subscribe. It is a lot more active than this one. And we have Fernando, the Great there :) Unfortunately, I am leaving tomorrow, and I will be away for a break until mid January. You folks will probably not hear from me during this period. I have a couple updates that I will push to the testing today. And they will stay there until I get back. I don't want to push something broken into stable because I won't have time to fix it. I hope you figure your way out by the time I am back. Cheers and welcome, Orcan From mschwendt at gmail.com Wed Dec 23 13:15:46 2009 From: mschwendt at gmail.com (Michael Schwendt) Date: Wed, 23 Dec 2009 14:15:46 +0100 Subject: [Fedora-music-list] Better information needed for noobs like me In-Reply-To: References: <1261562899.19844.16.camel@localhost.localdomain> Message-ID: <20091223141546.692739f6@gmail.com> On Wed, 23 Dec 2009 07:46:40 -0500, Orcan wrote: > * Pulseaudio is pain. As a Fedora developer, normally I shouldn't > recommend anything about not using it. But it is pain, at least for > me. As a side-note, it has started to burn Ubuntu users, too. It will be interesting to see whether that will result in any fixes. From birger at birger.sh Wed Dec 23 13:41:24 2009 From: birger at birger.sh (birger) Date: Wed, 23 Dec 2009 14:41:24 +0100 Subject: [Fedora-music-list] Better information needed for noobs like me In-Reply-To: References: <1261562899.19844.16.camel@localhost.localdomain> Message-ID: <1261575684.27398.34.camel@localhost.localdomain> On Wed, 2009-12-23 at 07:46 -0500, Orcan Ogetbil wrote: > * The documentation is possibly what we lack most for the time being. > Feel free to help us out if you have time and will to do so. We have > started a page in the Fedora wiki a while ago > https://fedoraproject.org/wiki/AudioCreation > for listing our audio creation type software (Fedora only) but yet it > needs a lot more work. I will be happy to write a little once I feel that I know what I am writing about :-D > > * PlanetCCRMA is ready for F-11 and F-12. See for instance: > http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/12/i386/ > http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/12/x86_64/ > You probably need the planetccrma-repo package from that repo. (Be > careful about the architecture) They have just forgotten to mention it on the web page? I only found links to the repo packages for F7 to F10... I'll add the ccrma repos if I bump into something that I want from there. For now it seems like everything I have needed has migrated over to rpmfusion. > * Install the multimedia-menus package Already done. :-) > * For guitarix, after you filed the bug, I saw that the application > looks for qjackctl and if it is missing it looks for a ~/.jackdrc file > in your home directory. If it cannot find either of them, it fails. > The ~/.jackdrc is always there when you have a working jack setup. I > didn't think about the case where someone would start guitarix on a > fresh installation, which hasn't run jackd yet. :-D That explains a lot. I guess this may bite more packages if they are the first jack app to get started. > * Check out the updates-testing repository frequently. New updates > usually go there first. Typically they stay there for 2 weeks and if > no bugs are reported they go to stable. For example, Martin is a very > good tester and I appreciate his contributions. But of course, having > more testers won't hurt :) I have a desktop PC at work running rawhide, so I am used to testing :-) > * Pulseaudio is pain. As a Fedora developer, normally I shouldn't > recommend anything about not using it. I understand the dilemma. What are the options for having jack and pulse coexist? I will not give up pulseaudio on my work PC, but I guess that in the end I will need a dedicated PC for music. Currently I have pulseaudio running with my USB headset as default output since jack doesn't see it yet. Jack then gets the soundcard. Both seem happy :-) > * Look at /usr/share/doc/jack-audio-connection-kit-0.118.0/README.Fedora Will have a look. :-) > * For tuxguitar, please try the version from updates-testing. Will definitely do. I tried getting it connected to jack, but it didn't seem to react to anything I did in qjackctl so I guess it was still talking to some other driver. > * qjackctl and qsynth are your friends. Must look at qsynth then. Thanks for the tip. > * For recording&mixing, ardour is still the best in my opinion. Great. I wasn't looking forward to wading through the app list to find what I needed for mixing. > * As Martin said, PlanetCCRMA list is a good list to subscribe. It is > a lot more active than this one. And we have Fernando, the Great there > :) I will definitely have to add myself there even if I don't plan to use the repos yet. :-) I will play around with all this new knowledge and see if I can find a suitable PC after the holidays. In the meantime, I'll just wish everybody here a merry christmas. From dtimms at iinet.net.au Wed Dec 23 13:49:01 2009 From: dtimms at iinet.net.au (David Timms) Date: Thu, 24 Dec 2009 00:49:01 +1100 Subject: [Fedora-music-list] Better information needed for noobs like me In-Reply-To: <1261567677.27398.15.camel@localhost.localdomain> References: <1261562899.19844.16.camel@localhost.localdomain> <1261567677.27398.15.camel@localhost.localdomain> Message-ID: <4B321FCD.8090800@iinet.net.au> On 12/23/2009 10:27 PM, birger wrote: > I have 3 kids with guitars. I have a keyboard somewhere. I need to > learn how to set up the software for them :-D Move over Jonas > Brothers... The future is getting ready. You mightn't think so, but even 'beginners' can be good documentation writers. Put down what steps it takes, and how it differs from earlier material (that you reference). The fact that it's written by a beginner could help it to be more easily used by other beginners... The wiki suggestion is good. I think the key is to try to write fairly short, task specific wiki pages, and then some fedoraproject process/tools can convert the individual pages into a spruced up, conforming document. See the Fedora 12 user guide [1], or pdf [2], and the source for that eg [3]. I think that you do need to sign a contributor license agreement before you can edit the fedoraproject wiki. This basically says that you won't post copyrighted material, and that you are making your contribution available as open content. One limitation of using fedora's wiki is you might not be able to directly link to troublesome, out of fedora, sites or packages. A first step would be to develop a table of contents in the wiki, to try to break the installation of audio tools into specific areas, and then break those tasks down into smaller tasks. eg. Working with MIDI and so on. [1] [2] [3] David. From oget.fedora at gmail.com Wed Dec 23 14:09:40 2009 From: oget.fedora at gmail.com (Orcan Ogetbil) Date: Wed, 23 Dec 2009 09:09:40 -0500 Subject: [Fedora-music-list] Better information needed for noobs like me In-Reply-To: <1261575684.27398.34.camel@localhost.localdomain> References: <1261562899.19844.16.camel@localhost.localdomain> <1261575684.27398.34.camel@localhost.localdomain> Message-ID: On Wed, Dec 23, 2009 at 8:41 AM, birger wrote: > On Wed, 2009-12-23 at 07:46 -0500, Orcan Ogetbil wrote: >> * The documentation is possibly what we lack most for the time being. >> Feel free to help us out if you have time and will to do so. We have >> started a page in the Fedora wiki a while ago >> https://fedoraproject.org/wiki/AudioCreation >> for listing our audio creation type software (Fedora only) but yet it >> needs a lot more work. > > I will be happy to write a little once I feel that I know what I am > writing about :-D > In a sense, it is good to have a beginner's documentation written by a beginner. As there are certain things which you only do once when you install a new system, it is easy for many of us to forget some of these steps for the documentation Thanks, Orcan From nando at ccrma.Stanford.EDU Sun Dec 27 19:11:45 2009 From: nando at ccrma.Stanford.EDU (Fernando Lopez-Lezcano) Date: Sun, 27 Dec 2009 11:11:45 -0800 Subject: [Fedora-music-list] Better information needed for noobs like me In-Reply-To: <1261575684.27398.34.camel@localhost.localdomain> References: <1261562899.19844.16.camel@localhost.localdomain> <1261575684.27398.34.camel@localhost.localdomain> Message-ID: <1261941105.2399.18.camel@localhost.localdomain> On Wed, 2009-12-23 at 14:41 +0100, birger wrote: > > > > * PlanetCCRMA is ready for F-11 and F-12. See for instance: > > http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/12/i386/ > > http://ccrma.stanford.edu/planetccrma/mirror/fedora/linux/planetccrma/12/x86_64/ > > You probably need the planetccrma-repo package from that repo. (Be > > careful about the architecture) > > They have just forgotten to mention it on the web page? I only found > links to the repo packages for F7 to F10... I'll add the ccrma repos if > I bump into something that I want from there. "They" is just "me" and I did not have time to update the web site before I left on vacation (I never recommended fc11 as it had a basic bug with the alsa sequencer not being loaded that took a _full_ release - 6 months! - to get fixed). Fc12 is basically there, there's basically just a few meta-packages missing. Sorry about the inconvenience... hope you find something useful there... -- Fernando From nando at ccrma.Stanford.EDU Sun Dec 27 19:15:10 2009 From: nando at ccrma.Stanford.EDU (Fernando Lopez-Lezcano) Date: Sun, 27 Dec 2009 11:15:10 -0800 Subject: [Fedora-music-list] Better information needed for noobs like me In-Reply-To: <20091223141546.692739f6@gmail.com> References: <1261562899.19844.16.camel@localhost.localdomain> <20091223141546.692739f6@gmail.com> Message-ID: <1261941310.2399.25.camel@localhost.localdomain> On Wed, 2009-12-23 at 14:15 +0100, Michael Schwendt wrote: > On Wed, 23 Dec 2009 07:46:40 -0500, Orcan wrote: > > > * Pulseaudio is pain. As a Fedora developer, normally I shouldn't > > recommend anything about not using it. But it is pain, at least for > > me. > > As a side-note, it has started to burn Ubuntu users, too. It will > be interesting to see whether that will result in any fixes. A lot of work on it has happened and it is getting better, but (sorry, no personal attack to the very busy developers meant here) there seems to be some sort of reality negation field surrounding it when more advanced users miss features that were there before. The need is there, apparently there are not enough of us (users that need better control of the audio configuration through the alsa mixer - default answer is "use alsamixer") to make any difference. In fc12 it does play nice with a properly packaged jack so that is very good (in fc11 that only happens if you use the Planet CCRMA jackd as it has a perl wrapper script that deals with pulse properly - bugs in pulse make the dbus interface not work when trying to release the card). Maybe in time... -- Fernando From nando at ccrma.Stanford.EDU Sun Dec 27 19:47:05 2009 From: nando at ccrma.Stanford.EDU (Fernando Lopez-Lezcano) Date: Sun, 27 Dec 2009 11:47:05 -0800 Subject: [Fedora-music-list] Better information needed for noobs like me In-Reply-To: <1261941310.2399.25.camel@localhost.localdomain> References: <1261562899.19844.16.camel@localhost.localdomain> <20091223141546.692739f6@gmail.com> <1261941310.2399.25.camel@localhost.localdomain> Message-ID: <1261943225.3437.7.camel@localhost.localdomain> On Sun, 2009-12-27 at 11:15 -0800, Fernando Lopez-Lezcano wrote: > On Wed, 2009-12-23 at 14:15 +0100, Michael Schwendt wrote: > > On Wed, 23 Dec 2009 07:46:40 -0500, Orcan wrote: > > > > > * Pulseaudio is pain. As a Fedora developer, normally I shouldn't > > > recommend anything about not using it. But it is pain, at least for > > > me. > > > > As a side-note, it has started to burn Ubuntu users, too. It will > > be interesting to see whether that will result in any fixes. > > A lot of work on it has happened and it is getting better, but (sorry, > no personal attack to the very busy developers meant here) there seems > to be some sort of reality negation field surrounding it when more > advanced users miss features that were there before. Not a fair assessment, I guess. >From the outside it looks like there is an absolute focus on making things work for the "average or low end user", simplifying the exposed interface to the absolute minimum possible. Anything that might distract or divert resources from that goal is just ignored. -- Fernando From birger at birger.sh Sun Dec 27 22:40:00 2009 From: birger at birger.sh (birger) Date: Sun, 27 Dec 2009 23:40:00 +0100 Subject: [Fedora-music-list] Better information needed for noobs like me In-Reply-To: <1261941105.2399.18.camel@localhost.localdomain> References: <1261562899.19844.16.camel@localhost.localdomain> <1261575684.27398.34.camel@localhost.localdomain> <1261941105.2399.18.camel@localhost.localdomain> Message-ID: <1261953600.1849.8.camel@localhost.localdomain> On Sun, 2009-12-27 at 11:11 -0800, Fernando Lopez-Lezcano wrote: > "They" is just "me" and I did not have time to update the web site > before I left on vacation (I never recommended fc11 as it had a basic > bug with the alsa sequencer not being loaded that took a _full_ release > - 6 months! - to get fixed). Fc12 is basically there, there's basically > just a few meta-packages missing. That explains a lot. In hindsight it is of course easy to recommend that the reason for omitting F11 should have been mentioned on that page so the project didn't seem like it had been without maintenance for 6 months. There are always a lot of dead or dying branches in the open source world and it is very easy to dismiss anything that looks stale and just search elsewhere. But then of course "Hindsight is foresight that happens too late". It isn't easy to see that when you work on the project and know it's alive. :-) birger From birger at birger.sh Sun Dec 27 22:59:14 2009 From: birger at birger.sh (birger) Date: Sun, 27 Dec 2009 23:59:14 +0100 Subject: [Fedora-music-list] Better information needed for noobs like me In-Reply-To: <1261941310.2399.25.camel@localhost.localdomain> References: <1261562899.19844.16.camel@localhost.localdomain> <20091223141546.692739f6@gmail.com> <1261941310.2399.25.camel@localhost.localdomain> Message-ID: <1261954754.1849.28.camel@localhost.localdomain> On Sun, 2009-12-27 at 11:15 -0800, Fernando Lopez-Lezcano wrote: > On Wed, 2009-12-23 at 14:15 +0100, Michael Schwendt wrote: > > On Wed, 23 Dec 2009 07:46:40 -0500, Orcan wrote: > > > > > * Pulseaudio is pain. As a Fedora developer, normally I shouldn't > > > recommend anything about not using it. But it is pain, at least for > > > me. > > > > As a side-note, it has started to burn Ubuntu users, too. It will > > be interesting to see whether that will result in any fixes. > > A lot of work on it has happened and it is getting better, but (sorry, > no personal attack to the very busy developers meant here) there seems > to be some sort of reality negation field surrounding it when more > advanced users miss features that were there before. I guess it's like a lot of open source projects; If you want to see features that are wanted only by a fraction of the community you have to make it happen yourself. In some way or another. Code it yourself, or advocate it until some developer does it for you. The best is of course to show how it integrates with something a bigger userbase wants so the core developers of the project do it. > The need is there, apparently there are not enough of us (users that > need better control of the audio configuration through the alsa mixer - > default answer is "use alsamixer") to make any difference. For pulseaudio there are some confusing dependencies on alsa tools when you step outside the very narrow track. I certainly hope some more advanced options will get built into pulse tools. On the other hand, F12 has become extremely user friendly for stuff like adding a USB headset, bluetooth headset, USB speakers and so on. For ordinary users it has the smoothest handling of such devices I have ever seen. That is the main focus for pulse. Have you ever tried adding a bluetooth headset to vista? > In fc12 it does play nice with a properly packaged jack so that is very > good (in fc11 that only happens if you use the Planet CCRMA jackd as it > has a perl wrapper script that deals with pulse properly - bugs in pulse > make the dbus interface not work when trying to release the card). I would like to know more about how to set up pulse and jack properly on F12. The definitive guide to what can be done and how well it works. :-) At the moment I stop everything that uses sound, then start jack and let it take over my soundcard. Pulse gets switched to a USB headset that jack doesn't want to see. This way pulse apps and jack apps seem to coexist nicely. With pulseaudio-module-jack I guess I could integrate them and let either one own the hardware and the other one plug in. Letting pulseaudio own the hardware and use it as a sink for jack sounds like the easiest solution. Perhaps jack will be able to use my USB headset that way. Will this kind of setup hurt latency badly? birger From nando at ccrma.Stanford.EDU Mon Dec 28 02:51:05 2009 From: nando at ccrma.Stanford.EDU (Fernando Lopez-Lezcano) Date: Sun, 27 Dec 2009 18:51:05 -0800 Subject: [Fedora-music-list] Better information needed for noobs like me In-Reply-To: <1261954754.1849.28.camel@localhost.localdomain> References: <1261562899.19844.16.camel@localhost.localdomain> <20091223141546.692739f6@gmail.com> <1261941310.2399.25.camel@localhost.localdomain> <1261954754.1849.28.camel@localhost.localdomain> Message-ID: <1261968665.5796.21.camel@localhost.localdomain> On Sun, 2009-12-27 at 23:59 +0100, birger wrote: > On Sun, 2009-12-27 at 11:15 -0800, Fernando Lopez-Lezcano wrote: > > On Wed, 2009-12-23 at 14:15 +0100, Michael Schwendt wrote: > > > On Wed, 23 Dec 2009 07:46:40 -0500, Orcan wrote: > > > > > > > * Pulseaudio is pain. As a Fedora developer, normally I shouldn't > > > > recommend anything about not using it. But it is pain, at least for > > > > me. > > > > > > As a side-note, it has started to burn Ubuntu users, too. It will > > > be interesting to see whether that will result in any fixes. > > > > A lot of work on it has happened and it is getting better, but (sorry, > > no personal attack to the very busy developers meant here) there seems > > to be some sort of reality negation field surrounding it when more > > advanced users miss features that were there before. > > I guess it's like a lot of open source projects; If you want to see > features that are wanted only by a fraction of the community you have to > make it happen yourself. In some way or another. Code it yourself, or > advocate it until some developer does it for you. Correct, of course (the "show me the code" mantra that drives open source). At some point even that does not work. If the developers have a vision that is not compatible with yours at a basic level there is no option. What I see happening is that the interface is being simplified to the lowest possible number of controls so that it is "simple to use". Anything else is/has been stripped out of the programs that control pulse. And by that I mean "gone and never coming back". Any suggestion to bring that back and enable it under an "expert" mode is shot down very fast. Eventually the argument boils down to "use alsamixer" if you need that functionality. I have read some of those threads (there are plenty) and participated in some and at some point you just give up. There is no consideration to more advanced users at all (that _I_ can see). [MUNCH] > > In fc12 it does play nice with a properly packaged jack so that is very > > good (in fc11 that only happens if you use the Planet CCRMA jackd as it > > has a perl wrapper script that deals with pulse properly - bugs in pulse > > make the dbus interface not work when trying to release the card). > > I would like to know more about how to set up pulse and jack properly on > F12. I don't think there's anything to set up (I imagine that depends on how you want to use the different programs). When starting jack it talks to pulse and aquires the soundcard. All current streams going to pulse get paused and they resume when jack exists. At least that is the behavior I have seen in my tests. > The definitive guide to what can be done and how well it works. :-) > > At the moment I stop everything that uses sound, then start jack and let > it take over my soundcard. Pulse gets switched to a USB headset that > jack doesn't want to see. Hmmm, not too good I guess. Pulse should not be guessing as to where to send things. Maybe that is configurable. > This way pulse apps and jack apps seem to > coexist nicely. With pulseaudio-module-jack I guess I could integrate > them and let either one own the hardware and the other one plug in. > Letting pulseaudio own the hardware and use it as a sink for jack sounds > like the easiest solution. Perhaps jack will be able to use my USB > headset that way. Will this kind of setup hurt latency badly? Yes, of course. It depends on what you want to do with jack, for anything worthwhile from my point of view jack has to control the soundcard directly. Then you can load the jack sink/source into pulse and use that to direct oulse streams to jack. -- Fernando From birger at birger.sh Mon Dec 28 06:39:59 2009 From: birger at birger.sh (birger) Date: Mon, 28 Dec 2009 07:39:59 +0100 Subject: [Fedora-music-list] Better information needed for noobs like me In-Reply-To: <1261968665.5796.21.camel@localhost.localdomain> References: <1261562899.19844.16.camel@localhost.localdomain> <20091223141546.692739f6@gmail.com> <1261941310.2399.25.camel@localhost.localdomain> <1261954754.1849.28.camel@localhost.localdomain> <1261968665.5796.21.camel@localhost.localdomain> Message-ID: <1261982399.1849.44.camel@localhost.localdomain> On Sun, 2009-12-27 at 18:51 -0800, Fernando Lopez-Lezcano wrote: pulse ought to follow the general gnome guidelines. simple user interface as today, but add all the advanced bells and whistles in a manner that most users won't even see. :-) How to make that happen? Obviously the mindset of pulse developers has to be turned around a bit, and that is rather difficult. One method that has worked for me earlier is to show the right people at Red Hat that there is a need for a certain change in Fedora as it would benefit RHEL from a business standpoint. I cannot see how that can be applied to audio, but perhaps someone here can come up with a nice tactic? > Hmmm, not too good I guess. Pulse should not be guessing as to where to > send things. Maybe that is configurable. Sorry, I didn't explain that well enough. I switch pulse to the USB headset on purpose to keep sound working in the pulse apps. As you noted, there is no sound from pulse apps otherwise as long as jack owns the audio hardware. > > > This way pulse apps and jack apps seem to > > coexist nicely. With pulseaudio-module-jack I guess I could integrate > > them and let either one own the hardware and the other one plug in. > > Letting pulseaudio own the hardware and use it as a sink for jack sounds > > like the easiest solution. Perhaps jack will be able to use my USB > > headset that way. Will this kind of setup hurt latency badly? > > Yes, of course. It depends on what you want to do with jack, for > anything worthwhile from my point of view jack has to control the > soundcard directly. Then you can load the jack sink/source into pulse > and use that to direct oulse streams to jack. I have installed the module. No new jacks that I can see immediately. I'll try a reboot and then play around a little bit. I anticipate a slow day at work. :-) birger