deb pack for chuck?

enrike · Joined: Nov 04, 2006 Posts: 1 Location: bilbao

i installed the debian package with apt-get on debian unstable and i get this error when i try to run chuck

$ chuck foo.ck
[chuck]: (via rtaudio): no devices found for compiled audio APIs!
[chuck]: cannot initialize audio device (try using --silent/-s)

is the debian package compiled for ALSA by default?

thanks

kijjaz · Posted: Mon Nov 06, 2006 1:45 pm Post subject:

enrike: i tried last time and i guess it was for Jack.
mainly i use chuck for alsa..
so i actually get used to having both versions ready for use on my debian machines.

Fojaneghe · Joined: Jan 17, 2007 Posts: 11 Location: Trento

Hi folks, I've read the posts and installed chuck on ubuntu 6.06 the way you did. So far so good. The only thing I don't get: Compiling (chucking) a file I don't here anything! Did I miss something? Thanks for your help.

Kassen · Posted: Wed Jan 17, 2007 11:35 am Post subject:

Hi, Fojaneghe!

You don't hear anything?

Let's take this step by step. First of all, let's make sure ChucK is installed properly at all. paste the following line to "test.ck" and try running that by typing

"chuck test.ck"

at the terminal

Fojaneghe · Joined: Jan 17, 2007 Posts: 11 Location: Trento

Hi, Kassen! Great that you've answered immediately! This is the output after the probe comand:

[chuck]: found 1 device(s) ...
[chuck]: ------( chuck -- dac1 )---------------
[chuck]: device name = "hw:Intel,0"
[chuck]: probe [success] ...
[chuck]: # output channels = 2
[chuck]: # input channels = 2
[chuck]: # duplex Channels = 2
[chuck]: default device = YES
[chuck]: natively supported data formats:
[chuck]: 16-bit int
[chuck]: 32-bit int
[chuck]: supported sample rates:
[chuck]: 44100 Hz
[chuck]: 48000 Hz
[chuck]: 88200 Hz
[chuck]: 96000 Hz
[chuck]: 176400 Hz
[chuck]: 192000 Hz
[chuck]:
ALSA lib seq_hw.c:456:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory
[chuck]: RtMidiIn::initialize: error creating ALSA sequencer input client object.
[chuck]:
ALSA lib seq_hw.c:456:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory
[chuck]: RtMidiOut::initialize: error creating ALSA sequencer client object.
[chuck]:

Seems that there is some trouble about the ALSA sequencer. How can I handle it? Greetings to all from italy[/img]

majutsu · Posted: Thu Jan 18, 2007 6:39 am Post subject:

it doesn't seem like you typed in the following (which was in the middle of the thread):

sudo su
modprobe snd-seq
if grep -q -x snd-seq /etc/modules; \
then echo && echo "NOTE: snd-seq is already in /etc/modules, no changes needed."; \
else cp /etc/modules /etc/modules_backup_`date +%Y%m%d%H%M` && echo snd-seq >> /etc/modules; \
fi
exit

that would explain the output you showed. Make sure you type in everything listed for ubuntu. Fixing the alsa sequencer is important.

i hope that helps.

Fojaneghe · Joined: Jan 17, 2007 Posts: 11 Location: Trento

Hi Majutsu! Hope that I got right what you tried to say. Having typed the lines from your post I got

[chuck]: found 1 device(s) ...
[chuck]: ------( chuck -- dac1 )---------------
[chuck]: device name = "hw:Intel,0"
[chuck]: probe [success] ...
[chuck]: # output channels = 2
[chuck]: # input channels = 2
[chuck]: # duplex Channels = 2
[chuck]: default device = YES
[chuck]: natively supported data formats:
[chuck]: 16-bit int
[chuck]: 32-bit int
[chuck]: supported sample rates:
[chuck]: 44100 Hz
[chuck]: 48000 Hz
[chuck]: 88200 Hz
[chuck]: 96000 Hz
[chuck]: 176400 Hz
[chuck]: 192000 Hz
[chuck]:
[chuck]: ------( chuck -- 1 MIDI inputs )------
[chuck]: [0] : "Midi Through Port-0"
[chuck]:
[chuck]: ------( chuck -- 1 MIDI outputs )-----
[chuck]: [0] : "Midi Through Port-0"
[chuck]:

But what do you mean with fixing the ALSA sequencer? To Kassen: Yes. Your toy code was compiled successfully! However. Maybe it's some package that's missing? I don't get the problem. Thanks for your help.

Kassen · Posted: Thu Jan 18, 2007 2:31 pm Post subject:

Well, if you look carefully above you'll see that your first attempt at --probe ran into problems with "creating ALSA sequencer input client object." and now those are gone. That's good.

