4 Aug
2005
4 Aug
'05
2:56 p.m.
It seems like every single linux midi app has it's own code for
reading/writing midi files. What's up with that? Are there no quality
libraries?
4 Aug
4 Aug
3:07 p.m.
On Thu, 2005-08-04 at 16:56 +0000, Will Woodruff wrote:
It seems like every single linux midi app has it's
own code for
reading/writing midi files. What's up with that? Are there no quality
libraries?
It seems like every single Windows audio app has to support like 6
different audio backends plus Rewire/Rewire2. What's up with that, is
there no single standard for interapplication audio routing like JACK?
;-)
Lee
5 Aug
5 Aug
7:52 a.m.
Lee Revell <rlrevell(a)joe-job.com> writes:
On Thu, 2005-08-04 at 16:56 +0000, Will Woodruff
wrote:
Lee, you are being exceptionally helpful today...
Reminds me of a saying of a friend of mine: "Why be helpful if I am not?"
Reusability of code is a quite valid point, and I thought the OP's
question was quite interesting.
We shouldn't define ourselves in terms of what windows does. Frankly, I don't
care anymore, its now 8 years since I switched to Linux completely.
libmidifile would be cute, is any of the existing codebases flexible
enough so that it could be massaged into a nice lib?
--
CYa,
Mario
It seems like every single linux midi app has
it's own code for
reading/writing midi files. What's up with that? Are there no quality
libraries?
It seems like every single Windows audio app has to support like 6
different audio backends plus Rewire/Rewire2. What's up with that, is
there no single standard for interapplication audio routing like JACK?
;-) 
8:19 a.m.
On Fri, 05 Aug 2005 11:52:44 +0200
Mario Lang <mlang(a)delysid.org> wrote:
Reusability of code is a quite valid point, and I
thought the OP's
question was quite interesting.
We shouldn't define ourselves in terms of what windows does. Frankly, I don't
care anymore, its now 8 years since I switched to Linux completely.
libmidifile would be cute, is any of the existing codebases flexible
enough so that it could be massaged into a nice lib?
vote++ to everything you said. dunno about any existing midi code though
flexible enough to be put into a lib.. After taking a glance at
rosegarden and muse's source it seems there's always app specifics
intertwined.
Wasn't a midi file pretty much a simple dump of midi events anyways?
Flo
--
Palimm Palimm!
http://affenbande.org/~tapas/
6 Aug
6 Aug
7:15 a.m.
Florian Schmidt <mista.tapas(a)gmx.net> writes:
On Fri, 05 Aug 2005 11:52:44 +0200
Mario Lang <mlang(a)delysid.org> wrote:
Sure, *because* there wasn't a standard midifile library around in the first
place, they all hacked it into the program directly, therefore it is
intertwined :-).
Reusability of code is a quite valid point, and I
thought the OP's
question was quite interesting.
We shouldn't define ourselves in terms of what windows does. Frankly, I don't
care anymore, its now 8 years since I switched to Linux completely.
libmidifile would be cute, is any of the existing codebases flexible
enough so that it could be massaged into a nice lib?
vote++ to everything you said. dunno about any existing midi code though
flexible enough to be put into a lib.. After taking a glance at
rosegarden and muse's source it seems there's always app specifics
intertwined. Wasn't a midi file pretty much a simple dump of
midi events anyways?
That is mostly true for type 0 files, but type 1 (and especially 2) is
a bit more involved. And of course, there are the SMF meta events.
--
CYa,
Mario
9 Aug
9 Aug
10:14 a.m.
On Sat, 2005-08-06 at 11:16 +0200, Mario Lang wrote:
[ Florian: ]
I would love to participiate in a type 0 effort. Extending to type 1
should only take about 10 minutes (The basic idea being that you attach
several type 0 with a delimiter.)
Mario!
What is type 2 ?
--
mvh // Jens M Andreasen
Wasn't a midi file pretty much a simple dump
of midi events anyways?
That is mostly true for type 0 files, but type 1 (and especially 2) is
a bit more involved. And of course, there are the SMF meta events.
10:27 a.m.
On Tue, 2005-08-09 at 14:10 +0200, Jens M Andreasen wrote:
On Sat, 2005-08-06 at 11:16 +0200, Mario Lang wrote:
[ Florian: ]
I would love to participiate in a type 0 effort. Extending to type 1
should only take about 10 minutes (The basic idea being that you attach
several type 0 with a delimiter.)
Correction: Type 1 includes a tempo/conductor track. So a the effort is
more like a sunday afternoon :)
/j
Wasn't a midi file pretty much a simple dump
of midi events anyways?
That is mostly true for type 0 files, but type 1 (and especially 2) is
a bit more involved. And of course, there are the SMF meta events.
Mario!
What is type 2 ?
--
mvh // Jens M Andreasen
--
11:31 a.m.
Jens M Andreasen wrote:
What is type 2 ?
Type 2 files contain several related tracks, like type 1, but instead
of being played in parallel, these tracks are to be used in some
unspecified way.
For example, the background music in Monkey Island 2 uses one type 2
file for each room where the other tracks contain endings/transitions
that are spliced into the main track when the figure leaves a room at
a specific time; or, when going from the graveyard to the tomb, the
music is blended to another track that plays the same melody with
different instruments for a more "closed" feeling.
Regards,
Clemens
1:01 p.m.
On Tue, 2005-08-09 at 15:31 +0200, Clemens Ladisch wrote:
Jens M Andreasen wrote:
Focus on the graveyard: Is the transition described in type 2, or is it
programmed by the game designer?
/j
What is type 2 ?
Type 2 files contain several related tracks, like type 1, but instead
of being played in parallel, these tracks are to be used in some
unspecified way.
For example, the background music in Monkey Island 2 uses one type 2
file for each room where the other tracks contain endings/transitions
that are spliced into the main track when the figure leaves a room at
a specific time; or, when going from the graveyard to the tomb, the
music is blended to another track that plays the same melody with
different instruments for a more "closed" feeling.
Regards,
Clemens
--
1:54 p.m.
Jens M Andreasen wrote:
On Tue, 2005-08-09 at 15:31 +0200, Clemens Ladisch
wrote:
Type 2 files contain just a bunch of tracks; the SMF specification
doesn't include any means to describe how these tracks are related,
except for non-standard sequencer-specific meta events which you have
to define for yourself. This is why type 2 files cannot be used to
interchange MIDI data.
Regards,
Clemens
[...] when going from the graveyard to the tomb,
the
music is blended to another track that plays the same melody with
different instruments for a more "closed" feeling.
Focus on the graveyard: Is the transition described in type 2, or is it
programmed by the game designer? 
5 Aug
5 Aug
8:19 a.m.
It seems like every single Windows audio app has to
support like 6
different audio backends plus Rewire/Rewire2. What's up with that, is
there no single standard for interapplication audio routing like JACK?
;-)
Ok, not *every* query about Linux audio has to be answered by pointing
out Windows deficiencies! (Though it can be fun.)
Will, it's a good question, I just had a look through
http://linux-sound.org/one-page.html and nothing stands out... very
likely, someday soon one of the authors of the "every single linux
midi apps" will use their copious free time to re-engineer their code
into a reusable library.
4 Aug
4 Aug
3:21 p.m.
New subject: [linux-audio-dev] Re: Libs for reading/writing midis
On 8/4/05, Will Woodruff <thatwill(a)gmail.com> wrote:
It seems like every single linux midi app has it's
own code for
reading/writing midi files. What's up with that? Are there no quality
libraries?
Oops, sorry about that. My browser crashed and I didn't realize the
first message got through.
7099
days inactive
7104
days old
linux-audio-dev@lists.linuxaudio.org
11 comments
7 participants
participants (7)
-
Clemens Ladisch -
Florian Schmidt -
James McDermott -
Jens M Andreasen -
Lee Revell -
Mario Lang -
Will Woodruff