<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-2" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#3366ff">
Loki Davison wrote:
<blockquote
cite="midec9314860607271827t320702ak89a2824ec2ab398d@mail.gmail.com"
type="cite">On 7/28/06, Renich Bon Ĉiriĉ
<a class="moz-txt-link-rfc2396E" href="mailto:renich@woralelandia.com"><renich@woralelandia.com></a> wrote:
<br>
<blockquote type="cite"><br>
<br>
Gene Heskett wrote:
<br>
> On Thursday 27 July 2006 15:02, Renich Bon Ĉiriĉ wrote:
<br>
>
<br>
>> Jay Vaughan wrote:
<br>
>>
<br>
>>>> > > There are public-domain RTOSes available
that are suitable for
<br>
>>>> > > this task. To those, you can add drivers
for USB and FAT32.
<br>
>>>> > > Without an RTOS to give you hard real-time
scheduling, you have
<br>
>>>> > > no chance to achieve the rock-steady timing
that the MPC
<br>
>>>> > > currently has.
<br>
>>>>
<br>
>>>> that sucks. that really does. because my linux systems
have the same
<br>
>>>> rock steady timing as the MPC. actually, their timing
is even better
<br>
>>>> than the MPC. somebody must have made a mistake around
here.
<br>
>>>>
<br>
>>> i assure you, linux performs on par with "other
public-domain RTOSes"
<br>
>>> in the real-time department, in the right hands .. like
all good
<br>
>>> instruments ..
<br>
>>>
<br>
>> Guys, one question that, I believe, has been answered before.
Is the
<br>
>> service manual enough to start the OS from scratch?
<br>
>>
<br>
>
<br>
> Finally, a question is raised that I can make a comment on, based
on 55
<br>
> years of chasing electrons around for a living. Yeah, I'm getting
to be a
<br>
> chrotchety old coot in my retirement years. :)
<br>
>
<br>
>
<br>
>> # Service Manual
<br>
>> <a class="moz-txt-link-freetext" href="http://www.woralelandia.com/openmpc/service_manual">http://www.woralelandia.com/openmpc/service_manual</a>
<br>
>>
<br>
>
<br>
> After spending about half an hour perusing that pdf, I can, as a
C.E.T.
<br>
who
<br>
> has carved some code in a past life, say that the answer is a
rather
<br>
> resounding no. There is nowhere near enough there, without
chaseing each
<br>
> and every chip maker down and somehow acquiring all the interface
<br>
> requirements. Properly specified, like we used to be able to get
chip
<br>
> info back in the 80's, I'd imagine that pdf would have to grow
another
<br>
> thousand pages.
<br>
>
<br>
>
<br>
>> # Where it all started
<br>
>> <a class="moz-txt-link-freetext" href="http://www.mpc-forums.com/viewtopic.php?t=54825">http://www.mpc-forums.com/viewtopic.php?t=54825</a>
<br>
>>
<br>
>> Thanks for all the help and comments! I am very glad to have
joined this
<br>
>> mailing list ;=)
<br>
>>
<br>
>
<br>
> I can't help but echo the reticence already expressed here
regarding the
<br>
> proprietary nature of this device. If Akai wants to make money on
the
<br>
> hardware by selling it to die-hard linux professional audio
people, either
<br>
> they do their own OS for it and charge whatever they think the
whole
<br>
> package is worth, or open the device up just as if it was a GPL
piece of
<br>
> software and be prepared to sell the hardware for a decent price
after
<br>
> assuming a sales level of x many units. I certainly don't see 3
grand
<br>
> worth of parts, pcb, drive and silk screening there, far less in
fact.
<br>
>
<br>
> I suspect that there will be very little support offered by the
average
<br>
> liux coder if he knows the patches he writes will disappear into
something
<br>
> that is not going to be open-sourced.
<br>
>
<br>
> From my viewpoint, Akai's legal dept., who is obviously
controlling what
<br>
> Renich can say, will see to it that the product fails. Its up to
Akai to
<br>
> make a liar out of me. If they would join the open source camp by
<br>
> supporting the coders with all the info, publicly available to any
and
<br>
> all, that they will need to write the drivers this device will
need,
<br>
> distribute this OS under the GPL with a server that lets *anyone*
download
<br>
> it for free, or on a mailable cd for a couple of bucks american,
while
<br>
> selling the hardware for $1000 to $1500, and watch the hardware
sales
<br>
> blossum like our wild flowers along the interstate. Thats because
the
<br>
> unshackled coders will write stuff that stretches the limits of
what the
<br>
> hardware can do, just to see if they can. Its rather like
climbing Mt.
<br>
> Everest, because its there. :)
<br>
>
<br>
<br>
Well, I think we are getting a bit... carried away. I am not from akai,
<br>
in fact, my purpose is to ask akai to help us help them because there
OS
<br>
sucks. It has too many bugs... that's the purpose of all this. If they
<br>
refuse, then I am willing to start an OS myself. That's all.
<br>
<br>
<br>
</blockquote>
<br>
you mean you are willing to try and find some one to write you a new
<br>
OS for free? How much of the coding will you do? How about you just
<br>
buy a little rack mount pc and an mpd16? then you have the pads from
<br>
the mpc and a whole lot more processing power. You could put a nice
<br>
interface in the same little rack box and then you'll have less random
<br>
stuff to carry to a gig and might actually build a better intergrated
<br>
solution that everyone can use. You might get a lot more support from
<br>
everyone then. Ebay might be a good place for your mpc.
<br>
<br>
Loki
<br>
</blockquote>
Well, that would be selfish. I have the other users in mind. What good
would it be for others if I do as you say? We already bought the
hardware and the OS isn't what it should be. Maybe they don't want to
support it, maybe they can't. I don't care, I do care about making
music and the users at the end. That is why I am trying.<br>
</body>
</html>