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

Hi 64 Studio list :)

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

Hi JACK list :)

when I tried to record a song using 64 Studio 3.3 alpha amd64 [1], I did
run

gnome-terminal --version
GNOME Terminal 2.28.1
dpkg -l gnome-terminal
2.28.1-0ubuntu1 (karmic)

jackd -V
jackdmp version 1.9.5 tmpdir /dev/shm protocol 7
dpkg -l jackd
1.9.4+svn3842-2~karmic1 (apt.64studio.com)

qtractor -v
Qt: 4.5.2
Qtractor: 0.4.6
dpkg -l qtractor
0.4.6-1 (self build)

using a MIDI track that runs

dpkg -l fluidsynth-dssi
0.9.1-3ubuntu3 (karmic)
+ 808Set.sf2
for the drums

a stereo audio track for a guitar that plays all the time without any
plug-ins

a second stereo audio track for guitar playing all the time, but also no
plug-ins were used

a second MIDI track that runs

Calf Monosynth DSSI
dpkg -l calf-plugins
0.0.18.5-0ubuntu1 (karmic)
+
GVerb
dpkg -l swh-plugins
0.4.15-2 (karmic)
for the bass + room

a third stereo audio track for guitar playing seldom, without running
any plug-ins

and

rakarrack --help
rakarrack 0.4.2
dpkg -l rakarrack
0.4.2-1 (self build)

to add more guitar to the third stereo audio track by using the Lil Blue
preset + enabling the compressor for the preset too

and when I run into the issue, getting distortion and dropouts for
rakarrack, not for qtractor too [3], nothing else was launched.

I started the session by a script [2], perhaps sometimes rakarrack
wasn't commented out or I launched it by the menu.

I only get this issue when running rakarrack to record the third guitar
stereo track, before it was ok, I could launch guitarix and envy24
control too, without getting trouble.

When I run into trouble now, I need (not all the time) to close and
restart all apps, so for a while everything will be ok.

I get the following messages again and again:

JackAudioDriver::ProcessAsync Process error
JackEngine::XRun: client = Qtractor was not run: state = 2

[3]
Ok, the stereo output of rakarrack is connected to Qtractor's stereo
input, the audible bad effect is for the signal of rakarrack.

Today I run firefox and evolution too, I didn't do this, when I tried to
record the song last Friday.

top

