1.3: Functions not available from the hardware

JAH wrote:These are functions in 1.3 that are not available from the hardware and that you must use a mouse:

1. Manually insert/delete slices markers at a selected location. *The Ren / Studio does allow you to split or join sliced regions but this is significantly different than samplers like Roland where you can use the data dial to control the sample position indicator and insert/delete a slice using function keys.

2. Browser

3. Open/close Plugin instrument GUI

4. Edit Zones

5. Input/Output Audio device

6. Submixer

7. Name/rename

8. Delete Unused Samples

9. Master Volume

10. Program Edit Audio route

Any other functions that can't be accessed via hardware?

1. selecting multiple zones from the hardware (Not sure if that was what you are referring to in #4)

2. delete individual automation events from hardware

3. load a folder of samples from hardware

4. initiate a program save from hardware

5. Track insert bypass (on/off) from hardware

6. Pad/Prog Insert bypass (on/off) from Pad/Prog mix screen on hardware
(I know program insert bypass is available from Prog Edit screen in hardware and software, but it is also available from Program mixer in software and should be available on the corresponding screen in hardware so it is consistent--and in my opinion makes more sense there since I associate inserts with mix channels)

There are probably more that I am not remembering and haven;t written down that I stumble on when I am actually working....not many are deal breakers, but do cause me to stumble in the workflow...

MPC-Tutor wrote:The resolution of the MPC2500 screen is I believe half that of the Ren's, so there's certainly more pixels to play with.

I think the key point is to do as much as it realistically possible - I can accept that some things will never be as good on the hardware screen (e.g. sample editing), but it should be good enough for 95% of editing tasks, at which point if I feel I need that extra accuracy or functionality, I can head over to the computer... and use Adobe Audition like I do already with my hardware MPCs

I think the main restricting thing with the Ren in this aspect is the 16 Q-Links. While I love how they tie the whole integration of the hardware and software together, they take up the whole damn screen on many modes that use them. I really don't understand the decision to not use a screen the size of a 4000/5000 with this design!

I really don't understand the decision to not use a screen the size of a 4000/5000 with this design!

$$$

Set Keyspan (low-/hi key) Rootkey and by hitting a Key on the keyboard.

They current zone editor is just a ridiculous

There's probably a few possibilities why a large screen wasn't used, maybe costs, ergonomics, or simply because they didn't think it would need it given the computer screen. I does seem like a missed opportunity, but maybe one for the Ren XL....

Bring back the track mixer on the LCD screen instead of numbers (man, I miss that)

Once again just look at how much JJOS can fit on the 1k screen.. Efficiently and effectively too

For the price paid for the Ren cost should not be a issue for screen size...

moyphee wrote:On could safely assume that if Akai actually built the thing they know (better than any customer) what's not available from their controller. So other keeping up appearances (with competition looming from multiple angles) this is really pretty pointless.

moyphee wrote:On could safely assume that if Akai actually built the thing they know (better than any customer) what's not available from their controller. So other keeping up appearances (with competition looming from multiple angles) this is really pretty pointless.

Point taken. I didn't really view Jah's post from the perspective of us trying to tell Akai what they already know is not in their software. As you said, we can safely assume they know since they built the damn thing. I viewed it from the perspective of them possibly not being aware of software features some users may want to use from hardware based on our respective workflows and preferences... Since the Ren has been out the forum is loaded with posts from people questioning design decisions that are against the grain of how that person works or how they are used to things working in prior mpcs, etc...and Akai has made some changes in the three 1/2 updates so far to bring the product closer to expectations.

I also think it would be useful info for someone who just picked up the Ren who hasn't dug into the volumes of forum posts yet, to see a quick summary of what they might not be able to do from the hardware, so their expectations (and frustration level) are better managed than some of us early adopters......nothing wrong with community in my opinion.

DaizM wrote:[I didn't really view Jah's post from the perspective of us trying to tell Akai what they already know is not in their software. As you said, we can safely assume they know since they built the damn thing. I viewed it from the perspective of them possibly not being aware of software features some users may want to use from hardware based on our respective workflows and preferences...

At least one person got the purpose of this thread.