HELP! Bad El capitan and ren issues!

MPC-Tutor wrote:While it's clearly not a bad sounding interface, I really don't think the Ren interface is anything special, in all probability it's likely just a rebrand of something else 'inMusic' (e.g. lower end M-Audio interface).

If it were me and my Mac refused to play nicely despite every other app and hardware working perfectly I'd be looking to offload the Ren (preferably directly back to Akai for a full refund). Then grab a decent interface and pair it with an mpc studio or touch (assuming you wish to stay with the MPC line - might have to change your username if you jump ship )

Thanks for the advice. I just wish akai would take it seriously or at least not pretend like im crazy! I will have to corner dan at the next NAMM. I have a avid/m audio fast track pro and the ren sounds way way better. I would rather not drop $200 on a new interface. It works fine for like 20 min and then gets distortion and pops. I change the settings and change them back and it goes away so this will just have to become my new work flow every half hour or so . Its obviously a driver issue that they refuse to acknowledge.

In terms of getting a touch I would rather just wait for the ren 2 because it will obviously have the touch interface and I don't want to loose the rens classic mpc feel. And I will never jump ship. Been using mpcs since 99 and im not going anywhere!

it seems like all the m-audio interfaces are having similar problems... What a surprise!

DannyBmpc wrote:it seems like all the m-audio interfaces are having similar problems... What a surprise!

Got a link for that?

http://community.m-audio.com/m-audio/to ... _questions

http://community.m-audio.com/m-audio/to ... atic_noise


http://duc.avid.com/showthread.php?t=305120


Its all over the net. If you search m audio interfaces its one of the suggestions that google makes. Seems to be the same exact issue. Popping and distortion when some one buys a new mac. It has to be a driver issue that they are ignoring or cant fix.

DannyBmpc wrote:

konc3pt wrote:What were you using before upgrading to the new Mac ?

a 2006 mac book pro. Had none of these issues. It was slow as **** but at least I could hear my projects

you could create time machine backup off your old mac and restore to that on your new mac and basically clone your old mac on to the new, it works well and is simple to do.

but as tutor said, ren's interface isnt something towaste too much time on

Its a hardware or driver issue which is not going to be helped by using an older version of the software but thanks for the suggestion

DannyBmpc wrote:Its a hardware or driver issue which is not going to be helped by using an older version

if it's driver(software) issue then it would correct

Some questions arise:

1. Did you actually update the firmware to 1.1 or are you still running 1.0?
2. Have you selected your Ren as system audio? If yes, deselect it in System Prefs and use internal audio instead.
3. Is your buffer size adequately chosen?
4. If it is, have you tried using the "bit accurate" interface instead of the "Core Audio" one (or vice versa)?
5. Did you try checking the "Activity Monitor" (in ~/Applications/Utilities) and have the "coreaudiod" app marked red? Shut it down, it should restart by itself.
6. Do you use any other RAM-heavy applications while running MPC Software?
7. If all fails, try using Soundflower (be careful with the version, Yosemite and El Capitan require a specific version not supporting SoundflowerBed) as output interface and monitor it via system sound, if by any means possible... (Not on my actual machine, but it's worth a try!)
8. Try deactivating your wireless. Sounds stupid, but that has helped various users, although it being a typical Windows problem.
9. Try a different screen! Some monitors just don't work with audio. It is strange, but I have experienced that in the last six years numeral times.
10. Does the problem occur with other Macs?
11. 2014 Mac Mini isn't "brand new".

I spoke with the head of customer support at akai. Its a hardware issue with new macs but they haven't been able to fix it. They basically said I have to use a different interface or buy a usb to thunderbolt converter for 80 bucks. Its stupid but at least I got a straight answer.