top - 15:04:06 up 1:34, 3 users, load average: 0.57, 0.54, 0.27
Tasks: 159 total, 1 running, 157 sleeping, 0 stopped, 1 zombie
Cpu(s): 35.7%us, 4.1%sy, 0.0%ni, 60.0%id, 0.0%wa, 0.0%hi, 0.2%si,
0.0%st
Mem: 2058160k total, 1192380k used, 865780k free, 104796k buffers
Swap: 4425824k total, 0k used, 4425824k free, 701132k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+
COMMAND
3788 spinymou 20 0 152m 96m 88m S 37 4.8 4:29.70
rakarrack
2555 spinymou 20 0 685m 146m 96m S 28 7.3 109:23.02
qtractor
1236 root 20 0 147m 35m 7984 S 7 1.8 1:28.66
Xorg
2107 spinymou 20 0 177m 16m 9944 S 3 0.8 0:16.49
gnome-terminal
1096 root -51 -5 0 0 0 S 1 0.0 0:30.26
irq/21-ICE1712
1387 root -51 -5 0 0 0 S 1 0.0 0:16.38
irq/18-nvidia
2484 spinymou 20 0 432m 67m 25m S 1 3.4 0:17.12
firefox
2550 spinymou 20 0 111m 87m 80m S 1 4.4 1:15.08
jackd
23 root -50 -5 0 0 0 S 0 0.0 0:13.42
sirq-tasklet/1
379 root -60 -5 0 0 0 S 0 0.0 0:03.34
irq/12-i8042
632 root -68 -5 0 0 0 S 0 0.0 0:08.55
irq/18-ohci_hcd
2089 spinymou 20 0 133m 13m 8152 S 0 0.7 0:15.74
lxpanel
2341 spinymou 20 0 636m 55m 35m S 0 2.8 0:33.49
evolution
4135 spinymou 20 0 19136 1372 988 R 0 0.1 0:00.24
top
1 root 20 0 19328 1700 1156 S 0 0.1 0:00.60
init
2 root 15 -5 0 0 0 S 0 0.0 0:00.00
kthreadd
3 root RT -5 0 0 0 S 0 0.0 0:00.00
migration/0
4 root -50 -5 0 0 0 S 0 0.0 0:00.00
sirq-high/0
5 root -50 -5 0 0 0 S 0 0.0 0:00.00
sirq-timer/0
6 root -50 -5 0 0 0 S 0 0.0 0:00.00
sirq-net-tx/0
7 root -50 -5 0 0 0 S 0 0.0 0:00.03
sirq-net-rx/0
8 root -50 -5 0 0 0 S 0 0.0 0:00.17
sirq-block/0
9 root -50 -5 0 0 0 S 0 0.0 0:05.44
sirq-tasklet/0
10 root -50 -5 0 0 0 S 0 0.0 0:00.00
sirq-sched/0
11 root -50 -5 0 0 0 S 0 0.0 0:00.04
sirq-hrtimer/0
12 root -50 -5 0 0 0 S 0 0.0 0:00.00
sirq-rcu/0
13 root RT -5 0 0 0 S 0 0.0 0:00.00
posixcputmr/0
14 root RT -5 0 0 0 S 0 0.0 0:00.00
watchdog/0
15 root 10 -10 0 0 0 S 0 0.0 0:00.01
desched/0
16 root RT -5 0 0 0 S 0 0.0 0:00.00
migration/1
17 root RT -5 0 0 0 S 0 0.0 0:00.00
posixcputmr/1
18 root -50 -5 0 0 0 S 0 0.0 0:00.00
sirq-high/1
19 root -50 -5 0 0 0 S 0 0.0 0:00.39
sirq-timer/1
20 root -50 -5 0 0 0 S 0 0.0 0:00.00
sirq-net-tx/1
21 root -50 -5 0 0 0 S 0 0.0 0:00.04
sirq-net-rx/1
22 root -50 -5 0 0 0 S 0 0.0 0:00.18
sirq-block/1
24 root -50 -5 0 0 0 S 0 0.0 0:00.00
sirq-sched/1
25 root -50 -5 0 0 0 S 0 0.0 0:00.00
sirq-hrtimer/1
26 root -50 -5 0 0 0 S 0 0.0 0:00.00 sirq-rcu/1

su root -c "lshw -short"
H/W path Device Class Description
================================================== ======
system System Product Name
/0 bus M2A-VM HDMI
/0/0 memory 128KiB BIOS
/0/5 processor AMD Athlon(tm) X2 Dual Core
Processor BE-2350
/0/5/b memory 128KiB L1 cache
/0/5/c memory 512KiB L2 cache
/0/30 memory 2GiB System Memory
/0/30/0 memory 1GiB DIMM DDR2 800 MHz (1.2
ns)
/0/30/1 memory 1GiB DIMM DDR2 800 MHz (1.2
ns)
/0/100 bridge RS690 Host Bridge
/0/100/2 bridge RS690 PCI to PCI Bridge
(PCI Express Graphics Port 0)
/0/100/2/0 display G72 [GeForce 7300 SE/7200
GS]
/0/100/7 bridge RS690 PCI to PCI Bridge
(PCI Express Port 3)
/0/100/7/0 eth0 network RTL8111/8168B PCI Express
Gigabit Ethernet controller
/0/100/12 scsi0 storage SB600 Non-Raid-5 SATA
/0/100/12/0 /dev/sda disk 320GB SAMSUNG HD321KJ
/0/100/12/1 /dev/cdrom disk DVD-RAM GH22LS30
/0/100/13 bus SB600 USB (OHCI0)
/0/100/13.1 bus SB600 USB (OHCI1)
/0/100/13.2 bus SB600 USB (OHCI2)
/0/100/13.3 bus SB600 USB (OHCI3)
/0/100/13.4 bus SB600 USB (OHCI4)
/0/100/13.5 bus SB600 USB Controller (EHCI)
/0/100/14 bus SBx00 SMBus Controller
/0/100/14.1 storage SB600 IDE
/0/100/14.1/0 ide0 bus IDE Channel 0
/0/100/14.1/0/0 /dev/hda disk 81GB Maxtor 6L080P0
/0/100/14.3 bridge SB600 PCI to LPC Bridge
/0/100/14.4 bridge SBx00 PCI to PCI Bridge
/0/100/14.4/6 multimedia ICE1712 [Envy24] PCI
Multi-Channel I/O Controller
/0/100/14.4/7 bus VT6306 Fire II IEEE 1394
OHCI Link Layer Controller
/0/101 bridge K8 [Athlon64/Opteron]
HyperTransport Technology Configuration
/0/102 bridge K8 [Athlon64/Opteron]
Address Map
/0/103 bridge K8 [Athlon64/Opteron] DRAM
Controller
/0/104 bridge K8 [Athlon64/Opteron]
Miscellaneous Control

