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 SLADE Thu Sep 13, 2012 12:50 am
What exactly is swing tied to?

Meaning, is my swing adjustable per track, per program, per sequence or per song?

Edit*
Probably an MPC101 question, apologies.
By master-ceo Thu Sep 13, 2012 1:20 am
SLADE wrote:What exactly is swing tied to?

Meaning, is my swing adjustable per track, per program, per sequence or per song?

Edit*
Probably an MPC101 question, apologies.


Note
Last edited by master-ceo on Sun Sep 23, 2012 4:10 am, edited 1 time in total.
By sparq Thu Sep 13, 2012 2:23 am
masada2502 wrote:just got mine today!!! but ive already found an issue.


http://www.youtube.com/watch?v=6V5arV-HNJ0


here's a stupid question... are you sure you are on the proper track that has track data for the velocity to work. maybe you are on an empty track.
By master-ceo Thu Sep 13, 2012 6:34 am
masada2502 wrote:found another bug


Am I the only person with these errors?


Probably not. just keep reporting them.

Tip: Turn your phone to landscape position when recording video. The video will playback full screen instead of portrait for a better picture.
By wakko1999 Sun Sep 16, 2012 9:42 pm
JAH wrote:I got something even better (for my needs) that is in the Ren. Check it out:

1. Load up a 8 bar drum loop

2. Enter Sample Edit Chop Mode

3. The drum loop is already sliced Recycle style via threshold (32 slices)

4. Press [Audition] so you can play the slices from the pads. Doesn't matter if its not perfect.

5. Press Convert Button

6. Set Convert to 'Sliced Samples'

7. Turn 'Crop Samples OFF'

8. Set 'Create New Program On'




I was messing around with this today and using the Create Events option on a 2 bar drum loop inside of a 2 bar sequence and have been getting annoyed at what the REn is doing... I've used similar features on Machine and in Ableton over the years (and I think my MV8000 could do it too, but I haven't used it in awhile so I can't remember right now) and I know what results to expect, but I'm taking a chance here that the Ren does it differently before I call this a bug so here goes...

1. I chop a two bar 80bpm drum loop using threshold detection making sure to have a slice on the transients (for this example lets say I end up with 32 slices to keep it simple..basically banks A and B are full)

2. I click convert and choose Sliced samples, crop off, create prog on, create events on, 2 bars, Do it

3. When I press play and look at the notes in the sequencer, only events for 1 bar are in the sequence and as a result the drumloop playback sounds very choppy.

Its spreading out the events of one bar over the two bars in the sequence. I have to double the bpm to 160 to get it to sound smooth, but there are no events created to trigger the rest of the slices that make up the second bar.

I'm pretty sure an event should have been created for every slice and that they should span the entire two bars of the sequence, but its not happening.

Is this a bug or am I dong something wrong and not understanding how Ren does Create events from Sliced Samples?
User avatar
By IMAKEMADBEATS Sun Sep 16, 2012 11:11 pm
wakko1999 wrote:
JAH wrote:I got something even better (for my needs) that is in the Ren. Check it out:

1. Load up a 8 bar drum loop

2. Enter Sample Edit Chop Mode

3. The drum loop is already sliced Recycle style via threshold (32 slices)

4. Press [Audition] so you can play the slices from the pads. Doesn't matter if its not perfect.

5. Press Convert Button

6. Set Convert to 'Sliced Samples'

7. Turn 'Crop Samples OFF'

8. Set 'Create New Program On'




I was messing around with this today and using the Create Events option on a 2 bar drum loop inside of a 2 bar sequence and have been getting annoyed at what the REn is doing... I've used similar features on Machine and in Ableton over the years (and I think my MV8000 could do it too, but I haven't used it in awhile so I can't remember right now) and I know what results to expect, but I'm taking a chance here that the Ren does it differently before I call this a bug so here goes...

1. I chop a two bar 80bpm drum loop using threshold detection making sure to have a slice on the transients (for this example lets say I end up with 32 slices to keep it simple..basically banks A and B are full)

2. I click convert and choose Sliced samples, crop off, create prog on, create events on, 2 bars, Do it

3. When I press play and look at the notes in the sequencer, only events for 1 bar are in the sequence and as a result the drumloop playback sounds very choppy.

Its spreading out the events of one bar over the two bars in the sequence. I have to double the bpm to 160 to get it to sound smooth, but there are no events created to trigger the rest of the slices that make up the second bar.

I'm pretty sure an event should have been created for every slice and that they should span the entire two bars of the sequence, but its not happening.

Is this a bug or am I dong something wrong and not understanding how Ren does Create events from Sliced Samples?


