The crashing is back, pulling my teeth. Need to vent!

Airyck wrote:Unfortunately there is a whole **** load of stuff happening when you copy a sequence so it could be a multitude of bugs inside that whole process. I hope they can dig in and figure it out. The should probably slow the process down intentionally so the computer isn't trying to do it all at once.

Hope this has been addressed in 1.4 for your sake at least.

Thanks!
Yeah. We'll see.
At the moment I can live with working with one sequence only as it really looks like it prevents crashing in my case; I can even save as wildly as I want and no crashing. heh.

It has its pros (only one mixer to worry about) and cons (clumsy / inadequate marker thing).

Yeah I've resorted to the same thing for now for the same reasons but when I have a 200+ bar sequence with 30+ tracks it definitely gets hard to move around quickly to the spots I need. Endless tiny red dots don't really tell me much.

I was thinking about ways to at least mark 8 bar sections, maybe a blank track with mutes recording on and off every 8 bars could help (since the mute makes the whole track red when it's on). You could make different mute patterns for different sections on that track so that you'd know that a red mute with dot dot dash dot dot dash is the breakdown or dot dot dot dot of red could mark the main section if you get what I mean. Might try this later tonight and see if it helps, seems like it should.

Or even better write various phrases with MIDI notes on a blank track that Say in big bold letters (MIDI Notes) things like breakdown, verse 1, intro, outro, chorus. Then you could save those sequences and load them and move them around as needed. All things to try later.

Would be cool if the bar showing bar count could be marked somehow – maybe with colors, text, etc.
Or, alternatively, they could just fix the crashing issues

Fanu wrote:Would be cool if the bar showing bar count could be marked somehow – maybe with colors, text, etc.
Or, alternatively, they could just fix the crashing issues

You could draw a bunch of long MIDI notes (the length of the marker) on all notes then change the velocity to give you different colors, obviously doing this on a blank track used as a sudo "marker track".

I agree it would be great if they just fixed the bugs.

I'm just trying to come up with some ideas we can use now.

That's not a bad workaround, actually – thanks
(and, Akai, if you're reading this, it don't mean you ain't gon' be workin' on it!)

Fanu wrote:

Airyck wrote:Unfortunately there is a whole **** load of stuff happening when you copy a sequence so it could be a multitude of bugs inside that whole process. I hope they can dig in and figure it out. The should probably slow the process down intentionally so the computer isn't trying to do it all at once.

Hope this has been addressed in 1.4 for your sake at least.

Thanks!
Yeah. We'll see.
At the moment I can live with working with one sequence only as it really looks like it prevents crashing in my case; I can even save as wildly as I want and no crashing. heh.

It has its pros (only one mixer to worry about) and cons (clumsy / inadequate marker thing).

Folks get irate when I suggest to use only one sequence. Duplicating sequences especially when it contains numerous plugin instruments and effects can exhaust your CPU. I get it that many here claim it's typical MPC workflow. But typical MPC workflow limits you to no plugin instruments tracks and only 4 send effects so duplicating sequences is no issue for hardware MPCs. Doing the same with the Ren/Studio and you will have no problems.

Start increasing the number of plugins used in the Ren and then start duplicating sequences....you are asking for a crash.

JAH wrote:using the Ren.... you are asking for a crash.

fobedafied wrote:I have never used the Ren/Studio so I don't have anything meaningful to add to the conversation...

fobedafied wrote:

JAH wrote:using the Ren.... you are asking for a crash.

JAH wrote:Start increasing the number of plugins used in the Ren and then start duplicating sequences....you are asking for a crash.

In this day and age, by doing that you're not really asking for a crash.

JAH wrote:Start increasing the number of plugins used IN THE REN [emphasis and capitals added] and then start duplicating sequences....you are asking for a crash.

Oh yeah, true.

I know Akai are young as software developer, but we're talking about some very rudimental features. Name one other DAW that crashes when you duplicate tracks.

Well, Ableton Live used to crash when it was still 32-bit and once you crossed the memory limit. Ever since, it's been rock solid, and even if you do some merging of some huge live sets and songs, it may get slow and sluggish, but it won't crash. And we're talking about memory consumption of several gigs.

In that light, working with one single song and then duplicating one sequence with a few tracks and just a few plugins should definitely NOT cause a crash.

Maybe it's some memory leak thing and 64-bit version will handle it better? Remains to be seen.

Fanu wrote:Well, Ableton Live used to crash when it was still 32-bit and once you crossed the memory limit. Ever since, it's been rock solid, and even if you do some merging of some huge live sets and songs, it may get slow and sluggish, but it won't crash. And we're talking about memory consumption of several gigs.

Ableton also when they realized it was a problem added a warning when you were about to go past 32 bit memory addressing limits which certainly is better than a crash. happy to say I haven't crashed Ableton for a couple years now.

Fanu wrote:

JAH wrote:Start increasing the number of plugins used in the Ren and then start duplicating sequences....you are asking for a crash.

In this day and age, by doing that you're not really asking for a crash.

JAH wrote:Start increasing the number of plugins used IN THE REN [emphasis and capitals added] and then start duplicating sequences....you are asking for a crash.

Oh yeah, true.

I know Akai are young as software developer, but we're talking about some very rudimental features. Name one other DAW that crashes when you duplicate tracks.

Well, Ableton Live used to crash when it was still 32-bit and once you crossed the memory limit. Ever since, it's been rock solid, and even if you do some merging of some huge live sets and songs, it may get slow and sluggish, but it won't crash. And we're talking about memory consumption of several gigs.

In that light, working with one single song and then duplicating one sequence with a few tracks and just a few plugins should definitely NOT cause a crash.

Maybe it's some memory leak thing and 64-bit version will handle it better? Remains to be seen.

I tried several apps such as Pro Tools, Maschine, etc and attempted to use numerous plugins until my system couldn't handle it and got similar results. I was able to crash both Pro Tools and Maschine. We had this conversation in this forum. I even posted a screen shot of Maschine's crash report.

Also there is a big difference between what the Ren does and these other apps. When you copy a Ren sequence, you immediately double the amount of effects being used. You don't work with the other apps in this manner.

Because they aren't designed in such a ridiculous way.

Metatron72 wrote:Because they aren't designed in such a ridiculous way.

Yeah.....Pro Tools and Maschine are not designed to duplicate multiple sequences and then chain them together in a Song Mode....what a ridiculous way to work.

My advice.....avoid products that work ridiculous so you can live a longer healthy, stress free life.

duplicating sequences is great.... but that resulting in duplicating pluggins is stupid... regardless of whether or not that causes stress on the cpu and ram.. copying a sequence should be about creating variations of a pattern... not about creating a duplicate of everything in ram.. how dumb is that. Who cares what pro tools does... but if they did that it would be no less dumb.