1.6 is here!!

SimonInAustralia wrote:

pspsounds wrote:I thought only the 4000 had 960 PPQN.

MPC4000 and 5000.

Yes, the easy way to identify the Ren as being 960 PPQ is to look at the Follow Now position. It is 1:1:000. 96PPQ would be 1:1:00.

Fanu wrote:

Obtainius wrote:Is there anyone who have tryed it with mavericks?

10.7 or later...

Yup. Works well.

Thank you, I will try again tomorrow

THIS SHOULD NOT STILL BE HAPPENING

bearhead wrote:

THIS SHOULD NOT STILL BE HAPPENING

This isn't a bug! This happens because you have nothing assigned to folder 3. If you assign a folder to slot 3 that is different than 2, this will not happen! But you have 2 and 3 set to the same (or default path) so both remain lit.

DJ Hellfire wrote:

bearhead wrote:

THIS SHOULD NOT STILL BE HAPPENING

This isn't a bug! This happens because you have nothing assigned to folder 3.

How would I fix this?

Also, THIS SHOULD NOT STILL BE HAPPENING!

sampler problem still exists

bearhead wrote:

DJ Hellfire wrote:

bearhead wrote:

THIS SHOULD NOT STILL BE HAPPENING

This isn't a bug! This happens because you have nothing assigned to folder 3.

How would I fix this?

Also, THIS SHOULD NOT STILL BE HAPPENING!

sampler problem still exists

Just edited my post with more info!

The sample problem is still a known issue. It mostly happens for me when using a 3rd party interface or Soundflower.

DJ Hellfire wrote:

bearhead wrote:Also, THIS SHOULD NOT STILL BE HAPPENING!

sampler problem still exists

Just edited my post with more info!

The sample problem is still a known issue. It mostly happens for me when using a 3rd party interface or Soundflower.

Yeah, I'm running Soundflower as the output of my computer, to the input of the MPC to sample from Spotify.

This also happens when I run audio through it via the audio inputs.

bearhead wrote:
Yeah, I'm running Soundflower as the output of my computer, to the input of the MPC to sample from Spotify.

Ah, so I'm not the only sampling tons of audio from Spotify!

bearhead wrote:

DJ Hellfire wrote:

bearhead wrote:Also, THIS SHOULD NOT STILL BE HAPPENING!

sampler problem still exists

Just edited my post with more info!

The sample problem is still a known issue. It mostly happens for me when using a 3rd party interface or Soundflower.

Yeah, I'm running Soundflower as the output of my computer, to the input of the MPC to sample from Spotify.

This also happens when I run audio through it via the audio inputs.

Yeah, Soundflower is a problem dude! Always has been for me, with the MPC software! Basically, sampling through anything other than the Ren has caused me grief, even my 003.

How do you fix that folder issue btw?

Still can't seem to figure it out.

Have you tried setting all the shortcut folders to specific/different locations on your computer?

bearhead wrote:How do you fix that folder issue btw?

Still can't seem to figure it out.

Simply assign a different location to each button. The reason multiple buttons are lit is that those ones are all assigned to the same location.

I agree, it seems odd that they chose to allow that, I don't see the benefit of the software basically saying 'Look, I know you pressed Folder 2, but while we're at it I'm going to let you know that Folder 3 is set to the same path.'

Obtainius wrote:Is there anyone who have tryed it with mavericks?

10.7 or later...

It apparently doesn't do well with Mavericks (10.9 and later) so far, but AKAI are supposedly working on that issue.

bearhead wrote:Yeah, I'm running Soundflower as the output of my computer, to the input of the MPC to sample from Spotify.

This also happens when I run audio through it via the audio inputs.

Have you tried updating Soundflower (Soundflowerbed 1.6.6)? I was quite astonished when I realized they had replaced 16ch with 64ch silently in an update in between.

Another tip: Try setting your buffer size for soundflower (via Soundflowerbed => Soundflower Xch => Buffer size => ?) to the same amount you use in your MPC Software.

Are you running in 32 bit or 64 bit? I had such sample dropouts a while ago while I used it in 64 bit, strangely enough this never ever happened in 32 bit mode. I regularely check for a proper bit depth value in the preferences just to make sure. You'll lose samples if you don't have any bit depth shown in your prefs.

I haven't had any problems at all sampling through Soundflower so far. Sometimes when my RAM is full Soundflower starts to crackle and stuff, but performing a RAM purge via Terminal plus deselecting and reselecting Soundflower as the MPC's input device always does the trick then.

Hope that helped.

i really prefer bugfixing and improving instead of featuritis...remenber it s never gonna be a fully...i mix it in reaper or cubase. export tracks as audiostems...


new features? they are welcome but first bugfixing and improving!!!

83dude wrote:

bearhead wrote:Yeah, I'm running Soundflower as the output of my computer, to the input of the MPC to sample from Spotify.

This also happens when I run audio through it via the audio inputs.

Have you tried updating Soundflower (Soundflowerbed 1.6.6)? I was quite astonished when I realized they had replaced 16ch with 64ch silently in an update in between.

Another tip: Try setting your buffer size for soundflower (via Soundflowerbed => Soundflower Xch => Buffer size => ?) to the same amount you use in your MPC Software.

Are you running in 32 bit or 64 bit? I had such sample dropouts a while ago while I used it in 64 bit, strangely enough this never ever happened in 32 bit mode. I regularely check for a proper bit depth value in the preferences just to make sure. You'll lose samples if you don't have any bit depth shown in your prefs.

I haven't had any problems at all sampling through Soundflower so far. Sometimes when my RAM is full Soundflower starts to crackle and stuff, but performing a RAM purge via Terminal plus deselecting and reselecting Soundflower as the MPC's input device always does the trick then.

Hope that helped.

Thanks man, I'm gonna go have a look at that now. I haven't updated Soundflower in a while. I'm running 64 bit (OSX Mavericks) btw.

What does a RAM purge accomplish?