Downgrading to 2.7

After updating to 2.9, I’ve decided to downgrade to 2.7. The bugs, I just can’t. Spent a couple hours making a beat last night on 2.9, and now if I try to open it it crashes every single time...I like the newer features since 2.8 - the pro ten time stretch, q-link preview, drum synth, etc - but in my case I just don’t know if they’re worth having with all of the other bugs. The track mute bug, midi routing issues, to name a few still haven’t been fixed by akai, let alone even acknowledged. Just frustrating, guys.

I just felt like venting honestly, I know a lot of you feel the same. I think I’ll just stick with 2.7 for now until these bugs get addressed because it’s been a lot of headaches for me and these things are killing my workflow. Sucks that all of the projects I made on 2.8 will be incompatible, but I’ll just back them up for now for when a more reliable update comes out. I just want some stability and some assurance knowing that my beats won’t break after making one. Just ranting...On a positive note, I do like the direction these machines are generally heading, and I’m looking forward to 3.0 and all of the workflow improvements that’ll hopefully come along with it. Just gotta work with what you got!

Honestly you have the right to vent. Its legit!
This bug thing has been going on since 2017 to be honest. This is crazy.

Hey in 2.8 why don't you just export what you did as audio wav tracks. At least you will have all what you did. Then you could bring that into a DAW and finish them. Then go back to 2.7.

Hope everything works out.

Is the track mute bug where you record a sequence in track mute mode, and then when you play it back, the track mutes don’t turn on, or off, as they’re supposed to? I just got my Live 2 last week, and I’ve been trying to finish up a track I did with track mutes, and the mutes just aren’t behaving as they should. Even in List Edit, I check to make sure all events were correct, but it’s still not doing what it should be. If you’re saying 2.9 is even buggier (I’m on 2.7), then I’m not going anywhere near it.

Danoc wrote:Honestly you have the right to vent. Its legit!
This bug thing has been going on since 2017 to be honest. This is crazy.

Hey in 2.8 why don't you just export what you did as audio wav tracks. At least you will have all what you did. Then you could bring that into a DAW and finish them. Then go back to 2.7.

Hope everything works out.

Haha seriously man. I know it’s a small team and staffing and support has probably taken a hit due to COVID, but it would be nice to at least get an acknowledgment from Akai that they’re working or even know about the bugs. Instead, all they do is flash their newest hardware and updates on their social media . I’ll either export them or just keep them on the computer and stay on 2.9 on the MPC software so that I can at least use them there.

So Fletch are you saying you're on 2.7 and having problems? From what lm seeing here bugs are prominent in 2.9.

Are any of you skipping upgrades? I had no problems cause l upgraded every time. I wonder if a person is on 2.4 and tries to upgrade to 2.9 will that cause a problem.

Cause to me 2.5,2.6, 2.7, 2.8 should be in 2.9 where you don't have to upgrade every time.

Fletchnyc wrote:Is the track mute bug where you record a sequence in track mute mode, and then when you play it back, the track mutes don’t turn on, or off, as they’re supposed to? I just got my Live 2 last week, and I’ve been trying to finish up a track I did with track mutes, and the mutes just aren’t behaving as they should. Even in List Edit, I check to make sure all events were correct, but it’s still not doing what it should be. If you’re saying 2.9 is even buggier (I’m on 2.7), then I’m not going anywhere near it.

It’s multiple issues. The one that I’m talking about in particular is not being able to play and hear pads on a track that’s muted. This used to be possible on 2.7. Also, since 2.8, whenever you mute a track it also mutes the midi and not just the audio. So if a track is playing and a midi note is triggered for example while it’s muted, the audio won’t play from the midi note when the track is unmuted because the note effectively was not triggered at all, if that makes sense. Also -and I don’t know if this is related-, sometimes when I go to a new sequence, tracks that have been muted in the previous sequence and continue to be muted in the current sequence still continue to play as if they haven’t been muted at all! It’s like a continuous ghost track playing in the background with no quantifiable source and that has no way of being edited! I don’t know, just really strange behavior.

Could you maybe show us a video of the exact behavior that you’re talking about?

Hold on, we had Covid19 in 2017? Then where the crap was l?
Bugs been prominent SINCE THEN! They just didn't start. Their team was small since then, probably got smaller in 2020 with Covid19. I was one of the first buyers in 2017 of the MPC Live. I got rid of mines not to long ago. I didn't experience bugs like the rest though.

That's why l saud get your audio tracks then roll back. You don't have to stay at 2.9.

RedW6lf wrote:Haha seriously man. I know it’s a small team and staffing and support has probably taken a hit due to COVID, but it would be nice to at least get an acknowledgment from Akai that they’re working or even know about the bugs. Instead, all they do is flash their newest hardware and updates on their social media . I’ll either export them or just keep them on the computer and stay on 2.9 on the MPC software so that I can at least use them there.

