Daniel James | 11 Jun 2010 15:33
Favicon
Gravatar

Re: Qtractor + Rakarrack + JACK2 = JackAudioDriver::ProcessAsync Process error

Hi Ralf,

> could you please add a JACK debuginfo version to the repository or send
> it by email?

There's an open question about whether we will use JACK2 or JACK1 for
future distros, since JACK 0.118.0 shows that JACK1 development is still
very much alive.

When jackdmp 1.9.1 was renamed to JACK2 I believed that JACK1
development was giving way to the newer C++ implementation, but that
does not appear to be the case now.

Cheers!

Daniel
Gabriel M. Beddingfield | 11 Jun 2010 15:46
Favicon

Re: Qtractor + Rakarrack + JACK2 = JackAudioDriver::ProcessAsync Process error


On Fri, 11 Jun 2010, Daniel James wrote:

> Hi Ralf,
>
>> could you please add a JACK debuginfo version to the repository or send
>> it by email?
>
> There's an open question about whether we will use JACK2 or JACK1 for
> future distros, since JACK 0.118.0 shows that JACK1 development is still
> very much alive.
>
> When jackdmp 1.9.1 was renamed to JACK2 I believed that JACK1
> development was giving way to the newer C++ implementation, but that
> does not appear to be the case now.

I think he was asking for some manner of libjack-dbg 
package so that he could get a sane backtrace.

-gabriel
Daniel James | 11 Jun 2010 15:50
Favicon
Gravatar

Re: Qtractor + Rakarrack + JACK2 = JackAudioDriver::ProcessAsync Process error

Hi Gabriel,

>> When jackdmp 1.9.1 was renamed to JACK2 I believed that JACK1
>> development was giving way to the newer C++ implementation, but that
>> does not appear to be the case now.
> 
> I think he was asking for some manner of libjack-dbg 
> package so that he could get a sane backtrace.

Right, but I meant that if we switch back to JACK1, then this bug may
not get followed up. I'm also looking into JACK MIDI to see if we can
satisfy Ralf's timing requirements that way :-)

Cheers!

Daniel
Ralf Mardorf | 11 Jun 2010 15:57

Re: Qtractor + Rakarrack + JACK2 = JackAudioDriver::ProcessAsync Process error

Daniel James wrote:
> Hi Ralf,
>
>   
>> could you please add a JACK debuginfo version to the repository or send
>> it by email?
>>     
>
> There's an open question about whether we will use JACK2 or JACK1 for
> future distros, since JACK 0.118.0 shows that JACK1 development is still
> very much alive.
>
> When jackdmp 1.9.1 was renamed to JACK2 I believed that JACK1
> development was giving way to the newer C++ implementation, but that
> does not appear to be the case now.
>
> Cheers!
>
> Daniel
>   

JACK 1 on many machines, for people who are happy with Linux, is still 
the merrily client disconnector. And within this and last month I guess 
I wasn't the only one on audio mailing lists, having now issues when 
using JACK 2 too, anyway JACK 2 seems to be the better choice. I don't 
know the reason, why most major distros now switch to JACK 2, this could 
regard to other issues, dunno, pulseaudio, dbus, session handling.

I didn't test current JACK 1, perhaps I should do it for 3.3 alpha and 
report, if I could run Qtractor + Rakarrack without issues, or if JACK 1 
(Continue reading)

Ralf Mardorf | 11 Jun 2010 16:08

Re: Qtractor + Rakarrack + JACK2 = JackAudioDriver::ProcessAsync Process error

Gabriel M. Beddingfield wrote:
> On Fri, 11 Jun 2010, Daniel James wrote:
>
>   
>> Hi Ralf,
>>
>>     
>>> could you please add a JACK debuginfo version to the repository or send
>>> it by email?
>>>       
>> There's an open question about whether we will use JACK2 or JACK1 for
>> future distros, since JACK 0.118.0 shows that JACK1 development is still
>> very much alive.
>>
>> When jackdmp 1.9.1 was renamed to JACK2 I believed that JACK1
>> development was giving way to the newer C++ implementation, but that
>> does not appear to be the case now.
>>     
>
> I think he was asking for some manner of libjack-dbg 
> package so that he could get a sane backtrace.
>
> -gabriel

