3 Mar
2003
3 Mar
'03
9:07 a.m.
Hello,
Has anyone gotten zynaddsubfx and/or iiwusynth to work with jack? The
programs fire up fine, but they output no sound.
I have tried zynaddsubfx 1.0.9 and the most recent cvs of iiwusynth
(fluidsynth).
I know i am calling jackd properly, because alsaplayer works fine with jackd,
as well as ecasound.
--
Levi Burton
http://www.puresimplicity.net/~ldb/
9:44 a.m.
They both work for me. Both are installed from Planet RPMs.
On Mon, 2003-03-03 at 04:55, Levi Burton wrote:
Hello,
Has anyone gotten zynaddsubfx and/or iiwusynth to work with jack? The
programs fire up fine, but they output no sound.
I have tried zynaddsubfx 1.0.9 and the most recent cvs of iiwusynth
(fluidsynth).
I know i am calling jackd properly, because alsaplayer works fine with jackd,
as well as ecasound.
--
Levi Burton
http://www.puresimplicity.net/~ldb/
10:11 a.m.
Hello again,
Thanks for your responses. I got iiwusynth to work with jack by passing the
-j option to iiwusynth. Now, to quoteth the output of iiwusynth -help
-j, --connect-jack-outputs
Attempt to connect the jack outputs to the physical ports
What does this mean? I am confused as to what are "jack outputs" and what are
"physical ports"
Thanks!
--
Levi Burton
http://www.puresimplicity.net/~ldb/
10:36 a.m.
Jack outputs are the output ports on the iiwusynth. Think of them as 1/4"
connectors.
Physical ports are the inputs to your output power amp in your sound card.
Think of them as your keyboard amp.
If you use qjackconnect, you'll get a GUI that will make this more obvious.
It will show you your sound card ports and your soft synth ports. iiwusynth
hook up automatically to playback_1 & 2, so I get sound automatically.
ZynAddSubFx does not. You must hook it up using qjc to get sound. (Or
possibly at the command line.)
-----Original Message-----
From: linux-audio-user-admin(a)music.columbia.edu
[mailto:linux-audio-user-admin@music.columbia.edu]On Behalf Of Levi
Burton
Sent: Monday, March 03, 2003 6:01 AM
To: linux-audio-user(a)music.columbia.edu
Subject: Re: [linux-audio-user] jackd, zynaddsubfx and iiwusynth
Hello again,
Thanks for your responses. I got iiwusynth to work with jack by
passing the
-j option to iiwusynth. Now, to quoteth the output of iiwusynth -help
-j, --connect-jack-outputs
Attempt to connect the jack outputs to the physical ports
What does this mean? I am confused as to what are "jack outputs"
and what are
"physical ports"
Thanks!
--
Levi Burton
http://www.puresimplicity.net/~ldb/
1:11 p.m.
Hi,
zynaddsubfx works fine with jackd.
But I have problems to connect iiwusynth (0.2.2) to jackd (0.51)
Maybe the options are not correct.
I start jackd with:
jackd -R -d alsa -d hw:0 -r 44100 -D
and iiwusynth with:
iiwusynth -m alsa_seq -a jack -z 1024 -c 2 -r 44100 VintageDreamsWaves.sf2'
*** libjack: WARNING! Use of function jack_set_buffer_size_callback() is
deprecated! ***
the sample rate is now 44100/sec
iiwusynth: error: Cannot activate the iiwusynth as a JACK client
Failed to create the synthesizer
Other applications like muse and alsaplayer works fine. But I always get the
massage
*** libjack: WARNING! Use of function jack_set_buffer_size_callback() is
deprecated! ***
any ideas?
thanks
chris
1:38 p.m.
New subject: [linux-audio-user] Incidental Re: jackd, zynaddsubfx and iiwusynth
On Monday 03 March 2003 17:04, chris wrote:
Other applications like muse and alsaplayer works
fine. But I always get
the massage
[snip]
I'm having problems getting any of it to work at all, and try as I might the
bodywork has NOT been forthcoming. Do I need to download XShiatsu or gRolf
for this?
tim hall
2:01 p.m.
chris <chbung321(a)compuserve.de> writes:
Hi,
zynaddsubfx works fine with jackd.
But I have problems to connect iiwusynth (0.2.2) to jackd (0.51)
Maybe the options are not correct.
I start jackd with:
jackd -R -d alsa -d hw:0 -r 44100 -D
and iiwusynth with:
iiwusynth -m alsa_seq -a jack -z 1024 -c 2 -r 44100 VintageDreamsWaves.sf2'
*** libjack: WARNING! Use of function jack_set_buffer_size_callback() is
deprecated! ***
the sample rate is now 44100/sec
iiwusynth: error: Cannot activate the iiwusynth as a JACK client
Failed to create the synthesizer
Other applications like muse and alsaplayer works fine. But I always get the
massage
*** libjack: WARNING! Use of function jack_set_buffer_size_callback() is
deprecated! ***
any ideas?
That warning was added to JACK version 0.50.0 (IIRC). It is just a
warning. The jack_set_buffer_size_callback() function is not invoked,
and in fact never was. The purpose of the message is to inform
developers not to use this function.
When newer versions of your applications are released, the message
will go away. Meanwhile, just ignore it. It should not cause a
problem connecting. So, iiwusynth must be encountering some other
problem.
"Pay no attention to the man behind the curtain."
--
Jack O'Quin
Austin, Texas, USA
3:37 p.m.
Its not dangerous, just inform the authors.
- Steve
On Mon, Mar 03, 2003 at 06:04:55 +0100, chris wrote:
Hi,
zynaddsubfx works fine with jackd.
But I have problems to connect iiwusynth (0.2.2) to jackd (0.51)
Maybe the options are not correct.
I start jackd with:
jackd -R -d alsa -d hw:0 -r 44100 -D
and iiwusynth with:
iiwusynth -m alsa_seq -a jack -z 1024 -c 2 -r 44100 VintageDreamsWaves.sf2'
*** libjack: WARNING! Use of function jack_set_buffer_size_callback() is
deprecated! ***
the sample rate is now 44100/sec
iiwusynth: error: Cannot activate the iiwusynth as a JACK client
Failed to create the synthesizer
Other applications like muse and alsaplayer works fine. But I always get the
massage
*** libjack: WARNING! Use of function jack_set_buffer_size_callback() is
deprecated! ***
any ideas?
thanks
chris
2:14 p.m.
On Monday 03 March 2003 08:28 am, Mark Knecht wrote:
[...]
If you use qjackconnect, you'll get a GUI that
will make this more obvious.
It will show you your sound card ports and your soft synth ports. iiwusynth
hook up automatically to playback_1 & 2, so I get sound automatically.
ZynAddSubFx does not. You must hook it up using qjc to get sound. (Or
possibly at the command line.)
Downloaded qjackconnect, ran it, hooked some things up and now zynaddsubfx
works with jack. (btw, zynaddsubfx absolutely rocks!)
Everything seems to be cooperating fine, except for the fact I get massive
amounts of xruns when sequencing with rosegarden. What is odd is that the
load goes up incrementally over time, roughly about 30 seconds and its xrun
city.
I looked at jackd options, maybe someone could explain what they do for me:
1. -p,--period <n> frames per period (default: 1024)
2. -n,--nperiods <n> number of periods in hardware buffer (default: 2)
3. -H,--hwmon use hardware monitoring, if available (default: no)
4. -s,--softmode soft-mode, no xrun handling (default: off)
Also, qjackconnect constantly segfaults. Is this common?
Another issue I ran into was my alsa drivers. When trying to use the rc7 and
rc8, some software runs into an ioctl() problem (iiwusynth in particular).
It looks like when it opens my /dev/snd/pcmC0D0p device, that it passes a bad
argument to ioctl(), then just sits in a tight loop until I ctrl-c it. The
problem appears to be in alsa-lib. I reverted back to rc5 and the problem
went away.
Has anyone tried the dmix plugin thats part of alsa rc8? This looks
interesting, but im scared if I install rc8, I will be bitten by that
alsa-lib bug again.
--
Levi Burton
http://www.puresimplicity.net/~ldb/
2:47 p.m.
New subject: [linux-audio-user] dmix vs alsaplayer [was jackd, zynaddsubfx and iiwusynth]
Levi Burton wrote:
Has anyone tried the dmix plugin thats part of alsa
rc8? This looks
interesting, but im scared if I install rc8, I will be bitten by that
alsa-lib bug again.
I was fscking around with it on Saturday. So far I have managed to use
multiple instances of aplay but other apps like alsaplayer bork at it. I
have yet to figure out why but I think I should probably submit a bug
report somewhere.
I had to remove /dev/dsp otherwise alsaplayer will use the oss drivers.
Both of these commands give the same error.
$ alsaplayer -o alsa -d "plug:'dmix:RATE=44100'" track_8.wav
$ alsaplayer -o alsa -d plug:\'dmix:SLAVE=\"hw:2,1\",RATE=44100\'
track_8.wav
--------
error on set_period_size (512)
Unavailable hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S16_LE
SUBFORMAT: STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (125011 125012)
PERIOD_SIZE: 5513
PERIOD_BYTES: 22052
PERIODS: (2 3)
BUFFER_TIME: (371519 371520)
BUFFER_SIZE: 16384
BUFFER_BYTES: 65536
TICK_TIME: ALL
error on set_period_size (1024)
Unavailable hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S16_LE
SUBFORMAT: STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (125011 125012)
PERIOD_SIZE: 5513
PERIOD_BYTES: 22052
PERIODS: (2 3)
BUFFER_TIME: (371519 371520)
BUFFER_SIZE: 16384
BUFFER_BYTES: 65536
TICK_TIME: ALL
failed to configure output device...trying OSS
error opening /dev/dsp
I could not find a suitable output module on your
system. Make sure they're in "/usr/local/lib/alsaplayer/output/".
Use the -o parameter to select one.
failed to load output plugin (alsa). exitting...
--------
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Being on stage with the band in front of crowds shouting, "Get off! No!
We want normal music!", I think that was more like acting than anything
I've ever done.
Goldie, 8 Nov, 2002
The Scotsman
3:18 p.m.
New subject: [linux-audio-user] Re: [Alsa-devel] dmix vs alsaplayer [was jackd, zynaddsubfx and iiwusynth]
On Tue, 4 Mar 2003, Patrick Shirkey wrote:
I've tried it with ecasound and seems to work just fine. One catch is that
dmix only supports a certain set of audio format parameters at a time. You
can change these via asoundrc (or dmix:x,y), but not at run time. Anyway,
with default dmix installation (on top of snd-intel8x0 hw):
ecasound -i foo.wav -o alsa,dmix -b:4096 &
ecasound -i bar.wav -o alsa,dmix -b:4096
... plays the two files at the same time. -b:4096 is needed because of the
abovementioned reasons.
Has anyone
tried the dmix plugin thats part of alsa rc8? This looks
I was fscking around
with it on Saturday. So far I have managed to use
multiple instances of aplay but other apps like alsaplayer bork at it. I
have yet to figure out why but I think I should probably submit a bug
report somewhere. $ alsaplayer -o alsa -d
plug:\'dmix:SLAVE=\"hw:2,1\",RATE=44100\'
track_8.wav
[...]
PERIOD_SIZE: 5513
PERIOD_BYTES: 22052
[...]
error on set_period_size (1024)
Unavailable hw params:
Try matching the alsaplayer period_size to the one used by dmix with
the "-f 22052" alsaplayer option.
PS Opening dmix in non-interleaved mode produces totally garbled output:
"ecasound -i foo.wav -f:16,2,44100,n -o alsa,dmix -b:4096"
--
http://www.eca.cx
Audio software for Linux!
3:44 p.m.
New subject: [linux-audio-user] Re: [Alsa-devel] dmix vs alsaplayer [was jackd, zynaddsubfx and iiwusynth]
On Mon, 3 Mar 2003, Kai Vehmanen wrote:
Try matching the alsaplayer period_size to the one
used by dmix with
the "-f 22052" alsaplayer option.
alsaplayer doesn't accept resolution other than multiple of 32 bytes
PS Opening dmix in non-interleaved mode produces totally garbled output:
"ecasound -i foo.wav -f:16,2,44100,n -o alsa,dmix -b:4096"
Works here - using standard stereo device.
Jaroslav
-----
Jaroslav Kysela <perex(a)suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
4 Mar
4 Mar
5:06 a.m.
On Mon, Mar 03, 2003 at 07:40:09 +0000, anton wrote:
I've allways had a problem with it quiting when other jack apps quit, but
i never bother checking to see if it was a segfault or not.
- Steve
Also, qjackconnect constantly segfaults. Is this
common?
I think it doesnt work well with jackd > 0.5
It used to be ok with older versions of jack. It is kind of unusuable for me
now with latest jack from cvs.
12:33 a.m.
Levi Burton <donburton(a)sbcglobal.net> writes:
I looked at jackd options, maybe someone could explain
what they do for me:
1. -p,--period <n> frames per period (default: 1024)
2. -n,--nperiods <n> number of periods in hardware buffer (default: 2)
3. -H,--hwmon use hardware monitoring, if available (default: no)
4. -s,--softmode soft-mode, no xrun handling (default: off)
I'll try. Someone please correct me if I get any of this wrong.
-p sets the number of frames between JACK process() calls. This
must be a power of two (IIRC).
-n is the number of such periods in the buffer. P*N*4 is the size
of the JACK buffer in bytes. Larger buffers yield higher latency,
but fewer xruns.
If you need low latency, set -p and -n as low as you can without xrun
problems. Reasonably well-tuned current-generation systems with a
decent sound card and JACK running --realtime on a low-latency kernel
can handle -p 128 -n 3 reliably. Some can do better. Tuning a system
for low latency is challenging.
If you don't need low latency, set -p and -n higher to insulate
yourself from xruns.
-H tells JACK that your sound card provides capture input
monitoring.
-s tells JACK's ignore xruns reported by the ALSA driver. This
makes JACK less likely to disconnect ports when running without
--realtime.
--
Jack O'Quin
Austin, Texas, USA
3 Mar
3 Mar
3:16 p.m.
New subject: [linux-audio-user] no mixers and distorted playback on maudio quattro
I'm curious about what's going wrong, I recompiled alsa from source and
found that though playback is ok from some apps, I get an error from
alsamixer that no mixer elems are found, and I get only super distorted
playback from terminatorX. I'm using a dell inspirion 2500 laptop with the
built in touchpad mouse.
http://www.brianredfern.org
7937
days inactive
7938
days old
linux-audio-user@lists.linuxaudio.org
16 comments
13 participants
participants (13)
-
anton -
Brian Redfern -
chris -
holborn -
Jack O'Quin -
Jaroslav Kysela -
Kai Vehmanen -
Levi Burton -
Mark Knecht -
Mark Knecht -
Patrick Shirkey -
Steve Harris -
Tim Hall