When Maschine Will Become Multicore ?

All they said is that it's not coming soon.

What is really sad is that we are basically back to the Maschine 1.0 days where NI wasn't giving out any info about updates. When they started the public betas and on the record, I thought things had changed. It seems we are right back where we started.

I don't care if they charge for time stretch or multi-core, I just want some information. I mean there are other companies who tied 64-bit support to major upgrade forcing you to pay, I see it as par for the course. If anyone think Ableton won't make you pay for 64-bit support, then I don't know what to tell you.However, just like Ableton and Apple, there is virtually no information from NI on updates. Is this some sort of trend, I'm not aware of?

 

Sorry for being off topic... but also with being silent, they create a buzz... we are in such a silent phase right now. (but I hate it)

 

its all good and all... when someone asks me what i recommend for them in a groovebox i just point them to ableton or logic and a mpd... or hey even the ren...


see i use to really be cool with maschine and all this. but we are waiting for this to work, and we are waiting for basic things to happen... its not hard to code this stuff. its just a simple string of text... if NI would like to provide me source code for maschine i will write this into it in 1 day...

pull ur ****ing fingers out of ur ass NI... its been 3 ****ing years!

you arnt creating OS's and your products arnt even that detailed... hurry the hell up with these features and for free because when REN hits the place. cya later...

it will work and ppl who use it and buy it will recommend it to ppl...

you will slip away in the midst with ur silly maschine controller... soon to be discontinued like the kore... 5 years from now we will look down and say "ohh remember the maschine,,, was a decent attempt"

hahahaha

 

in fact, modifying an existing single threaded code to a multi thread code means redesigning all the program.

 

it just means editing the source code to use more cores or ram or watever u want it to do... its not hard to do ok.. its not writing the whole software again... dont say something so stupid...

 

Though I could be wrong, my guess is that neither of you (bcoco85 and yaren) are actually in a position to say such things and, basically, you don't know. I know I don't have a clue how easy it would be to do, but I believe it was implemented and they took it out because it caused other problems.

Bottom line is that it could be the easiest thing in the entire world, but NI will put it into operation for Maschine when they're ready to do so and no sooner.

(So shut up. )

 

Keep on mind maschine is the only vst host not multicore on the market !

I understand peoples who don't understand why.

But i imagine to keep the hard-soft good
work and fast workflow is not so easy...

Multiple instances work nice with hardware and 64 bit version is slighty better and gain most of time a little bit precious %cpu.

Thank you NI !
hurry up !

 

The 2 most important facts about the whole thing.
Nothing else has any relevance.

 

i too wish they would hurry up on this... if akai comes out and does it right.. multicore support, timestreach, and all is up to par, i know alotta cats that are gonna be gettin rid of thier maschines.. timestreach aint a issue for me, the issue is baby'n the damn cpu like a ho.....wtf, im tired of it...sooooo tired of it:angry:

 

agree
i prefer things when they are ready

peace

 

The only one saying stupid things is you. Multithreaded/multicore programming is still an issue that programmers have to deal with. Its not just adding more ram or more cores. If that were the case both Microsoft and Apple wouldn't be writing specific libraries and apis to make it easier for programmers to do. I won't even mention that software that do have multicore support don't always handle it correctly. Cubase didn't even handle hyperthreading. Logic still has major issues with with its multicore design. Ableton doesn't even have 64-bit support. Multicore support isn't exactly hard but its not non-trivial. It takes planning ahead and yes you do have to design your software with that type of extensibility in mind. I never get the feeling that NI thinks these things that far ahead, imo. Kore is a good example of what not to do.

If you were really a programmer you wouldn't say such silly things.

 

now let me just ask you this mezzurius.... are you a programmer?
do you have a degree in comp science?

 

"Kore is a good example of what not to do."
It seems maschine too because NI have to make a new build for midi routing and
multi core/threads(?) too.
So this take time....

 

I think it's not really necessary to be so unfriendly to each other... But it's clear it is a big frustration there is no multicore.

I am not a programmer, I only use computers, but I think it is not only important for the user to have multicore, it's also important for NI. We can only wait and hope it will not take too long.

 

I honestly think this needs to be the number priority.

I don't think it's trivial to implement (as NI were trying to implement it from the word go and couldn't get it stable) but it needs to be done.

Having Maschine start to clog up after adding a few VSTs and a couple of ideas to have to start rendering to audio is a real flow killer.

 

thank you! someone actually sees the biger picture instead of all these fanboys getting all upset cause we are not talking maschine up.... its our workflow you FANBOYS. thats all we are crying about, we are tired of waiting for our workflow to be somewhat normal

 

I work doing IT for programmers at my day job if you must know, I've spoken to them at length about programming and multicore programming. Do you have a CS degree? If so where is your version of Maschine that you wrote in a day since you are such an uber programmer.

Can someone tell me why this joker hasn't been banned yet?

 

I would just like to hear about what the hell is going on.....I have a feeling they are holding out till all that akai stuff ships out and is released into the wild. I just wish they would show us something. Kind of seems they stopped competing for a while.

 

only using maschine standalone, also for the mix, is not that bad for the workflow

fanboy... pfff... sucker

 

It's not fan boy, it's trying to understand what you are doing that will max Maschine out so easily.
I have been using Maschine for a year and other than a bad plug in I have never seen a red CPU meter.

I would say it's not your workflow it's your lack of workflow that is the problem.

If it's really not working for you with one core more than likely those same bad methods will increase with multi-core.