You are right, but testing JACK 1 first couldn't harm. If needed I could 
compile a dbg version for JACK 2 myself, I just was asking because I 
wish to keep the distro's "default" JACK, instead of compiling a custom 
distro ;).

Cheers!
(Continue reading)

Ralf Mardorf | 11 Jun 2010 16:20

Re: Qtractor + Rakarrack + JACK2 = JackAudioDriver::ProcessAsync Process error

Daniel James wrote:
> Hi Gabriel,
>
>   
>>> When jackdmp 1.9.1 was renamed to JACK2 I believed that JACK1
>>> development was giving way to the newer C++ implementation, but that
>>> does not appear to be the case now.
>>>       
>> I think he was asking for some manner of libjack-dbg 
>> package so that he could get a sane backtrace.
>>     
>
> Right, but I meant that if we switch back to JACK1, then this bug may
> not get followed up. I'm also looking into JACK MIDI to see if we can
> satisfy Ralf's timing requirements that way :-)
>
> Cheers!
>
> Daniel

Daniel keep in mind that JACK 1 tend to disconnect clients. Not only the 
0.109.0 version or what version was infamous for doing this.

Someone off-list the jack-devel list last month wrote, that he have been 
happily using jack2 for quite a while, as jack1 is just like I put it, a 
merry client disconnector. He added that it also fucks up as soon as 
some graph glitch occurs. The audio becomes as a result totally 
distorted and only a server restart fixes it. So no, jack1 is a nogo for 
him.

(Continue reading)

Ralf Mardorf | 12 Jun 2010 03:51

JACK1 for 3.3alpha - libjack.so.0: cannot open shared object file: No such file or directory

Hi all :)

with JACK1 installed I get "libjack.so.0: cannot open shared object file: No such file or directory", when I reinstalled JACK2 I can start and play my test audio session again.

That's too funny, I compiled JACK1 0.118.0 for another Karmic install, but 64 Studio 3.3alpha and didn't get this issue.
Perhaps I made a mistake and I don't see the forest for the trees.

The essential steps I did to build JACK1, you might notice that I skip some unimportant steps, e.g. removing the source code in /usr/src/jack-audio-connection-kit*.

spinymouse <at> 64studio:/usr/src/jack-audio-connection-kit-0.118.0/dummies$ equivs-control jackd
spinymouse <at> 64studio:/usr/src/jack-audio-connection-kit-0.118.0/dummies$ gedit jackd
Edited the file to:

Section: misc
Priority: optional
Standards-Version: 3.6.2
Package: *
Version: 2010.118.0-1dummy~64studio3.3a
Depends: jackd (=2010.118.0-1dummy~64studio3.3a),libjack0 (=2010.118.0-1dummy~64studio3.3a), libjack-dev (=2010.118.0-1dummy~64studio3.3a), libjack0.100.0-dev (=2010.118.0-1dummy~64studio3.3a),jack-audio-connection-kit
Architecture: all
Description: JACK Audio Connection Kit dummy package

Replaced the * by jackd and saved the file as jackd. Repeated this for libjack0, libjack-dev and libjack0.100.0-dev. Then replaced the * by jack-audio-connection-kit and replaced "Version: 2010.118.0-1dummy~64studio3.3a" by "Version: 0.000.0-1dummy~64studio3.3a", didn't change anything for "(=2010.118.0-1dummy~64studio3.3a)".
spinymouse <at> 64studio:/usr/src/jack-audio-connection-kit-0.118.0/dummies$ equivs-build jackd
spinymouse <at> 64studio:/usr/src/jack-audio-connection-kit-0.118.0/dummies$ equivs-build libjack0
spinymouse <at> 64studio:/usr/src/jack-audio-connection-kit-0.118.0/dummies$ equivs-build libjack-dev
spinymouse <at> 64studio:/usr/src/jack-audio-connection-kit-0.118.0/dummies$ equivs-build libjack0.100.0-dev
spinymouse <at> 64studio:/usr/src/jack-audio-connection-kit-0.118.0/dummies$ equivs-build jack-audio-connection-kit
spinymouse <at> 64studio:/usr/src/jack-audio-connection-kit-0.118.0/dummies$ mv *.deb ../
spinymouse <at> 64studio:/usr/src/jack-audio-connection-kit-0.118.0/dummies$ cd ..
spinymouse <at> 64studio:/usr/src/jack-audio-connection-kit-0.118.0$ rm -r dummies
spinymouse <at> 64studio:/usr/src/jack-audio-connection-kit-0.118.0$ su root -c "dpkg --force-depends -i *.deb"
spinymouse <at> 64studio:/usr/src/jack-audio-connection-kit-0.118.0$ su
root <at> 64studio:/usr/src/jack-audio-connection-kit-0.118.0# ./configure
jack-audio-connection-kit 0.118.0 :

