I can hear my guitar and record with Audacity, but when jackd enter into the escenario everything blows up. I read that nowadays almost any sound card will work with QJackCtl with the default options. I play with the parameters and sometimes jack refuse to start. With the default options on i can make it run, but i get no sound of the racks or guitar effects processors neither the guitar tuners that use jack takes the sound from the guitar. My line input is in capture via alsamixer, but still no luck. Any clue on this? I'm skipping steps?

Re: jackd + guitar: "timeouts and broken pipes"

hi iamgabo,I've been using jack for 5-6yrs now, so i might be able to help you. I also used to own the exact soundcard you are using and it does work with jackd (although, i tend to use proaudio cards, not consumer grade)... But first, you should provide more information, k?

- can you post ~/.jackdrc ? (with settings that are working in qjackctl/jackd)- what kernel are you using? (uname -a)- what hardware are you using (cpu, etc)

At first glance, the way you are trying to start jackd from the commandline looks wrong... It seems like you should be using a couple more switches than you are... For example, on my machine if i execute jackd from the commandline, it would look like this;

You'll notice i've given jackd realtime priorites (-R -P89), specify the device (-dfirewire), sampling rate (in my case, 96000), the frames/period length (-p256) and finally period/buffer length (-n3).... This config was created by qjackctl (with me setting it up via the gui), which is then saved in my home folder, as a hidden file ~/.jackdrc ... As far as 'playing with the settings & jackd not starting' - if you don't know what you are doing and use settings that don't work with your soundcard, yes, jackd will fail to start... That is why i think it might be best for you to start (and post here) a working config, then we can possibly figure out what might be adjusted best for your setup

Now, you've mentioned that with jackd running, you get no sound out of the rack, tuners, etc... 1st, you do not use ALSAMIXER for your inputs, when using jack. The only time you _might_ need to use alsamixer, is if your input is on 'mute', or you need to adjust the volume, itself... You need to connect everything using qjackctl. (it sounds to me like you didn't have anything connected properly, to actually produce sound - thus probably are skipping a step or two). But no worries, i can give a quick tutorial;

1. start jackd/qjackctl2. launch your app(s)3. Open qjackctl and open the connections window; You should see your h/w inputs and outs, as well as whatever apps you have launched.4. route your h/w input (ie: guitar) into your app, then connect your app to h/w output.

Here is a very quick video, showing me connecting my guitar to an app, then sending it's output to my system outputs;

sorry about no sound, but my mics are not here right now. but i tried my best to atleast point out that it was making sound, and how things relate by drawing circles with my pointer. - it should be somewhat obvious what i am doing though (just connecting/routing from input to app to speaker).

Re: jackd + guitar: "timeouts and broken pipes"

I think you may want to hit linuxaudio user list and possibly the jack-devel list for help.

I am not sure what your issue is and to be honest, since the end of last week have had zero time to look further into it.

I will say though, i find some of your configs to be a bit strange. For example; why do you have 2 different prio values for your @audio user?? ~ furthermore why do you have both limits.conf and 99-audio.conf editing the same things that only need to be defined in one or the other (not both with different values). Your .asoundrc also seems a bit odd, you don't even have jackd working and yet you've added jack-specific stuff (like alsa to jack - the old crappy method... ie: when you do get jackd running you should be looking at using zita-ajbridge, instead)...

I know for myself anyway, i never blindly add anything to a config - i always go step by step, making sure things are working properly on each step before going onto the next one (i also tend to keep working configs. ie: you said at one point qjackctl was working - it would have been nice if you had kept that config to work from)...out of curiosity, were you doing a lot of googling, seeing what other people have and then just copying and pasting bits from their configs?? (it kind of seems that way, although i could be wrong).

anyway, sorry for not getting back to you sooner - but i am swamped with work and preperations for the holidays. (sorry)

but again, if i were you i might hit both of the lists mentioned and ask for help there