When you say my example code compiled, I take it that that still means no sound?

Ok, next step, I gather that this package is for Jack audio? (I got my own to compile, didn't see the package yet) In that case it would be good to make sure you actually have Jack properly installed. Do you?

Fojaneghe · Joined: Jan 17, 2007 Posts: 11 Location: Trento

OK. Since I don't know what you meant with the Jack package, here is the list of those jack-packages I've already installed or those I can get from the servers (stable). Still, there is no sound. There's even no message that's something's wrong. Maybe you can suggest me which package you've got in mind?!

i alsaplayer-jack
p dssi-host-jack
i jack
p jack-rack
p jack-tools
p jackbeat
i A jackd
p jackeq
p liballegro4.1-plugin-jack
p liballegro4.2-plugin-jack
v libjack-dev
i A libjack0.100.0-0
i libjack0.100.0-dev
p libjackasyn-dev
p libjackasyn0
p qjackctl
p xmms-jack
p xmms-jackasyn

Again, thanks a lot for your suggestions!

Kassen · Posted: Fri Jan 19, 2007 3:19 am Post subject:

Ok, let's cover some fundamentals (just to make sure). "Jack" is a system through which multiple programs can deal with eachother and with the soundcard. It's kinda like a big virtual patchbay/mixer. Once it works it's very nice, kinda like Rewire but without the client-host structure.

As I understand the situation the ChucK package is compiled to output sound through this system. I'm just asuming that based on what people wrote above; I never tried that package.

So; if that's true then your ChucK install will depend on the presence of the Jack audio server on your system. If it's there it should either start itself when you boot your computer and so you'll know it's there or you'll need to start it manually. Starting it manually will probably work by starting "Jack controll". That'll give you the interface to the Jack system and this interface should start the Jack server for you.

If ChucK still doesn't work once you have made sure Jack is running it would be a good idea to make sure Jack is working properly at all using something that you know uses Jack and that you are sure outputs sound.

The plan here is to exclude factors that could be causing the problem before blaming this on a real bug. It's kinda hard to pinpoint problems like this at a distance Smile

If none of this helps to find and fix the issue then I'm out of ideas and it might be time to ask Ge or Spencer. It could of cource be a bug, those happen, i heard....

majutsu · Posted: Fri Jan 19, 2007 10:58 am Post subject:

Jackd is what you need. But Ubuntu works well/best with Alsa build IMHO.

did you compile chuck for alsa, jack or oss? Oss will not work with ubuntu. Ubuntu is alsa system, and the oss system is defined as alsa. I had trouble with chuck in jack because I usually have to start qjackctl and fire up server, which i found awkward for shredding. . .

I would strongly recommend compiling for alsa. If you typed in the instructions from this thread, they were given for alsa build. I gave up on jack build.

majutsu · Posted: Fri Jan 19, 2007 11:06 am Post subject:

do this step by step:

Download the latest chuck.

Right click - extract here.

open up terminal, cd to the chuck directory.

cd chuck*
cd src
sudo apt-get install build-essential bison flex libjack-dev libasound2-dev libsndfile1-dev
make linux-alsa
sudo make install

This will definitely work on ubuntu 6.06 or recommended to upgrade to 6.10 (Edgy Eft). Feisty Fawn is due out soon, but chuck already works on the beta.

once installed, cd chuck*
cd examples
chuck otf*

you should hear a groovy little trance number. If that doesn't play. Save Kassen's 2 sec beep in the text editor as test.ck. Then chuck test.ck. Let us know exactly what you hear or what the screen says. Are you using any funky sound cards? What is your hardware?

Fojaneghe · Joined: Jan 17, 2007 Posts: 11 Location: Trento

Hi Majutsu, my soundcard is a HDA Intel on a Dell machine. My chuck version is 1.2.0.7. The packages you listed in your post are all installed. Even jackd. When I compile test.ck chuck prompts
"Fojaneghe will soon be a real ChucKist!" : (string)
But I don't hear any sound!

I must admit that the fundamentals are sometimes puzzling me. Yet, I don't know how to use jack. When I was working in windows with rewire the concept seemed clear to me since it connects many audio tools.

Be patient!

majutsu · Posted: Sun Jan 21, 2007 11:18 am Post subject:

you still did not mention whether you compiled chuck for alsa or jack. Did you type make-alsa or make-jack?

It wouldn't hurt you to just type what was posted step by step and print your output and results. You won't hurt anything by typing in, as ubuntu won't reinstall something already in place. I can only guarantee the alsa install using the steps above with your hardware. If you are trying to do a jack install let me know.

It is not clear right now what you are doing or trying to do.[/b]

Fojaneghe · Joined: Jan 17, 2007 Posts: 11 Location: Trento

OK. Here we go. I redownloaded the chuck package and extracted it somewhere. I typed
sudo apt-get install build-essential bison flex libjack-dev libasound2-dev libsndfile1-dev
Password:
Reading package lists... Done
Building dependency tree... Done
build-essential is already the newest version.
bison is already the newest version.
flex is already the newest version.
Note, selecting libjack0.100.0-dev instead of libjack-dev
libjack0.100.0-dev is already the newest version.
libasound2-dev is already the newest version.
libsndfile1-dev is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

as I already expected... Then

make linux-alsa
make -f makefile.alsa
make[1]: Entering directory `/home/sascha/Klang/chuck/chuck-1.2.0.7/src'
make[1]: `chuck' is up to date.
make[1]: Leaving directory `/home/sascha/Klang/chuck/chuck-1.2.0.7/src'

and finally

sudo make install
cp chuck /usr/bin/
chmod 755 /usr/bin/chuck

That's it. Testing chuck revealed the usual behavior.

Kassen · Posted: Mon Jan 22, 2007 9:36 am Post subject:

Hmmmmm, I think this bit "`chuck' is up to date. " might mean nothing actually changed at that compile attempt. It can and will say this if you first compile it for Jack, then try again for Alsa which will suck if the "Jack" version wasn't what you wanted. I had that myself when I tried.

Majutsu is clearly the Ubuntu expert here but I think I'd try deleting that whole ChucK download and deleting chuck from /usr/bin to make sure any trace of previous faulty attempts are gone, then trying again.

If that doesn't help we might have a real bug and it might be time to ask Spencer.

sjef · Joined: Jan 22, 2007 Posts: 6 Location: Netherlands

Hi all,

Today I found out about Chuck and I'm really enthusiastic about it. In fact, as soon as I got home from work, I started installing Chuck. I'm using Ubuntu Dapper, and after installing flex and bison (the replacements for lex and yacc, as I found out) I did a make linux-alsa, and everything went well.

First I had the problems with ALSA sequencer, which I solved using majutsu's input. Now I have the problem that none of the examples given by Kassen work ! Not even the string output. Except when I specify the --silent option.

My chuck --probe output:

majutsu · Posted: Mon Jan 22, 2007 3:23 pm Post subject:

very helpful guys -- that's the kind of thing we need

I don't have any easy answers yet, just read the posts. But i will go look into it.

As for original poster, I agree with kassen. The compile was not redone. Use whereis command to identify chuck places, then remove and reinstall.

As for why you have no sound, i don't know yet. It works on most computers in Ubuntu as above. Of course, i would recommend ubuntu users to upgrade to Edgy since Feisty's out soon, and Dapper is definitely not a current release. But i got 1.2.7 to work on dapper the same way before edgy, so i know that's not the problem.

Does rhythmbox music player (which comes with ubuntu) work? xmss, etc, your other alsa apps (kaconnect etc) do they work? I will assume so for now.

when you go into examples directory and chuck otf* what happens? I've figured you get no sound. But are there any printed messages. I am tempted to use gdb to debug . . .

majutsu · Posted: Mon Jan 22, 2007 3:32 pm Post subject:

p.s. to the two guys having problems:

cd chuck*
cd examples
cd basic

chuck --verbose moe

let me know what you get, your printout:

spencer · Posted: Mon Jan 22, 2007 5:32 pm Post subject:

sjef,
This looks suspiciously like a bug in the real-time audio system. rtaudio could be having trouble with your particular device setup, as it is apparenty not finding a default audio output device. This is something of a shot in the dark, but try running chuck with the --dacN option, where N is 2, 3, or 4. This will tell it to use audio device N as the output destination. i.e.

Kassen · Posted: Mon Jan 22, 2007 6:46 pm Post subject:

Hey, Sjef, Welcome on board! Good to see a fellow Dutch ChucKist (to be)!

Fojaneghe · Joined: Jan 17, 2007 Posts: 11 Location: Trento

This the output (I haven't cancelled all yet) after typing chuck --verbose moe

Fojaneghe · Joined: Jan 17, 2007 Posts: 11 Location: Trento

Oh I've forgotten to reply to Majutsu's question: Yes, Xmms works fine! The Rythmbox music player instead not. Confused

sjef · Joined: Jan 22, 2007 Posts: 6 Location: Netherlands

Hi, Majutsu,

I did as you said, here's the output of

sjef · Joined: Jan 22, 2007 Posts: 6 Location: Netherlands

Hi all,

I got sound!! I was playing around with the --dac parameter, and found --dac1 to be the only one that gets ChucK past 'starting kb loop'. The error I get with this, is the audio read error in my previous post.

So I started experimenting with passing --adcN options. None work, except N values above 4 !!

so with