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.

Which sample editing functions are most important?

2
1%
5
3%
6
4%
11
8%
20
14%
8
6%
0
N/A
1
1%
19
13%
5
3%
9
6%
9
6%
1
1%
12
8%
10
7%
6
4%
0
N/A
0
N/A
13
9%
4
3%
1
1%
3
2%
By rougenavarre Sun Feb 17, 2013 9:43 pm
Thank you very much, Jah, for this thread. This is all we need. This thread alone would suffice, if they were reasonably, to definitely close the mouths all these thirsty disputants of pathetic conflicts, that infests sometimes this forum. It is an indisputable proof of the work that is made. The only useful one.

I do not have enough time these days to improve the Ren, so i will come back to vote soon. :-D
User avatar
By DJ Hellfire Wed Feb 20, 2013 12:51 am
I'm actually pretty satisfied with the sampler/editor if you count the things they announced for 1.3. Only thing I would really desire, which I would think would be an obvious no brainer, is Q Link zooming and scrolling for the sampler, sequencer as well! If I had my way it would work as follows:

Sample Edit:
1. Q4 turned right zooms in on sample
2. Q4 turned left zooms out on sample
3. Q8 turned right scrolls right on the sample
4. Q8 turned left scrolls left on sample

Sequencer:
1. Shift + Q4 turned right zooms in on piano roll
2. Shift + Q4 turned left zooms out on piano roll
3. Shift + Q8 turned right increases piano roll height
4. Shift + Q8 turned left decreases piano roll height


NDC would be great too!
By Luigi Wed Feb 20, 2013 2:46 am
U should be able to pitchshift/timestrech individual slices non destructively. :nod:

When using midi devices, the patch names shuold be visible on the ren hardware istead of just numbers
User avatar
By JAH Thu Feb 21, 2013 1:38 am
Luigi wrote:When using midi devices, the patch names shuold be visible on the ren hardware istead of just numbers

I agree...been wanting this since the MPC 2500 was released. But this has nothing to do with Sample Editing. :P
User avatar
By DJ Hellfire Thu Feb 21, 2013 10:56 pm
JAH wrote:
Luigi wrote:When using midi devices, the patch names shuold be visible on the ren hardware istead of just numbers

I agree...been wanting this since the MPC 2500 was released. But this has nothing to do with Sample Editing. :P


This would be dope. Would probably boost CPU consumption though!
User avatar
By JAH Fri Feb 22, 2013 12:43 am
DJ Hellfire wrote:
JAH wrote:
Luigi wrote:When using midi devices, the patch names shuold be visible on the ren hardware istead of just numbers

I agree...been wanting this since the MPC 2500 was released. But this has nothing to do with Sample Editing. :P


This would be dope. Would probably boost CPU consumption though!

It shouldn't boost CPU conumption. The names could just be contained in an XML file which the Ren already supports. With 1.3, you can already create custom skins and XML files for plugins. You can change the names of params displayed on the Ren's LCD to include the F keys.

Akai would simply have to expand on this for the new MIDI Programs seen in 1.3. DAWs like Cubase already support this.
User avatar
By DJ Hellfire Fri Feb 22, 2013 12:46 am
JAH wrote:
DJ Hellfire wrote:
This would be dope. Would probably boost CPU consumption though!

It shouldn't boost CPU conumption. The names could just be contained in an XML file which the Ren already supports. With 1.3, you can already create custom skins and XML files for plugins. You can change the names of params displayed on the Ren's LCD to include the F keys.

Akai would simply have to expand on this for the new MIDI Programs seen in 1.3. DAWs like Cubase already support this.



LMAO! I quoted the wrong post. I was talking about this one below:
Luigi wrote:U should be able to pitchshift/timestrech individual slices non destructively. :nod:
User avatar
By JAH Fri Feb 22, 2013 1:24 am
DJ Hellfire wrote:
JAH wrote:
DJ Hellfire wrote:
This would be dope. Would probably boost CPU consumption though!

It shouldn't boost CPU conumption. The names could just be contained in an XML file which the Ren already supports. With 1.3, you can already create custom skins and XML files for plugins. You can change the names of params displayed on the Ren's LCD to include the F keys.

Akai would simply have to expand on this for the new MIDI Programs seen in 1.3. DAWs like Cubase already support this.



LMAO! I quoted the wrong post. I was talking about this one below:
Luigi wrote:U should be able to pitchshift/timestrech individual slices non destructively. :nod:

:lol:
The technology for this appears to already be in place since the Ren uses the Radius engine.
User avatar
By JAH Tue Feb 26, 2013 6:53 am
Some improvements in Software V1.3:
1. Add/remove slices by double clicking (downward arrow & Plus + sign)
2. Split/Join slices via hardware controller
3. Improvements to Slice GUI (slected slice turns gold)
4. Audition Slices On by Default
5. Easier to select slices; slices are not triggered when editing
6. Page and Scroll Mode options
7. Improved lag when editing via Qlinks
8. Edit via data dial when Snap 0 is on
By foge1 Tue Feb 26, 2013 8:21 pm
Using the Ren as 1.3 it is much better yes but there are things the computer could easily do to make things easier.

Yes we could assign a set of keys to zoom in out and now we kind of have that BUT....

Why would I grab the x1000 knob unless I want to make big changes
Why would I grab the x1 knob unless I want to make very fine changes.

Okay given that that information is accepted to be true why not just have an auto zoom function. The knobs are touch sensitive so....

if x1 is touched {set zoom to huge amount}
else if x10 is touched {set zoom to big amount}
else if x100 is touched {set zoom to average amount}
else if x1000 is touched {set zoom right out}


Geoff
User avatar
By Fanu Tue Feb 26, 2013 8:35 pm
foge1 wrote:if x1 is touched {set zoom to huge amount}
else if x10 is touched {set zoom to big amount}
else if x100 is touched {set zoom to average amount}
else if x1000 is touched {set zoom right out}


This might be useful, TBH.
Would love to test that in action.

I'd also love it if auditioning the clip while adjusting the end point didn't revert the view to the start point.
By Danny Tue Feb 26, 2013 9:10 pm
foge1 wrote:
if x1 is touched {set zoom to huge amount}
else if x10 is touched {set zoom to big amount}
else if x100 is touched {set zoom to average amount}
else if x1000 is touched {set zoom right out}


i thought of this yesterday but i just thought whats the point they just don't
understand that you want one hand hittin the pad the other scrolling and zooming
this would work perfectly and make editing a dream. these small pieces of detail
really can have huge impact on work flow. i've given up on the them ever getting the zoom right. once they committed to shift cursor there's no going back i just use the mouse which i was hoping to get away from, it's really a shame. :cry:

but on a positive note the edit page is so much quicker now it's a vast improvement