26 Jan
2003
26 Jan
'03
5:33 p.m.
I just noticed the announcement from RME about their Hammerfall DSP MADI
PCI card. From the announcement:
"MADI, the professionals' multichannel audio interface, offers 64
channels of 24 bit audio at a sample rate of up to 48 kHz and 32
channels at up to 96 kHz. Transmission is done via a single line, either
coaxial with BNC plugs or with fibre cable. In both cases more than 100
m cable length can be achieved. Hammerfall DSP is fully compatible to
all devices with MADI interface."
This will make seriously high end gear available for use with standard
PC's. As ardour nears readiness, I have been contemplating a total
upgrade of my recording gear but I don't like the idea of Toslink in
general (short cable length), or adat optical in particular (high
jitter), but I do like the idea of optical coupling of audio gear to
computer gear (cleaner electricity for the audio gear). I'm glad I
waited. Availability is predicted to be within the next 6 months. Now
if manufacturers of reasonably priced a/d converters can offer something
with a MADI interface within the next 6 months...
Tom
28 Jan
28 Jan
8:19 a.m.
On Sun, Jan 26, 2003 at 01:27:28 -0800, Tom wrote:
I just noticed the announcement from RME about their
Hammerfall DSP MADI
PCI card. From the announcement:
"MADI, the professionals' multichannel audio interface, offers 64
channels of 24 bit audio at a sample rate of up to 48 kHz and 32
channels at up to 96 kHz. Transmission is done via a single line, either
coaxial with BNC plugs or with fibre cable. In both cases more than 100
m cable length can be achieved. Hammerfall DSP is fully compatible to
all devices with MADI interface."
Argh, what's the great thing about standards again. I still prefer mLAN, as
it uses generic, consumer i/o cards, and firewire is fitted to almost all
laptops without needing expensive audio only hardware.
- Steve
9:37 a.m.
On Sun, Jan 26, 2003 at 01:27:28 -0800, Tom wrote:
i had an interesting conversation with the tech lead of the mLAN
project at yamaha and with a professor in south africa who has been
significant in spurring yamaha's coming linux efforts. i was
complaining about what they've done with mLAN in terms of licensing
etc. and how i feel this has held back the adoption of mLAN.
the situation turns out to be pretty interesting. 90% of mLAN is now
part of the IEEE music+audio firewire standard (the number escapes
me). but yamaha couldn't get IEEE (they say) to adopt the connection
management part of things. as a result, they've had to continue on
with their own "proprietary" connection management layer, which
prevents mLAN from being useful with generic devices that speak the
IEEE protocol. in fact, those generic devices are pretty useless too,
since they have no way to discover each other and link up.
its not clear from the conversation and email exchanges whether the
IEEE's problem was with the technical merits of yamaha's connection
management, or some political issues. in addition, yamaha are now
working on round 2 of the connection management layer to allow better
forward compatibility as other parts of the protocol change/evolve.
it all still sounds pretty dubious to me, and i still am not clear on
whether yamaha will let someone write an open source mLAN driver, but
i'm working on it.
hopefully, this should echo the fact that i'm with steve: MADI is an
audio-only system, its expensive, and i don't think it has any
particular technical benefits over mLAN. its sole advantage at this
point is that anyone (as i understand it) can implement it without the
licensing and other uncertainties that surround mLAN at this time.
--p
I just noticed the announcement from RME about
their Hammerfall DSP MADI
PCI card. From the announcement:
"MADI, the professionals' multichannel audio interface, offers 64
channels of 24 bit audio at a sample rate of up to 48 kHz and 32
channels at up to 96 kHz. Transmission is done via a single line, either
coaxial with BNC plugs or with fibre cable. In both cases more than 100
m cable length can be achieved. Hammerfall DSP is fully compatible to
all devices with MADI interface."
Argh, what's the great thing about standards again. I still prefer mLAN, as
it uses generic, consumer i/o cards, and firewire is fitted to almost all
laptops without needing expensive audio only hardware.
10:40 a.m.
On Tue, Jan 28, 2003 at 08:36:23 -0500, Paul Davis wrote:
Your mention of "yamaha's coming linux efforts" interests me strangly ;)
Care to share anything?
Granted the connection mangement part of mLAN is dubious, I've not been
able to read the specs (for obvious reasons). When I spoke before I was
thinking more of A+M over IEEE-1394, which the linux kernel allready
supports to some extent, not mLAN as a whole.
Hopefully Yamaha will address the licencing issues, otherwise it may be
neccesary for software providers to go our own way with connection
management, which would be a shame.
- Steve
Argh,
what's the great thing about standards again. I still prefer mLAN, as
it uses generic, consumer i/o cards, and firewire is fitted to almost all
laptops without needing expensive audio only hardware.
i had an interesting conversation with the tech lead of the mLAN
project at yamaha and with a professor in south africa who has been
significant in spurring yamaha's coming linux efforts. i was
complaining about what they've done with mLAN in terms of licensing
etc. and how i feel this has held back the adoption of mLAN.
10:47 a.m.
Your mention of "yamaha's coming linux
efforts" interests me strangly ;)
Care to share anything?
they announced last month that next year or soon after, they would be
using embedded linux in just about all their consumer keyboards and
some other products. it was mentioned here on LAD as well as
elsewhere.
Granted the connection mangement part of mLAN is
dubious, I've not been
able to read the specs (for obvious reasons). When I spoke before I was
thinking more of A+M over IEEE-1394, which the linux kernel allready
supports to some extent, not mLAN as a whole.
right, but this is more or less useless by itself, as i understand it,
because nobody knows whether to connect to the datastream(s) or
not. sending a stream from A to B involves telling B to listen to A by
hand, or something like that.
Hopefully Yamaha will address the licencing issues,
otherwise it may be
neccesary for software providers to go our own way with connection
management, which would be a shame.
it seemed to me that they didn't want this to happen. but as i
mentioned, it wasn't clear from what i've heard so far why IEEE didn't
take up the CM stuff. did yamaha not want them to? did the IEEE not
like it? i don't know.
--p
11:27 a.m.
On Tue, Jan 28, 2003 at 09:46:38 -0500, Paul Davis wrote:
Yes, of course, I forgot.
Yes, iso 1394 works a bit like IP multicast from what I remeber.
- Steve
Your mention of
"yamaha's coming linux efforts" interests me strangly ;)
Care to share anything?
they announced last month that next year or soon after, they would be
using embedded linux in just about all their consumer keyboards and
some other products. it was mentioned here on LAD as well as
elsewhere. Granted the
connection mangement part of mLAN is dubious, I've not been
able to read the specs (for obvious reasons). When I spoke before I was
thinking more of A+M over IEEE-1394, which the linux kernel allready
supports to some extent, not mLAN as a whole.
right, but this is more or less useless by itself, as i understand it,
because nobody knows whether to connect to the datastream(s) or
not. sending a stream from A to B involves telling B to listen to A by
hand, or something like that. 
2:23 p.m.
On Tue, Jan 28, 2003 at 09:46:38AM -0500, Paul Davis wrote:
I got all excited for a moment, then I remembered that
all the software running on top of that kernel will still,
of course, be proprietary.
--
Paul Winkler
http://www.slinkp.com
Look! Up in the sky! It's AMINO-DAGGER-WEARER!
(random hero from isometric.spaceninja.com)
Your mention of
"yamaha's coming linux efforts" interests me strangly ;)
Care to share anything?
they announced last month that next year or soon after, they would be
using embedded linux in just about all their consumer keyboards and
some other products. it was mentioned here on LAD as well as
elsewhere. 
3:34 p.m.
On Tue, 2003-01-28 at 14:46, Paul Davis wrote:
they announced last month that next year or soon
after, they would be
using embedded linux in just about all their consumer keyboards and
some other products. it was mentioned here on LAD as well as
elsewhere.
Happy to use the linux community's efforts, but not happy to let the
linux community use the SW1000XG. Cool dudes.
Bob
7:24 p.m.
Of course, any kernel enhancements they make will have to be GPL'd.
That could help us.
-dgm
Bob Ham wrote:
On Tue, 2003-01-28 at 14:46, Paul Davis wrote:
they announced last month that next year or soon
after, they would be
using embedded linux in just about all their consumer keyboards and
some other products. it was mentioned here on LAD as well as
elsewhere.
Happy to use the linux community's efforts, but not happy to let the
linux community use the SW1000XG. Cool dudes.
Bob
7770
days inactive
7772
days old
linux-audio-dev@lists.linuxaudio.org
8 comments
6 participants
participants (6)
-
Bob Ham -
David Gerard Matthews -
Paul Davis -
Paul Winkler -
Steve Harris -
Tom