Ren Bug or System Limitation?

IMO, the way to solved this is for akai to implent track (plugin) freeze.

LMSW wrote:As far as being able to "copy multipe sequences" that contain numerous samples, numerous instances of CPU heavy plug-ins, and still have access to 128 tracks within the 128 sequences in Ren without utilizing your CPU is a tall order.


Please, let's be fair.

You're right. That is a tall order. That's why we're asking to be able to use the same instance. When you do that, your not tacking on any extra cpu/memory usage.

I don't see what's not fair about that. I could bring their competition up in this matter, but I won't. I'll just say this: Fair, is giving people an option. Like I said before, if they feel this is current implementation is the way to go so be it, but at least give people the option to use the original instance.

and for the record...just to stay on target... this thread was about copying sequences and crashes happening due too many plugins. I just want to remind that my copy sequence crashes still happen, involving no instrument plugins what so ever. It's 1.0, so we gotta get a few bugs worked out, I'm down for that. The information necessary for Akai to figure out what's going on has been sent, and they've received it, through multiple channels, some confirming the problem. I'm just stating this to stay factual. Hiding problems doesn't get them fixed. Fixing these problems could make the Ren the greatest beat machine ever, in my humble opinion.

LMSW wrote:We have to be resonable about what we are asking AKAI to do when making feature recommedations, yes?

As far as being able to "copy multipe sequences" that contain numerous samples, numerous instances of CPU heavy plug-ins, and still have access to 128 tracks within the 128 sequences in Ren without utilizing your CPU is a tall order.

The efficiency in MPC Ren is your ability to use a workflow that is tried and true inside of your existing computer system. AKAI supplies the hardware and software, it is up to the user to provide the system in which it operates.

Please, let's be fair.

MPC's have always worked the way we are suggesting. It holds a program and your sequence tracks simply trigger those programs. You can select the same program for multiple tracks. Duplicating the sequence never created another new program or added to ram because the new sequence just pointed to the same one program. If I am not mistaken, the Renaissance drum and key programs still work that way. It is only the VST instruments that are doing the odd thing and creating more load when copying. All I am asking is to make plug-ins load as one of the 128 available programs.

and for the record...just to stay on target... this thread was about copying sequences and crashes happening due too many plugins. I just want to remind that my copy sequence crashes still happen, involving no instrument plugins what so ever.

Interesting. So there is still a bug in the current OS with copy sequence command without plug-ins? I saw there are some crashes with using undo after sample editing too. Hopefully Akai will get things straight. Until then I will stay on the sidelines.

b-righteous wrote:

LMSW wrote:We have to be resonable about what we are asking AKAI to do when making feature recommedations, yes?

As far as being able to "copy multipe sequences" that contain numerous samples, numerous instances of CPU heavy plug-ins, and still have access to 128 tracks within the 128 sequences in Ren without utilizing your CPU is a tall order.

The efficiency in MPC Ren is your ability to use a workflow that is tried and true inside of your existing computer system. AKAI supplies the hardware and software, it is up to the user to provide the system in which it operates.

Please, let's be fair.

MPC's have always worked the way we are suggesting. It holds a program and your sequence tracks simply trigger those programs. You can select the same program for multiple tracks. Duplicating the sequence never created another new program or added to ram because the new sequence just pointed to the same one program. If I am not mistaken, the Renaissance drum and key programs still work that way. It is only the VST instruments that are doing the odd thing and creating more load when copying. All I am asking is to make plug-ins load as one of the 128 available programs.

+109890

It sounds like some of you are requesting that Ren provides multiple access to your one VST or AU instrument plug-in, is this correct? So you would like Ren to treat your VST instruments like an effect plug-in?

Does this sound like an AKAI Ren issue or a plug-in/system issue?

I am sure the copy sequence issue will be addressed in future updates, but I am not sure if AKAI can perform miracles beyond the limitations of your computer systems. Time will tell. . .

LMSW wrote:I am sure the copy sequence issue will be addressed in future updates

I too am sure eventually this will be solved.

LMSW wrote:but I am not sure if AKAI can perform miracles beyond the limitations of your computer systems. Time will tell. . .

no offense homey, really, but to call asking for this "Akai performing miracles beyond the limitations of your computer systems"....cmon... are you serious?
Again, no offense, but what other software have you used to make beats? I'm genuinely curious.

You'd be surprised how some device(s?), already do this. And I'm only bringing this up not to directly compare, but to show it does not take a miracle to accomplish what we are asking for.

Perhaps the future will bring the desired updates.

Perhaps the future will bring the desired updates.

I didn't answer your question, I have used various software for years.

Yes other software may accomplish what you all suggest, but this is the first time AKAI MPC is implementing this hybrid. So, what I am suggesting is that you all may not receive exactly what you desire from Ren. AKAI did deliver what was promised in this feature--the ability to "copy" sequences.

IMAKEMADBEATS wrote:

LMSW wrote:I am sure the copy sequence issue will be addressed in future updates

I too am sure eventually this will be solved.

I honestly don't believe this will be solved any time soon. Seems like it would take a lot of rewriting code by altering the way the feature works. But I'm no programmer, so don't take my word for it!

DJ Hellfire wrote:I honestly don't believe this will be solved any time soon. Seems like it would take a lot of rewriting code by altering the way the feature works. But I'm no programmer, so don't take my word for it!

Yeah, everything written into the code is a conscious decision on behalf of Akai and the programmers. They should go back to the drawing board with some of the stuff they've implemented.

sounds like you got a weak computer

wait, so.... if you have a pattern (sequence) made and the bass was done with predator.... and you want to copy let's say sequence 3 to sequence 4 so you can make a high hat variation ... it duplicates your predator so now you have 2 predators loaded?

so what predator is the midi data pointing to in sequence 4? and why didn't the copied sequence just copy it as is instead of also "cloning" every virtual instrument as well? (if i'm reading this right) ... that seems ridiculous.


Forget about ram... if you create a tweak to a parameter on the predator in sequence 3, because you want your bass synth to sound a bit different in the song (maybe to fit it around the kick drum once you layered that 808 with it or something) you want that change to happen in every sequence... no? (instead of deleting the cloned vsti and copy/pasting the midi data to the first loaded predator or making the same change in every new predator that was created) ... and it would be a bonus if the software didn't crash just because you cloned a few pluggins... that will get old real fast if that doesn't get resolved because cloning pluggins is IMO... a staple to making music on the computer just like copying sequences is a staple on the mpc...

InspectahEX wrote:sounds like you got a weak computer

sounds more like he got a weak mpc

what does the mpc have to do with the limitations of the computer? not the mpcs fault

InspectahEX wrote:what does the mpc have to do with the limitations of the computer? not the mpcs fault

the ren is a controller. the software runs on the computer. and since the software isn´t able to run properly on older computers it IS the mpcs fault.