Bug reports & end-user support for Akai's MPC Software 'controllers' including the new MPC Studio 2, the MPC Touch, MPC Renaissance & original MPC Studio and MPC StudioB lack.
By TT_Lab Fri Nov 01, 2013 4:50 am
LarryT63 wrote:I'll wait...

The suggestion you made doesn't seem logical or helpful.

I don't think it's wrong for an end user to expect hardware/software to work, especially with a company as big and as established as Akai.

Yes I'm a bit put off by this incident, however, I don't think anything I've said should be considered "theoretical"

I've been using Midi gear since the Mid 80's and know how "the business works. I've owned a lot of gear in the past 30 or so years, so I think with that, I know how things SHOULD work.

Akai, FIX the issues and problems you have, you owe that to the people that buy your products! Not directly dealing with it causes customers to not trust or use your products. Just look at all the other problems people are having. I'm not alone here...

For real?? Sorry Spock, you'd better burn your mac and your mpc maybe there are bugs in it!That would be completely logical! XD
Image
The shit sometimes I have to read is unbelivable!
Did you read anywhere that mavericks is supported with the MPC software? So you have options:
1. Don't update OSX til it's fully supported (wiser option, not what I did...I use mavericks with studio no probs).
2. Don't use your mpc until AKAI updates the drivers.(what does not guarantied that will be signed with apple).Put a FEATURE REQUEST up in both here and AKAI's official support forum.
3. try solutions people is giving you.
4. Burn everything! and dedicated your life to sculpture, painting or other things! :P
User avatar
By SimonInAustralia Fri Nov 01, 2013 8:14 am
LarryT63 wrote:Akai, FIX the issues and problems you have, you owe that to the people that buy your products! Not directly dealing with it causes customers to not trust or use your products. Just look at all the other problems people are having. I'm not alone here...

Image
By LarryT63 Fri Nov 01, 2013 3:41 pm
Like I said, I'll wait...

log·i·cal (lj-kl)
adj.
1. Of, relating to, in accordance with, or of the nature of logic.
2. Based on earlier or otherwise known statements, events, or conditions; reasonable: Rain was a logical expectation, given the time of year.
3. Reasoning or capable of reasoning in a clear and consistent manner.

If you have a user base that includes Mac users, it would be a "logical" (reasonable) expectation, that if you had a few months to get a release ready, you would make it compatible with what you know would be the most current version of that OS and to have it run optimally on it!
Last edited by LarryT63 on Fri Nov 01, 2013 3:52 pm, edited 1 time in total.
By LarryT63 Fri Nov 01, 2013 3:51 pm
"The **** sometimes I have to read is unbelivable!"

Don't read or answer my post then.

"Did you read anywhere that mavericks is supported with the MPC software? So you have options:
1. Don't update OSX til it's fully supported (wiser option, not what I did...I use mavericks with studio no probs). "

If you didn't do it either, wouldn't you suggesting that make you a hypocrite? :)


"2. Don't use your mpc until AKAI updates the drivers.(what does not guarantied that will be signed w"ith apple).Put a FEATURE REQUEST up in both here and AKAI's official support forum.

I'm new here and wasn't I suppose to make a bug report? (which I did) I'd expect not to get flamed for observations I made, with the hopes of helping someone not have the same issue.

"3. try solutions people is giving you."

I did look into "your solution" but my computer was already set up that way. Spending hours reverting to an older OS or spending hours uninstalling and reinstalling the MPC Ren in hopes it "might" fix the problem would be a waste of time.

"4. Burn everything! and dedicated your life to sculpture, painting or other things!"

See the first line of your comment above... :)
User avatar
By pk1 Fri Nov 01, 2013 4:11 pm
Ok so did I miss something here. The kid is scared to click "download from anywhere" option. And now you guys are f.u.c.k.i.n.g. With him simply because of that.

In "all logic" spok talk here you guys are completely wrong if you think clicking that option will help our issue. It's actually stupid suggestion.

And simon I know your not stupid. We upgraded the os. And the mpc software is already on the computer so this security option is irrelevant. You really have not explained why he would NEED to do this and just turned it around on him cause he won't do this little thing. Granted he is being a little more scarred then needed.


For the record, changing the security option did nothing. Reinstalled the drivers and in the audio midi set up, there is the option to select the ren but you can't really select it. It is a dead option like there is no drivers for the devise it see's.