The same thing happens to me. If i want it (a 2 bar loop chopped up in chop mode) to spread over 2 bars, I just set it to 1 bar. The same for 4 bars, I set it to 2. Not sure whats up, I just figured I was doing something wrong lol, but as long as I put half the amount of bars in, it came out ok.
Last edited by IMAKEMADBEATS on Sun Sep 16, 2012 11:16 pm, edited 1 time in total.
User avatar
By JAH Sun Sep 16, 2012 11:16 pm
wakko1999 wrote:I was messing around with this today and using the Create Events option on a 2 bar drum loop inside of a 2 bar sequence and have been getting annoyed at what the REn is doing... I've used similar features on Machine and in Ableton over the years (and I think my MV8000 could do it too, but I haven't used it in awhile so I can't remember right now) and I know what results to expect, but I'm taking a chance here that the Ren does it differently before I call this a bug so here goes...

1. I chop a two bar 80bpm drum loop using threshold detection making sure to have a slice on the transients (for this example lets say I end up with 32 slices to keep it simple..basically banks A and B are full)

2. I click convert and choose Sliced samples, crop off, create prog on, create events on, 2 bars, Do it

3. When I press play and look at the notes in the sequencer, only events for 1 bar are in the sequence and as a result the drumloop playback sounds very choppy.

Its spreading out the events of one bar over the two bars in the sequence. I have to double the bpm to 160 to get it to sound smooth, but there are no events created to trigger the rest of the slices that make up the second bar.

I'm pretty sure an event should have been created for every slice and that they should span the entire two bars of the sequence, but its not happening.

Is this a bug or am I dong something wrong and not understanding how Ren does Create events from Sliced Samples?

Try this:
1. Load MPC Content '1980 808" program and MIDI file (2 bars, BPM 120)

2. Enter Sample Record Mode; set to RESAMPLE

3. Press F6 [Record] and [Play Start] to resample this sequence

4. Return Main Mode; select new Sequence

5. Enter Same Edit Mode; edit sample so its 2 bars in length

6. Enter Chop Mode; press F5 [Convert]

7. Covert to Sliced Samples, Crop Samples On, Create New Program On, Number of Bars 2

8. Press F5 [Do It]

9. Return to Main Mode and start sequencer.
By wakko1999 Mon Sep 17, 2012 3:29 am
JAH wrote:Try this:
1. Load MPC Content '1980 808" program and MIDI file (2 bars, BPM 120)

2. Enter Sample Record Mode; set to RESAMPLE

3. Press F6 [Record] and [Play Start] to resample this sequence

4. Return Main Mode; select new Sequence

5. Enter Same Edit Mode; edit sample so its 2 bars in length

6. Enter Chop Mode; press F5 [Convert]

7. Covert to Sliced Samples, Crop Samples On, Create New Program On, Number of Bars 2

8. Press F5 [Do It]

9. Return to Main Mode and start sequencer.



This is what I got:

1. Resampled 1980 808 midi seq played @ 120bpm and edited sample to 2 bars
2. Chopped via threshold detection 50/100 and got 20 slices (A1..B4) did not make any adjustments
3. Converted as sliced samples, crop on, create new prog, events @ 2 bars, Do it
4. Pressed play on sequencer and it played back choppy and only created events to trigger the first 9 slices


The first time I did it it look like threshold detection incorrectly detected a transient in the middle of a kick drum, so I turn off Link Slices and manually adjusted that one and converted again. That time I got 22 slices and in the sequence there were only events created to trigger the first 10 slices of the drum loop and it played back choppy. The only way to get it to sound smooth was to double the bpm to 240.

Here are the chops

Image



Here is the Seq- this is from the second time..note only 10 events created
Image
By wakko1999 Mon Sep 17, 2012 3:54 am
IMAKEMADBEATS wrote:The same thing happens to me. If i want it (a 2 bar loop chopped up in chop mode) to spread over 2 bars, I just set it to 1 bar. The same for 4 bars, I set it to 2. Not sure whats up, I just figured I was doing something wrong lol, but as long as I put half the amount of bars in, it came out ok.



Well ain't that a trip? I just saw your message and did the convert again using only 1 bar and it put all the slices in over two bars and it played back smoothly at 120bpm....?? Thanks !!

Soooo, let's see, I put in two bars it only creates events for 1 bar and spreads them over two. I put in 1 bar it creates all events within two bars...I can't wrap my head around that right now, but that seems like that might be buggy or I don't get the logic


Image
User avatar
By JAH Mon Sep 17, 2012 7:04 am
This converting slices to sequence issue is confirmed and reported.

Using my steps above, I had to double the BPM (change to 240) of the resulting sequence and increase the number of Bars from 2 to 4.
By wakko1999 Mon Sep 17, 2012 5:19 pm
JAH wrote:This converting slices to sequence issue is confirmed and reported.

Using my steps above, I had to double the BPM (change to 240) of the resulting sequence and increase the number of Bars from 2 to 4.


Thanks for checking that out and reporting