By Renich Thu Jul 27, 2006 2:20 am
>> Illiac, I am glad to have someone like you interested.
Glad to be interested.
>> Could it be possible to develop starting from a beta version? (0.1, 0.5 or 0.9)
Well, haha, this would negate a lot of the advantage of getting the existing OS, because the difference between beta and final release is a ton of debugging and testing and refinement. But I can't see why Akai would give out a beta release -- they are most probably either going to say YES or NO. YES means they license their sources in a way that makes this development possible, and NO means go away.
By the way, it doesn't have to be an open source license per se. It could be a very specific source code license that permits OSes for the MPC4000 to be developed as a derivative work, and nothing else (no other use permitted for the code). It really depends on what their management is thinking about the future of the MPC product line in hardware and software. I can't guess what they are thinking.
>> If the beta version is not released, you think we could start an alternative OS that had the MPC4000 Working as much as possible as it works today?
No. I think you mean, can you build an OS if you don't start with sources from Akai, and the answer is that you can build something but it would fall very far short of the current functionality and stability.
>> If we manage to start an alternative OS with no/little support for the actual Akai files, would that give us better ground on asking them to provide the format definitions so it can be compatible?
Probably not. You know, the format definitions are a lot less proprietary and contain a lot less intellectual property than their source code, so I think it's pretty likely they would give you those even if they refused to give away source code.
> Is it hard to add compatibility to a working OS if we manage to make one (and if Akai supports this part)?
Of course. Look, just think about a multi. It describes a mixer -- a bunch of simultaneous audio sources being summed. Each of the programs describes a bunch of keygroups which map midi events to samples that go through envelopes and get shaped by a modulation matrix and you name it. You gotta make all of that stuff work like it does now. It's all specified in the multi and the programs and samples that make up the multi. It's a ton of work and a ton of detail. All of this has to be programmed in a way that doesn't overtax the CPU and memory, which are finite resources.
>> Who will benefit the most if we manage to release a stable OS that is fully compatible and bug free?
The people who use it.