So when I open the software I can hear the track but the computer audio does not come out of the monitors. So no youtube or iTunes. Or listening to soundcloud battle contestants. I can still play vinyl threw the ren just no comp sound. So the ren still works just needs the driver. In which the kid is rite. Nukia is really tripping for not taking cafe of this ASAP. If we need to wait till 1.6 I'd be very disappointed.
By LarryT63 Fri Nov 01, 2013 4:37 pm
thanks PK1!

I'm not a kid though (I'm 50) LOL

But again, I think it would be unwise to allow any source to be allowed on the system, though I have a few programs I did install (Scrivener as an example) directly from the web, outside of the app store or from a disc.

Also, since it was just a picture and not an explanation, it didn't make sense to change that setting if 1.5 was already installed on the system. My understanding from Akai is when a new update is available the MPC software will mention it and that setting wouldn't affect it being installed (as it didn't the first time I installed it running OS X 10.8).

My rant is this, I told Akai the problem I was having, and they just basically said "Too bad, so sad, it won't work." without even saying they were working on a Mavericks compatible version.

again here is the communication they sent me:


"EMPLOYEE
J Sandeen (Technical Representative) 23 hours ago
The Renaissance driver and MPC Software has not been cleared/updated for official OS X 10.9 support. We recommend using OS X 10.6-10.8. The software will grab any driver update download upon launching the software with the internet on.

You most likely not be able to use the audio card with your Mac's global sound settings - 'Audio MIDI Setup'."
User avatar
By pk1 Fri Nov 01, 2013 4:46 pm
I know he is copying and pasting this crap to all of us that are having the issue.

Hell I guess I'm getting to be an old man too. It's funny how easy it is to stereo type fellow bloggers.

What Simon was tryin to get you to do is not a big deal though. I think he ment for you to open your security so you can try to reinstall the drivers. Then you can go back and up your security back to where you are comfortable. Regardless it doesn't work. We are :fku: until they drop a new driver.

And this is support to be a mac. I don't remember windows 11 or whatever the hell their new os system they got a few months back is called, but I don trembler their driver not existing. I could be wrong
User avatar
By SimonInAustralia Fri Nov 01, 2013 6:32 pm
LarryT63 wrote:If you have a user base that includes Mac users, it would be a "logical" (reasonable) expectation, that if you had a few months to get a release ready, you would make it compatible with what you know would be the most current version of that OS and to have it run optimally on it!

Again, that is your theory about how it should work, but it doesn't.

Manufacturers do not have access to release versions of an OS months before it is available to the public, the OS is changed right up until release.

You posted a link to some DAW manufacturer that said their software was not compatible with Mavericks.

This is what Avid has to say about Mavericks support...
It is not recommended to use Media Composer, Pro Tools or Sibelius with Mac OS X 10.9 (Mavericks) as they are not supported at this time.


It is simply the way it works.


LarryT63 wrote:I'm new here and wasn't I suppose to make a bug report? (which I did) I'd expect not to get flamed for observations I made, with the hopes of helping someone not have the same issue.

You were not flamed in any way for making a bug report.



LarryT63 wrote:"3. try solutions people is giving you."

I did look into "your solution" but my computer was already set up that way. Spending hours reverting to an older OS or spending hours uninstalling and reinstalling the MPC Ren in hopes it "might" fix the problem would be a waste of time.

If you are spending hours to uninstall and reinstall MPC Software and drivers, you have more serious issues than it not working on Mavericks.

Your computer is already setup...so you can never install software or change any OS settings ever again?


LarryT63 wrote:I'm not a kid though (I'm 50) LOL

Not everyone here is a kid.


LarryT63 wrote:But again, I think it would be unwise to allow any source to be allowed on the system, though I have a few programs I did install (Scrivener as an example) directly from the web, outside of the app store or from a disc.

That is just plain stupid.

The default for this security setting has only just changed. It has worked fine for years for everyone else, without this setting.

Like you say, you have a few programs that you did install, but now it is being suggested as a troubleshooting step, it is some major drama and threat to national security.


LarryT63 wrote:Also, since it was just a picture and not an explanation, it didn't make sense to change that setting if 1.5 was already installed on the system. My understanding from Akai is when a new update is available the MPC software will mention it and that setting wouldn't affect it being installed (as it didn't the first time I installed it running OS X 10.8).

You don't know unless you try, it is called troubleshooting.

That setting was already there in 10.8.


LarryT63 wrote:My rant is this, I told Akai the problem I was having, and they just basically said "Too bad, so sad, it won't work." without even saying they were working on a Mavericks compatible version.

It doesn't take much logic to work out that they will provide Mavericks support in an upcoming release.


pk1 wrote:What Simon was tryin to get you to do is not a big deal though. I think he ment for you to open your security so you can try to reinstall the drivers. Then you can go back and up your security back to where you are comfortable. Regardless it doesn't work. We are :fku: until they drop a new driver.

Yes, not a big deal in anyway at all.

And you tried it, and it doesn't work, then great, at least you have tried, you are not going to know otherwise.
By LarryT63 Fri Nov 01, 2013 9:05 pm
Like I said, my computer was already set that way, but how would "trying it" after the software is already installed being helpful?

You do understand that the setting prevents malware from being installed, not affect software that is already installed right?

Akai had an opportunity to make 1.5 Mavericks compatible as they had access to the Mavericks preview since September. The way the framework is made up, the essentials are there at the first preview, and nothing major is changed. All the developers are asked to chase down bugs and report them to Apple if it has to do with the Apple feature set. However, it is up to the developer (Akai, in this case) to make sure version 1.5 was up to snuff with Mavericks, something Akai DIDN'T DO. So in essence everyone that updated to Mavericks is now hunting down the bugs for them. As an end user that paid upwards of $700+ do you enjoy being a beta tester with no reward? :)

I take full responsibility for installing Mavericks and version 1.5 of the Ren software not working, it was never advertised to do so, however, what I am bitching/whining about is Akai's lack of response to us as a user base. At least the other manufacturers of DAW software are addressing the issue by either working on it and/or making a statement of where they are. Akai has said and done nothing to appease us. I have again, posted to the Akai pro site, and have received nothing back from them.

I think that is a legitimate beef.

Again, I posted this as a bug report, with them you all of you. Not expecting a fix here, though I appreciate the input. I am sorry, if I rubbed people the wrong way by showing my frustration with the situation. I didn't expect a "you shouldn't have, or you should have known better, or erase your OS and start from scratch" approach though. While it would be a valid solution for a professional musician who makes his/her living doing this, I have a lot of other creative endeavors going on that I use my computer for other than music, so it wouldn't be worth my time....

Your opinions and mileage may vary :)
User avatar
By SimonInAustralia Fri Nov 01, 2013 9:26 pm
LarryT63 wrote:Like I said, my computer was already set that way, but how would "trying it" after the software is already installed being helpful?

You do understand that the setting prevents malware from being installed, not affect software that is already installed right?

You do understand what uninstall/reinstall means, right?


LarryT63 wrote:Akai had an opportunity to make 1.5 Mavericks compatible as they had access to the Mavericks preview since September.

However, it is up to the developer (Akai, in this case) to make sure version 1.5 was up to snuff with Mavericks, something Akai DIDN'T DO.

No, it is up to the developer to make sure their software is compatible with Mavericks whenever they want to.


LarryT63 wrote:As an end user that paid upwards of $700+ do you enjoy being a beta tester with no reward? :)

Get used to it, every other Renaissance/Studio owner has had to.


LarryT63 wrote:what I am bitching/whining about is Akai's lack of response to us as a user base. At least the other manufacturers of DAW software are addressing the issue by either working on it and/or making a statement of where they are. Akai has said and done nothing to appease us. I have again, posted to the Akai pro site, and have received nothing back from them.

Again, get used to it, Akai does not have very good communication with it's customers.

They don't even seem to have any communication between their support staff on their own forum, and their development team.


LarryT63 wrote:I didn't expect a "you shouldn't have, or you should have known better

You should expect that, because many have been through OS upgrades many, many times, with audio hardware/software, and that is how it works, if you don't want problems, you leave it the way it is until compatibility is sorted out.

There really is no reason to upgrade the OS or software as soon as it is available, if you can't wait for support/compatibility, then you just have to deal with the issues that will most likely occur.
By LarryT63 Fri Nov 01, 2013 9:46 pm
Simon, if you're an "Advanced User" in this forum, why do you feel the need to nitpick someone's bug report and antagonize them? You are, by your own admission, in the same boat as the rest of us that pulled the trigger on Mavericks.