| Build with ALSA support............................... : true
| Build with old FireWire (FreeBob) support............. : false
| Build with new FireWire (FFADO) support............... : false
| Build with OSS support................................ : true
| Build with Sun audio support.......................... : false
| Build with CoreAudio support.......................... : false
| Build with PortAudio support.......................... : false
| Build with Celt support............................... : false
| Build with dynamic buffer size support................ : yes
| Compiler optimization flags........................... : -g
| Compiler full flags................................... : -I$(top_srcdir)/config -I$(top_srcdir) -I$(top_srcdir) -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -Wall -g
| Install dir for libjack + backends.................... : ${exec_prefix}/lib64/jack
|
| Default driver backend................................ : "alsa"
| Shared memory interface............................... : "System V"
| IPC Temporary directory............................... : /dev/shm
| Install prefix........................................ : /usr/local
| Default tmp dir....................................... : /dev/shm

root <at> 64studio:/usr/src/jack-audio-connection-kit-0.118.0# checkinstall
package docs?  [y]: n
0 -  Maintainer: [ root <at> 64studio ]
1 -  Summary: [ JACK Audio Connection Kit ]
2 -  Name:    [ jack-audio-connection-kit ]
3 -  Version: [ 0.118.0 ]
4 -  Release: [ 1~64studio3.3a ]
5 -  License: [ GPL ]
6 -  Group:   [ checkinstall ]
7 -  Architecture: [ amd64 ]
8 -  Source location: [ jack-audio-connection-kit-0.118.0 ]
9 -  Alternate source location: [  ]
10 - Requires: [ jackd (=2010.118.0-1dummy~64studio3.3a),libjack0 (=2010.118.0-1dummy~64studio3.3a), libjack-dev (=2010.118.0-1dummy~64studio3.3a), libjack0.100.0-dev (=2010.118.0-1dummy~64studio3.3a) ]
11 - Provides: [ jack-audio-connection-kit ]
list them?  [n]: n
exclude them from the package? (Saying yes is a good idea)  [y]: y
root <at> 64studio:/usr/src/jack-audio-connection-kit-0.118.0# exit
spinymouse <at> 64studio:/usr/src/jack-audio-connection-kit-0.118.0$ jackd -V
jackd version 0.118.0 tmpdir /dev/shm protocol 24
spinymouse <at> 64studio:/usr/src/jack-audio-connection-kit-0.118.0$ cd /mnt/music/all-in-one_supplier/a64
spinymouse <at> 64studio:/mnt/music/all-in-one_supplier/a64$ cat start-session
#!/bin/sh
# sh start-session

song_path=`pwd`
song_name="a64"
song_version="06-slide"
song_date="Jun/04/2010"
song_info="
\n############################
\n# Project: $song_name
\n# Version: $song_version
\n# $song_date Ralf Mardorf
\n############################\n"

if [ $USER = "root" ] ; then
echo "\nOnly a user is allowed to run this script :)\n"
else
echo $song_info

### Killall
apps="qtractor guitarix rakarrack jackd envy24control"
echo "\nkillall -9 -w $apps"
killall -9 -w $apps

