19 Dec
2009
19 Dec
'09
1:32 p.m.
Hi all,
I have a Korg Oasys synth that has some digital based drums, and a
Jomox xbase 999 analog drum machine, which also has an analog filter.
I'd like to use some of the preset drum patterns on the Oasys as a
starting point, and play them on the Jomox via midi and run the output
thru the analog filter.
Problem is: The MIDI notes on the jomox aren't the same as the kit I
want to use in the Oasys. I have a midisport 2x2 that works fine in
linux (opensuse 11.2) . I have jackd seemingly running properly. I'd
like to capture the MIDI coming out of the Oasys, capture it on linux
into perhaps a midi file, and then edit the notes so that they match
the kit on the Jomox. If that plan makes sense, once I get to that
point I could use any midi sequencer to get the pattern to the jomox.
Can anyone give me some advice on this?
Googling brought me to Qtractor and CSound for midi capture, but they
don't seem to be the right tool for midi capture over usb. If they
are, any pointers would be helpful.
19 Dec
19 Dec
1:40 p.m.
On Sat, 19 Dec 2009, robert lazarski wrote:
linux (opensuse 11.2) . I have jackd seemingly running
properly. I'd
like to capture the MIDI coming out of the Oasys, capture it on linux
into perhaps a midi file, and then edit the notes so that they match
the kit on the Jomox. If that plan makes sense, once I get to that
point I could use any midi sequencer to get the pattern to the jomox.
Can anyone give me some advice on this?
Simplest solution I can think of:
1. Use arecordmidi (ALSA) to record the output of the MIDI
port to a SMF (simple midi file).
2. Use your favorite SMF editor to remap the notes.
Another option is if someone has something like a MIDI
plug-in that you could configure to translate MIDI events.
I don't know of any off the top of my head... but maybe
someone else does.[1]
HTH,
Gabriel
[1] If it were /me/, I would write one because it sounds
like a simple and fun side project. But, it's not
me and would take longer than using arecordmidi.
2:39 p.m.
On Sat, Dec 19, 2009 at 2:40 PM, Gabriel M. Beddingfield
<gabriel(a)teuton.org> wrote:
On Sat, 19 Dec 2009, robert lazarski wrote:
I'm trying arecordmidi for now, but nothing is happening. With the
Oasys connected to the Jomox, the wrong notes are being played as
explained but it produces sound. See my shell output below with the
Oasys connected to the midisport:
/root> jackd -d alsa &
jackd 0.116.2
Copyright 2001-2005 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
JACK compiled with System V SHM support.
loading driver ..
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 (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
[3] 24613
[dhcppc0(root)]
/root> ALSA: final selected sample format for playback: 32bit integer
little-endian
ALSA: use 2 periods for playback
[dhcppc0(root)]
/root> arecordmidi -l
Port Client name Port name
14:0 Midi Through Midi Through Port-0
16:0 M Audio Audiophile 24/96 M Audio Audiophile 24/96 MIDI
24:0 MidiSport 2x2 MidiSport 2x2 MIDI 1
24:1 MidiSport 2x2 MidiSport 2x2 MIDI 2
[dhcppc0(root)]
/root> arecordmidi --port 24:0 oasys.mid
Doing "ls -l oasys.mid" from another window shows oasys.mid as zero
bytes. "arecordmidi --port 24:1 oasys.mid" doesn't work either, though
I believe 24:0 is correct.
I tried opening Qsynth to see if it could receive sound, but I get
this error even though, as shown above, jack is connected:
15:29:52.606 Qsynth1: Failed to create the audio driver (jack). Cannot
continue without it.
fluidsynth: error: Jack server not running?
I tried psycosynth but its not obvious to me how it accepts midi in.
Please help,
- R
linux (opensuse 11.2) . I have jackd seemingly
running properly. I'd
like to capture the MIDI coming out of the Oasys, capture it on linux
into perhaps a midi file, and then edit the notes so that they match
the kit on the Jomox. If that plan makes sense, once I get to that
point I could use any midi sequencer to get the pattern to the jomox.
Can anyone give me some advice on this?
Simplest solution I can think of:
1. Use arecordmidi (ALSA) to record the output of the MIDI
port to a SMF (simple midi file).
2:57 p.m.
On Sat, 19 Dec 2009, robert lazarski wrote:
/root> jackd -d alsa &
For now, don't use JACK unless you have to (e.g. to use
QSynth or something).
Also, don't do this stuff as root.
/root> arecordmidi -l
Port Client name Port name
14:0 Midi Through Midi Through Port-0
16:0 M Audio Audiophile 24/96 M Audio Audiophile 24/96 MIDI
24:0 MidiSport 2x2 MidiSport 2x2 MIDI 1
24:1 MidiSport 2x2 MidiSport 2x2 MIDI 2
[dhcppc0(root)]
Connect the Oasys to the IN on one of the midisport ports
and start your sequence. Meanwhile, do:
$ aseqdump --port=24:0
(or 24:1) and see if anything registers. If you see
anything, then the MIDI port is working and the problem is
something else. If you're not getting /anything/ -- then
the problem is between the keyboard and ALSA. Otherwise,
it's probably a problem with using arecordmidi.
/root> arecordmidi --port 24:0 oasys.mid
I wonder if the tempo settings (man arecordmidi) have
anything to do with this?
-gabriel
3:16 p.m.
On Sat, Dec 19, 2009 at 3:57 PM, Gabriel M. Beddingfield
<gabriel(a)teuton.org> wrote:
The Oasys sequence is playing at 78 bpm, but this didn't help:
arecordmidi --port 24:0 --bpm=78 oasys.mid &
Any other ideas?
Thanks!
- R
On Sat, 19 Dec 2009, robert lazarski wrote:
Connect the Oasys to the IN on one of the midisport ports and start your
sequence. Meanwhile, do:
$ aseqdump --port=24:0
(or 24:1) and see if anything registers. If you see anything, then the MIDI
port is working and the problem is something else. If you're not getting
/anything/ -- then the problem is between the keyboard and ALSA. Otherwise,
it's probably a problem with using arecordmidi.
/home/iksrazal> aseqdump --port=24:0
Waiting for data. Press Ctrl+C to end.
Source Event Ch Data
24:0 Note off 1, note 54, velocity 64
24:0 Clock
24:0 Clock
24:0 Control change 1, controller 10, value 13
...
Good, the Oasys to Linux seems to be working...
/root> arecordmidi --port 24:0 oasys.mid
I wonder if the tempo settings (man arecordmidi) have anything to do with
this?
-gabriel
4:51 p.m.
On Sat, 19 Dec 2009, robert lazarski wrote:
The Oasys sequence is playing at 78 bpm, but this
didn't help:
arecordmidi --port 24:0 --bpm=78 oasys.mid &
Any other ideas?
Yes....
1. It *was* simple to do.
2. It *was* phun.
Download this, and make sure you have the libjack-dev and
g++ installed:
http://www.teuton.org/~gabriel/code/midixlate-0.1.0.tar
http://www.teuton.org/~gabriel/code/midixlate-0.1.0.tar.bz2.sha1
To set up your mapping, go to line 232 of main.cpp and set
up your mapping. Here's what it looks like:
void MidiTranslate::init_note_map()
{
/* Here, add your midi mappings. If you don't
* map a note here, then the note will not be translated
* but pass through unchanged.
*
* Syntax:
*
* _note_map[orig] = xlate;
*
* Where 'orig' is the value of the "Original" note, and
* 'xlate' is the value of the translated note.
*/
_note_map[36] = 40;
_note_map[37] = 36;
_note_map[38] = 41;
_note_map[39] = 37;
}
Add and change lines as you see fit. These are all decimal
note numbers. When you're done, save the file and issue the
'make' command.
To run it, make sure you start jackd with the -Xseq option
to create the bridge between ALSA MIDI and JACK MIDI. Then,
run this program. Use something lack qjackctl to insert it
between your input and output ports on the 2x2.
Hope it helps!!
-gabriel
5:11 p.m.
Gabriel M. Beddingfield wrote:
Add and change lines as you see fit. These are all
decimal
note numbers. When you're done, save the file and issue the
'make' command.
To run it, make sure you start jackd with the -Xseq option
to create the bridge between ALSA MIDI and JACK MIDI. Then,
run this program. Use something lack qjackctl to insert it
between your input and output ports on the 2x2.
Hope it helps!!
Hmmm, couldn't the same thing have been done using midish????
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
6:57 p.m.
On Sat, Dec 19, 2009 at 10:23 PM, Gabriel M. Beddingfield
<gabriel(a)teuton.org> wrote:
On Sat, 19 Dec 2009, david wrote:
Some more options: qmidiroute (GUI), puredata
(semiGUI) and mididings (noGUI) can do
realtime remapping of midi events.
The only one I have experience with is
puredata, never used the others.
An example patch is attached.
I can't tell what is more appropriate in Roberts
case - setting up one of these realtime
translations or editing recorded SMF files.
Since the drum patterns are most likely
loops it would make sense to record them
in a loop based sequencer (like seq24).
For that, syncing the hardware with Jack
transport would be desirable.
Some things I unfortunately don't know:
Does the realtime remapping introduce timing
issues apart from a constant offset fore each note?
How big is the offset?
Does this depend on the app used?
greetings,
d
Hmmm, couldn't the same thing have been done
using midish????
Probably. I've tried a couple times to learn midish... and
had the sudden urge to do the dishes. :-)
-gabriel
20 Dec
20 Dec
1:08 a.m.
On Sat, 19 Dec 2009, David Adler wrote:
Some things I unfortunately don't know:
Does the realtime remapping introduce timing
issues apart from a constant offset fore each note?
How big is the offset?
Does this depend on the app used?
For a typical jack app (like midixlate), you only have
latencies for the hardware ports. (Usually estimated by
SAMPLES_PER_PERIOD * PERIODS_PER_BUFFER / SAMPLE_RATE,
e.g. 1024*2/48000 = 42.7 ms.) I
think you get 2x that figure if you're doing both input and
output -- but it might be 1x.
There's no additional latency for the software
processing.[1] This is the main advertisement for the JACK
API -- it adds *no* additional latency.[2]
Peace,
Gabriel
[1] That is, unless you have a complicated JACK
connection graph, or a processor that
intentionally creates delays.
[2] See http://jackaudio.org/faq "Doesn't use [sic] JACK
add latency?"
11:11 a.m.
On Sat, Dec 19, 2009 at 11:11:45AM -1000, david wrote:
Gabriel M. Beddingfield wrote:
yep, for instance to exchange notes 60 and 61:
dnew 0 nil wo # register 0 as output device
dnew 1 "MyClient:MyPort" ro # register 1 as input devices
fnew myfilt # create a filter
fmap {any 1} {any 0} # map anything on 1 -> 0
fmap {note 1 60} {note 0 61} # map note 60 -> note 61
fmap {note 1 61} {note 0 60} # map note 61 -> note 60
i # start processing
at this stage, midish processes notes from MyClient:MyPort
and sends the result on midish:midish/0, example:
$ aseqdump -l |grep midish
130:0 midish midish/0
applications connecting to "midish:midish/0" will see what you play
on MyClient:MyPort, but with notes 60 and 61 exchanged.
-- Alexandre
Add and change lines as you see fit. These are
all decimal
note numbers. When you're done, save the file and issue the
'make' command.
To run it, make sure you start jackd with the -Xseq option
to create the bridge between ALSA MIDI and JACK MIDI. Then,
run this program. Use something lack qjackctl to insert it
between your input and output ports on the 2x2.
Hope it helps!!
Hmmm, couldn't the same thing have been done using midish????
19 Dec
19 Dec
7:35 p.m.
On Sat, Dec 19, 2009 at 5:51 PM, Gabriel M. Beddingfield
<gabriel(a)teuton.org> wrote:
On Sat, 19 Dec 2009, robert lazarski wrote:
Kool!
Any other ideas?
Yes....
1. It *was* simple to do.
2. It *was* phun.
Download this, and make sure you have the libjack-dev and g++ installed:
http://www.teuton.org/~gabriel/code/midixlate-0.1.0.tar
For those following along, that link should have been:
http://www.teuton.org/~gabriel/code/midixlate-0.1.0.tar.bz2
I got this error compiling:
/usr/local/midixlate-0.1.0> make
g++ -ggdb -fno-inline -fno-default-inline -c -o main.o main.cpp
main.cpp: In member function int MidiTranslate::process(jack_nframes_t):
main.cpp:279: error: memcpy was not declared in this scope
Here's my g++ version:
/usr/local/midixlate-0.1.0> g++ --version
g++ (SUSE Linux) 4.4.1 [gcc-4_4-branch revision 150839]
Copyright (C) 2009 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Googling shows lots of reports of that error. This include fixed it:
#include <cstring>
Add and change lines as you see fit. These are all decimal note numbers.
When you're done, save the file and issue the 'make' command.
To run it, make sure you start jackd with the -Xseq option to create the
bridge between ALSA MIDI and JACK MIDI. Then, run this program. Use
something lack qjackctl to insert it between your input and output ports on
the 2x2.
I did my mappings and ran it. Looking at the code, I'm not exactly
sure what the intention of the output of a successful translation is -
stdout, midi file etc? I don't see anything happening, though
"aseqdump --port=24:0" shows data comming in. Here's my qjackctl
config:
http://braziloutsource.com/random/qjackctl_midixlate.png
Hope it helps!!
-gabriel
Looks very promising and could likely be exactly what I need, once I
figure out how to get its output.
Thanks!
- R
7:52 p.m.
On Sat, 19 Dec 2009, robert lazarski wrote:
Looks like it's "wired up" right. Did you plug the output
port from the 2x2 into your drum machine?
The output is a MIDI output port (not a SMF file or
anything). So, it would be just as if you (somehow)
remapped the notes on your Oasys and sent it to your drum
machine over a MIDI cable.
You can also use aseqdump to view the output of midixlate.
If you start aseqdump while jack is up... you'll see it on
the qjackctl connections dialog so that you can wire it up
and see what midixlate is outputting.
HTH,
Gabriel
For those following along, that link should have
been:
http://www.teuton.org/~gabriel/code/midixlate-0.1.0.tar.bz2
Doh!
main.cpp: In member function int
MidiTranslate::process(jack_nframes_t):
main.cpp:279: error: memcpy was not declared in this scope
2x Doh!
Googling shows lots of reports of that error. This
include fixed it:
#include <cstring>
Correct! (Long story....)
bridge between
ALSA MIDI and JACK MIDI. Then, run this program. Use
something lack qjackctl to insert it between your input and output ports on
the 2x2.
I did my mappings and ran it. Looking at the code, I'm not exactly
sure what the intention of the output of a successful translation is -
stdout, midi file etc? I don't see anything happening, though
"aseqdump --port=24:0" shows data comming in. Here's my qjackctl
config:
http://braziloutsource.com/random/qjackctl_midixlate.png
8:24 p.m.
On Sat, Dec 19, 2009 at 8:52 PM, Gabriel M. Beddingfield
<gabriel(a)teuton.org> wrote:
On Sat, 19 Dec 2009, robert lazarski wrote:
Ah, now I understand - it works great! The jomox analog drums sounds
fat! All my problems are solved!
http://www.google.com/search?q=snoopy+dance
I did my mappings and ran it. Looking at the
code, I'm not exactly
sure what the intention of the output of a successful translation is
The output is a MIDI output port (not a SMF file or anything). So, it would
be just as if you (somehow) remapped the notes on your Oasys and sent it to
your drum machine over a MIDI cable.
You can also use aseqdump to view the output of
midixlate. If you start
aseqdump while jack is up... you'll see it on the qjackctl connections
dialog so that you can wire it up and see what midixlate is outputting.
I see that, thanks!
HTH,
Gabriel
20 Dec
20 Dec
12:46 a.m.
On Sat, 19 Dec 2009, robert lazarski wrote:
LOL! Glad I could help.
-gabriel
5496
days inactive
5497
days old
linux-audio-user@lists.linuxaudio.org
14 comments
5 participants
participants (5)
-
Alexandre Ratchov -
david -
David Adler -
Gabriel M. Beddingfield -
robert lazarski