Bug reports & end-user support for Akai's MPC Software 'controllers' including the new MPC Studio 2, the MPC Touch, MPC Renaissance & original MPC Studio and MPC StudioB lack.
User avatar
By JAH Tue Jun 04, 2013 9:10 am
Multicore support is industry standard? How about 64 Bit? The fact remains that the Ren/Studio, Maschine, and Pro Tools doesn't currently meet what has been identified here as 'industry standard.' If you purchase these products not knowing their limitations….that is all on you.

Answering some responses directly...It is absurd to imply I have a problem with users wanting to make full use of the processing power of their computers. It is head scratching that anyone would come to this and similar conclusions. I have acknowledged more than once that Multicore support should be implemented at some point. The same goes for several other features. I make as many features requests as anybody. But what I don't do is go on a rant nor do I turn off the products I buy until Akai, NI, JJ, Motu, Avid, etc implement the features I want. I make my feature suggestions and come up with work arounds while I wait for these companies to address some of my needs…which may or may not ever come. If a product doesn't meet my needs, I get rid of it and move on. In the case of Ren & multicore support…me, myself, and I simply use less plugins….or better yet, use powered plugins like UAD platform. This is my work around. I m not suggesting everyone should do the same.

This is along the lines of any other feature discussed. If you don't know now you will know after this post that I will always offer up suggestions and work arounds when discussing any limitation of the Ren or any other product.

I must note that while Akai has continued to advance the Ren/Studio software, I would not buy these product 'expecting' certain features will be implemented.

....the bottom line is that these are all tools...and in the rights hands everything has great possibilities.
User avatar
By SimonInAustralia Tue Jun 04, 2013 9:39 am
Pro Tools is the industry standard due to being the standard DAW used in the industry.

Pro Tools has supported multicores for something like 6 or more years.

It is stupid that Akai didn't support multicores in MPC Software from the start.

Workaround whatever you want, we will discuss what we want.
User avatar
By JAH Tue Jun 04, 2013 9:53 am
And 64 bits is quite a few years old as well.....yet the 'industry standard' Pro Tools doesn't currently support it.

There is nothing new you can say on this topic that you haven't already said. Akai and NI will most likely add multicore support when they deem the time is right and not a moment sooner.
User avatar
By SimonInAustralia Tue Jun 04, 2013 9:59 am
JAH wrote:And 64 bits is quite a few years old as well.....yet the 'industry standard' Pro Tools doesn't currently support it.

Yes, and Pro Tools is not a brand new application, there are reasons inherent to being the industry standard DAW that have probably delayed the move to 64 bit until now.

Akai's MPC Software is a brand new application, and should be multicore, Pro Tools has been for 6+ years.


JAH wrote:There is nothing new you can say on this topic that you haven't already said. Akai and NI will most likely add multicore support when they deem the time is right and not a moment sooner.

There is nothing new you can say either, but thanks for your concern, I will say whatever I like.

Akai not being multicore from the start, and for at least a year, who knows how long, after release, when it is a plugin host, is stupid. Who knows WTF they were thinking.
User avatar
By JAH Tue Jun 04, 2013 10:06 am
Pro Tools is not a new application. But all these other leading DAWs (that have been around as long as Pro Tools) have been 64 bit for quite some time. Why?

The Ren is a new application. And Akai decided to delay 64 Bit (now coming in 1.4)...and likewise delaying multicore support to be determined at a later date. It is what it is....

I know what Akai developers are thinking in some aspects. But can't discuss. Stay tuned.

:popcorn:
User avatar
By SimonInAustralia Tue Jun 04, 2013 10:12 am
JAH wrote:Pro Tools is not a new application. But all these other leading DAWs (that have been around as long as Pro Tools) have been 64 bit for quite some time. Why?

Doesn't really matter why Pro Tools has not moved to 64 bit until now, there are plenty of reasons, I really couldn't be bothered explaining it to you.

Akai MPC Software not being multicore is stupid.


JAH wrote:The Ren is a new application.