### Restore session
echo "\nRestoring session :)"
sample_rate=96000
frames_period=512
echo "\njackd -Rdalsa -dhw:0 -r$sample_rate -p$frames_period -n2"
#envy24control & sleep 2
jackd -Rdalsa -dhw:0 -r$sample_rate -p$frames_period -n2 & sleep 2
#rakarrack & sleep 4
#guitarix & sleep 2
qtractor "$song_path/qtr/$song_name-$song_version.qtr" & sleep 2
echo
fi
exit 0
spinymouse <at> 64studio:/mnt/music/all-in-one_supplier/a64$ ls /usr/src/jack-audio-connection-kit-0.118.0 -hAl
total 288K
-rw-r--r-- 1 spinymouse src 2.2K 2010-06-12 01:59 jack-audio-connection-kit_0.000.0-1dummy~64studio3.3a_all.deb
-rw-r--r-- 1 root       src 266K 2010-06-12 02:33 jack-audio-connection-kit_0.118.0-1~64studio3.3a_amd64.deb
-rw-r--r-- 1 spinymouse src 2.2K 2010-06-12 01:56 jackd_2010.118.0-1dummy~64studio3.3a_all.deb
-rw-r--r-- 1 spinymouse src 2.2K 2010-06-12 01:58 libjack0.100.0-dev_2010.118.0-1dummy~64studio3.3a_all.deb
-rw-r--r-- 1 spinymouse src 2.2K 2010-06-12 01:57 libjack0_2010.118.0-1dummy~64studio3.3a_all.deb
-rw-r--r-- 1 spinymouse src 2.2K 2010-06-12 01:57 libjack-dev_2010.118.0-1dummy~64studio3.3a_all.deb
spinymouse <at> 64studio:/mnt/music/all-in-one_supplier/a64$ sh start-session
qtractor: error while loading shared libraries: libjack.so.0: cannot open shared object file: No such file or directory

spinymouse <at> 64studio:/mnt/music/all-in-one_supplier/a64$ su root -c ldconfig
spinymouse <at> 64studio:/mnt/music/all-in-one_supplier/a64$ sh start-session
qtractor: error while loading shared libraries: libjack.so.0: cannot open shared object file: No such file or directory
spinymouse <at> 64studio:/mnt/music/all-in-one_supplier/a64$ killall jackd
jack main caught signal 15
spinymouse <at> 64studio:/mnt/music/all-in-one_supplier/a64$ killall jackd
jackd: no process found
spinymouse <at> 64studio:/mnt/music/all-in-one_supplier/a64$ ls /usr/local/lib64/libjack.so* -hAl
lrwxrwxrwx 1 root root  17 2010-06-12 02:33 /usr/local/lib64/libjack.so -> libjack.so.0.0.28
lrwxrwxrwx 1 root root  17 2010-06-12 02:33 /usr/local/lib64/libjack.so.0 -> libjack.so.0.0.28
-rwxr-xr-x 1 root root 92K 2010-06-12 02:31 /usr/local/lib64/libjack.so.0.0.28
spinymouse <at> 64studio:/mnt/music/all-in-one_supplier/a64$ jackd -Rdalsa -dhw:0 -r96000 -p512 -n2
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn 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


Memory locking is unlimited - this is dangerous. You should probably alter the line:
     <at> audio   -  memlock    unlimited
