Ren Bug or System Limitation?

LMSW wrote:I don't believe this to be a design flaw. Remember how MPC utilizes tracks within a sequence, which allows song structure flexability....Additional instances of the plug-in allows you to be more creative with the same sound on numerous tracks.

LMSW....That's not rain homie that's piss!

This is not about flexibility this about a poor Quality Assurance!

I understand that you needed a solution that worked for varying types of VST's, and you probably could not implement multi-timbral fast enough to make the deadline. But you guys need to stop this app from crashing...That is priority #1!

I don't care what solution is implemented as long as the product DOES NOT CRASH!

QA should have found this with stress testing and sent it back to the developers, the developers job is to prevent the app from crashing. You don't know what the user is running, but if a user is meeting the recommended system requirements your software should be stable under those conditions. In this scenario the only way to do that is to limit what happens when the sequence is copied. Yes reloading the plugins would be a pain in the A$$ too, and yes someone would have called that a bug and requested a feature that maintained the plugins on the copy...this is unfortunately one of the catch 22's in development...but you have some amount of honorable ground to stand on from that position...and you have an application that is stable.

LMSW wrote:Perhaps the future will bring the desired updates.

I believe it will, though I am not sure how they will now because you can't go back and remove features...for some users this is a problem but for others, either because their system can handle it or because they have less resource intensive plugins, their machine does not crash and they are loving the fact that the plugins and sounds are copied with the sequence. Akai will have to have a setting that determines how a VST is handled when a sequence is copied. The responsibility, at that point, will be on the user to setup the software to copy or not copy plugins. In fact another option is, just pop up a message box that asks the user "Do you want to COPY your plugins with the Sequence". That is a partial solution, ultimately you need to integrate an OPTION to use the same plugin instance multi-timbrally (if that's a word).

At the end of the day, if you are using VST instruments for your tracks you need to have a seriously powerful system to use MPC Ren without constant crashes.

I doubt AKAI will be able to change the way their copy sequence duplicates VST instances. Their sequencing, that many people love, is much different than the way Maschine and other software operates.

In closing, if you do not have a seriously powerful system you may be better served by skipping MPC Ren and using some other music production software/hardware.

Don't think the situation is that grim and hopeless. There is no need to remove the current instrument per track feature. The Ren has two mixers, one for tracks and another for programs. The VSTi load as track instruments following that design. They just need to also add VSTi to load as a program. The MPC programs and program mixer and effects act a s a sort of rack that can be accessed by different tracks across multiple sequences. Just add VST instruments there too. The same is already with effects. They can load via program mixer or track mixer. Loading effects via track mixer will have the same issue when copying sequences but you don't have to add effects there.

Jah has recently provided some answers regarding this issue in the bug thread.

As I mentioned, he stated that this is not an AKAI MPC Ren bug exactly. Perhaps updates will make better use of the weaker computer systems that some have.

LMSW wrote:Jah has recently provided some answers regarding this issue in the bug thread.

interesting. well jah seems to be familiar with bugs.

It is misleading to future Ren consumers to report individual system frailty as software bugs.

We are all having different experiences based on our different systems. Why blame the one consistent application?

LMSW wrote:It is misleading to future Ren consumers to report individual system frailty as software bugs.

We are all having different experiences based on our different systems. Why blame the one consistent application?

Yeah those people should be spending $$$$ and figuring out it crashes on their own.....
I mean it's pretty **** up that people would be discussing the success and failures of a device in its deticated forum.....

I for one am glad people are discussing everything so thouroughly, especially something that could likely cause the program to crash and loose your work. I don't know why you have akai's back so hard, next are you gonna say its perfect? everyone that's been posting about this issue is actually helping akai make the program better...

The issue we are discussing with sequence copy has nothing to do with systems. The most high spec system customized for DAW would still be limited with Akai's current VSTi implementation. Sounds more like some are trying to sweep this under the rug imo. As far as the ones saying it crashes with no plug-in instruments loaded, I wonder if it has something to do with using the built in interface (poor drivers?) Of course some crashes can always be system specific but does not sound like the case here.