The Ren is a MIDI controller, not an application.


JAH wrote:And Akai decided to delay 64 Bit (now coming in 1.4)...and likewise delaying multicore support to be determined at a later date. It is what it is....

It is stupid, that's what it is.
Last edited by SimonInAustralia on Tue Jun 04, 2013 10:23 am, edited 1 time in total.
User avatar
By MPC-Tutor Tue Jun 04, 2013 10:20 am
It is stupid, that's what it is.


I agree, watching you two going at it like it's your own private forum is definitely stupid. You've both made your points. Endlessly. We get it. Stop now.

I'm not going to lock this topic ATM, I'm just going to delete any more posts you two make in it towards each other.
User avatar
By SimonInAustralia Tue Jun 04, 2013 4:22 pm
cpm31 wrote:my english are not very good and i know sh@t about computers.so i'm asking to make it clear, if 1.4 is 64 bit but no multicore how much better (how much more power) the software will run, how much power will use from my 16 giga ram?

Any performance increase from moving from 32 bit to 64 bit really depends on what sort of calculations are being performed, and how the application is programmed.

I have seen examples that suggest you might only get around 10% increase in real world processing power.

Moving from single processor to multi-processors/cores would give much greater increases in performance than moving from 32 bit to 64 bit.

Would be interesting to compare a maxed out 32 bit MPC Project with a 64 bit equivalent, on the same system, to see if it could run many more plugins.
Last edited by SimonInAustralia on Tue Jun 04, 2013 7:14 pm, edited 2 times in total.
By MiniDX Tue Jun 04, 2013 5:07 pm
Multicore will be implemented soon or late. Just relax. Everyone knows it's important.
But things need to get done step by step. Main crashes issues (1.3). 64 bit (1.4). Multicore (1.5?). Akai comes a long way with his mpc software but is on the good way, slowly but surely.

BTW i see 64 bits a bigger priority atm. I use Studio one pro 2.5 64 bits and vst's 64 bits. I don't wanna bother bridging everything (with obvious stability issues) so i'm just waiting 1.4 to be serious with my Ren.
User avatar
By AnSolas Tue Jun 04, 2013 6:40 pm
MiniDX wrote:I use Studio one pro 2.5 64 bits and vst's 64 bits. I don't wanna bother bridging everything (with obvious stability issues) so i'm just waiting 1.4 to be serious with my Ren.


In Studio One you currently cant resize the MPC Window.

Just as side note ;D
User avatar
By AnSolas Tue Jun 04, 2013 6:48 pm
I wonder how long the Sample List gets if you fill up 16 GIG of RAM

And how funny it gets to find specific sounds :D

Or do you guts want the 16 GIG to use with Kontakt ?
In that case you can already use more than 4 GIG with Kontakt's Memory Server no?

Where we are at Kontrakt..., did you guy noticed that you CANT drop samples to Kontakt from the Finder (or AudioFinder) when it is loaded as Plugin inside the Ren?!
User avatar
By Metatron72 Tue Jun 04, 2013 6:55 pm
AnSolas wrote:I wonder how long the Sample List gets if you fill up 16 GIG of RAM


Looking at a folder I have here that is all singles and loops similar to the kind of WAVS you'd have in an MPC session, it looks like 16GB is on average 21,500+ sounds in your list. :shock:
User avatar
By AnSolas Tue Jun 04, 2013 7:01 pm
Metatron72 wrote:
Looking at a folder I have here that is all singles and loops similar to the kind of WAVS you'd have in an MPC session, it looks like 16GB is on average 21,500+ sounds in your list. :shock:


yeah, I already posted a feature request (see in my signature),
to be able to show only not mapped samples in the list.

Code: Select allAssigning Samples to a keygroup is currently anything else than optimal.
The workflow (sample -> create keyzone -> select sample from sample dropdown ?!) is cluttered.
*

Such kind of improvements* are IMO much more important. than being able to load 21,500+ Samples...

Especially if you like to use the MPC as a Sampler and record and map SAMPLEs and not just load them...