1.7 No Multicore Support? [Troll Mode OFF]

+1 for multicore support. To be fair I dont have any issues with glitching on my laptop with just 8 normal kits loaded. But I do get glitching as soon as I start using any CPU hungry VSTs like uHe ACE or Reaktor Prism.

But by the same token I am very happy to have NI Plugin integration too. Multi core support should make this baby run smooth as silk on my system without needing to bounce synth loops as I do now from time to time.

 

what about using a multicore DAW and several instances of maschine plugin as a workaround? The host will balance the load on to the cores, no?

switching instances can be easy done with the controller?

 

this discussion has been going on for 2 years now. everytime the answer is "soon" - still wondering when it will happen. it definitely is needed very much...

get your act together guys

 

As long as NI does not relegate maschine to KORE2 status I'm fine. I want time stretch and a more solid sampler.

 

Maybe mikro maschine is maschines replacement!

 

Yep.

 

I'm on a MacBook pro i7 2010. I used machine to perform my own Tracks live synced to Traktor pro 2. I use kontakt to load my samples which are not one shots. so i'm fine on the timestretch side.
i always used to switch off hyperthreading and use machine in stand alone. performance was ok and quite stable.
now with Lion os there is no way to switch off hyperthreading anymore! so it is NOT possible for me to run machine stand alone (plug in is even worse) anymore. that means i can not take machine out to gigs anymore and my performance suffers immensly :-( i love machine and everything about it and it becam an essential tool in my production and Performance.

PLEASE give us multicore for standalone before anything else. all mac Lion users are suffering. i want to use my machine again.!
---
i mean it does work, but not without lots of CPU spikes causing sound artifacts and glitches.

 

yust use a PC and kick out your yupi mac things. my maschine runs fantastic on a lenovo thinkpad with 4gb ram and a 2.66ghz i5

 

Hey, thanks for the fantastic advice, NI Forums Poster 'Nord Kietz Rocker'! Thanks to your genuinely prophetic insight I have come to realise that any issues I and others might be having with Maschine are because I run it on a 'yupi mac thing' and not a Lenovo Thinkpad with Intel i5 CPU running at 2.66 ghz! With four (count 'em! FOUR!) gigs of RAM to boot!

I sure hope you make a living offering advice professionally because dang man, you sure are good at dishing it out on the internet!

 

dont take me to serios, i yust whant to yoke a bit.
and try to say that is no need to spend 2000eur for a mac that is not running well.
how often i have to here from mac users " you work on win? nothing runs proper on a win"
i m sorry when i piss on somebodys leg.

 

Let's not turn this into a PC/MAC battlefield...you'd lose out quickly with a PC. I have suffered fo years and will never go back. Will not explain why...Anyway, that's on that subject.

Let's keep it focused on 1.7 and all the extras we had no idea about!

I think, NI is too much marketing (>>Cash) driven...yes there are plenty of new features/products, Maschine Mikro, iMaschine etc...BUT the basic features for a properly functional product are still not sorted. I am not surprised the developers had no time with all the new features and products that came out now...they only work on what the plan is 'from above'.

I can only hope NOW they will start focusing on probably the two most wanted (and OBVIOUS!) features. Multicore & Timestretch

Have fun with 1.7...off installing

 

Why do people pretend they know the inner-workings of NI development process, especially on things like multicore and timestretch that NI have been very communicative about having worked on them for a while and that they'll be implemented when they're actually ready? :S

And sorry but I don't agree that Maschine is something that "basic features for a properly functional product are still not sorted". It might be worth looking at how you're approaching it and expecting it to behave instead.

 

i agree 110%

 

I agree. Before 1.6 there was no real reason for multicore support. Everything ran fine on a single core. With plugin support its definitely more apparent that its needed but doesn't make machine useless. I've been happily using machine without issues since it was first released and it really changed my whole outlook on how to approach music. My output has risen substantially because I can get from idea to song in far less time than when I just used a DAW.

I do have to say that mutlicore support should be pretty straight forward to implement. All you are really doing is load balancing, but who knows how Maschine was programmed so there maybe issues threading jobs for some reason.

 

Thats a good way to win an argument; Say stop talking about this, but before we do let me have the last word....

 

I don't pretend I know... just looking at the facts based on 1.7 update. It's all about Komplete integration, which is fine. I personally use all my plugins in DAW so for me it's not a great deal. Anyhow, It's a great update in that respect and I am sure many of us do love it. But this should have come later -imho. If you read on the forum - not just me- but many are suffering because of the lack of multicore support.

I am approaching my workflow and Maschine to behave like any other plugin I am using. Omnishpere, Trilian etc are all very CPU hungry beasts, yet I have never ever had to juggle around (even with 4-5 instances) to achieve what I want to do. If Maschine has 8 kits, then I would expect to be able to load all 8 kits within the DAW and use it without any problem within my set-up. As it stands I can only go up to 5 kits maybe without CPU spikes. It kills me in a live situation.

I know it's difficult to please everyone, because we all use it differently. I think it's fair to say though, that many of use would like to use it to its full potential in DAW - where multicore is an issue. And that's a fact. (on that not it's equally bad that Live is still 32bit)

I am not argumental as some may suggest here, simply describing why multicore would be important - in my particular set-up. I am sure it'll come...at some point.
---

I am happy to get into this, but this is not the right place for it - hence I am happy for you to have the last word.

 

Time Stretch! & Multi Kore Support! Pleeeeease!

 

Are you guys talking about multi core support in standalone mode only?

I ask because Sonar supports 8 cores, and when I hook up Maschine and load it into Sonar as a 64 bit vst plugin tomorrow I expect that Sonar will make use of all 8 of those cores while Maschine is running. And since I plan to never use Maschine in standalone mode, this thread doesn't really need to be followed by me...do I have that right?

 

If you use multiple instances of Maschine across multiple tracks then Sonar will balance the tracks across multiple cores on a track by track basis just like all DAW's. A single instance of Maschine or most any other plug-in will only make use of a single core in your DAW. It is when you use multiple tracks that the load is spread out among cores. If you are using Maschine in a DAW then multicore support in Maschine may not make a difference in your workflow.

There are a couple of instruments out there like Kontakt that have a multiprocessing option for the plug-in version too. You would disable the multiprocessor option in your DAW to make effective use of this. This is only useful if the bulk of your CPU load will be coming from that single Kontakt instance.

 

A couple of thoughts:

@using in a daw: I haven't used maschine in sonar but in reaper there seems to be an issue where using more than one instance confuses any instance of maschine and thus there is no input for any. One other thing that really bugs me about the "use the daw" mantra...maybe I want to work within MASCHINE with the swing/tempo/etc?

@multicore only important for "vst's" : Maybe, but since it IS 1.6 (1.7 now) and DOES support vst's, it is certainly important. 1.6 has been available since day one for me so I'd imagine a few people would just assume that it was MP aware. In a perfect world, they did some homework and found out first (me!) but still it's really important.

Anyways, these are not to pick or nit at points that have been made.....just want to *subliminal message DO IT NOW NI......DO IT NOW NI subliminal message* share my thoughts :lol: