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 LarryT63 Thu Oct 31, 2013 2:51 am
when I first installed Mavericks, I got this message:

"the (AKAI)ext found in the library not being registered and to contact the manufacturer."

Now my Mac Mini doesn't get any signal from my mac, to either record, monitor or sample from it. when I choose it as an output source, it selects it, but doesn't play any sounds from the Mac (itunes, alert sounds etc), however, in the MPC program, a song or project will play fine.


Come on Akai, let's fix this!

Who do I contact at Akai and where do I report this?
By LarryT63 Thu Oct 31, 2013 5:20 pm
Great!

J Sandeen (Technical Representative) 11 minutes ago
The Renaissance driver and MPC Software has not been cleared/updated for 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'.
By LarryT63 Thu Oct 31, 2013 8:11 pm
I don't want to revert to an older version of the OS!

I want to know why Akai didn't jump on development earlier, since the preview of Mavericks was available to developers in September, why didn't you have version 1.5 Mavericks compatible?
By LarryT63 Thu Oct 31, 2013 8:29 pm
My current work around was to plug back in my M-Audio Fast Track Pro and use it to monitor, however, I bought an Akai Ren instead of a Studio, so I could eliminate the Fast Track Pro...
User avatar
By SimonInAustralia Thu Oct 31, 2013 8:40 pm
LarryT63 wrote:I don't want to revert to an older version of the OS!

I want to know why Akai didn't jump on development earlier, since the preview of Mavericks was available to developers in September, why didn't you have version 1.5 Mavericks compatible?

I never suggested that you should revert to an older version of the OS!

I am referring to TT_Lab's reply in this thread, where he says to try the security settings...
viewtopic.php?f=36&t=169266


Loading up a new computer OS as soon as it is released is questionable practice anyway, just wait a couple of weeks to make sure the tools you use are compatible, let others deal with these issues.
By LarryT63 Thu Oct 31, 2013 9:05 pm
Sorry, I posted to Akai as well and someone suggested that I reinstall an old OS.

The workaround isn't for Mac OS X 10.9, (the control panel is different in Mavericks as it says Security & Privacy) however I checked my settings, and it is set to recognize other known developers.

My guess is Akai didn't submit the ext to Apple for Mavericks, so it isn't recognized by Mavericks.

As I am a hobbyist, it's not a big deal thus far, however Akai should have really been on top of this in September, seems like a small thing, I mean you're working on version 1.5 and the developer preview is available to you, why not make sure it's compatible? Did Akai just rush the release of 1.5 because Maschine 2.0 came out?

Makes you wonder doesn't it?
User avatar
By SimonInAustralia Thu Oct 31, 2013 9:10 pm
Did you try changing the setting?

Once you start working with external audio interfaces, and other things that need system level device drivers, it is never a good idea to jump on a new OS as soon as it is released, give it a couple of weeks, let the dust settle, see what problems others are having with the same hardware as you, before you upgrade.

There really is no need to upgrade the computer OS so soon after release, you are just asking for these sort of issues.
By LarryT63 Thu Oct 31, 2013 10:41 pm
my setting was set to that anyway, if I change it to Apple store only, that wouldn't do anything.

Like I said, I'm a hobbyist, HOWEVER, that doesn't negate Akai's responsibility to be compatible with the CURRENT OS. What if I was a professional and I bought a new computer and then shelled out all the money on the Akai Ren? I'd be screwed wouldn't I?

Would you then start saying "As a seasoned professional, you should have researched and found out that buying a new computer isn't necassarily the way to go as until a new computer is considered stable, you should use what is known to be a stable (legacy) device/computer.

I've been using midi gear since it's inception, and there is really no reason Akai couldn't have made their latest release of 1.5 Mavericks compatible.

The fact they are saying that it isn't tested/approved etc = laziness or lack of caring for their end user. Neither is good.

Looks like most DAW software are working on it,

http://createdigitalmusic.com/2013/10/o ... lmusic.com)

It would be nice if Akai would acknowledge issues and release a statement that it is working on a release that is stable with Mavericks...
User avatar
By Coz Thu Oct 31, 2013 11:44 pm
LarryT63 wrote:It would be nice if Akai would acknowledge issues and release a statement that it is working on a release that is stable with Mavericks...



It's very slack if they haven't even announced that they are working on it. Every time they demo their gear it's on a Mac, which makes it look worse IMO.
User avatar
By SimonInAustralia Fri Nov 01, 2013 12:04 am
LarryT63 wrote:my setting was set to that anyway, if I change it to Apple store only, that wouldn't do anything.

Did you try setting it to "Allow applications downloaded from: Anywhere"?
By LarryT63 Fri Nov 01, 2013 12:59 am
As the software is already installed on my system, I don't think that would help. Also, it would cause a security risk, I'm not willing to take...

Version 1.5 is on the system already, unless Akai releases new software that Mavericks can recognize as being legit, I don't think anything will "fix" this issue...
User avatar
By SimonInAustralia Fri Nov 01, 2013 1:27 am
You don't know if anything will fix the issue unless you try the available options.

Seriously, get over your irrational fear of changing that setting.

- Change the setting
- Test to see if it fixes the problem
- If it doesn't fix the problem, uninstall/reinstall the MPC Software and drivers
- Test to see if it fixes the problem
- Change the setting back

The world is not going to end if you change that setting temporarily, then change it back.


Otherwise, just get used to waiting for support after the release of a new OS version, that is simply how it works in the real world, no matter how you think it should theoretically work.
By LarryT63 Fri Nov 01, 2013 2:38 am
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...
User avatar
By SimonInAustralia Fri Nov 01, 2013 3:01 am
LarryT63 wrote:The suggestion you made doesn't seem logical or helpful.

You get an error message saying that an Akai extension is not registered, which is most likely meaning it is not registered with Apple as coming from Akai as a trusted developer providing secure applications.

There is a security setting that seems related to this situation of developer/software being registered with Apple...
"Allow applications downloaded from: Mac App Store and other identified developers"

It is possible that the extension in question is related to the Akai audio interface working within System Preferences/Sound to provide system sound output.

It is also possible that if that setting is changed, as suggested, to "Anywhere", and you reinstall, it might avoid that error message, and it might allow the audio drivers to operate within the OS.

If you can't see the logic in that, or that it is trying to help you overcome the problem, then there really isn't anything more I can do, you should just continue whining about it and not try to fix it.


LarryT63 wrote: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.

Yet you post a link showing how all the other DAW manufacturers do not yet have support for the new OS.

That is standard procedure with software that has system level device drivers, they often do not work with new OS versions, and you often have to wait a while after release until support is provided.


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

It is theoretical to suggest that manufacturers should have support for a new OS as soon as it is available.

That is great in theory, in practice, in the real world, from my observation after over 25 years of working with this gear, it simply does not work like that.


LarryT63 wrote: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.

I have owned, used, and supported this equipment in my job, for over 25 years.

I know how it works.


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...

Akai will fix the issues with OSX Mavericks, they know about them, you just have to wait, like users pretty much always have to do when new OS versions are released.