time to face reality ?

1.3 has made some progress and certainly made using the Ren easier but i looked at some of the requests that people have made which are all genuine and valid but it's only possible a few of these will come to fruition as there is still existing features that have problems.with only a small development team this all seems far too much to cope with and what may seem simple to us to implement could really involve a horrendous amount
of work.maybe we need to consider a paid update at some point so that the we can have our cake and eat it too.i'd rather have paid software update than a new bit of hardware in the future.i know a lot of people are gonna be "noway" but just have a look at what's being requested in reality it's not gonna happen.i would certainly pay for some of the things that have been requested knowing that it would really push the ren to the next level.
what about you guys?

I might return my ren and just go back to my 1000 cause this is getting a lil out of hand.

I would pay for an update, but only when 2.0 is released with following features :

1. an universal midi controller mode like Maschine has with an editor. I have here the ren an must keep my mpd 32 for other things , because the REN is not able to take also his full potential as midicontroller for other software. every crampy controller is able to do.

2. I would like to see the ability to transfer one license to an ilok

3. Automation of every parameter with Q links and easy midi learn function.

4. Faster scrolling with Q links in Sample Edit mode.....when I have a whole track over 5 minutes and more ....it takes a long time....scrolling in Maschine is faster
5. Sample import without interrupting the software.
6. longer sample preview
7. Create new program from Hardware not only for plugin
8. When I assign a parameter ( i.e. cutoff ) to a qlink, we should be able to say fix this parameter with that qlink. The idea behind....when i am in sequencer mode or song mode i dont need to go back to main page and open the plug in mixer mode for controlling the cutoff parameter....look ableton with APC 40...assign parameter to a knob or fader and you can change the parameters without to open the plugin or change the mode

Someone on here pointed out reaper is written by a two person team.

That is a seriously brilliant and complex piece of software.
G

After paying all that money for the Ren, you want to pay for updates?
Let the developers get the software right and make the neccessary adjustments.
The day 1.3 came out, people were making lists of what they wanted in 1.4.......I want this, I want that lol

foge1 wrote:Someone on here pointed out reaper is written by a two person team.

That is a seriously brilliant and complex piece of software.
G

It's a 3 person team and it dropped in 2005, so they've had time to really craft the product. The philosophy between Nukai and Cockos is also night and day. Poles apart.

I find it amazing that three people have created reaper.
They are some seriously talented people.
Someone told me it was the guy who created win amp all those years ago
G

Paid updates? Hell no.

It's too early to be talking about that. It doesn't even work how an Iconic MPC works. Once they get it stable and they are talking about adding major features that isn't already in other software that'll be something to consider paying for.

Sorry, I like the Ren and where it's going for the most part (have some concerns about the slightly growing disconnect between what can be done in software versus the hardware and the lack of some common sense feedback in certain hardware screens), but no my satisfaction with the current state of the product has not reached that level of gratitude to be agreeable to pay for updates...

The reality I'm going to have to face is that I'm never going to be able to use the Ren hardware exclusively (monitor off to do at least 98% of everything and no mouse). Just ain't gonna happen...

Danny wrote:1.3 has made some progress and certainly made using the Ren easier but i looked at some of the requests that people have made which are all genuine and valid but it's only possible a few of these will come to fruition as there is still existing features that have problems.with only a small development team this all seems far too much to cope with and what may seem simple to us to implement could really involve a horrendous amount
of work.maybe we need to consider a paid update at some point so that the we can have our cake and eat it too.i'd rather have paid software update than a new bit of hardware in the future.i know a lot of people are gonna be "noway" but just have a look at what's being requested in reality it's not gonna happen.i would certainly pay for some of the things that have been requested knowing that it would really push the ren to the next level.
what about you guys?

I agree! That's why my feature request list for 1.4 is mostly simple shit! More of workflow enhancements than feature requests!

Not really down for paying for bug fixing though! I'd pay for a software upGRADE, but not a bug update!

I will not pay for a software update.!

peace

Regular free updates, that's what I want. If a product that I spent a lot of money on can not be supported fully. Then it will be the last product I purchase from that company again.

But, so far, I am loving my Ren. :O)

Right now I wouldn't pay for an update...There is less than 6 months since I bought my ren in 1.0 Beta stage...If akai steps up and next year give us 2.0 with a big leap forward I wouldn't have problems to throw some cash in...but right now I feel there is a lot of things that we should have got when it was released that çi think maybe there is more than a year of development til akai catch up with the advertised ren and studio features. So until all advertised features are there and work right I don't think we should pay.
Cheers

I think it's far too early to be talking paid anything. It needs to be completely stable with a reasonable feature set first before they even contemplate anything else (IMO).

MPC-Tutor wrote:I think it's far too early to be talking paid anything. It needs to be completely stable with a reasonable feature set first before they even contemplate anything else (IMO).

This!