Click here to register.

Comments

Flat
missing input device
User: volkerbradley
Date: 1/2/2013 6:33 am
Views: 5276
Rating: 15

Just tried to use the julian quickstart on my 64-bit Ubuntu Linux 12/04 system.

I tried this:~/julius-3.5.2-quickstart-linux$ ./julian -input mic -C julian.jconf

and received the following error message:

include config: julian.jconf
###### check configurations
###### initialize input device
adin_mic_standby: device=/dev/dsp
adin_mic_standby: open device: No such file or directory
Error: failed to ready input device
Terminated

I suspect that this has to do with the use of PulseAudio.

Can you tell me how to make it possible for julius to use my USB mic with PulseAsudio?

 

Re: missing input device
User: kmaclean
Date: 1/2/2013 12:34 pm
Views: 209
Rating: 17

>Can you tell me how to make it possible for julius to use my USB mic with PulseAsudio?

try your sound settings and make sure your usb device has been selected for sound input.

Re: missing input device
User: volkerbradley
Date: 1/3/2013 4:22 pm
Views: 313
Rating: 17

I have done that.  As you know, there is no /dev/dsp file in PulseAudio even though the USB mic works just fine in Google Voice, Skype, etc..

Re: missing input device
User: kmaclean
Date: 1/3/2013 8:45 pm
Views: 239
Rating: 15

>As you know, there is no /dev/dsp file in PulseAudio

I did not know that...   :)

>how to make it possible for julius to use my USB mic with PulseAsudio?

From this post: Installing Julian

padsp julius -iput mic -C julian.conf

Re: missing input device
User: volkerbradley
Date: 1/7/2013 7:29 pm
Views: 192
Rating: 16

Thank you for the information.

I tried the command but it did not work for me. 

"~/julius-3.5.2-quickstart-linux$ padsp julius -iput mic -C julian.conf
/usr/bin/padsp: 88: exec: julius: not found"

However, ~/julius-3.5.2-quickstart-linux$ padsp ./julian -input mic -C julian.jconf  seems to do something.

Unfortunately the output is very complex. I cannot see that my spoken words were recognized.

Wished the output was a little easier to understand.

 

Re: missing input device
User: kmaclean
Date: 1/7/2013 7:39 pm
Views: 276
Rating: 17

>Unfortunately the output is very complex.

Did it look something like this?:

Julian Startup Output

Re: missing input device
User: volkerbradley
Date: 1/8/2013 4:07 am
Views: 201
Rating: 17

Thank you very much for taking the time to look at this and helping me learn.

I have posted my output to:

https://docs.google.com/document/d/1pGHdT__5sDbELTJxhf7q7nOM5JZ-LbEQKFIpcROJysI/edit

Does the output look OK to you?

Re: missing input device
User: kmaclean
Date: 1/8/2013 7:34 pm
Views: 297
Rating: 18

>I have posted my output to:

a google search on: "adin_mic_read: no data fragment after 300 msec?"

returns the following posts:

Voice Recognition in Ubuntu

Adding padsp in front of the command fixed that problem [...]I still got warnings though… [...] If you open the Sound Settings, the warnings go away.  I thought was kind of flakey, but it worked.

colbec says in USB headset and "no data fragment"

Pulseaudio seems to be an excellent way of dynamically redirecting audio in and out, I use it a lot. When running Julius it is important to have PA pointed to the right input device with others deactivated.
running my model with no padsp results in either a "failed to open device" if multiple inputs are seen by PA with no mic device in the PCI card or a <please speak> if PA has the PCI deactivated, USB activated but Julius never hears anything despite ALSA apparently set up.
padsp julius results in a <please speak> and eventually gets audio input, however there seem to be delays - it is essential to wait for the system to get itself set up before uttering the first input.
Julius is not happy with some wireless hardware setups.

PreviousNext