Akai support

MPC-Tutor wrote:Here's the direct link

http://www.mpc-tutor.com/mpc-bug-reports/

Once we have a few more bugs I'll link to it from the main menu. There's a few I've added already, plus one I added on behalf of another forum member.

Add anything you like, doesn't have to be just pure bugs. Even stuff like screen lag, slow loading etc. I still cannot get over how long the 5k takes to load up projects compared to a 1000 - same project on the same CF card takes significantly longer on the 5k.

Thank you so much. Excellent setup!

I have a few bugs and i'm going to recreate every bug listed, but i have more suggestions for improvements then bugs. Will there be a seperate list for that or should i just use the bug list?

Just use the bug list for the moment, I can separate things off once we have some submissions.

This link is getting lost in the mail...... please promote the link or there is no point to all of this.

Akai Pro is giving me the silence treatment now. They've been ignoring me like a plague. I have a feeling the 5000 is a product of theirs they wish never existed.......

They said the 5000 was being discussed intrenally and they take my feedback very seriously;). That was April 8th.

If people are up to it give them a tweet, because they do react asap to other people with questions. Ask the what the plans are with the 5000.

I'm not salty but a bit dissapointed in Akai.


Moving on............

CoinOP! wrote:Akai Pro is giving me the silence treatment now. They've been ignoring me like a plague. I have a feeling the 5000 is a product of theirs they wish never existed.......

They said the 5000 was being discussed intrenally and they take my feedback very seriously;). That was April 8th.

If people are up to it give them a tweet, because they do react asap to other people with questions.

I'm not salty but a bit dissapointed in Akai.


Moving on............

man, that's just them.... they just do that.

I think since numark bought out akai and alesis... they have just been recycling designs that they still had the ability to easily make... mostly discontinued alesis products. I mean that is okay... if the product works, but when something is designed a certain way.... if you want to make a change to that design you may wind up with more problems then if you had created a new design from scratch.

I think that is what happened with the 5000. It seems like they bit off a bit more then they could chew. They needed to make a money making machine but they had no budget... that is why they did all this basically free stuff to get the job done for example the 3500 to 5000 name switch would make it seem more attractive, they used a pre-existing design for the machine, they didn't spend much time debugging the OS... and the OS2 (which my guess they already were making this right from the start... but launched early to start making sales) well if they were really in the market of fixing up their OS and adding features.... they would be doing it and we wouldn't be using JJOS on the other models. We would be seeing bug fixes being fixed that maybe we didn't even know about. Fact is, akai knows about the bugs. it's their business to know... but it aint in their business to do things other then making profit without spending.

It sucks to be disappointed in our favourite company but it is what it is.

I just cannot comprehend the lack of communication from such a huge company. Just say "**** you and shove that 5000 up your ass" to me Akai, but don't ignore me like I don't exist.

I enjoy the 5000 very much, I will keep doing that. But it would be nice to do that without tiptoing around it. The fear of the 5000 might crash only when auditioning samples. I backup more often then I wish, which is a drag, but I have no choice......

Finally got a response just now; "This is a work in progress. Not sure on the exact date of release at this time" they replied after me asking them again if there was any news from the devs about the 5000.

What do they mean? Is the news about the future of the 5000 a work in progress or will there be a new OS on the way?

Anyways now is the time to add to the buglist and forward it asap so they can use it while in progress.

I think it's commonly known as being fobbed off.

oh one other thing, akai the company that makes TV's and things are completely not linked with akaipro the one we care about... not any more at least.... as you know so I dont even know how huge they still are.

man, like... I never understood how they could have went down this road. It sucks really, because from an outside perspective it seems like it's management decisions that are responsible for their own problems.

Nice bright and cheery tweets from Akai_Pro. They are hiring Social Media Interns. That says it all. Looking cool on the net is more important than quality products. Hunting down the smallest bug and releasing an update should be their highest priority. I dislike that all developers now only release updates with new features - and bug fixes quietly done in the background. What would be wrong with fairly frequent updates with just bug fixes? Oh right, they already have our money. It seems like integrity and being proud of your product is a sooo last century...

LivePsy wrote:Nice bright and cheery tweets from Akai_Pro. They are hiring Social Media Interns. That says it all.

Those are the same guys handling your submission via the Akai Pro site. Unfortunately to reach the devs you have to go through them first. These guys are no product specialist and or not part of the frequent product meetings. They have no priorities! They are not going to stress the devs to fix the 5000?! They just forward stuff.

So please holla at them about anything of the 5000 via email or twitter many times so the devs notice something needs to be done.

Have a got selection of bugs now, so I'll get the first bulk submission of bug reports to Akai next week

If they want to hire social media experts, let's give them some work then!

I suggest twittering:

Dear @akaipro - Please update the products that you asked us to pay hard money for. http://www.mpc-tutor.com/mpc-bug-reports/