Love all the updates but I think JJ needs

Guys I know we all love with JJ has done to the MPC1000/2500 and I know or believe that Akai will move towards using all that JJ has done and more on there next MPC 7XXXX.

Not sounding like a newb but dont you think before releasing updates maybe after all $$ he made and making which is great that he for one did this to help us out with a worthless beatmachine with the orginal OS.

I just think he needs someone to QA his updates before he releases them.just about every 2 weeks there is an update with bug fixes but then again there is bug in the fix. Just seems to get boring after while to see UPDATE 3.XX.. Just my thoughts I am very happy with the functions just would like to see new improvement and not bug fixes..

Ty Blak

it's a release/development style. it beats the hell out of the alternatives, but it requires more participation on the side of the user...instead of a "set it and forget it" approach that most software companies traditionally have.

check this out:

http://en.wikipedia.org/wiki/Agile_software_development

cockos reaper is a more advanced example of agile software

I aggree totally and the wiki read i have read this before and did not link that with this approach by JJ...Thanks good find!

Nym wrote:
http://en.wikipedia.org/wiki/Agile_software_development

cockos reaper is a more advanced example of agile software

*smile and nod*

not going to university is starting to seem like a bad idea right about now.

yeah it's a dense read but here are the hilights:

Twelve principles underlie the Agile Manifesto, including:[7]
Customer satisfaction by rapid delivery of useful software
Welcome changing requirements, even late in development
Working software is delivered frequently (weeks rather than months)
Working software is the principal measure of progress
Sustainable development, able to maintain a constant pace
Close, daily co-operation between business people and developers
Face-to-face conversation is the best form of communication (co-location)
Projects are built around motivated individuals, who should be trusted
Continuous attention to technical excellence and good design
Simplicity
Self-organizing teams
Regular adaptation to changing circumstances

i bolded the ones that i feel jj does best. i've beta tested for several developers and i've never felt as motivated/useful as i do for the jj team.

props!

Certified Beatz wrote:Guys I know we all love with JJ has done to the MPC1000/2500 and I know or believe that Akai will move towards using all that JJ has done and more on there next MPC 7XXXX.

Akai is cooking up something now as we speak. I just wonder if they are going to use the best collaboration combo (Lynn drum and Akai working together) to make something on the next level.

If I were Akai I would allow users to be able to load their old MPC 1000 OS. Doing this would allow JJ to continue to develop the OS well beyond what any company is willing to pay for software engineering.

Lets be realistic, with all the feature request that are possible this could be another 5 year project.

Akai needs to just work on its sound (ADC,DAC,24 bit sampling with down converting to 16 bit wave) presentation.Roland has the best sound IMO because I used to own a VS 1680.

So JJ and Roger Lynn has made Akai a legendary company when it comes to music. JJ is Akai and Akai is JJ.

Certified Beatz wrote:
I just think he needs someone to QA his updates before he releases them.just about every 2 weeks there is an update with bug fixes but then again there is bug in the fix. Just seems to get boring after while to see UPDATE 3.XX.. Just my thoughts I am very happy with the functions just would like to see new improvement and not bug fixes..

Well I think he is trying to create a balance between updates for bugs and updates for features.

I want to see more features also but peeps will start to complain about bugs not being fixed. Take Sally for instance. He makes video bugs on you tube so if a consumer sees them they will not buy the product; those bus JJ must fix right away. A bug fix is always good.

It would be nice if he would give us more heads up on whats next like he did with the pattern mode--he made a video two months before it was released.

As for Q and A, I say ask him if he could get on the boards one day.

Nym wrote:it's a release/development style. it beats the hell out of the alternatives, but it requires more participation on the side of the user...instead of a "set it and forget it" approach that most software companies traditionally have.

check this out:

http://en.wikipedia.org/wiki/Agile_software_development

cockos reaper is a more advanced example of agile software

MPC forums has a good team here to help JJ similar to that workflow. Right now JJ OS does things a DAW can't do.

Nym wrote:it's a release/development style. it beats the hell out of the alternatives, but it requires more participation on the side of the user...instead of a "set it and forget it" approach that most software companies traditionally have.

check this out:

http://en.wikipedia.org/wiki/Agile_software_development

cockos reaper is a more advanced example of agile software

exactly

I think that JJ needs someone that could write plain english.
It's astonishing the way they write great code and - on the other side - are totally unable to say things like "push this" but "the pressure of the button it is needed".
Honestly thats the most difficult part of their work: understand what are saying