According to some user this means you can't fill a 4 bar loop.

I feel you tho.

Danoc wrote:So Fletch are you saying you're on 2.7 and having problems? From what lm seeing here bugs are prominent in 2.9.

Are any of you skipping upgrades? I had no problems cause l upgraded every time. I wonder if a person is on 2.4 and tries to upgrade to 2.9 will that cause a problem.

Cause to me 2.5,2.6, 2.7, 2.8 should be in 2.9 where you don't have to upgrade every time.

I’m on 2.7.1. I just got the Live 2, and this Is what it came with.

RedW6lf wrote:

Fletchnyc wrote:Is the track mute bug where you record a sequence in track mute mode, and then when you play it back, the track mutes don’t turn on, or off, as they’re supposed to? I just got my Live 2 last week, and I’ve been trying to finish up a track I did with track mutes, and the mutes just aren’t behaving as they should. Even in List Edit, I check to make sure all events were correct, but it’s still not doing what it should be. If you’re saying 2.9 is even buggier (I’m on 2.7), then I’m not going anywhere near it.

It’s multiple issues. The one that I’m talking about in particular is not being able to play and hear pads on a track that’s muted. This used to be possible on 2.7. Also, since 2.8, whenever you mute a track it also mutes the midi and not just the audio. So if a track is playing and a midi note is triggered for example while it’s muted, the audio won’t play from the midi note when the track is unmuted because the note effectively was not triggered at all, if that makes sense. Also -and I don’t know if this is related-, sometimes when I go to a new sequence, tracks that have been muted in the previous sequence and continue to be muted in the current sequence still continue to play as if they haven’t been muted at all! It’s like a continuous ghost track playing in the background with no quantifiable source and that has no way of being edited! I don’t know, just really strange behavior.

Could you maybe show us a video of the exact behavior that you’re talking about?

It’s probably not worth a video. It’s just tracks that have been automated to unmute, but then they don’t unmute, and there doesn’t seem to be anyway to fix it. The automation just seems to be hit, or miss.

Danoc wrote:Hold on, we had Covid19 in 2017? Then where the **** was l?
Bugs been prominent SINCE THEN! They just didn't start. Their team was small since then, probably got smaller in 2020 with Covid19. I was one of the first buyers in 2017 of the MPC Live. I got rid of mines not to long ago. I didn't experience bugs like the rest though.

That's why l saud get your audio tracks then roll back. You don't have to stay at 2.9.

RedW6lf wrote:Haha seriously man. I know it’s a small team and staffing and support has probably taken a hit due to COVID, but it would be nice to at least get an acknowledgment from Akai that they’re working or even know about the bugs. Instead, all they do is flash their newest hardware and updates on their social media . I’ll either export them or just keep them on the computer and stay on 2.9 on the MPC software so that I can at least use them there.

Facts. I was with them when the MPC Studio first came out so I’ve seen the software evolve since the beginning. Lots of great changes along with bugs through the times. And the support always has felt lackluster since then. But yes, 2.7 it is. Sometimes you gotta take one step back to move two steps forward...err you get what I mean.

64hz wrote:According to some user this means you can't fill a 4 bar loop.

I feel you tho.

Huh, could you enlighten me on that or point me to the right place for more info good sir?

Ok gotcha.

Fletchnyc wrote:

I’m on 2.7.1. I just got the Live 2, and this Is what it came with.

Fletch,
Can’t say I’ve experienced the same. If i ever have I probably just ended up deleting all the automation and redoing it. But I’m sure you’ve crossed that bridge already.

RedW6lf wrote:It’s multiple issues. The one that I’m talking about in particular is not being able to play and hear pads on a track that’s muted. This used to be possible on 2.7. Also, since 2.8, whenever you mute a track it also mutes the midi and not just the audio.

The funny thing is they actually fixed it. If you mute a track, everything on that track should be muted, even midi. People just got used to having that bug and thought that's how it suppose to work.

RedW6lf wrote: So if a track is playing and a midi note is triggered for example while it’s muted, the audio won’t play from the midi note when the track is unmuted because the note effectively was not triggered at all, if that makes sense.

Maybe the Automation is on?

RedW6lf wrote:Also -and I don’t know if this is related-, sometimes when I go to a new sequence, tracks that have been muted in the previous sequence and continue to be muted in the current sequence still continue to play as if they haven’t been muted at all! It’s like a continuous ghost track playing in the background with no quantifiable source and that has no way of being edited! I don’t know, just really strange behavior.

This is a new are you able to consistently reproduce this?