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 NavNek Sat Feb 08, 2014 10:15 pm
Thanks for all the help guys.

Trying to figure things out. A bit of a change up coming from the 2500.

Still can't get the following right:
- I have one program (mono) with different samples. I made a loop in a sequence on track 5. Next I want to make another loop in the same sequence from that program, so I mute track 5 I recorded with that program. Next I want to use track 6 with that same program to build another loop. The problem: the (muted) samples i played in track 5 keep cutting off the samples (of the same program) i'll play on track 6. Im baffled...Does this mean I have to create a new program for every track I want to make or make every sample NOTE ON and set the programs on poly?
By NavNek Sun Feb 09, 2014 12:51 pm
Is that only way to work around? That's serious a big flaw...
So I can't work with one shot samples, unless they're precisely chopped. And if I want to cut them off early, i need to make them NOTE ON... bummed out.
User avatar
By SimonInAustralia Sun Feb 09, 2014 2:22 pm
NavNek wrote:Is that only way to work around? That's serious a big flaw...
So I can't work with one shot samples, unless they're precisely chopped. And if I want to cut them off early, i need to make them NOTE ON... bummed out.

Can't use Mute Groups?
By NavNek Sun Feb 09, 2014 2:23 pm
Yes I understand. But I don't know if I have explained it the right way, cause im in the assumption that there must be a solution, since this was no problem on the mpc2500. The problem i have, i have never had on the mpc2500.

On the MPC2500
When I use the same program on a different tracks and the program is set to mono, samples cut eachother off. (of course) But when I mute a track built with program1 and then build another track with that same mono program1, the muted events won't cut off my new built track with the same program1.

On the MPC Renaissance
muted events still cut off unmuted events in the same program. I'm very used to this workflow: making different loops with the same mono program and switch between them by muting the single tracks, but I can't apply this flow on the renaissance
User avatar
By SimonInAustralia Sun Feb 09, 2014 2:37 pm
So, events on a muted track are cutting off one-shot/mono sounds, in the same program, on a different and unmuted track?

Sounds like it needs a request for a bug fix to be submitted.
User avatar
By SimonInAustralia Sun Feb 09, 2014 8:48 pm
Yes, I was debating with myself whether to refer to it as a bug, or not.

I think it actually is a bug.

But anyway, it needs a bug report, or change request, to be submitted for it to be made to operate the way it should.
User avatar
By Rokgod Sun Feb 09, 2014 10:52 pm
dude expects the Ren to work exactly like a 2500, trying pressing shift+note repeat in reverse order, it won't lock in place on the Ren like it did the 2500, there's another example for you, doesn't make it a bug bc it was different on the 2500. just because thats the way the mpc software is programmed, its different from the 2500, not a bug, and yes there are many logical features from past mpc that have been absent since launch of the mpc ren/studio.
User avatar
By SimonInAustralia Sun Feb 09, 2014 11:00 pm
I suppose it depends on what you use as a definition for 'bug'.

The wiki definition...
A software bug is an error, flaw, failure, or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways. Most bugs arise from mistakes and errors made by people in either a program's source code or its design, or in frameworks and operating systems used by such programs, and a few are caused by compilers producing incorrect code.

I would say this problem is a flaw, resulting from an error in design, causing an unexpected result, and for it to behave in an unintended way.

That is assuming they didn't necessarily mean for it to behave the way it is now, and that they didn't design it to work correctly, the way it logically should.

I see what you mean though, when I think of bug, I probably normally associate it with an error message or program crash, for example.

Just semantics really, whether you refer to it as a bug or something else, it needs to be sorted so that it works the way it should.
User avatar
By ThobRom Tue Feb 11, 2014 12:05 am
NavNek wrote:... thus, ...

:shock:
:worthy:

I'm afraid I'm gonna have to steal that.
Call it a homage, a salutation, a tribute to greatness.
(kanye west is so fired!)

Thats a pretty cool idea.
There needs to be more thinking outside of the box like that.

And by outside of the box I dont just mean rap with skater-metal or backup singers and a guitar.
I mean whole new concepts towards samples, sounds and arranging them.


Although there is a precedent for this concept.
The shimmery chorus vocals from "I'm not in love" by 10cc were done by recording each note to a different track, and then punching them in and out on the mixing board to play them like keys.
They describe it on the wiki article for that song,
check it out.
User avatar
By 83dude Tue Feb 11, 2014 7:13 am
SimonInAustralia wrote:Can't use Mute Groups?


Or did you try using pad mutes (see bottom left of software)?

I think this would be a nice feature for the prefs as tickbox, but actually I don't mind that much. Apparently the output's muted, not the MIDI notes. Furthermore, I don't think it's a big deal duplicating a program since it only uses up 200 kB or so and doesn't need the samples to be duplicated, too.
Last edited by 83dude on Thu Feb 13, 2014 9:25 am, edited 1 time in total.