hearingaid-prototype icon indicating copy to clipboard operation
hearingaid-prototype copied to clipboard

jackd will not start

Open mischa1967 opened this issue 4 years ago • 4 comments

Hi,

I've been trying to get this project up and running for two days. Unfortunately I can't get the jackd started. There is always the error message: JackAudioDriver::ProcessAsync: read error, stopping...

I tried both, the complete image and an installation via stretch lite. In both cases the same result. The sound card itself is fine and also the microphone amplifiers work.

Anyone else have an idea?

Thank you Henri

mischa1967 avatar Sep 11 '19 20:09 mischa1967

Hi,

do you employ exactly the recommended hardware (including model versions)? Above all, do you use a Raspberry Pi 3 model B with the Audioinjector stereo sound card?

Please tell us more about you exact setup and the steps which led to the error message (and also where you read it? Did you connect a display to the Raspberry Pi?

m-r-s avatar Sep 12 '19 19:09 m-r-s

Hi,

yes, i use exactly the recommended hardware. An audioinjector stereo soundcard on a Raspberry Pi 3b. I tried the image with version 2.2, 2.0 and also 1.2, always with the same result and i think i followed the instructions exactly.

I have connected a monitor to the Raspberry Pi and the start.sh script reports exactly the described error. Therefore the rest doesn't work anymore because e.g. the jack client can't be started.

Also a start of the jackd by hand with different parameters ends with the same error.

mischa1967 avatar Sep 12 '19 21:09 mischa1967

Okay, thank you!

One frequently encountered problem was that the GPIO pins were not connected properly. Then starting jack fails and you might find related error messages in the output of "dmesg". The solution always was to push down firmly the extension card to make sure that the pins are well connected.

m-r-s avatar Sep 13 '19 08:09 m-r-s

Hello again,

today i found an entry in the forum of the manufacturer of the soundcard where the user has the same problem. Then it came out that the card was probably defective. With a second card it worked there. So I ordered a second card to and i will get back here as soon as it arrived.

Many thanks first of all.

mischa1967 avatar Sep 13 '19 09:09 mischa1967