Who else isn't having issues with 2.3?

I'm seeing all these complaints about 2.3, but I've yet to experience any of these issues. My MPC X works fine.

No hiccups, no glitches, no new problems of any sorts.

Do I still want PDC, sidechaining, automation lanes, and user presets for the mixer?

Of course...

It works like a charm for me.
No issues, all is going perfectly.
I also notice Grid view now follows the beat, I don't know if its a fix but it was not going good before

A few hiccups for sure but nothing that stops me from using it at all. If I push to hard on the XY it doesn't register, so that's an easy solution, and today I observed if I hold a pad down from a keygroup and push menu, the sound holds as if I was still pushing the pad.

Had my first MPC crash in years last week. No other issues so far. Tested the CPU a lil bit by stacking up multiple tubesynths and a baseline, which the Live handled quite well. Really loving the ability to scroll through the grid and moving around the playhead with the Q-links.

There haven't been many people complaining about 2.3.
People have been complaining about Akai's focus in 2.3:

*Fix Clip Launch (I don't care about this but others do)
*Add Automation lanes to the touch screen (This one is on the top of my list)
*We need sidechaining
*Portamento
*Implement PDC

For as long as 2.0 already exists.. One should think that these things would have been implemented already.
It would have silenced a majority of complaining people (including myself).

But than again.. Akai can never do it right and they can't satisfy everyone..

No problems here yet.

zangetsu01 wrote:There haven't been many people complaining about 2.3.
People have been complaining about Akai's focus:

*Fix Clip Launch (I don't care about this but others do)
*Add Automation lanes to the touch screen (This one is on the top of my list)
*We need sidechaining
*Portamento
*Implement PDC

For as long as 2.0 already exists.. One should think that these things would have been implemented already.
It would have silenced a majority of complaining people (including myself).

But than again.. Akai can never do it right and they can't satisfy everyone..

I still think Akai as of late have been more timely with the updates over the competition. In less then 2 years there's been two major updates from Akai. Native Instruments has been slow as sh*t with addressing the concerns and requests of their users. It's a part of the game, always has been. Some company's are just more concerned and pressed for time with their platforms over others. I like how Akai been moving as of late.. I'm also a long time user of Akai and NI products..

I’ve never had a crash, and still the case with 2.3. Not saying it’s perfect, because for some it isn’t. My only gripe is that 2.3 broke the convert song to sequence function. But there are work arounds.

IM GOOD. My Live been good since l bought it.

No issues here either....

The one bug I have experienced is when converting a song to a sequence. Songs repeatedly bouncing to sequence 1 regardless of the sequence destination I assign. This is integral in my workflow so I hope it gets fixed soon. I’m 100% untethered.

JeriKo Jackson wrote:The one bug I have experienced is when converting a song to a sequence. Songs repeatedly bouncing to sequence 1 regardless of the sequence destination I assign. This is integral in my workflow so I hope it gets fixed soon. I’m 100% untethered.

A workaround was posted in the meantime, did you see that?

JeriKo Jackson wrote:The one bug I have experienced is when converting a song to a sequence. Songs repeatedly bouncing to sequence 1 regardless of the sequence destination I assign. This is integral in my workflow so I hope it gets fixed soon. I’m 100% untethered.

I started a thread about this. It’s definitely a bug. Integral to my workflow too.

Let’s say I have a 10 sequence song, if I choose sequence 11 for the converted sequence, it overwrites sequence one. Instead, select sequence 12 and it won’t overwrite sequence 1. That’s the workaround for now. But you said it doesn’t matter what sequence destination you select? For me, if I choose one sequence past the next available one, it converts it to there.

Hope this gets fixed soon too.

Everything seems to be working well, but the screen on mine slows a bit when sequencing, doesn't seem to effect the sequence, but the screen lags a bit.

-The lag in the touchscreen response in 2.3 is noticeably worse (sometimes it doesn't even work for seconds on certain screens. Mostly noticed it in browsing and new effects GUIs)
-XY automation is broken
-song to sequence bug like others have mentioned.

These are the things I've noticed messing up my work flow. That being said, I like the new standalone plugins (getting some good results with all 3) so it's a toss up for me