Mac OS X Mavericks Bug with 1.5

Yep, just like all the other DAW/audio manufacturers, some with much larger development teams, and most likely those making other types of software, who do not have Mavericks support as yet.

The MPC 1.5 update was released before the Mac 10.9 golden masters were released.

They are probably not going to waste their development time/efforts until there is an actual release version available, they are a small development team (1 person?), and most likely need to concentrate on supporting actually released and available computer OS versions.

Why were they not ready with the 1.5 update? Because that is the way it works.

You are obviously not willing to listen to others who have been through this exact same process, over many years, with many different OS versions/platforms/applications, and to accept that this is just the way it works in the real world, so feel free to continue your childish battle.

If you read my referral to the other manufacturers many have already been working on it, or made statements.

and I think I might have had a little more experience with these matters than you give me credit for.

Like I've mentioned, I've been into midi since its' inception. I know how the "game" works, but there is no excuse for such sloppiness nowadays.

There is no reason Akai should have been able to submit an ext for inclusion into Mavericks over a 5 month period, so at least it's recognized at the install of Mavericks.

What's funny is MPC Ren version 1.5 functions fine (for me) other than the driver not being able to be utilized by the core apple functionality (i.e. as a sound output) So, as I mentioned, when the installer for Mavericks installed it said, paraphrasing: "hey this Akai ext in your library, well I don't know what it is, so I can't use it, please contact the manufacturer and have them fix this issue with us"

So, it's not a battle, should be an easy fix for Akai, it's clear Mavericks didn't break any functionality, they just didn't give Apple info on the ext before Mavericks release, even though, like I previously mentioned, they had 5 months to do so.

LarryT63 wrote:If you read my referral to the other manufacturers many have already been working on it, or made statements.

Which means that they do not have Mavericks support yet, just like Akai, after 5 months.

That is the point, this is the way it works, as demonstrated by the other manufacturers not having support as well.

LarryT63 wrote:and I think I might have had a little more experience with these matters than you give me credit for.

I have owned and used Pro Tools for over 15 years, and have worked a fulltime job for the last 15 years supporting this sort of gear, and owned/used similar gear for 10 years before that, along with working in IT support for 10 or more years before that.

I know exactly how support for new computer OS versions from audio application/hardware manufacturers happens in the real world, and it has been demonstrated in your own observations above.

But please, continue to upgrade to new OS versions as soon as they are released, maybe going through it multiple times is the only way you will actually learn.

SimonInAustralia wrote:
But please, continue to upgrade to new OS versions as soon as they are released, maybe going through it multiple times is the only way you will actually learn.

from Logic Pro to Protools, nothing is immune from the "OS upgrade". You have to be easy and wait

As you take this this way I'm not going to give you any more advice. What I see is a person that is not wanting people to help him, instead of silence to my "possible solution" you could have answer with, "i already tried that" so maybe another fellow user would give you another solution. Instead, I see you started a 2nd threat with the same issue.
Using the dictionary is not going to make you smarter, words have to be defined in context.
I have mavericks because I like to test things, plus I'm an Octane Render beta tester, it is working for me.
BTW I'm not hypocrite, more like a sophist if you like to call me names
Are you really 50? I woukd have guess more like 15...
See you around.

I think this topic is about done.