in your /etc/limits.conf to read:
     <at> audio   -  memlock    1543620
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 96000
creating alsa driver ... hw:0|hw:0|512|2|96000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 96000Hz, period = 512 frames (5.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback

spinymouse <at> 64studio:/mnt/music/all-in-one_supplier/a64$ rakarrack
rakarrack: error while loading shared libraries: libjack.so.0: cannot open shared object file: No such file or directory
spinymouse <at> 64studio:/mnt/music/all-in-one_supplier/a64$ qjackctl
qjackctl: error while loading shared libraries: libjack.so.0: cannot open shared object file: No such file or directory
spinymouse <at> 64studio:/mnt/music/all-in-one_supplier/a64$ jack_capture
jack_capture: error while loading shared libraries: libjack.so.0: cannot open shared object file: No such file or directory
root <at> 64studio:/mnt/music/all-in-one_supplier/a64# apt-get --force-yes install jackd=1.9.4+svn3842-2~karmic1 libjack0=1.9.4+svn3842-2~karmic1
Reading package lists... Done
Building dependency tree      
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libdbus-1-dev
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  jackd jackd-firewire libfreebob0 libjack0
Suggested packages:
  jack-tools libjackasyn0
The following packages will be REMOVED:
  dssi-dev jack-audio-connection-kit libjack-dev libjack0.100.0-dev
The following NEW packages will be installed:
  jackd-firewire libfreebob0
The following packages will be DOWNGRADED:
  jackd libjack0
0 upgraded, 2 newly installed, 2 downgraded, 4 to remove and 1 not upgraded.
Need to get 768kB of archives.
After this operation, 1,196kB of additional disk space will be used.
Do you want to continue [Y/n]?
root <at> 64studio:/mnt/music/all-in-one_supplier/a64# exit
spinymouse <at> 64studio:/mnt/music/all-in-one_supplier/a64$ sh start-session

Cheers!

Ralf
_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel
Michael Alexander | 12 Jun 2010 08:05

Invitation to connect on LinkedIn

LinkedIn

I'd like to add you to my professional network on LinkedIn.

- Michael

Michael Alexander
Owner at Frog's Pool and Spa
Fresno, California Area

Confirm that you know Michael

© 2010, LinkedIn Corporation

_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel
Michael Alexander | 12 Jun 2010 08:05

Invitation to connect on LinkedIn

LinkedIn

64,

I'd like to add you to my professional network on LinkedIn.

- Michael

Michael Alexander
Owner at Frog's Pool and Spa
Fresno, California Area

Confirm that you know Michael

© 2010, LinkedIn Corporation

_______________________________________________
64studio-devel mailing list
64studio-devel@...
http://lists.64studio.com/mailman/listinfo/64studio-devel
Ralf Mardorf | 12 Jun 2010 11:39

Re: Invitation to connect on LinkedIn

Hi :)

perhaps " " and "64" won't confirm, if so, I fear that a reminder will 
send each week this two requests to the mailing list. I had this with 
the house management and another social network. So " " and "64", if you 
know him, confirm soon, but if it's a mistake by you Michael, please 
remove the lists address from this social network.
Those network reminders can become a PITA. Very often they ask people 
who won't confirm, to set them self on a blacklist on the server of such 
a network. The result might be, that people who aren't interested in 
those networks will receive spam by the 10 rootkits, that captured the 
network's server, so such a blacklist is a no-go.

Perhaps I'm über-distrusting ;).

Ralf

PS:

64studio-devel <at> lists.64studio.com and 64studio-devel <at> 64studio.com are 
the same address, while the first one is currently the formal.

Michael Alexander wrote:
>
>
>   LinkedIn
>
> I'd like to add you to my professional network on LinkedIn.
>
> - Michael
>
> Michael Alexander
> Owner at Frog's Pool and Spa
> Fresno, California Area
>
> Confirm that you know Michael 
> <https://www.linkedin.com/e/isd/1381030860/l3sJJA-U/EML-invg_59/>
>
> © 2010, LinkedIn Corporation
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 64studio-devel mailing list
> 64studio-devel <at> lists.64studio.com
> http://lists.64studio.com/mailman/listinfo/64studio-devel
>         
>

Michael Alexander wrote:
>
>
>   LinkedIn
>
> 64,
>
> I'd like to add you to my professional network on LinkedIn.
>
> - Michael
>
> Michael Alexander
> Owner at Frog's Pool and Spa
> Fresno, California Area
>
> Confirm that you know Michael 
> <https://www.linkedin.com/e/isd/1381031026/s4foavYM/EML-invg_59/>
>
> © 2010, LinkedIn Corporation
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 64studio-devel mailing list
> 64studio-devel <at> lists.64studio.com
> http://lists.64studio.com/mailman/listinfo/64studio-devel
>         
>
_______________________________________________
64studio-devel mailing list
64studio-devel <at> lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-devel

Gmane