A little more empathy would be nice and not this "get use to it, get over it" attitude.

We are all in this boat together, it would be nice if you wouldn't try to push me overboard and be a little bit more "supportive"

I'm just giving my viewpoint and observations here.
User avatar
By SimonInAustralia Fri Nov 01, 2013 10:03 pm
LarryT63 wrote:Simon, if you're an "Advanced User" in this forum, why do you feel the need to nitpick someone's bug report and antagonize them? You are, by your own admission, in the same boat as the rest of us that pulled the trigger on Mavericks.

The advanced member tag is automatically generated based on how many posts you have made, it really doesn't mean anything.

This is a discussion forum, you are entitled to whine about Akai, others are entitled to respond to that whining.

Go back to the start of this thread, and read through it, I was trying to help, and what you call nitpicking is just ongoing discussion from that.

I am not in the same boat as anyone who has pulled the trigger on Mavericks.


LarryT63 wrote:A little more empathy would be nice and not this "get use to it, get over it" attitude.

Anyone who has dealt with Akai long enough knows how they treat their customers.

You really should get used to it, and get over it, as it is going to keep happening.

And empathy is not going to happen...upgrading your OS the second it is available, then whining about the resultant incompatibility, does not deserve empathy, it requires education.


LarryT63 wrote:We are all in this boat together, it would be nice if you wouldn't try to push me overboard and be a little bit more "supportive"

Offering suggestions to try and troubleshoot your issues, rather than just whining about it, which will not get you anywhere, is being supportive.

If you mean supportive in terms of joining in on your whinge about Akai not having support for Mavericks, it isn't going to happen, because it is your fault for upgrading without ensuring compatibility, not Akai's.

You don't seem to need any pushing, you are already overboard, we are just trying to get you back on board with some facts and a reality check.
Last edited by SimonInAustralia on Fri Nov 01, 2013 10:50 pm, edited 2 times in total.
User avatar
By SimonInAustralia Fri Nov 01, 2013 10:39 pm
LarryT63 wrote:If you have a user base that includes Mac users, it would be a "logical" (reasonable) expectation, that if you had a few months to get a release ready, you would make it compatible with what you know would be the most current version of that OS and to have it run optimally on it!

LarryT63 wrote:However, it is up to the developer (Akai, in this case) to make sure version 1.5 was up to snuff with Mavericks, something Akai DIDN'T DO.

MPC Sofware OS1.5 released 1st October 2013.

Mac OS X 10.9 released 22nd October 2013.

log·i·cal (lj-kl) :?: :hmmm:
By LarryT63 Fri Nov 01, 2013 11:56 pm
not logicial:

Mavericks preview release dates:


Release Number Build Date Note Install Type
10.9 13A476u June 10, 2013
Developer Preview 1
Full
10.9 13A497d June 24, 2013
Developer Preview 2
Incremental
10.9 13A510d July 8, 2013
Developer Preview 3[26]
Incremental
10.9 13A524d July 22, 2013
Developer Preview 4[27]
Full
10.9 13A538g August 7, 2013
Developer Preview 5[28]
Incremental
10.9 13A558 August 21, 2013
Developer Preview 6[29]
Incremental
10.9 13A569 September 3, 2013
Developer Preview 7[30]
Incremental
10.9 13A584 September 16, 2013
Developer Preview 8[31]
Incremental
10.9 13A598 October 3, 2013
Golden Master[32]
Full
10.9 13A603 October 20, 2013
Golden Master 2[33]
Public Release
Full


Akai had 5 months to get it compatible! :)

whine (hwn, wn)
v. whined, whin·ing, whines
v.intr.
1. To utter a plaintive, high-pitched, protracted sound, as in pain, fear, supplication, or complaint.
2. To complain or protest in a childish fashion.
3. To produce a sustained noise of relatively high pitch: jet engines whining.

Since I'm not making a high pitched sound, I find your action of calling me childish in my observations very ignorant:

ig·no·rant (gnr-nt)
adj.
1. Lacking education or knowledge.
2. Showing or arising from a lack of education or knowledge: an ignorant mistake.
3. Unaware or uninformed.

Touche'

:P :)