64 Studio 3.3 alpha, resp. Ubunbtu Karmic seems to be based on
cat /etc/debian_version
squeeze/sid

FWIW:

/usr/src/rakarrack-0.4.2$ ./configure
[snip]
checking whether closedir returns void... no
[snip]
checking for floor... no
[snip]
checking for pow... no
[snip]
checking for sqrt... no
[snip]
/usr/src/qtractor-svn$ ./configure
[snip]
checking for jack_set_session_callback in -ljack... no
[snip]
Qtractor 0.4.6

Build target . . . . . . . . . . . . . . . . . . .: release

JACK Audio Connection Kit support . . . . . . . .: yes
ALSA MIDI Sequencer support . . . . . . . . . . .: yes
General audio file support (libsndfile) . . . . .: yes
Ogg Vorbis audio file support (libvorbis) . . . .: yes
MPEG-1 Audio Layer 3 file support (libmad) . . . .: yes
Sample-rate conversion support (libsamplerate) . .: yes
Pitch-shifting support (librubberband) . . . . . .: yes
OSC service support (liblo) . . . . . . . . . . .: yes
IEEE 32bit float optimizations . . . . . . . . . .: yes
SSE optimization support (x86) . . . . . . . . . .: yes
LADSPA Plug-in support . . . . . . . . . . . . . .: yes
DSSI Plug-in support . . . . . . . . . . . . . . .: yes
VST Plug-in support . . . . . . . . . . . . . . .: yes
LV2 Plug-in support (libslv2) . . . . . . . . . .: yes
LV2 Plug-in Event/MIDI support . . . . . . . . . .: yes
LV2 Plug-in External UI support . . . . . . . . .: yes
LV2 Plug-in Save/Restore support . . . . . . . . .: yes

JACK Session support (EXPERIMENTAL) . . . . . . .: no

X11 Unique/Single instance . . . . . . . . . . . .: no
XInitThreads() support (DANGEROUS) . . . . . . . .: no
Gradient eye-candy . . . . . . . . . . . . . . . .: yes
Debugger stack-trace (gdb) . . . . . . . . . . . .: no

Install prefix . . . . . . . . . . . . . . . . . .: /usr/local
[snip]

Any ideas?

Cheers!

Ralf

[1]
uname -a
Linux 64studio 2.6.31-2-multimedia-amd64 #1 SMP PREEMPT RT Thu Oct 1
16:14:20 BST 2009 x86_64 GNU/Linux

dpkg -l rtirq-init
20090810-0ubuntu1 (karmic)

groups
spinymouse adm dialout cdrom audio src plugdev lpadmin sambashare

cat /etc/security/limits.conf | grep @audio
@audio - rtprio 99
@audio - memlock unlimited

