MPC1000 OS V3.0 beta ?

what bugs have u run into?

Antonym wrote:what bugs have u run into?

Nym, experienced any saving problems yet?

i haven't saved anything yet on it

Antonym wrote:what bugs have u run into?

When I resampled the main using "magic" track 61 the metronome click was recorded into my sample too I've forgotten the other one, something else equally minor.

I've been saving stuff to a CF card ... no probs there.

p.

Beta version "03" now available.

Midi Sync bug fixed June 25, 2005. Maybe the guy is monitoring this site.

this is nuts lol... i wonder if akai even knows about this yet, and more so what they'll do about it? akai needs to put this guy on the payroll and fire everyone else programming these things

I think this could actually boost MPC1000 sales. Instead of viewing it as a threat to the 2500, Akai Pro should pay this guy a grip of cash, give him the source code to the 2500 and have him overhaul that for them too.

its frozen on me a few times. when entering 'mode + pad11' and also whilst editing in grid mode. again autoload folder isnt having any effect. i dont like the presets loading at the beginning. erm....and slice mode doesnt work properly, (this has already been mentioned)...no matter how many slices i choose it chops it up the same amount. but really liking the new features. as i said in an earlier post, if u could alter settings in 'mode +pad11' screen on the fly whilst ur beat is playing, then i would b a very happy chappy.

man, gotta chime in...this is amazing on so many levels.
so many simple problems with the 1000 os are fixed (alphabetized browser? word!...the worst tap tempo ever now works). plus, adding new features that make so much sense...grid edit just makes me look at step editing and laugh.

its **** incredible that some random person can come in and **** slap the manufacturer by coding their own much-improved os.
but what will happen when akai drops the hammer on this? i'm 99.9% positive that this is not legal (akai's code has got to be proprietary), so when akai gets their shit together it seems like this guy will get sued somethin fierce. tho if they're smart they'll hire him for double the pay of whoever was working on the os before.
this all just makes the 2500 look like a 1000 with slightly bigger pads and a tilty screen....not worth the extra cash.
whatever the result, i'll be paying for the official release as soon as its available. bravo, ****!

edit: dangmn, didn't realize this board edits the curse words...here they are in rhyme, in order of appearance: plucking, pitch, pit, 'notherplucker. substitute as necessary.

Hopefully the guy won't get shut down because all he's doing is improving their product. The differences between MPC's should be hardware related. I can go out and buy a Mac mini or I can go out and buy a Power Mac G5. They both run Mac OSX, it just depends on how much power I need under the hood. If Akai isn't offering better hardware in a machine that costs 2x the price, that's pretty poor. With that being said, surely the 2500 has a better processor for the price they are charging.

Anyway, good news for us is that this guy caught Akai sitting around with their cocks in their hands, and if they block us from getting features we now know are technically possible, they are going to look like complete asses. I'd say at this point they'll have to step up their game with an official release. I would hate to be an in house programmer at Akai Pro right now.

Hey this guy is great. yesterday i mailed him the midi sync bug. a day later it´s fixed. we should make a new forum for a wish list - maybe he can realize some of our wishes. thanks to the os 3 developer!!! i will buy it for sure!

utty wrote:Hey this guy is great. yesterday i mailed him the midi sync bug. a day later it´s fixed. we should make a new forum for a wish list - maybe he can realize some of our wishes. thanks to the os 3 developer!!! i will buy it for sure!

how did you email him?

you can report bugs on his homepage!

utty wrote:you can report bugs on his homepage!

When you hit enter, a note comes up in Japanese that says he's not accepting information on bugs until the 28th. I doubt if what you sent went through...

There's also a link at the bottom of that page that goes to a list of reported bugs. Nothing up yet except a note that says he will only list bugs which can be reproduced. If he can't reproduce it he says he's going to chalk it up to some kind of operational error.

Guys, we need to forget "wishlists" for now and just make sure we only feedback on actual bugs, so this guy can get this version stable ASAP.

What would be better is for us to compile a list of definate bugs and present them to him in an organised manner (perhaps in Japanese) rather thatn all of us emailing him the same stuff!
Maybe Murahachibu could help with this, if he's up for it?
Just an idea!?!