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.
User avatar
By Jive Talking Robot Mon May 20, 2013 4:57 am
Hi Gang,

Just got the Goldbaby SuperAnalog 808 sample set and it is basically made for round robin sample "cycling" to make each hit give the flavor of a real analog drum machine triggering. So I went to the program edit and tried it out. Just making sure I am not missing something here:

1) You are limited to 4 samples per pad, correct? If so, that's too bad as Huggie set a lot of those samples for 8 layer round robin style cycling. I know work arounds (put x4 samples on one pad and x4 on the other and then switch between them every other bar), but it would be nice to cycle 8 samples on one pad as was intended by the set.

2) I take it the velocity becomes "fixed" once you enter a cycle or random mode? i.e. the sample will now only play at one, fixed volume? It seemed to work that way for me and an ancient forum post confirmed it, but just making sure I didn't miss anything...

Thanks all,
JTR
User avatar
By MPC-Tutor Mon May 20, 2013 7:10 am
Jive Talking Robot wrote:1) You are limited to 4 samples per pad, correct?


Yes, 4 sample layers per pad.

I take it the velocity becomes "fixed" once you enter a cycle or random mode? i.e. the sample will now only play at one, fixed volume?


Not to my knowledge, you should still be able to play the pad at varying velocities unless FULL LEVEL is on.
User avatar
By JAH Mon May 20, 2013 9:16 am
Jive Talking Robot wrote:
1) You are limited to 4 samples per pad, correct? If so, that's too bad as Huggie set a lot of those samples for 8 layer round robin style cycling. I know work arounds (put x4 samples on one pad and x4 on the other and then switch between them every other bar), but it would be nice to cycle 8 samples on one pad as was intended by the set.


Thanks all,
JTR

Why don't you find a sampler that supports 8 layer round robin style cycling and use that as a VST inside of the Ren/Studio?
User avatar
By Jive Talking Robot Mon May 20, 2013 12:44 pm
MPC-Tutor wrote:
Not to my knowledge, you should still be able to play the pad at varying velocities unless FULL LEVEL is on.


Thanks for the reply. FULL LEVEL is not on. In fact, if you set "Layer Play" to VEL then all is good - the sample(s) will respond with velocity; the moment you go to "CYC" or "RAN", then it simply triggers the sample as is regardless of the velocity with which you hit the pad - it clearly cycles through the samples, but they are all played at the same level.

I just found a post back in December where someone else brought up the same issue: viewtopic.php?f=36&t=161801

IMAKEMADBEATS suggested it was designed this way. Is that true or is this a bug? How do hardware MPCs do this?

JAH wrote:Why don't you find a sampler that supports 8 layer round robin style cycling and use that as a VST inside of the Ren/Studio?


I hadn't considered that, but I don't know if that is the workaround for me. My workaround of using two pads gets the job done and I suspect it's less fussy than trying to work with an alternative VST sampler in my, well, Akai VST sampler. For me, the less fiddly the better and the fewer VSTs involved typically means the faster I work.

Thx!
User avatar
By MPC-Tutor Mon May 20, 2013 12:50 pm
All other MPCs will play each layer at the velocity it was hit - I'm on 1.4 beta, so cannot confirm whether this was a problem in 1.31

Thanks for the reply. FULL LEVEL is not on. In fact, if you set "Layer Play" to VEL then all is good - the sample(s) will respond with velocity; the moment you go to "CYC" or "RAN", then it simply triggers the sample as is regardless of the velocity with which you hit the pad - it clearly cycles through the samples, but they are all played at the same level.
User avatar
By JAH Mon May 20, 2013 12:59 pm
In 1.3.1, setting Layer Play to Cycle or Random will trigger samples at Full Level regardless of whether [FULL LEVEL] is activated or not. I am not sure if this is as designed or if this is a bug. But there is a feature request to have this changed.