23 May
2006
23 May
'06
6:09 p.m.
So I'm looking into using seq24 as my midi sequencer (Rosegarden is
slow as all hell, as well as bloated for my tastes, and MusE seems to
have problems on my system).
I'm fairly sure that I made some use of it when I first installed it,
however, I've tried using it with qsynth over the last few days and I
just can't seem to be able to connect the two at all. I'm rather
concerned that seq24 doesn't seem to have any ports/clients listed in
qjackctl's midi section.
I can connect seq24 to busses and channels from inside seq24, but that
doesn't seem to have any effect. The problem doesn't seem to lie with
qsynth as I've been able to connect a software keyboard to it no
problem.
Has anyone else experienced this at all and can offer some advice on
the subject?
Cheers!
--
Joe Jones
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT/MU d-- s+:-- a-- C++ UL+ L++ E---- W++ w M t(++) 5++ tv D++ e+ h--
------END GEEK CODE BLOCK------
23 May
23 May
6:21 p.m.
I'm fairly sure that I made some use of it when I
first installed it,
however, I've tried using it with qsynth over the last few days and I
just can't seem to be able to connect the two at all. I'm rather
concerned that seq24 doesn't seem to have any ports/clients listed in
qjackctl's midi section.
Depending on what version you're using of seq24; older versions tried to
connect without using aconnect/qjackctl (i.e. it finds qsynth and others
automatically), but IIRC recent versions can choose between either
behaviour. I know I have it set up to show up in qjackctl at the moment.
Look in the preferences or the readme (a file named SEQ24).
7:46 p.m.
sunnan(a)handgranat.org wrote:
Wow I was just contemplating how much i would have to learn if i wanted
to write a patch that would add alsa-midi ports behavior to seq24.
looks like i should keep up with the change logs. thanks for the tip.
Patching the midi signals to their apropriate posts is the ideal
behavior for me as the synths never seem to have the same port number
twice, and i was often in the position of saying to a prospective
listener "just wait a sec... it's really cool, promise..." while
fiddling with those pop up port lists to reconfigure the outputs every
time, trying to remember what zyn channel number i put that sound on.
Now it's just drag one line across the screen, and wham. sound.
now if seq24 could just lash, it and zyn would be the ultimate time
sucking beat looping dohicky.
is any one working on adding lash support to seq24?
brian
I'm fairly
sure that I made some use of it when I first installed it,
however, I've tried using it with qsynth over the last few days and I
just can't seem to be able to connect the two at all. I'm rather
concerned that seq24 doesn't seem to have any ports/clients listed in
qjackctl's midi section.
Depending on what version you're using of seq24; older versions tried to
connect without using aconnect/qjackctl (i.e. it finds qsynth and others
automatically), but IIRC recent versions can choose between either
behaviour. I know I have it set up to show up in qjackctl at the moment.
Look in the preferences or the readme (a file named SEQ24).
7:52 p.m.
On Tue, 23 May 2006 16:46:08 -0500
Brian Dunn <job17and9(a)sbcglobal.net> wrote:
Wow I was just contemplating how much i would have to
learn if i
wanted to write a patch that would add alsa-midi ports behavior to
seq24. looks like i should keep up with the change logs. thanks for
the tip. Patching the midi signals to their apropriate posts is the
ideal behavior for me as the synths never seem to have the same port
number twice, and i was often in the position of saying to a
prospective listener "just wait a sec... it's really cool,
promise..." while fiddling with those pop up port lists to
reconfigure the outputs every time, trying to remember what zyn
channel number i put that sound on. Now it's just drag one line
across the screen, and wham. sound. now if seq24 could just lash, it
and zyn would be the ultimate time sucking beat looping dohicky.
is any one working on adding lash support to seq24?
brian
If i see that right, seq24 0.8.6 has --enable-lash switch.
Cheers,
Tom
10:36 p.m.
On Tue, 2006-05-23 at 23:52 +0200, Thomas Kuther wrote:
On Tue, 23 May 2006 16:46:08 -0500
Brian Dunn <job17and9(a)sbcglobal.net> wrote:
The new ports thing is in part to allow Seq24 to restore properly as a
LASH client.
Let me know how it works.
-DR-
Wow I was just contemplating how much i would
have to learn if i
wanted to write a patch that would add alsa-midi ports behavior to
seq24. looks like i should keep up with the change logs. thanks for
the tip. Patching the midi signals to their apropriate posts is the
ideal behavior for me as the synths never seem to have the same port
number twice, and i was often in the position of saying to a
prospective listener "just wait a sec... it's really cool,
promise..." while fiddling with those pop up port lists to
reconfigure the outputs every time, trying to remember what zyn
channel number i put that sound on. Now it's just drag one line
across the screen, and wham. sound. now if seq24 could just lash, it
and zyn would be the ultimate time sucking beat looping dohicky.
is any one working on adding lash support to seq24?
brian
If i see that right, seq24 0.8.6 has --enable-lash switch.
25 May
25 May
12:48 a.m.
The new ports thing is in part to allow Seq24 to
restore properly as a
LASH client.
Let me know how it works.
-DR-
I *love* it.
My studio just got a lot more flexable. now i can close my music
projects, do the work, and be right back where i was with the click of (
two or three ) buttons. great work.
brian
24 May
24 May
6:05 a.m.
On 5/23/06, sunnan(a)handgranat.org <sunnan(a)handgranat.org> wrote:
Ahh, I see. I tried doing an upgrade last night, as I hadn't realised
that my installed version was actually older than god, which involved
a partial upgrade to DeMuDi unstable. Unfortunately I seem to have
broken everything audio related, so I'm gonna have another bash at it
tonight, probably just do a base install and then actually follow the
instructions for upgrading.
--
Joe Jones
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT/MU d-- s+:-- a-- C++ UL+ L++ E---- W++ w M t(++) 5++ tv D++ e+ h--
------END GEEK CODE BLOCK------
I'm fairly
sure that I made some use of it when I first installed it,
however, I've tried using it with qsynth over the last few days and I
just can't seem to be able to connect the two at all. I'm rather
concerned that seq24 doesn't seem to have any ports/clients listed in
qjackctl's midi section.
Depending on what version you're using of seq24; older versions tried to
connect without using aconnect/qjackctl (i.e. it finds qsynth and others
automatically), but IIRC recent versions can choose between either
behaviour. I know I have it set up to show up in qjackctl at the moment.
Look in the preferences or the readme (a file named SEQ24).
30 May
30 May
4:49 a.m.
On Wednesday 24 May 2006 09:04, Joseph Jones was like:
Ahh, I see. I tried doing an upgrade last night, as I
hadn't realised
that my installed version was actually older than god, which involved
a partial upgrade to DeMuDi unstable. Unfortunately I seem to have
broken everything audio related, so I'm gonna have another bash at it
tonight, probably just do a base install and then actually follow the
instructions for upgrading.
Good idea, there is no DeMuDi unstable. Upgrading from stable to testing is an
all-or-nothing affair. You're lucky to have a system that still boots.
--
cheers,
tim hall
http://glastonburymusic.org.uk/tim
We are the people We've been waiting for.
23 May
23 May
6:53 p.m.
If you want it to revert to the old behaviour (see client names inside
pattern windows -- much less of a hassle IMO), change
[manual-alsa-ports] to say 0 in ~/.seq24rc, or if it was 1 -- I'm not
sure. There's a bug with the rc file versus the cli flag.
Joseph Jones wrote:
So I'm looking into using seq24 as my midi
sequencer (Rosegarden is
slow as all hell, as well as bloated for my tastes, and MusE seems to
have problems on my system).
I'm fairly sure that I made some use of it when I first installed it,
however, I've tried using it with qsynth over the last few days and I
just can't seem to be able to connect the two at all. I'm rather
concerned that seq24 doesn't seem to have any ports/clients listed in
qjackctl's midi section.
I can connect seq24 to busses and channels from inside seq24, but that
doesn't seem to have any effect. The problem doesn't seem to lie with
qsynth as I've been able to connect a software keyboard to it no
problem.
Has anyone else experienced this at all and can offer some advice on
the subject?
Cheers!
6548
days inactive
6555
days old
linux-audio-user@lists.linuxaudio.org
10 comments
8 participants
participants (8)
-
Brian Dunn -
Dave Phillips -
Dave Robillard -
Joseph Jones -
Petter Sundlöf -
sunnan＠handgranat.org -
Thomas Kuther -
tim hall