28 Jul
2005
28 Jul
'05
11:36 p.m.
Hello,
I am a fairly new Linux user - I like what I see so far, but having
great diffculties with MIDI.
Specs:
Ubuntu Linux 5.04
KDE
Compaq Pressario 333 mhz (..I know.....)
256 RAM (again...I know...old machine)
SoundCard - Turtle Beach Santa Cruz 5.1
(manufacturer tells me it does indeed have an onboard hardware synth)
Roland Sound Canvas SC-88 hooked up via joystick port
Audio such as MP3 works fine through such things as Alsaplayer and Xine.
KDE's KInfoCenter / Sound tells me:
Sound Driver:3.8.1a-980706(ALSA v1.06 emulation code)
Kernal: Linux PhilLinx 2.6.10-5-386#1 and so forth
Config options:0
Installed Drivers: Type 10:ALSA emulation
Card Config: Sound Fusion CS46xx at 0x41300000/0x41200000,irq 11
Audio devices:0:CS46XX(DUPLEX)
Synth devices: NOT ENABLED
Midi devices: 0:CS46XX
Timers:
7:system timer
Mixers:
0:Cirrus Logic CS4297A rev 4,Cirr
lsmod | grep snd tells me:
snd_emu10k1_synth 6656 0
snd_emu10k1 81668 1 snd_emu10k1_synth
snd_emux_synth 33280 1 snd_emu10k1_synth
snd_seq_virmidi 7296 1 snd_emux_synth
snd_seq_midi_emul 7424 1 snd_emux_synth
snd_hwdep 9220 2 snd_emu10k1,snd_emux_synth
snd_util_mem 4608 2 snd_emu10k1,snd_emux_synth
snd_cs46xx 80328 0
snd_ac97_codec 64608 2 snd_emu10k1,snd_cs46xx
snd_pcm_oss 47652 0
snd_mixer_oss 16768 1 snd_pcm_oss
snd_pcm 84872 4 snd_emu10k1,snd_cs46xx,snd_ac97_codec,snd_pcm_os
s
snd_page_alloc 9604 3 snd_emu10k1,snd_cs46xx,snd_pcm
gameport 4608 2 analog,snd_cs46xx
snd_seq_midi 8224 0
snd_rawmidi 22944 4 snd_emu10k1,snd_seq_virmidi,snd_cs46xx,snd_seq_m
idi
snd_seq_oss 30080 0
snd_seq_midi_event 7424 3 snd_seq_virmidi,snd_seq_midi,snd_seq_oss
snd_seq 46992 8 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul
,snd_seq_midi,snd_seq_oss,snd_seq_midi_event
snd_timer 23300 2 snd_pcm,snd_seq
snd_seq_device 8332 7 snd_emu10k1_synth,snd_emu10k1,snd_emux_synth,snd
_seq_midi,snd_rawmidi,snd_seq_oss,snd_seq
snd 50276 14 snd_emu10k1,snd_emux_synth,snd_seq_virmidi,snd_
hwdep,snd_cs46xx,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,sn
d_seq_oss,snd_seq,snd_timer,snd_seq_device
soundcore 9824 1 snd
Any ideas if ALSA simply cannot recognize this soundcard or I simply have something out of
whack?
thanks,
PhilJ
8:34 p.m.
Christoph Eckert wrote:
Am Freitag, 29. Juli 2005 03:36 schrieb PhilJackson:
result of
cat /proc/asound/cards
Any ideas if ALSA simply cannot recognize this
soundcard or
I simply have something out of whack?
Could you post the output of
cat /proc/asound/cards
and
aconnect -io
?
Best regards
ce
0 [CS46xx ]: CS46xx - Sound Fusion CS46xx
Sound Fusion CS46xx at 0x41300000/0x41200000, irq 11
----------------------------
result of
aconnect -io
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 64: 'CS46XX' [type=kernel]
0 'CS46XX '
thanks,
Phil J.
1 Aug
1 Aug
2:36 a.m.
On Fri, 2005-07-29 at 17:34 -0500, PhilJackson wrote:
aconnect -io
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 64: 'CS46XX' [type=kernel]
0 'CS46XX '
What app are you using to play the MIDI files? IOW where are the MIDI
messages that play the SoundCanvas supposed to come from?
Normally to play an external MIDI module from your computer you'd either
run a sequencer, or connect an external MIDI keyboard. But none of
these are showing up in your list.
Also are you sure the joystick port is enabled in the BIOS? Normally it
would show up as "MPU-401" or something.
Lee
2:49 a.m.
On Mon, 2005-08-01 at 00:36 -0400, Lee Revell wrote:
On Fri, 2005-07-29 at 17:34 -0500, PhilJackson wrote:
Hmm, I have the "Midi Through" port. I don't think older versions of
ALSA had it.
root@mindpipe:/home/rlrevell# aconnect -io
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 62: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 64: 'Audigy MPU-401 (UART)' [type=kernel]
0 'Audigy MPU-401 (UART)'
32 'Audigy MPU-401 #2'
client 65: 'Emu10k1 WaveTable' [type=kernel]
0 'Emu10k1 Port 0 '
1 'Emu10k1 Port 1 '
2 'Emu10k1 Port 2 '
3 'Emu10k1 Port 3 '
Lee
aconnect -io
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 64: 'CS46XX' [type=kernel]
0 'CS46XX '
3:07 a.m.
Lee,
I am coming from a Windows environement where MIDI and such just
"works" . The screen capture was just doing the aconnect from the
command window with no other app running. Ultimately I'd
like to be running some algo software like KeyKit generating the MIDI
and directing it to the soundcanvas, or using some utlility like pmidi
to play an existing midi file through the soundcanvas.
Joystick port - at this point I am unsure of most anything. In this
machine's previous life as a Win ME machine it did work, though with a
different soundcard.
thanks,
Phil J.
Lee Revell wrote:
On Fri, 2005-07-29 at 17:34 -0500, PhilJackson wrote:
aconnect -io
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 64: 'CS46XX' [type=kernel]
0 'CS46XX '
What app are you using to play the MIDI files? IOW where are the MIDI
messages that play the SoundCanvas supposed to come from?
Normally to play an external MIDI module from your computer you'd either
run a sequencer, or connect an external MIDI keyboard. But none of
these are showing up in your list.
Also are you sure the joystick port is enabled in the BIOS? Normally it
would show up as "MPU-401" or something.
Lee
3:18 a.m.
On Mon, 2005-08-01 at 00:07 -0500, PhilJackson wrote:
Lee,
I am coming from a Windows environement where MIDI and such just
"works" .
OK, this is a common point of confusion, because Windows and MacOS come
with a toy softsynth, so you can just double click on a .mid file and
hear sound.
On linux, to do the same you would have to run a soft synth like
Fluidsynth. Launching the softsynth will cause an input MIDI port and
output Audio port to appear in qjackctl, and you'd just connect the
output of fluidsynth to the ALSA playback input of alsa_playback to hear
the sound.
Joystick port - at this point I am unsure of most
anything. In this
machine's previous life as a Win ME machine it did work, though with a
different soundcard.
OK. It's not clear that ALSA is seeing this port.
Lee
10:50 p.m.
OK. It's not clear that ALSA is seeing this port.
Lee
Hi Lee,
This tells me what it is seeing:
root@PhilLinux:/home/fractalvibes # aconnect -io
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 64: 'CS46XX' [type=kernel]
0 'CS46XX '
Since I've been told that Alsa does not support the hardware synth on
the soundcard type CS46XX, getting the MIDI routed through the soundcard
to the Sound Canvas seems the only thing to do. I take it that the
joystick port should be showing as some type of "through"
port? So maybe anything Alsa,jack, etc. tries to route to CS46XX just
goes into the "bit bucket"?
thanks,
Phil
2 Aug
2 Aug
5:49 a.m.
PhilJackson wrote:
This tells me what it is seeing:
root@PhilLinux:/home/fractalvibes # aconnect -io
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 64: 'CS46XX' [type=kernel]
0 'CS46XX '
Since I've been told that Alsa does not support the hardware synth on
the soundcard type CS46XX, getting the MIDI routed through the soundcard
to the Sound Canvas seems the only thing to do.
Yes.
I take it that the joystick port should be showing as
some type of
"through" port?
No, it should be showing as "CS46XX". Fortunately, it does. :-)
So maybe anything Alsa,jack, etc. tries to route to
CS46XX just
goes into the "bit bucket"?
Anything sent to this port should go to the Sound Canvas.
Does "aplaymidi -p 64:0 something.mid" work?
Regards,
Clemens
29 Jul
29 Jul
1:19 p.m.
PhilJackson wrote:
SoundCard - Turtle Beach Santa Cruz 5.1
(manufacturer tells me it does indeed have an onboard hardware synth)
The wavetable synth of CS46xx-based sound cards isn't supported by
ALSA.
Roland Sound Canvas SC-88 hooked up via joystick port
This one should work.
Regards,
Clemens
8:36 p.m.
Clemens Ladisch wrote:
PhilJackson wrote:
Thanks for confirming that. How doI make it route the MIDI through the
soundcard to the soundcanvas (and then back into the card to be played
as audio)?
thanks,
Phil J.
SoundCard - Turtle Beach Santa Cruz 5.1
(manufacturer tells me it does indeed have an onboard hardware synth)
The wavetable synth of CS46xx-based sound cards isn't supported by
ALSA.
Roland Sound Canvas SC-88 hooked up via joystick
port
This one should work.
Regards,
Clemens
30 Jul
30 Jul
12:47 a.m.
Christoph Eckert wrote:
Ok thanks. I fired up qjackctl and haven't the foggiest idea what to
do with it. Sorry -Windows user and quite unfamiliar. I don't know
Jack about Jack. The task at hand is probably quite simple for the old
hands but I haven't a clue.
thanks,
Phil J.
Thanks for
confirming that. How doI make it route the MIDI
through the soundcard to the soundcanvas (and then back
into the card to be played as audio)?
On the command line you can use aconnect to do so, if you
prefer GUI programs then install qjackctl.
Best regards
ce
1:05 a.m.
On Fri, 2005-07-29 at 21:47 -0500, PhilJackson wrote:
Christoph Eckert wrote:
Ok thanks. I fired up qjackctl and haven't the foggiest idea what to
do with it. Sorry -Windows user and quite unfamiliar. I don't know
Jack about Jack. The task at hand is probably quite simple for the old
hands but I haven't a clue.
Click the "connect" button, then click "MIDI". The rest should be
self
explanatory.
Lee
Thanks for
confirming that. How doI make it route the MIDI
through the soundcard to the soundcanvas (and then back
into the card to be played as audio)?
On the command line you can use aconnect to do so, if you
prefer GUI programs then install qjackctl.
Best regards
ce
1:25 a.m.
On Fri, 2005-07-29 at 21:47 -0500, PhilJackson wrote:
Ok thanks. I fired up qjackctl and
haven't the foggiest idea what to
do with it. Sorry -Windows user and quite unfamiliar. I don't know
Jack about Jack. The task at hand is probably quite simple for the old
hands but I haven't a clue.
not suprising that you'd find it confusing. it is confusing.
1) sending MIDI to a h/w synth on a souncard
a) you need to find out which ALSA sequencer port is representing
the synth. the simplest way to find out is from the command line
with the command:
aconnect -o
the output should give you some clue about a pair of numbers
to use that correspond to your soundcanvas. For example:
---- output from aconnect -o on my system -------
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 62: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 72: ' MIDI 1' [type=kernel]
0 ' MIDI 1 '
32 ' MIDI 2 '
--------------------------------------------------
that third client, mysteriously enough, is an RME HDSP
with 2 h/w MIDI ports. the first h/w port would be
sequencer port 72:0, the second 72:32.
the pattern is: <client ID>:<port ID>
b) then get hold of pmidi, a nice command line tool
for sending MIDI to an ALSA sequencer port. use this
command to do what you want:
pmidi -p <clientID>:<portID> yourmidifile.mid
changing the values of <clientID>, <portID> and the name
of the file to something more appropriate, such as
pmidi -p 72:0 bach_tocatta_and_fugue.mid
2) getting audio back
This is actual much harder to describe. It depends on the
intimate and ugly details of your Soundscape's builtin
h/w mixer, and without access to it, it will be hard
to describe what you need to do. Every h/w mixer in every
card is different, despite the presence of a few
"standards" for such things.
What you will need is an ALSA program to manipulate the
h/w mixer. I like alsamixer, which runs in a terminal
window; I like it because it shows me everything and
doesn't try to be all cute like a generic windows mixer app.
The goal is to identify which signal stream corresponds
to the output of the MIDI h/w synth, and select it
as the capture source (in alsamixer, done by moving
the "focus" to that mixer/signal stream, and pressing
the spacebar.
After that, every app that records from the soundscape
will be listening to the output from the MIDI synth.
If this all appears arcane and absurd, don't worry, it is.
The problem on linux is that we (generally) attempt to use generic tools
that are independent of the particular h/w installed. For very simple
things, this works well, but audio + MIDI interfaces really do not tend
to benefit from the current approach that has been taken, and it
requires a lot of knowledge on the part of the user to make sense of the
information that is presented.
--p
Thanks for confirming that. How doI make it route the
MIDI
through the soundcard to the soundcanvas (and then back
into the card to be played as audio)?
2:18 a.m.
On Fri, 2005-29-07 at 23:26 -0400, Paul Davis wrote:
The problem on linux is that we (generally) attempt to
use generic tools
that are independent of the particular h/w installed. For very simple
things, this works well, but audio + MIDI interfaces really do not tend
to benefit from the current approach that has been taken, and it
requires a lot of knowledge on the part of the user to make sense of the
information that is presented.
IMO, it's not this approach that's intrinsically confusing - we just
need shinier GUI tools to make it more intuitive for newbs (and simpler
for everyone)
-DR-
6:25 a.m.
IMO, it's not this approach that's
intrinsically confusing
- we just need shinier GUI tools to make it more intuitive
for newbs (and simpler for everyone)
one idea was that MIDI and even audio connections can be made
from within an application's interface, or at least if an
application had a button to invoke [qjackctl, qjackconnect,
aconnect, ...].
Best regards
ce
10:05 p.m.
Thanks very much for the info! When I did the aconnect -i and aconnect
-o I didn't see any of the through-ports - bad sign?
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 64: 'CS46XX' [type=kernel]
0 'CS46XX '
fractalvibes@PhilLinux:~$ aconnect -o
client 64: 'CS46XX' [type=kernel]
0 'CS46XX '
thanks,
Phil J.
not suprising that you'd find it confusing. it is
confusing.
1) sending MIDI to a h/w synth on a souncard
a) you need to find out which ALSA sequencer port is representing
the synth. the simplest way to find out is from the command line
with the command:
aconnect -o
the output should give you some clue about a pair of numbers
to use that correspond to your soundcanvas. For example:
---- output from aconnect -o on my system -------
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 62: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 72: ' MIDI 1' [type=kernel]
0 ' MIDI 1 '
32 ' MIDI 2 '
--------------------------------------------------
that third client, mysteriously enough, is an RME HDSP
with 2 h/w MIDI ports. the first h/w port would be
sequencer port 72:0, the second 72:32.
the pattern is: <client ID>:<port ID>
b) then get hold of pmidi, a nice command line tool
for sending MIDI to an ALSA sequencer port. use this
command to do what you want:
pmidi -p <clientID>:<portID> yourmidifile.mid
changing the values of <clientID>, <portID> and the name
of the file to something more appropriate, such as
pmidi -p 72:0 bach_tocatta_and_fugue.mid
2) getting audio back
This is actual much harder to describe. It depends on the
intimate and ugly details of your Soundscape's builtin
h/w mixer, and without access to it, it will be hard
to describe what you need to do. Every h/w mixer in every
card is different, despite the presence of a few
"standards" for such things.
What you will need is an ALSA program to manipulate the
h/w mixer. I like alsamixer, which runs in a terminal
window; I like it because it shows me everything and
doesn't try to be all cute like a generic windows mixer app.
The goal is to identify which signal stream corresponds
to the output of the MIDI h/w synth, and select it
as the capture source (in alsamixer, done by moving
the "focus" to that mixer/signal stream, and pressing
the spacebar.
After that, every app that records from the soundscape
will be listening to the output from the MIDI synth.
If this all appears arcane and absurd, don't worry, it is.
The problem on linux is that we (generally) attempt to use generic tools
that are independent of the particular h/w installed. For very simple
things, this works well, but audio + MIDI interfaces really do not tend
to benefit from the current approach that has been taken, and it
requires a lot of knowledge on the part of the user to make sense of the
information that is presented.
--p
1 Aug
1 Aug
10 a.m.
PhilJackson wrote:
$ aconnect -o
client 64: 'CS46XX' [type=kernel]
0 'CS46XX '
This is the MIDI port of your sound card. The cs46xx driver names it
"CS46XX" to differentiate it from any other MIDI ports you (might)
have.
You should be able to play to this port with
aplaymidi -p 64:0 something.mid
(or pmidi instead of aplaymidi). This port will also show up in your
sequencer application.
When I did the aconnect -i and aconnect -o I
didn't see any of the
through-ports - bad sign?
No; you don't need any Through port unless you want to route MIDI data
in complicated ways. If you really want it, you can load the
snd-seq-dummy module manually (newer versions of ALSA load it by
default).
HTH
Clemens
10:57 p.m.
Hi Clemmens,
From what I've learned so far, routing MIDI through the
"through"
port may be my only options. Apparently Alsa does not support the
hardware synth on the CS64XX (Turtle Beach Santa Cruz) sound
card. Routing to the external sound module appears to be
neccessary, and was my ultimate goal anyhow.
thanks,
Phil
When I did the aconnect -i and aconnect -o I
didn't see any of the
through-ports - bad sign?
No; you don't need any Through port unless you want to route MIDI data
in complicated ways. If you really want it, you can load the
snd-seq-dummy module manually (newer versions of ALSA load it by
default).
HTH
Clemens
31 Jul
31 Jul
12:15 a.m.
I think #2 might be the easy part. The external soundcanvas has a
button which will generate a "test" signal - this seems to come back
through and out the speakers just fine. Seems to be "Line" on the
Alsamixer.
Perhaps ALSA is not seeing the port through which the MIDI signal needs
to go through to the external module? Your example of aconnect -o
showed a Midi Through port - mine does not show.
Minor fix or fundamental problem? Thinking the latter, as
[type=kernel] sounds like something fundamental to the OS I am guessing.....
thanks to all for the suggestions - at least it is narrowed down to some
"might work / should work" and "won't work" answers.
Phil J.
This is actual much harder to describe. It
depends on the
intimate and ugly details of your Soundscape's builtin
h/w mixer, and without access to it, it will be hard
to describe what you need to do. Every h/w mixer in every
card is different, despite the presence of a few
"standards" for such things.
What you will need is an ALSA program to manipulate the
h/w mixer. I like alsamixer, which runs in a terminal
window; I like it because it shows me everything and
doesn't try to be all cute like a generic windows mixer app.
The goal is to identify which signal stream corresponds
to the output of the MIDI h/w synth, and select it
as the capture source (in alsamixer, done by moving
the "focus" to that mixer/signal stream, and pressing
the spacebar.
After that, every app that records from the soundscape
will be listening to the output from the MIDI synth.
If this all appears arcane and absurd, don't worry, it is.
The problem on linux is that we (generally) attempt to use generic tools
that are independent of the particular h/w installed. For very simple
things, this works well, but audio + MIDI interfaces really do not tend
to benefit from the current approach that has been taken, and it
requires a lot of knowledge on the part of the user to make sense of the
information that is presented.
--p
30 Jul
30 Jul
6:30 a.m.
Ok thanks. I fired up qjackctl and haven't the
foggiest
idea what to do with it.
Audio applications which use MIDI via the ALSA sequencer or
even JACK do usually not autoconnect to [MIDI/AUDIO][In/Out].
You have to do it manually.
In Qjackctl klick on connect and connect your applications and
hardware ports as desired, regardless if it was MIDI or
audio.
Best regards
ce
9:51 p.m.
Christoph Eckert wrote:
Readable Clients /output on the other Writeable Clients /input
Under both are two "ports"
one with a plugin port icon -64:CS46XX
one that looks like the plug on a cable 0:CS64XX
Which is which?
Under the Audio tab it is simply blank
When I click "Start" I get the message below -don't know what they mean,
but it doesn't look good...
Phil J.
Error messages from Jack below:
18:28:24.341 Statistics reset.
18:28:25.558 MIDI connection graph change.
18:28:25.565 MIDI connection change.
18:34:12.073 MIDI connection change.
18:34:17.703 MIDI connection change.
18:34:42.249 Startup script...
18:34:42.254 artsshell -q terminate
18:34:43.299 Startup script terminated with exit status=256.
18:34:43.436 JACK is starting...
18:34:43.438 /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p1024 -n2
18:34:43.473 JACK was started with PID=7800 (0x1e78).
jackd 0.99.0
Copyright 2001-2003 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 ..
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
Couldn't open hw:0 for 32bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 16bit instead
ALSA: cannot set period size to 1024 frames for capture
ALSA: cannot configure capture channel
cannot load driver module alsa
18:34:43.998 JACK was stopped successfully.
18:34:45.500 Could not connect to JACK server as client.
18:36:16.931 Startup script...
18:36:16.941 artsshell -q terminate
18:36:17.460 Startup script terminated with exit status=256.
18:36:17.464 JACK is starting...
18:36:17.466 /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p1024 -n2
18:36:17.484 JACK was started with PID=7803 (0x1e7b).
jackd 0.99.0
Copyright 2001-2003 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 ..
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
Couldn't open hw:0 for 32bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 16bit instead
ALSA: cannot set period size to 1024 frames for capture
ALSA: cannot configure capture channel
cannot load driver module alsa
18:36:17.686 JACK was stopped successfully.
18:36:19.532 Could not connect to JACK server as client.
Ok thanks. I
fired up qjackctl and haven't the foggiest
idea what to do with it.
Audio applications which use MIDI via the ALSA sequencer or
even JACK do usually not autoconnect to [MIDI/AUDIO][In/Out].
You have to do it manually.
In Qjackctl klick on connect and connect your applications and
hardware ports as desired, regardless if it was MIDI or
audio.
Best regards
ce
Thanks. I clicked "connect" and am looking at the MIDI tab.On one side is
31 Jul
31 Jul
9:05 a.m.
Last Sunday 31 July 2005 00:51, PhilJackson was like:
Christoph Eckert wrote:
Readable Clients /output on the other Writeable Clients /input
Under both are two "ports"
one with a plugin port icon -64:CS46XX
one that looks like the plug on a cable 0:CS64XX
Which is which?
64 should drive the SoundCanvas. This is usually the external MIDI port.
Ok thanks.
I fired up qjackctl and haven't the foggiest
idea what to do with it.
Audio applications which use MIDI via the ALSA sequencer or
even JACK do usually not autoconnect to [MIDI/AUDIO][In/Out].
You have to do it manually.
In Qjackctl klick on connect and connect your applications and
hardware ports as desired, regardless if it was MIDI or
audio.
Best regards
ce
Thanks. I clicked "connect" and am looking at the MIDI tab.On one side is
Under the Audio tab it is simply blank
When I click "Start" I get the message below -don't know what they mean,
but it doesn't look good...
Phil J.
Error messages from Jack below:
18:28:24.341 Statistics reset.
18:28:25.558 MIDI connection graph change.
18:28:25.565 MIDI connection change.
18:34:12.073 MIDI connection change.
18:34:17.703 MIDI connection change.
18:34:42.249 Startup script...
18:34:42.254 artsshell -q terminate
18:34:43.299 Startup script terminated with exit status=256.
18:34:43.436 JACK is starting...
18:34:43.438 /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p1024 -n2
18:34:43.473 JACK was started with PID=7800 (0x1e78).
jackd 0.99.0
Copyright 2001-2003 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 ..
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
Couldn't open hw:0 for 32bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 16bit instead
ALSA: cannot set period size to 1024 frames for capture
ALSA: cannot configure capture channel
cannot load driver module alsa
18:34:43.998 JACK was stopped successfully.
18:34:45.500 Could not connect to JACK server as client.
18:36:16.931 Startup script...
18:36:16.941 artsshell -q terminate
18:36:17.460 Startup script terminated with exit status=256.
18:36:17.464 JACK is starting...
18:36:17.466 /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p1024 -n2
18:36:17.484 JACK was started with PID=7803 (0x1e7b).
jackd 0.99.0
Copyright 2001-2003 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 ..
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
Couldn't open hw:0 for 32bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 16bit instead
ALSA: cannot set period size to 1024 frames for capture
ALSA: cannot configure capture channel
cannot load driver module alsa
18:36:17.686 JACK was stopped successfully.
18:36:19.532 Could not connect to JACK server as client.
This means ALSA isn't configured properly. Try alsaconf.
cheers,
tim hall
http://glastonburymusic.org.uk
12:13 p.m.
Tried alsaconf:
root@PhilLinux:/home/fractalvibes # alsaconf
bash: alsaconf: command not found
What might I be missing?
Phil J.
This means ALSA isn't configured properly. Try
alsaconf.
cheers,
tim hall
http://glastonburymusic.org.uk
2:33 p.m.
> When I click "Start" I get the message
below -don't know what they mean,
> but it doesn't look good...
>
> Phil J.
> Error messages from Jack below:
>
[ messages from JACK ]
> configuring for 48000Hz, period = 1024 frames,
buffer = 2 periods
> Couldn't open hw:0 for 32bit samples trying 24bit instead
> Couldn't open hw:0 for 24bit samples trying 16bit instead
> ALSA: cannot set period size to 1024 frames for capture
> ALSA: cannot configure capture channel
This means ALSA isn't configured properly. Try
alsaconf.
cheers,
tim hall
http://glastonburymusic.org.uk
It does not mean that at all.
It means that Phil's h/w cannot support 1024 frames/period on the
capture channel and/or cannot support full-duplex operation.
Phil - try configuring JACK to use 2048 frames/period, and try using the
-P and/or -C flag to specify playback-only or capture-only respectively.
This has nothing to do with alsaconf.
--p
3:26 p.m.
Last Sunday 31 July 2005 17:33, Paul Davis was like:
It does not mean that at all.
It means that Phil's h/w cannot support 1024 frames/period on the
capture channel and/or cannot support full-duplex operation.
Phil - try configuring JACK to use 2048 frames/period, and try using the
-P and/or -C flag to specify playback-only or capture-only respectively.
This has nothing to do with alsaconf.
I stand corrected.
cheers,
tim hall
http://glastonburymusic.org.uk
5:36 p.m.
Ok, so if this is not an ALSA problem at all, then how
do I go about configuring
JACK in this manner? (I suppose there are some command line
commands to run?)
thanks,
Phil J.
p.s. I did find alsaconf in the KDE menu -
Debian/Apps/System/Admin/Alsaconf
but it wants me to log in as root (not as sudo su) and I don't recall
the password I set...arrg!
It means that Phil's h/w cannot support 1024
frames/period on the
capture channel and/or cannot support full-duplex operation.
Phil - try configuring JACK to use 2048 frames/period, and try using the
-P and/or -C flag to specify playback-only or capture-only respectively.
This has nothing to do with alsaconf.
--p
7:08 p.m.
I did find alsaconf in the KDE menu -
It's a shell script and it will be most likely not in the K
menu.
Open a terminal window, type su...
Debian/Apps/System/Admin/Alsaconf
but it wants me to log in as root (not as sudo su) and I
don't recall the password I set...arrg!
...and enter the root passphrase, then type /sbin/alsaconf.
OTOH, Paul Davis threw in that it's not an ALSA problem but a
JACK one. Try setting the parameters on the command line or
in qjackctl as he recommended instead of running alsaconf.
BTW: Never forget the root password! But before you reinstall:
there are ways to reset the root passphrase...
Best regards
ce
1 Aug
1 Aug
1:05 a.m.
I did as Paul suggested in qjackctl and set the frames/period to 2048.
Same error. At 512 frames per period and below qjackctl seems to run
fine. Above 512 I get the same errors that jack server cannot start.
Still no evidence of anything hitting the soundcanvas. Qjackclt
gave me the options of hw:0, default, and hw:1. The latter gave me the
heinous error message popup, former 2 did not.
BTW - alsaconf is not at all installed, nor appears available. My
synaptic package manager informs me that I do indeed have alsa-utils,
looking at the properties/dependancies the file alsaconf falls under the
category of :
Conflicts: alsaconf
Conflicts: alsaconf-0.4
...
Replaces: alsautils
Replaces:alsaconf
for what it's worth.
thanks,
Phil J.
Debian/Apps/System/Admin/Alsaconf
but it wants me to log in as root (not as sudo su) and I
don't recall the password I set...arrg!
...and enter the root passphrase, then type /sbin/alsaconf.
OTOH, Paul Davis threw in that it's not an ALSA problem but a
JACK one. Try setting the parameters on the command line or
in qjackctl as he recommended instead of running alsaconf.
BTW: Never forget the root password! But before you reinstall:
there are ways to reset the root passphrase...
Best regards
ce
1:22 a.m.
On Sun, 2005-07-31 at 22:05, PhilJackson wrote:
I did as Paul suggested in qjackctl and set the
frames/period to 2048.
Same error. At 512 frames per period and below qjackctl seems to run
fine. Above 512 I get the same errors that jack server cannot start.
Still no evidence of anything hitting the soundcanvas. Qjackclt
gave me the options of hw:0, default, and hw:1. The latter gave me the
heinous error message popup, former 2 did not.
I don't know if this will help or if it even has anything to do with
it but you can write in your hardware in qjackctl. I only had default,
hw:0, and hw:1 but I wrote in ice1712 and that's what I'm using now.
--
Jan "Evil Twin" Depner
The Fuzzy Dice
http://myweb.cableone.net/eviltwin69/fuzzy.html
"As we enjoy great advantages from the invention of others, we should be
glad of an opportunity to serve others by any invention of ours, and this
we should do freely and generously."
Benjamin Franklin, on declining patents offered by the governor of
Pennsylvania for his "Pennsylvania Fireplace", c. 1744
1:37 a.m.
Jan Depner wrote:
I don't know if this will help or if it even has anything to do with
it but you can write in your hardware in qjackctl. I only had default,
hw:0, and hw:1 but I wrote in ice1712 and that's what I'm using now.
An idea - how do I know what to write in and how would I do it?
thanks,
Phil J.
8:36 a.m.
Hi Phil,
An idea - how do I know what to write in and how would
I do
it?
let me summarize:
* JACK runs well on top of your card. Did you try if audio
output via any JACK application works? I'd try playing an mp3
or ogg file with xmms via its JACK output plugin. But
currently you try to get MIDI working so this isn't urgent
* The Card appears in ALSA as a writable MIDI port, correct?
* If so you should test if MIDI goes out of the card. The
simplest way to do so is running something like vkeybd, an
onscreen MIDI keyboard. If you haven't it install, please try
installing it.
* It is important to know that Linux has very flexible MIDI
routing abilities thanks to the ALSA sequencer. OTOH, this
means that MIDI applications usually don't connect
automatically. Use qjackctl, Connections, MIDI to connect the
vkeybd to the MIDI out port of your card.
* Use the mouse or the computer keyboard to play some notes.
Does the Soundcanvas receive MIDI data?
Best regards
ce
11:16 p.m.
Hi Christoph,
let me summarize:
* JACK runs well on top of your card. Did you try if audio
output via any JACK application works? I'd try playing an mp3
or ogg file with xmms via its JACK output plugin. But
currently you try to get MIDI working so this isn't urgent
Now that is an interesting question! I usually download/play mp3s
using alsaplayer, which seems the default. Xine usually plays my
CDs. When I open up XMMS with nothing else running except
browser and email client and go to Preferences / Audio - IO plugins,
I see Alsa,DiskWriter, eSound, and OSS as options. No mention of
Jack. I am quite newbie enough to not know if there is a sequence
of operations - i.e this has to be already running and that has to be
running....would think things should instantiate themselves as needed.
* The Card appears in ALSA as a writable MIDI port,
correct?
I think it is 64:0 CS46XX.
* If so you should test if MIDI goes out of the card.
The
simplest way to do so is running something like vkeybd, an
onscreen MIDI keyboard. If you haven't it install, please try
installing it.
I looked, and my package manager doesn't have anything like
that. pmidi or rosegarden should be able to send MIDI to the
card....
* It is important to know that Linux has very flexible
MIDI
routing abilities thanks to the ALSA sequencer. OTOH, this
means that MIDI applications usually don't connect
automatically. Use qjackctl, Connections, MIDI to connect the
vkeybd to the MIDI out port of your card.
* Use the mouse or the computer keyboard to play some notes.
Does the Soundcanvas receive MIDI data?
Yes, it seems that it does. Maybe I have an unfortunate mix
of hardware / software?
thanks,
Phil J.
Best regards
ce
2 Aug
2 Aug
2:56 a.m.
On Mon, 2005-08-01 at 20:15 -0500, PhilJackson wrote:
I looked, and my package manager doesn't have
anything like
that. pmidi or rosegarden should be able to send MIDI to the
card....
If Rosegarden is running it would show up in the list from aconnect,
which it doesn't for some reason. Then you would just connect it to the
output port.
Lee
3 Aug
3 Aug
12:06 a.m.
Hi Lee,
Perhaps I may have a fundamental lack of understanding of how all of this
works in concert? What widgets need I fire up in what order? Within a week
or so I may go in search of a sound card that Alsa and that system will use
And play midi via onboard synth hardware and has the required 15-pin
joystick port and put the Turtle Beach Santa Cruz card in this Win XP
machine. Any recommendations on cards meeting those requirements?
Many many thanks,
Phil J.
If Rosegarden is running it would show up in the list from aconnect,
which it doesn't for some reason. Then you would just connect it to the
output port.
Lee
4 Aug
4 Aug
2:46 p.m.
On Tue, 2005-08-02 at 21:06 -0500, pjfjacks wrote:
Hi Lee,
Perhaps I may have a fundamental lack of understanding of how all of this
works in concert? What widgets need I fire up in what order?
First launch Rosegarden. Then go into "Connect" in qjackctl, click the
"MIDI" tab, and connect Rosegarden's MIDI output to the CSxxx MIDI
input.
Lee
10:23 p.m.
Hi Lee,
Well things went form bad to worse...a post earlier this week suggested I go
here:
http://demudi.agnula.org/wiki/InstallApt
so I did and followed these instructions:
If you want to use the latest A/DeMuDi stable release (currently 1.2.1) you
can download packages from the Internet inserting the following lines in
your /etc/apt/sources.list file:
# A/DeMuDi stable
deb http://demudi.agnula.org/packages/demudi stable main
So I did that. Later I ran synaptic it wanted to update - took about 2
hours or so. Went back and fetched vkeybd as suggested. All ok until I
rebooted the machine - now I have no internet connectivity at all! Ubuntu
pretty much took care of setting up the network connections when initially
installed, so I've no idea what to change or to what. How can I get back to
where I was before? Reintall Ubuntu? Wipe the Disk? ARRRG!
BTW - tried as you suggested - cranked up ROseGarden, then fired up qjackctl
- under MIDI connections RoseGarden shows up as a Writable Client / Input
port - is that right? Anyways, jack won't tun now no matter the
frames/period selected....
Deep sigh...
Phil J.
On Tue, 2005-08-02 at 21:06 -0500, pjfjacks wrote:
Hi Lee,
Perhaps I may have a fundamental lack of understanding of how all of this
works in concert? What widgets need I fire up in what order?
First launch Rosegarden. Then go into "Connect" in qjackctl, click the
"MIDI" tab, and connect Rosegarden's MIDI output to the CSxxx MIDI
input.
Lee
11:45 p.m.
On Thu, 2005-08-04 at 19:23 -0500, pjfjacks wrote:
BTW - tried as you suggested - cranked up ROseGarden,
then fired up
qjackctl
- under MIDI connections RoseGarden shows up as a Writable Client /
Input
port - is that right? Anyways, jack won't tun now no matter the
frames/period selected....
That should have been all you needed to get it working. If you're jsut
trying to play an external MIDI module JACK does not need to be running.
I guess you'll have to reinstall Ubuntu.
Lee
5 Aug
5 Aug
12:03 a.m.
That should have been all you needed to get it working. If you're jsut
trying to play an external MIDI module JACK does not need to be running.
Yes, precisely what I am trying to do...
I guess you'll have to reinstall Ubuntu.
Was afraid you'd say that...here goes months of doing the minimal install
and painstakingly adding bits and pieces and struggling to get it all
working...arrrg!
Phil
Lee
12:21 a.m.
On Thu, 2005-08-04 at 21:03 -0500, pjfjacks wrote:
Was afraid you'd say that...here goes months of
doing the minimal install
and painstakingly adding bits and pieces and struggling to get it all
working...arrrg!
Eh, I've wiped out my systems a bunch of times, and it's always a lot
faster to get your settings back the second time.
Lee
12:54 a.m.
Just wish I'd taken better notes along the way...it pains me greatly.
Everything but MIDI was working so well. Totally shameful as the XP system
hums right along ...this isn't right at all..
Phil J.
Eh, I've wiped out my systems a bunch of times, and it's always a lot
faster to get your settings back the second time.
Lee
3:17 a.m.
On Thu, 2005-08-04 at 21:54 -0500, pjfjacks wrote:
Just wish I'd taken better notes along the
way...it pains me greatly.
Everything but MIDI was working so well.
Um, it sounded like things were working. Are you saying you connected
Rosegarden's outs to the MPU port in qjackctl, played a MIDI file and it
still didn't work?
Lee
9:16 a.m.
On Thu, 2005-08-04 at 21:54 -0500, pjfjacks wrote:
Just wish I'd taken better notes along the
way...it pains me greatly.
Everything but MIDI was working so well. Totally shameful as the XP system
hums right along ...this isn't right at all..
Phil J.
Eh, I've wiped out my systems a bunch of times, and it's always a lot
faster to get your settings back the second time.
phil, you are getting some very poor advice here, i am not sure why.
system reinstalls are *NOT* the way to solve problems with linux.
please would provide a summary of the story so far, and i'll try to get
you out of the hole you're in. if you have access to IRC, that could
also help move things along more rapidly.
3:52 p.m.
On Fri, 2005-08-05 at 07:16 -0400, Paul Davis wrote:
On Thu, 2005-08-04 at 21:54 -0500, pjfjacks wrote:
Hey,
I only said a reinstall might be a good idea as Phil had installed
Ubuntu (which worked perfectly AFAICT, except the MIDI thing which I
think was a config error), then added a Demudi source to his
sources.list which I don't think is supposed to work, and which really
hosed things (lost the network).
So he asked me if a Ubuntu reinstall is the best way to go from here and
I said probably. Obviously don't reinstall if you have data you care
about!
Maybe this was poor advice. However when I was a new Linux user and
really hosed things I often found a reinstall was teh quickest and
easiest way to get back to square one.
I'd actually be quite impressed by any newb who could install a Debian
based system correctly the first time.
Lee
Just wish I'd taken better notes along the
way...it pains me greatly.
Everything but MIDI was working so well. Totally shameful as the XP system
hums right along ...this isn't right at all..
Phil J.
Eh, I've wiped out my systems a bunch of times, and it's always a lot
faster to get your settings back the second time.
phil, you are getting some very poor advice here, i am not sure why.
system reinstalls are *NOT* the way to solve problems with linux.
4:07 p.m.
I only said a reinstall might be a good idea as Phil
had installed
Ubuntu (which worked perfectly AFAICT, except the MIDI thing which I
think was a config error), then added a Demudi source to his
sources.list which I don't think is supposed to work, and which really
hosed things (lost the network).
thats what i get for not paying enough attention. apologies.
phil, i take it back. reinstall. preferably not debian or anything
related to it ;) [ that was joke, for all you debian woody-head sid's
out there ]
--p
8:55 p.m.
Hi Paul,
Well it looks like a reinstall it is...will be a few days before I do this
most likely. Lee mentions something about the MIDI thing might have been a
config error - what should I look for during/after the reinstall?
I very much appreciate all the help and patience with a newbie!
Phil
(and I might mention that I did ask a good many questions when getting the
system up and running - and got some good advice - thanks Gavin and others!)
thats what i get for not paying enough attention. apologies.
phil, i take it back. reinstall. preferably not debian or anything
related to it ;) [ that was joke, for all you debian woody-head sid's
out there ]
--p
9:30 p.m.
On Fri, 2005-08-05 at 17:55 -0500, pjfjacks wrote:
Hi Paul,
Well it looks like a reinstall it is...will be a few days before I do this
most likely. Lee mentions something about the MIDI thing might have been a
config error - what should I look for during/after the reinstall?
I very much appreciate all the help and patience with a newbie!
Because you never said that you tried connecting Rosegarden's outputs to
the MPU-401 port in qjackctl and playing back a midi file with
Rosegarden and it didn't work.
Lee
11:09 p.m.
Lee,
I never saw a MPU-401 port at all. A post a few days ago established the
fact that ALSA does not support the hardware synth on this card. Playing
MIDI appears to be dependant upon getting MIDI generated via software on the
Linux machine routed through the soundcard to the external sound canvas, the
audio output of the sound canvas being routed back through the soundcard and
to the speakers and also able to be captured by some software on the Linux
machine to be recorded. Is anything Jack-related needed to do this? I have
been told both yes and no, perhaps due to my lack of clarity in explaining
what is needed to be accomplished. I've tried running Rosegarden and then
Starting qjackctl and since my large blunder it cannot start the Jack server
at all (until I do the reinstall).
Thanks!
Phil
Because you never said that you tried connecting Rosegarden's outputs to
the MPU-401 port in qjackctl and playing back a midi file with
Rosegarden and it didn't work.
Lee
5 Aug
5 Aug
9:46 p.m.
On Fri, 2005-08-05 at 17:55 -0500, pjfjacks wrote:
Hi Paul,
Well it looks like a reinstall it is...will be a few days before I do this
most likely. Lee mentions something about the MIDI thing might have been a
config error - what should I look for during/after the reinstall?
Rather than change a bunch of settings, if MIDI does not work OOTB after
you reinstall, then post a new bug report to the ALSA list.
Lee
13 Aug
13 Aug
9:01 a.m.
On Saturday 06 August 2005 00:46, Lee Revell wrote:
You are most likely to need to
# modprobe snd_mpu401 [or maybe| snd_mpu401_uart]
if ALSA doesn't configure it automatically.
cheers,
tim hall
http://glastonburymusic.org.uk/tim
Well it looks
like a reinstall it is...will be a few days before I do
this most likely. Lee mentions something about the MIDI thing might have
been a config error - what should I look for during/after the reinstall?
Rather than change a bunch of settings, if MIDI does not work OOTB after
you reinstall, then post a new bug report to the ALSA list. 
5 Aug
5 Aug
6:33 p.m.
Lee Revell wrote:
On Fri, 2005-08-05 at 07:16 -0400, Paul Davis wrote:
i'll second that ... a re-install can really learn you some fast lessons
about linux, too. of course, re-installing is something i avoid like the
plague now, but back when i was beginning .... man, i re-installed every
other day. one of the things i learnt to do from this, which makes
re-installing pretty painless if you've got a bunch of data and
configurations, is to have your /home folder on a seperate partition.
shayne
On Thu, 2005-08-04 at 21:54 -0500, pjfjacks
wrote:
Hey,
I only said a reinstall might be a good idea as Phil had installed
Ubuntu (which worked perfectly AFAICT, except the MIDI thing which I
think was a config error), then added a Demudi source to his
sources.list which I don't think is supposed to work, and which really
hosed things (lost the network).
So he asked me if a Ubuntu reinstall is the best way to go from here and
I said probably. Obviously don't reinstall if you have data you care
about!
Maybe this was poor advice. However when I was a new Linux user and
really hosed things I often found a reinstall was teh quickest and
easiest way to get back to square one.
Just wish I'd taken better notes along the
way...it pains me greatly.
Everything but MIDI was working so well. Totally shameful as the XP system
hums right along ...this isn't right at all..
Phil J.
Eh, I've wiped out my systems a bunch of times, and it's always a lot
faster to get your settings back the second time.
phil, you are getting some very poor advice here, i am not sure why.
system reinstalls are *NOT* the way to solve problems with linux.
11:44 p.m.
Thanks for the tip, Shayne. I'll hold off on the reinstall until next week.
Though it doesn't have internet access at the moment due to my blunders,
Everything else (except MIDI) appears to be functioning fine; my Father is
visiting from out of town Monday and I want to show him what Linux looks
like as he seems curious from all my "evangelizing" about it...
Plus I need to document some things about the system as is (minus my oops!)
Thanks,
Phil J.
i'll second that ... a re-install can really learn you some fast lessons
about linux, too. of course, re-installing is something i avoid like the
plague now, but back when i was beginning .... man, i re-installed every
other day. one of the things i learnt to do from this, which makes
re-installing pretty painless if you've got a bunch of data and
configurations, is to have your /home folder on a seperate partition.
shayne
8:48 p.m.
Hi Lee,
Yes, it installed and ran perfectly the first time. However, the full
install of Ubuntu proved a bit much for that little 333 mhz machine, so
I had to do more or less a custom install - install the minimal Ubuntu
(server install option I think). Apt-get some pieces, get synaptic, and
then selected apps. As far as I can tell, a correct install the first
time....
Phil
Hey,
I only said a reinstall might be a good idea as Phil had installed
Ubuntu (which worked perfectly AFAICT, except the MIDI thing which I
think was a config error), then added a Demudi source to his
sources.list which I don't think is supposed to work, and which really
hosed things (lost the network).
So he asked me if a Ubuntu reinstall is the best way to go from here and
I said probably. Obviously don't reinstall if you have data you care
about!
Maybe this was poor advice. However when I was a new Linux user and
really hosed things I often found a reinstall was teh quickest and
easiest way to get back to square one.
I'd actually be quite impressed by any newb who could install a Debian
based system correctly the first time.
Lee
6:23 a.m.
OH Yes!!
Been there on that, all working fine and then that little thought!!!
I'll just install that (?insert not really needed app on an audio WS!)
and Bye bye OS.
You really learn what not to install this way.
cheers
Bob
Lee Revell wrote:
On Thu, 2005-08-04 at 21:03 -0500, pjfjacks wrote:
Was afraid you'd say that...here goes months
of doing the minimal install
and painstakingly adding bits and pieces and struggling to get it all
working...arrrg!
Eh, I've wiped out my systems a bunch of times, and it's always a lot
faster to get your settings back the second time.
Lee
2:46 a.m.
New subject: [linux-audio-user] PD question - serial control?
hi - this is really a PD list question, but I thought it might be smart to
crosspost...sorry for any inconveinance...
I am currently, among other things (one step at a time), trying to figure
out how to control PD via the serial port. that is the question of the
hour. just want to use hyperterminal to send a word, like "hello", and have
pd do something based on that word, like print hello or something.
for background, the project (due tommorrow, handed to me last night) is:
a button box has 6 buttons: five record and one play. when a child who is
standing between a green screen and a camera (connected to s-video input of
a capture card) hits, say, record 1, a chip inside sends the text "record1"
to a serial output. on the other end, a computer running max/jitter or
pd/gem (probably the former) plays back a set video file (a different one if
it's "record2"), placing it in the fill of a chroma key, and records the
composite of the camera and the fill for 20 seconds, while the kid dances
around in front of the background. if the kid pushes the play button, the
last combined video is played back via the s-video output of the regular
video card.
i don't even have max yet cuz they haven't sent the serial number. so all I
want to do this minute is send the word "play" to PD via the serial port and
have it do something, anything, even just say hello. i'm very new to PD
though. I can get it to, for example, print hello in its terminal. but so
far documentation i read makes me think that the "serial" object only
outputs to the serial port as opposed to reading from it and parsing what
it's getting...
2 Aug
2 Aug
7:27 a.m.
Last Tuesday 02 August 2005 02:15, PhilJackson was like:
Hi Christoph,
You can get vkeybd from A/DeMuDi - you could possibly make life easier for
yourself by including these sources:
http://demudi.agnula.org/wiki/InstallApt
See also:
http://demudi.agnula.org/wiki/DocumentsFaq
Much of this applies to making music on any Debian system.
cheers,
tim hall
http://glastonburymusic.org.uk
let me summarize:
* JACK runs well on top of your card. Did you try if audio
output via any JACK application works? I'd try playing an mp3
or ogg file with xmms via its JACK output plugin. But
currently you try to get MIDI working so this isn't urgent
Now that is an interesting question! I usually download/play mp3s
using alsaplayer, which seems the default. Xine usually plays my
CDs. When I open up XMMS with nothing else running except
browser and email client and go to Preferences / Audio - IO plugins,
I see Alsa,DiskWriter, eSound, and OSS as options. No mention of
Jack. I am quite newbie enough to not know if there is a sequence
of operations - i.e this has to be already running and that has to be
running....would think things should instantiate themselves as needed.
* The Card appears in ALSA as a writable MIDI
port, correct?
I think it is 64:0 CS46XX.
* If so you should test if MIDI goes out of the
card. The
simplest way to do so is running something like vkeybd, an
onscreen MIDI keyboard. If you haven't it install, please try
installing it.
I looked, and my package manager doesn't have anything like
that. pmidi or rosegarden should be able to send MIDI to the
card....
* It is important to know that Linux has very
flexible MIDI
routing abilities thanks to the ALSA sequencer. OTOH, this
means that MIDI applications usually don't connect
automatically. Use qjackctl, Connections, MIDI to connect the
vkeybd to the MIDI out port of your card.
* Use the mouse or the computer keyboard to play some notes.
Does the Soundcanvas receive MIDI data?
Yes, it seems that it does. Maybe I have an unfortunate mix
of hardware / software?
1 Aug
1 Aug
11:10 a.m.
On Sun, 2005-07-31 at 22:37, PhilJackson wrote:
Jan Depner wrote:
It depends on what kind of card you have. In your /etc/modules.conf
file there should be a line similar to this:
alias snd-card-0 snd-ice1712
my card uses the ice1712 driver.
--
Jan "Evil Twin" Depner
The Fuzzy Dice
http://myweb.cableone.net/eviltwin69/fuzzy.html
"As we enjoy great advantages from the invention of others, we should be
glad of an opportunity to serve others by any invention of ours, and this
we should do freely and generously."
Benjamin Franklin, on declining patents offered by the governor of
Pennsylvania for his "Pennsylvania Fireplace", c. 1744
I don't know if this will help or if it even has anything to do with
it but you can write in your hardware in qjackctl. I only had default,
hw:0, and hw:1 but I wrote in ice1712 and that's what I'm using now.
An idea - how do I know what to write in and how would I do it?
2:39 a.m.
On Sun, 2005-07-31 at 22:05 -0500, PhilJackson wrote:
I did as Paul suggested in qjackctl and set the
frames/period to 2048.
Same error. At 512 frames per period and below qjackctl seems to run
fine. Above 512 I get the same errors that jack server cannot start.
Interesting. If this common device can't capture at 1024 frames maybe
JACK should default to 512. This still seems high enough to work OK in
non realtime mode.
Lee
31 Jul
31 Jul
7:17 p.m.
PhilJackson wrote:
root password lost check out
http://www.granneman.com/techinfo/linux/emergency/lostrootpassword.htm
or http://aplawrence.com/Linux/lostlinuxpassword.html
Ok, so if this is not an ALSA problem at all,
then how do I go about
configuring
JACK in this manner? (I suppose there are some command line commands
to run?)
thanks,
Phil J.
p.s. I did find alsaconf in the KDE menu -
Debian/Apps/System/Admin/Alsaconf
but it wants me to log in as root (not as sudo su) and I don't recall
the password I set...arrg!
> It means that Phil's h/w cannot support 1024 frames/period on the
> capture channel and/or cannot support full-duplex operation.
>
> Phil - try configuring JACK to use 2048 frames/period, and try using the
> -P and/or -C flag to specify playback-only or capture-only respectively.
>
> This has nothing to do with alsaconf.
>
> --p
>
7044
days inactive
7060
days old
linux-audio-user@lists.linuxaudio.org
63 comments
14 participants
participants (14)
-
Aaron Trumm -
Christoph Eckert -
Clemens Ladisch -
Dave Robillard -
Jan Depner -
Lee Revell -
Paul Davis -
PhilJackson -
pjfjacks
-
rheise＠it.uts.edu.au -
robin -
Shayne O'Connor -
studio-64 -
tim hall