dpkg -l lxde-core
0.4.2-1ubuntu3 (karmic)

[2]
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="

############################

# Project: $song_name

# Version: $song_version

# $song_date Ralf Mardorf

############################
"

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

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

### Restore session
echo "
Restoring session :)"
sample_rate=96000
frames_period=512
echo "
jackd -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

_______________________________________________
64studio-devel mailing list
64studio-devel@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-devel

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
_______________________________________________
64studio-devel mailing list
64studio-devel@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-devel

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
_______________________________________________
64studio-devel mailing list
64studio-devel@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-devel

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
_______________________________________________
64studio-devel mailing list
64studio-devel@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-devel

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
still will disconnect clients on my machine too.

I try to test it during the weekend or next week. I'll compile current
JACK 1 if the repositories version should be outdated.

Cheers!

Ralf
_______________________________________________
64studio-devel mailing list
64studio-devel@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-devel

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!

Ralf
_______________________________________________
64studio-devel mailing list
64studio-devel@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-devel

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.

Unfortunately I get totally distorted results when using JACK2, Qtractor
and Rakarrack for the 3.3 alpha and I need to restart all apps too.
Dunno if it's currently possible to compile Rakarrack for 3.0 beta. I
should try to do it and test if it's for 3.0 the same problem.

Cheers!

Ralf
_______________________________________________
64studio-devel mailing list
64studio-devel@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-devel

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

Hi Ralf,

> I don't
> know the reason, why most major distros now switch to JACK 2

It's hard to say if that's true, without a proper survey. Ubuntu Lucid
has JACK1 (0.118) but Debian Squeeze will have JACK2 (1.9.5 or later).

I assumed that because of the numbering, all JACK developers would be
working on JACK2 from now on. However it seems that some people (like
Torben Hohn and Florian Faber) prefer to continue work on JACK1 - it is
a different implementation in a different language, after all.

Fortunately, the API is kept synchronised, although if you take a binary
app compiled against an older version of JACK1 and try to run it on a
system with current JACK2, it may or may not work. For example, we found
that amsynth needed to be rebuilt for it to work with JACK2.

Cheers!

Daniel
_______________________________________________
64studio-devel mailing list
64studio-devel@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-devel

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

Daniel James wrote:
> Hi Ralf,
>
>
>> I don't
>> know the reason, why most major distros now switch to JACK 2
>>
>
> It's hard to say if that's true, without a proper survey. Ubuntu Lucid
> has JACK1 (0.118) but Debian Squeeze will have JACK2 (1.9.5 or later).
>
> I assumed that because of the numbering, all JACK developers would be
> working on JACK2 from now on. However it seems that some people (like
> Torben Hohn and Florian Faber) prefer to continue work on JACK1 - it is
> a different implementation in a different language, after all.
>
> Fortunately, the API is kept synchronised, although if you take a binary
> app compiled against an older version of JACK1 and try to run it on a
> system with current JACK2, it may or may not work. For example, we found
> that amsynth needed to be rebuilt for it to work with JACK2.
>
> Cheers!
>
> Daniel
>

Hi Daniel :)

I guess that more and more people got issues when using JACK1 on a
multi-core machine. JACK2 is (was?) very good. I nearly left Linux for
audio, but then 3.0 beta came with JACK2 and I was surprised, that I
could use Linux to make music.
At the moment I'm a "hardcore fan" (might be a German idiom, pardon) of
Rakarrack, but when using it with 3.3 alpha for a production with some
audio and MIDI tracks, I'll end in a "cul-de-sac" (might be a "German
only" idiom too, but I guess you do understand).

I guess tonight I'll have the time to check if I'm able to build JACK1
for 3.3 alpha, perhaps I missed a mistake I made, when I tried to build it.

I don't have any objections, if I could install JACK1 from the
repositories tonight ;).

To be continued :).

Ralf
_______________________________________________
64studio-devel mailing list
64studio-devel@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-devel