On Tuesday 18 March 2003 12:54, guenter geiger wrote:
On Tue, 18 Mar 2003, Antonis Galanopoulos wrote:
Hi I got latest Jack (yesterdays CVS) , alsa rc8a. Everithing works fine (ardour,freqtweak,tappir, pressgang) besides qjackconnect. I use pd_devel from cvs a couple of weeks ago. Tried to get the newer one, 2 days ago from CVS but it wasn't working wth JACK.I haven't tried today though. Hope that helps
No :(
It works on my system, and it seems to work on several other systems too. It is hard to say what went wrong without additonal information What does pd say when it starts ? Did you check out the devel_0_36 version ? Did you compile with --enable-jack ?
Ok, I'm not Antonis, but I have a datapoint for you. This whole issue is frustrating, because everytime I rebuild Jack or Rosegarden or PD, it seems I get a different set of errors. Like I said before, I really don't have much more time to spend on this, especially since PD istself has disk streaming boxes that seems to work fine for me. But in case it's any help, here's a log:
~ ~ ~ begin paste from shell, comments inserted with ';' ~ ~ ~
; jack was built and installed from CVS a day ago, using the default branch.
; I nuked the old libjack and jack.h from planet CCRMA first.
[root@dhcp-25-2 ~]$ ls -l which jackd
-rwxr-xr-x 1 root root 125786 Mar 17 18:56 /usr/local/bin/jackd
[root@dhcp-25-2 ~]$ ldd which jackd
libjack.so.0 => /usr/local/lib/libjack.so.0 (0x40013000)
libm.so.6 => /lib/libm.so.6 (0x4002e000)
libdl.so.2 => /lib/libdl.so.2 (0x4004f000)
libpthread.so.0 => /lib/libpthread.so.0 (0x40052000)
libc.so.6 => /lib/libc.so.6 (0x40082000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
[root@dhcp-25-2 ~]$ cat which J
#!/bin/bash
jackd -R -d alsa -d hw:0 -r 44100 -p 512 -P &
[root@dhcp-25-2 ~]$ J [root@dhcp-25-2 ~]$ jackd 0.62.0 Copyright 2001-2002 Paul Davis and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details
loading driver .. driver client name = [alsa_pcm] creating alsa driver ... hw:0|512|2|44100|swmon|rt delivering event 2 to IP client alsa_pcm delivering event 5 to IP client alsa_pcm starting engine
[root@dhcp-25-2 ~]$ pd -version
reading startup file: /root/.pdrc
Pd version 0.36-0
compiled 20:31:06 Mar 18 2003
[root@dhcp-25-2 ~]$ cat which PJ
#!/bin/sh
pd -r 44100 -jack -outchannels 2 -audiobuf 20 $1 $2 $3
[root@dhcp-25-2 ~]$ PJ -rt & [2] 1126 reading startup file: /root/.pdrc Testing for Jack [root@dhcp-25-2 ~]$ *** libjack: WARNING! Use of function jack_set_buffer_size_callback() is deprecated! ***
jack: sample rate 44100/sec jackd: pcm.c:5860: snd_pcm_mmap_commit: Assertion `pcm' failed. received signal 6 during shutdodelivering event 5 to IP client alsa_pcm cannot open specified fifo [/tmp/jack-ack-fifo-1117-1] for writing (No such device or address) bad status for client event handling (type = 5) got connect request cannot open specified fifo [/tmp/jack-ack-fifo-1117-1] for writing (No such device or address) bad status for client event handling (type = 5) delivering event 5 to IP client alsa_pcm delivering event 3 to IP client alsa_pcm got connect request cannot open specified fifo [/tmp/jack-ack-fifo-1117-1] for writing (No such device or address) bad status for client event handling (type = 5) delivering event 5 to IP client alsa_pcm delivering event 3 to IP client alsa_pcm using JACK audio interface priority 98 scheduling enabled. memory locking enabled. priority 96 scheduling enabled. memory locking enabled. watchdog: signaling pd... watchdog: signaling pd... jackd watchdog: timeout - killing jackd received signal 11 during shutdwatchdog: signaling pd... watchdog: signaling pd... watchdog: signaling pd... watchdog: signaling pd...
(and then I had to kill -9 it)
.. I know there are already too many instructions to get this going. What do people think about makeing the devel_0_36 branch the main branch in CVS ?
Can't answer that question, but maybe you can answer one for me - is devel_0_36 really the PD 0.37 development branch? If so, could I humbly ask why it's called devel_0_36? If not, does this mean that the latest PD official release was 0.35? If so, why is there a 0.36 on planet CCRMA? Does that mean the planet CCRMA is jumping the gun, and if so, which snapshot is used for their RPM? Sorry for my confusion, but I'm well, confused :-). I had thought that 0.36 was already released and not still in development. Maybe that's what I'm mistaken about.
Regards
Larry Troxler