Support and discussion for all of Akai’s modern standalone MPCs including the MPC X / X SE, MPC Live 1, 2 & 3, MPC One / One+, MPC Key 37/61.
By Lex Luthor71 Fri Nov 29, 2024 4:20 pm
omygod wrote:It wasn't in my activation last night. Woke up this morning and restarted my MPC and it was there with download.. Downloaded it and it's been working fine in Beta. No issues


Ok, thanks. I can confirm it finally showed and worked going back to MPC 3.4.0.105 BETA.
By marctronixx Fri Nov 29, 2024 5:51 pm
so i signed up a couple days ago but didn't get the notification today. saw the alert on youtube about the launch of this filterbank thingy and signed up again. got email a couple minutes later with code. link into email went to the site to put in vendor code and info so it syncs to your akai profile. it showed up in the list on the mpc(s). click activate and download and boom goes the dynamite!
User avatar
By Juxx Fri Nov 29, 2024 10:08 pm
So is a Use for this... Say you got a Track with crazy subs seems in the top you can drag your subs a bit up into your mids... so you can make sure people with ear pods and playing from phone speakers can get a hit of it?

Any manual released?

Or we can just do the push buttons till it sounds good and print it.
By Masi Sat Nov 30, 2024 9:50 am
Juxx wrote:Any manual released?

The manual will only tell you the plain facts of each buttons ... if your lucky :)

Most manuals of Akai (and Arturia, etc) failed to answer many of my questions what and in which way, say an knob, works. I love "explanations" like that:

The knob Foobar adjusts the foobar: 0%-100%

Nothing about what foobar is and what the range in % means.
By dustyslices Sat Nov 30, 2024 11:33 pm
renegadebliss wrote:So looks like with at least the Qubik plugins that Akai doesn't need to do an OS update to add new plugins

at first glance, it looks like this qubiq thingy runs some sort of JIT compiler as it doesn't seems that plugins are precompiled.
I've missed that one because instead of a full plugin, there was a bunch of loose functions this plugin use such as: 'Spectrum_visualiser' or 'qbqTwoDVisualizer' etc.. (it looks like this will allow them to reuse such functions in other plugins).
On top of it, it looks like everything is "assembled" on the device itself via 'qbq::createQubiqPlugin' which takes all of the nesesary info from the "/content/*.qbqz" file downloaded along with skins from the server.
It contains stuff like: product name, vendor name, vstid(?), synth/FX, number of inputs/outputs, category and memory required. Then it runs 'qbq::getQubiqescriptionFromQbqz' and assemble full dsacription/configuration of the plugin. Once it's done it possibly create a virtual filesystem and run the plugin… but don't take my word for it, I just had a literally 5mins, quick look trying to find out why I missed those qubiq plugins before.

Yeah… I suppose they've finally achieved what they always wanted, meaning that it's not worth the effort to have a peak at it - lot's of obfuscated stuff and too many functions to track just find out their next plugin. I mean, it's still doable and most probably if you do it once, you'll be set for next couple of updates but it's really not worth the effort to deal with that outdated and underpowered platform. What else they possibly put in it ? Spectrum visualiser that barely runs at 10-15 FPS? another filter or another disguised rompler that can be easily replaced by keygroups and several FX ? Me personally gave up on plugins some time ago - more interested in what they can do to the system itself - CV / MIDI tools etc... even without any real processing power, this box potentially could be everything you ever wanted in terms of MIDI sequencing and manipulation - if they only ever wanted it, and judging by the midi bug... if they had an idea of what they're doing :lol:
User avatar
By Jean-Marc Liotier Sun Dec 01, 2024 10:26 pm
dustyslices wrote:even without any real processing power, this box potentially could be everything you ever wanted in terms of MIDI sequencing and manipulation - if they only ever wanted it, and judging by the midi bug... if they had an idea of what they're doing :lol:
As a software guy, this puzzles me: we regularly get new synths and effects, all of which require loads of signal processing wizardry the likes of which I can barely imagine... MIDI stuff is ridiculously simple in comparison - tiny amounts of data, very low throughput, negligible memory usage, integer algorithms that could be used for a programming introduction course and UI has been done and redone by everyone in the business by now. Yes, achieving sharp and stable timing is hard, seriously so... But old MPCs got it right. Yes, they did it with a much simpler system rather they high-concurrency nightmare that is a modern MPC. But nevertheless they have the institutional knowledge of how to get it right.

At this point, I get into conspiration theories where Akai doesn't invest a cent into making current MPC better but overloads it with glutton expansions that prime their sample heavy users into lusting for future hardware... But even that doesn't make sense: better MIDI would make future MPC better too.

Maybe the core team just has its hands full with the rippling impacts of 3.0 on the whole system, so all the new stuff comes from external teams. That would make more sense - I know the pain of marketing-driven development.

But still, Akai, get your priorities in order: this thing is a sequencer before anything else !