LMSW wrote:It is misleading to future Ren consumers to report individual system frailty as software bugs.

We are all having different experiences based on our different systems. Why blame the one consistent application?

No, it's only misleading if people have an axe to grind or are reporting user error as a bug. If it's a repeatable bug it's best to get that info out there.

Yes, some configurations will have things happen and others won't, but again it's best for Akai and the customers to report what is happening on different configurations. This is all just the nature of bug reporting and how a customer base and vendor can work together and accelerate fixes.

The one consistent application has to be blamed when a bug is repeatable and user error and system malfunction/faulty components are ruled out.

Tell them and they'll probably fix it, it's not a bad thing

Metatron72 wrote:Tell them and they'll probably fix it, it's not a bad thing

+1

Ok, I'm seriously getting confused here. Is the crashing of systems during "copy Seq" a bug or not?

Might I make a suggestion.....

for all those honestly trying to help Akai get the possible future updates and fix of this solved, why don't you send your repeat bug to Akai or whomever with a Sandra Report.

Pro Tools DUC forum members are familiar with this process. You can't talk about a problem your having with Pro Tools unless you submit to the forum super super detailed specs of the system your using the software/hardware on.

http://download.cnet.com/SiSoftware-San ... 56571.html

"A Sandra provides a robust package of diagnostic tools for testing your system and teasing out its problems--or potential headaches of your computer."

A lot of times when it comes to software for PC or MAC the differences in the computer systems makes the difference in how good the software will or will not run....It might be something as small as the generic video card your computer has that stops the damn thing from loading right......

Hopefully this will help us all.....just a suggestion....

DJ A-Sharp wrote:...whomever with a Sandra Report...

http://download.cnet.com/SiSoftware-San ... 56571.html

"A Sandra provides a robust package of diagnostic tools for testing your system and teasing out its problems--or potential headaches of your computer."

A lot of times when it comes to software for PC or MAC the differences in the computer systems makes the difference in how good the software will or will not run....It might be something as small as the generic video card your computer has that stops the damn thing from loading right......

This is a great idea. Get on this guys and gals!! .... Beta testers ... Akai....

It's almost like homey is either taking this personally, or purposely forgetting portions of whats described as the problem here.

I come back to this post, and he's still going lol. Hey man, it's all good. Like i said, I've communicated with certain people with this company that have confirmed this problem with said session. I don't know what you don't get about that. You're defending something they won't even defend lol.

And how my system was deemed a weaker system, is unknown to me. Who here knows what I'm running this on, and how many computers I have? Who here even knows how many Ren's I have on how many computers?



It's amazing how much people talk about things they know nothing about. You have no idea what I've seen, who I've talked to, how many times this was tried on how many different computers, the specs of said computers, etc. You don't even know how much I know about computers. To say someone is misleading people due to having a weaker system, THAT'S misleading.

I'm on my cranberry juice break. Back to the beats, and getting paid from said beats.

IMAKEMADBEATS wrote::lol:
It's almost like homey is either taking this personally, or purposely forgetting portions of whats described as the problem here.

I come back to this post, and he's still going lol. Hey man, it's all good. Like i said, I've communicated with certain people with this company that have confirmed this problem with said session. I don't know what you don't get about that. You're defending something they won't even defend lol.

And how my system was deemed a weaker system, is unknown to me. Who here knows what I'm running this on, and how many computers I have? Who here even knows how many Ren's I have on how many computers?



It's amazing how much people talk about things they know nothing about. You have no idea what I've seen, who I've talked to, how many times this was tried on how many different computers, the specs of said computers, etc. You don't even know how much I know about computers. To say someone is misleading people due to having a weaker system, THAT'S misleading.

I'm on my cranberry juice break. Back to the beats, and getting paid from said beats.

I never meant my writings to be taken personally. Just wondering if AKAI's Ren software is far advanced beyond our limited computer systems? Could this be the reason that we are having crashes and numerous feature issues?

LMSW wrote: Just wondering if AKAI's Ren software is far advanced beyond our limited computer systems? Could this be the reason that we are having crashes and numerous feature issues?

No, they just f*cked up the implementation.