1 Sep
2007
1 Sep
'07
4:52 a.m.
thomas fisher wrote:
On Friday 31 August 2007 01:09:07 david wrote:
I don't know - and each week I play a Yahama PSR-740 keyboard with
Yamaha's XG. I've recorded some MIDIs using it, and they open just fine
in Rosegarden and play in fluidsynth. Or maybe you're talking about
something else?
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
Steve McConville wrote:
That could be separated fairly easily, I'd think.
How does the " XG " extension play into this? How proprietary is it? I am
curious - has there been any move to modernize the MIDI
connectivity standards to include USB or Ethernet?
There has been - there is a
midi over usb standard.
Midi is a poor starting point for modernisation not just beacause of
the pragmatic compromises mentioned above but also because it is
wholly unlayered (the spec covers everything from the physical up to
the presentational layer), and has it's expansion room squeezed into
the SysEx ghetto.
That's a big problem.
Midi over ethernet would be even less pleasant,
and
less logical, than doing RS-232 over ethernet.
Only reason I mentioned Ethernet is
that there are analog musical
instruments around already that can transmit their audio via Ethernet
(instead of analog audio cables).
OSC has fixed these problems and should have been
built into
everything since the mid-90s but so many people have invested time in
learning MIDI that they wouldn't countenance working with anything
else. It looks like RESTful web services may eventually replace both,
however.
I suspect that MIDI won't be budged. It is a standard in the music
world, and I doubt that many musicians care about it's limitations. They
may not even be aware of them. MIDI certainly keeps time in a lot finer
increments than I'm able to play - that's why sequencer programs have
quantization functions! 
1 Sep
1 Sep
1:08 p.m.
New subject: An atrocity committed with PD (MIDI Spec) + (XG)
On Friday 31 August 2007 23:52:33 david wrote:
thomas fisher wrote:
I do not know either, and was asking in the context of the MIDI discussion. I
have always assumed that XG was an extension to the standard MIDI
specification. And again I always assumed that an interpretative function
existed somewhere in software layers either within a driver or in a filter.
As with your Yamaha PSR-740 XG are all functions / prsets & ?? interpreted by
the Linux MIDI? I am only guessing how all of this works.
Tom
On Friday 31 August 2007 01:09:07 david wrote:
I don't know - and each week I play a Yahama PSR-740 keyboard with
Yamaha's XG. I've recorded some MIDIs using it, and they open just fine
in Rosegarden and play in fluidsynth. Or maybe you're talking about
something else? Steve McConville wrote:
How does the " XG " extension play into this? How proprietary is it? > I am curious - has there been any move to
modernize the MIDI
> connectivity standards to include USB or Ethernet?
There has been - there is a midi over usb standard.
Midi is a poor starting point for modernisation not just beacause of
the pragmatic compromises mentioned above but also because it is
wholly unlayered (the spec covers everything from the physical up to
the presentational layer),
That could be separated fairly easily, I'd think.
and has it's expansion room squeezed into
the SysEx ghetto.
That's a big problem.
Midi over ethernet would be even less pleasant,
and
less logical, than doing RS-232 over ethernet.
Only reason I mentioned Ethernet is that there are analog musical
instruments around already that can transmit their audio via Ethernet
(instead of analog audio cables).
OSC has fixed these problems and should have been
built into
everything since the mid-90s but so many people have invested time in
learning MIDI that they wouldn't countenance working with anything
else. It looks like RESTful web services may eventually replace both,
however.
I suspect that MIDI won't be budged. It is a standard in the music
world, and I doubt that many musicians care about it's limitations. They
may not even be aware of them. MIDI certainly keeps time in a lot finer
increments than I'm able to play - that's why sequencer programs have
quantization functions! 
1:14 p.m.
New subject: An atrocity committed with PD (MIDI Spec) + (XG)
On 9/1/07, thomas fisher <studio1(a)commspeed.net> wrote:
On Friday 31 August 2007 23:52:33 david wrote:
I don't know - and each week I play a Yahama PSR-740 keyboard with
Yamaha's XG. I've recorded some MIDIs using it, and they open just fine
in Rosegarden and play in fluidsynth. Or maybe you're talking about
something else?
I do not know either, and was asking in the context of the MIDI
discussion. I
have always assumed that XG was an extension to the standard MIDI
specification. And again I always assumed that an interpretative function
existed somewhere in software layers either within a driver or in a
filter.
As with your Yamaha PSR-740 XG are all functions / prsets & ?? interpreted
by
the Linux MIDI? I am only guessing how all of this works.
Tom
You could have a look for yourself, the spec seems to be freely available:
http://www.yamaha.co.uk/xg/reading/pdf/xg_spec.pdf
Chris
_______________________________________________
thomas fisher wrote:
> On Friday 31 August 2007 01:09:07 david wrote:
>> Steve McConville wrote:
>>>> I am curious - has there been any move to modernize the MIDI
>>>> connectivity standards to include USB or Ethernet?
>>>
>>> There has been - there is a midi over usb standard.
>>>
>>> Midi is a poor starting point for modernisation not just beacause of
>>> the pragmatic compromises mentioned above but also because it is
>>> wholly unlayered (the spec covers everything from the physical up to
>>> the presentational layer),
>>
>> That could be separated fairly easily, I'd think.
>>
>>> and has it's expansion room squeezed into
>>> the SysEx ghetto.
>>
>> That's a big problem.
>>
>>> Midi over ethernet would be even less pleasant, and
>>> less logical, than doing RS-232 over ethernet.
>>
>> Only reason I mentioned Ethernet is that there are analog musical
>> instruments around already that can transmit their audio via Ethernet
>> (instead of analog audio cables).
>>
>>> OSC has fixed these problems and should have been built into
>>> everything since the mid-90s but so many people have invested time
in
>>> learning MIDI that they wouldn't
countenance working with anything
>>> else. It looks like RESTful web services may eventually replace
both,
>>> however.
>>
>> I suspect that MIDI won't be budged. It is a standard in the music
>> world, and I doubt that many musicians care about it's limitations.
They
>> may not even be aware of them. MIDI
certainly keeps time in a lot
finer
increments than I'm able to play - that's why
sequencer programs have
quantization functions!
How does the " XG " extension play into this? How proprietary is it? Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
1:17 p.m.
New subject: An atrocity committed with PD (MIDI Spec) + (XG)
On 9/1/07, chris beagles <christhemonkey(a)gmail.com> wrote:
On 9/1/07, thomas fisher <studio1(a)commspeed.net> wrote:
Ok, my bad, should have followed the link on wikipedia before sharing it...
It doesn't seem to be available anymore.
Chris
_______________________________________________
On Friday 31 August 2007 23:52:33 david wrote:
fine
You could have a look for yourself, the spec seems to be freely
available:
http://www.yamaha.co.uk/xg/reading/pdf/xg_spec.pdf
Chris
thomas fisher wrote:
> On Friday 31 August 2007 01:09:07 david wrote:
>> Steve McConville wrote:
>>>> I am curious - has there been any move to modernize the MIDI
>>>> connectivity standards to include USB or Ethernet?
>>>
>>> There has been - there is a midi over usb standard.
>>>
>>> Midi is a poor starting point for modernisation not just beacause
of
>>> the pragmatic compromises mentioned
above but also because it is
>>> wholly unlayered (the spec covers everything from the physical up
to
>>> the presentational layer),
>>
>> That could be separated fairly easily, I'd think.
>>
>>> and has it's expansion room squeezed into
>>> the SysEx ghetto.
>>
>> That's a big problem.
>>
>>> Midi over ethernet would be even less pleasant, and
>>> less logical, than doing RS-232 over ethernet.
>>
>> Only reason I mentioned Ethernet is that there are analog musical
>> instruments around already that can transmit their audio via
Ethernet
>> (instead of analog audio cables).
>>
>>> OSC has fixed these problems and should have been built into
>>> everything since the mid-90s but so many people have invested time
in
>>> learning MIDI that they wouldn't
countenance working with anything
>>> else. It looks like RESTful web
services may eventually replace
both,
>>> however.
>>
>> I suspect that MIDI won't be budged. It is a standard in the music
>> world, and I doubt that many musicians care about it's limitations.
They
>> may not even be aware of them. MIDI
certainly keeps time in a lot
finer
>> increments than I'm able to play -
that's why sequencer programs
have
>
quantization functions!
How does the " XG " extension play into this? How proprietary is it?
I don't know - and each week I play a Yahama PSR-740 keyboard with
Yamaha's XG. I've recorded some MIDIs using it, and they open just in Rosegarden and play in fluidsynth. Or maybe
you're talking about
something else?
I do not know either, and was asking in the context of the MIDI
discussion. I
have always assumed that XG was an extension to the standard MIDI
specification. And again I always assumed that an interpretative
function
existed somewhere in software layers either within a driver or in a
filter.
As with your Yamaha PSR-740 XG are all functions / prsets & ??
interpreted by
the Linux MIDI? I am only guessing how all of this works.
Tom
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
2 Sep
2 Sep
3:42 a.m.
New subject: An atrocity committed with PD (MIDI Spec) + (XG)
On Saturday 01 September 2007 08:17:18 chris beagles wrote:
On 9/1/07, chris beagles
<christhemonkey(a)gmail.com> wrote:
http://www.borg.com/~jglatt/tech/midispec.htm This may not be the most
current specification as of 09/2007
http://www.ibiblio.org/emusic-l/info-docs-FAQs/MIDI-doc/index.html tutorial
http://swami.resonance.org/trac instrument fonts editor
http://freepats.opensrc.org/sf2/ Sound Fonts
Creative Labs
http://swami.resonance.org/trac/wiki/DLS Downloadable Sound Fonts
MIDI assoc
http://swami.resonance.org/trac/wiki/GigaSampler Tascam Gigastudio
http://sounds.resonance.org/patches.py Free Instrument database
Hope this helps
On 9/1/07, thomas fisher
<studio1(a)commspeed.net> wrote:
Ok, my bad, should have followed the link on wikipedia before sharing it...
It doesn't seem to be available anymore.
Chris
On Friday 31 August 2007 23:52:33 david wrote:
You could have a look for yourself, the spec seems to be freely
available:
http://www.yamaha.co.uk/xg/reading/pdf/xg_spec.pdf
Chris thomas fisher wrote:
> On Friday 31 August 2007 01:09:07 david wrote:
>> Steve McConville wrote:
>>>> I am curious - has there been any move to modernize the MIDI
>>>> connectivity standards to include USB or Ethernet?
>>>
>>> There has been - there is a midi over usb standard.
>>>
>>> Midi is a poor starting point for modernisation not just beacause
of
>>> the pragmatic compromises mentioned
above but also because it is
>>> wholly unlayered (the spec covers everything from the physical up
to
>>> the presentational layer),
>>
>> That could be separated fairly easily, I'd think.
>>
>>> and has it's expansion room squeezed into
>>> the SysEx ghetto.
>>
>> That's a big problem.
>>
>>> Midi over ethernet would be even less pleasant, and
>>> less logical, than doing RS-232 over ethernet.
>>
>> Only reason I mentioned Ethernet is that there are analog musical
>> instruments around already that can transmit their audio via
Ethernet
>> (instead of analog audio cables).
>>
>>> OSC has fixed these problems and should have been built into
>>> everything since the mid-90s but so many people have invested
>>> time
in
>>> learning MIDI that they wouldn't
countenance working with
>>> anything
>>>
>>> else. It looks like RESTful web services may eventually replace
both,
>>> however.
>>
>> I suspect that MIDI won't be budged. It is a standard in the music
>> world, and I doubt that many musicians care about it's
>> limitations.
They
>> may not even be aware of them. MIDI
certainly keeps time in a lot
finer
>> increments than I'm able to play -
that's why sequencer programs
have
>> quantization functions!
>
> How does the " XG " extension play into this? How proprietary is
> it?
I don't know - and each week I play a Yahama PSR-740 keyboard with
Yamaha's XG. I've recorded some MIDIs using it, and they open just
fine
in Rosegarden and play in fluidsynth. Or maybe
you're talking about
something else?
I do not know either, and was asking in the context of the MIDI
discussion. I
have always assumed that XG was an extension to the standard MIDI
specification. And again I always assumed that an interpretative
function
existed somewhere in software layers either within a driver or in a
filter.
As with your Yamaha PSR-740 XG are all functions / prsets & ??
interpreted by
the Linux MIDI? I am only guessing how all of this works.
Tom
1 Sep
1 Sep
11:35 p.m.
New subject: An atrocity committed with PD (MIDI Spec) + (XG)
thomas fisher wrote:
On Friday 31 August 2007 23:52:33 david wrote:
I've no clue. I have a Yamaha PSR-740 configuration file I use with
Rosegarden that lists all the extended XG voices. I don't know if it has
any support for presets or the pile of other things the keyboard has. I
haven't tried driving the PSR-740 from Rosegarden, since I don't yet
have MIDI set up.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
thomas fisher wrote:
I do not know either, and was asking in the context of the MIDI discussion. I
have always assumed that XG was an extension to the standard MIDI
specification. And again I always assumed that an interpretative function
existed somewhere in software layers either within a driver or in a filter.
As with your Yamaha PSR-740 XG are all functions / prsets & ?? interpreted by
the Linux MIDI? I am only guessing how all of this works. On Friday 31 August 2007 01:09:07 david wrote:
I don't know - and each week I play a Yahama PSR-740
keyboard with
Yamaha's XG. I've recorded some MIDIs using it, and they open just fine
in Rosegarden and play in fluidsynth. Or maybe you're talking about
something else? Steve McConville wrote:
>> I am curious - has there been any move to modernize the MIDI
>> connectivity standards to include USB or Ethernet?
> There has been - there is a midi over usb standard.
>
> Midi is a poor starting point for modernisation not just beacause of
> the pragmatic compromises mentioned above but also because it is
> wholly unlayered (the spec covers everything from the physical up to
> the presentational layer),
That could be separated fairly easily, I'd think.
> and has it's expansion room squeezed into
> the SysEx ghetto.
That's a big problem.
> Midi over ethernet would be even less pleasant, and
> less logical, than doing RS-232 over ethernet.
Only reason I mentioned Ethernet is that there are analog musical
instruments around already that can transmit their audio via Ethernet
(instead of analog audio cables).
> OSC has fixed these problems and should have been built into
> everything since the mid-90s but so many people have invested time in
> learning MIDI that they wouldn't countenance working with anything
> else. It looks like RESTful web services may eventually replace both,
> however.
I suspect that MIDI won't be budged. It is a standard in the music
world, and I doubt that many musicians care about it's limitations. They
may not even be aware of them. MIDI certainly keeps time in a lot finer
increments than I'm able to play - that's why sequencer programs have
quantization functions!
How does the " XG " extension play into this?
How proprietary is it?
6345
days inactive
6346
days old
linux-audio-user@lists.linuxaudio.org
5 comments
3 participants
participants (3)
-
chris beagles -
david -
thomas fisher