If the OS development is slow... make it Open Source!

it's been how long since the last upgrade? akai is probably trying to beat roland before they come out with a new machine.new feature's =new machine...if some could crack the code they probably would have done it by now unless there's something legal to be dealt with,other than that for me it's software help.

mpc500
mpc1000
mpc2000
mpc200xl
mpc2000mcd
mpc3000
mpc4000

and still no upgrade? I guess it will be the 4000xl next with free monitor.

Renich wrote:That is a question for Illiac. He made the contact. He posted something on page 11... i think

In any case, we can show them the stuff first instead of contacting only. Besides, there should be a public bug database so we are aware of what not to do... no?

It`s sounds good, but still we would need to know who they are right?

Just a thought is a great idea. How about the legwork of finding the person or persons who will impliemnt and use this database when it is finished or we will just have that a database with no action or plan from the ones that can make this into an reality?






I assume that the they is Akai U.S.A and that the 4k is still in development?

The thing is that they would not listen to talks only. We need some action. These database is not so hard to make, we just have to convince the users to add the bugs they find to it. There is a number of interfases we could use (bugzilla, phpBugTracker, drupal, etc)

In any case, maybe you can PM illiac and ask him. He made phone contact as far as I recall.

I read pages 1- 3 then skipped to the end to see how this thing turned out....I'm not banking on getting much more out of my 4k than is already there.....the cats with the skill, the information, the resources, and the knowledge of what we need may not exist. And if they do, they're probably making more money doing other things...It's still one hell of a sequencer....

Renich wrote:The thing is that they would not listen to talks only. We need some action. These database is not so hard to make, we just have to convince the users to add the bugs they find to it. There is a number of interfases we could use (bugzilla, phpBugTracker, drupal, etc)

In any case, maybe you can PM illiac and ask him. He made phone contact as far as I recall.

I have already asked former (Akai Pro Japan) and now Pro Audio last yr before the shut down. Everything is in Akai U.S.A now and nothing is happening since the last O.S. of two yrs now. You might think of build a bridge and they will come, but.................... Even when you are finished you still will need a contact to give the information too and a decision-maker to take action. So I ask again who in Akai will it be? You and or illac footwork is needed it`s our idea.

And I will link you with the past threads on this as this have been over 4 to 5 yrs running now.

Blue Haze wrote:You might think of build a bridge and they will come, but.....................

I think they are underestimating a re-release of the MPC4000, as a black MPC4000SE, or a re-release of a black MPC4000LE(no HD, no CDRW, no Expansions)

When paired with a fresh Operating system, and a lower price for a re-released LE, they could make money off of excess old parts stock, instead of building a whole new frame/motherboard/etc. for the 3500...

Yo Akai !!!

alpha80 wrote:instead of building a whole new frame/motherboard/etc. for the 3500...

I seriously doubt they're gonna make a all new technological foundation for the 3500, its prolly gonna be 2500 on steroids. All I know is that Akai is LAZY.

Past O.S requests and bugs listed.

http://www.mpc-forums.com/viewtopic.php ... hlight=o+s

Who will add this to the list it is up to you guys and who will impliment it at Akai still up to you. Feline has been contacting Akai since time past.... I guess if you are more cordial and effective you I hope have a better chance of getting a positive response.

All the best until late Fall next 2007 I`m out.

i cant believe everybody is still going on about this.. i think it might be time for people to upgrade themselves and count their limitations as blessings, after all wishes arent tangible nor are they functional. limitations on the other hand, are concrete and give us a frame of reference in which to assimilate what we can.

threshed wrote:bla bla

I cant believe your negativity. Why even post here? Do you work for Akai?

hey threshed, I'm sitting here thinking about it, but I'm drawing a blank, so maybe you can help me out.

How can I turn a crash of my MPC into a blessing?

think think think think think ...

-illiac

illiac wrote:hey threshed, I'm sitting here thinking about it, but I'm drawing a blank, so maybe you can help me out.

How can I turn a crash of my MPC into a blessing?

think think think think think ...

-illiac

well my 4000 doesn't crash.. when does yours? but you could use the time constraint to force you to compose tunes faster or be quick to learn saving regularly. im not trying to say you guys arent entitled to a better os or trying to be negative. rather im trying to be positive and note that we have alot to learn from the limitations of the machine. we are very spoiled with these things. people still make tunes using 12 second samplers and we spend time bitchin about small features and system errors.

adapt and thrive

well my 4000 doesn't crash.. when does yours?

-when I send sysex data into it from an Access Virus
-when I change note durations or quantize tracks that have very long note durations
-when I save directories to my PC or Mac using ak.sys, where the directories have a lot of files.

It doesn't crash every time I do those things of course, but often enough for it to be a pain in the neck. I really need for my sequencer to be able to handle sysex data; it's the only way I can save multis on the Virus. I've taken to using a QY700 for this task, but that requires recabling my MIDI stuff.

Honestly, there is no bright side to bugs that crash the machine. It's not really possible to whistle it off and write a tune or something: I'm in the middle of a recording session when it happens. It stinks and I wish that Akai would fix these bugs, which I don't think would be very difficult for them.

I know lots of folks don't run into this, but I don't think I'm doing unreasonable things with the machine, just stressing it hard like all gear gets stressed in a pro setting.

-illiac

threshed wrote:well my 4000 doesn't crash.. when does yours?

@ Least a few times a week, when loading samples VIA CD-Rom, I get numerous seek errors (404), and then......

.....A complete freeze....

I have lost so many detail-intensive programs before saving this way.

Now, I save so frequently that it HAS become a workflow disruption when making programs.

The machine is still great, but it is not @ all finished.

alpha80 wrote:

threshed wrote:well my 4000 doesn't crash.. when does yours?

@ Least a few times a week, when loading samples VIA CD-Rom, I get numerous seek errors (404), and then......

.....A complete freeze....

I have lost so many detail-intensive programs before saving this way.

Now, I save so frequently that it HAS become a workflow disruption when making programs.

The machine is still great, but it is not @ all finished.

I think this is a drive issue, not an os problem........Probably easy to change out too