looked through what i have in my /etc/modprobe.d/alsa and it was: alias char-major-116 snd alias char-major-14 soundcore alias snd-card-0 snd-powermac alias sound-slot-0 snd-card-0 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss alias /dev/mixer snd-mixer-oss alias /dev/dsp snd-pcm-oss alias /dev/midi snd-seq-oss options snd cards_limit=1 oh my god! does this mean am using oss and just making the system behave in a fake alsa way? if i am to stck on using chuck on this "snapper" oriented machine i should quit alsa and make linux-oss? without changing this fake-alsa-tuned system made the oss version of chuck chuck --loop & chuck + moe.ck makes no complaints but also makes no sound

On 7/26/07, Martin Ahnelöv wrote:

...

tor 2007-07-26 klockan 10:13 +0900 skrev 2g:

...

slackintosh12.0: [chuck]: (via rtaudio): no devices found for given stream parameters: ... RtApiAlsa: error setting sample rate (48000) on device (hw:Snapper,0): Invalid argument. [chuck]: cannot initialize audio device (try using --silent/-s)

debian-ppc-stable: [chuck]: (via rtaudio): no devices found for compiled audio APIs! [chuck]: cannot initialize audio device (try using --silent/-s)

debian-ppc-unstable: JACK tmpdir identified as [/dev/shm] [chuck]: (via rtaudio): no devices found for compiled audio APIs! [chuck]: cannot initialize audio device (try using --silent/-s)

ubuntu-ppc-7.04: [chuck]: (via rtaudio): no devices found for compiled audio APIs! [chuck]: cannot initialize audio device (try using --silent/-s)

Well, if you compiled it with alsa, jakc shouldn't have anything to do with it. Are you sure alsa is running? (if you dont know any better way, you can check with 'alsaplayer') Did configure/make return any errors?

You do try to run it on the same computer/setup as the one you compiled it on, right?

Martin

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

-- 2g http://micro.ispretty.com

-- 2g http://micro.ispretty.com

oh thanx for keeping me never give up where am standing now is that on DebainPPCStable jackd -R -dalsa -r48000 -S works!! but this doesn't do it on Ubuntu and DebianUnstable and Slackintosh on Ubuntu jackd -R -doss -r44100 on Unstable jackd -R -doss -r48000 could launch jack and i think i remember chuck could make sound but on Slackintosh -doss launch jack but makes no sound wonder why Stable only does the -dalsa way.. well ... okay will check what you told me after posting this when trying to setup a CUI-DJ environment on old notebooks had an experience that the cheap cards didn't support 44100 nor 48000 but was based on weired freq and they couldn't even do "play"(of sox) @ oss but setting up the a-rate & k-rate properly in csound.orc file a very secial donewithcsound.wav could make the card make sound mmm...maybe iBookG4 is still something like that? even if other OS like OSX could make the card behave as if it was supporting well known freq it maybe emulating then hey?! ... am a fool saying "am a strict micro-tuning oriented person! calculating overtones to bring out a real clean harmony to this world!" but the soundcard is just pretending to do it right? aaaaaaarrrrh!! On 8/10/07, Michal Seta wrote:

Hi,

Just catching up with old email. Did you get it to work?

When I tried chuck a couple of times in the past, I remember that it would not work if I did not specify the sample rate when starting it (but hen again, I always run it with jack).

the best way to check whether alsa found a device and loaded the driver is this: cat /proc/asound/cards

where you should see at least one entry. There are other files that can be queried in the /proc/asound directory.

You should start with that and see where it takes you. Also, check /proc/asound/version and read alsa release notes on that version. Perhaps your hardware is only partially supported.

This is probably irrelevant, but long time ago I had this cheap card where the clock was running at 44099Hz or something, and many audio applications were complaining about it...

also, alsa does OSS emulation by default.

HTH

./MiS

On 7/26/07, 2g wrote:

...

looked through what i have in my /etc/modprobe.d/alsa and it was:

alias char-major-116 snd alias char-major-14 soundcore alias snd-card-0 snd-powermac alias sound-slot-0 snd-card-0 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss alias /dev/mixer snd-mixer-oss alias /dev/dsp snd-pcm-oss alias /dev/midi snd-seq-oss options snd cards_limit=1

oh my god! does this mean am using oss and just making the system behave in a fake alsa way? if i am to stck on using chuck on this "snapper" oriented machine i should quit alsa and make linux-oss?

without changing this fake-alsa-tuned system made the oss version of chuck chuck --loop & chuck + moe.ck makes no complaints but also makes no sound

...

On 7/26/07, Martin Ahnelöv wrote:

...

tor 2007-07-26 klockan 10:13 +0900 skrev 2g:

...

slackintosh12.0: [chuck]: (via rtaudio): no devices found for given stream parameters: ... RtApiAlsa: error setting sample rate (48000) on device (hw:Snapper,0): Invalid argument. [chuck]: cannot initialize audio device (try using --silent/-s)

debian-ppc-stable: [chuck]: (via rtaudio): no devices found for compiled audio APIs! [chuck]: cannot initialize audio device (try using --silent/-s)

debian-ppc-unstable: JACK tmpdir identified as [/dev/shm] [chuck]: (via rtaudio): no devices found for compiled audio APIs! [chuck]: cannot initialize audio device (try using --silent/-s)

ubuntu-ppc-7.04: [chuck]: (via rtaudio): no devices found for compiled audio APIs! [chuck]: cannot initialize audio device (try using --silent/-s)

Well, if you compiled it with alsa, jakc shouldn't have anything to do with it. Are you sure alsa is running? (if you dont know any better way, you can check with 'alsaplayer') Did configure/make return any errors?

You do try to run it on the same computer/setup as the one you compiled it on, right?

Martin

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

-- 2g http://micro.ispretty.com

-- 2g http://micro.ispretty.com _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

-- 2g http://micro.ispretty.com