uhhhh - 1.5 beta testing started :)

The emulation modes are applied to each sound individually. You can of course set the mode for every sound in a group or project to SP1200 or MPC60, but the effect is more pronounced on some sounds than others so I would recommend only applying it where necessary. They're more CPU intensive than normal Sampler mode.

 

Another reason why I was looking for a way to put a single instance over a Group, like one would a compressor or such over a drum group when mixing, or a single reverb over an aux send/return instead of one on every vox channel for example. It's not really hitting my CPUs hard with multiple instances, but it's still more "economic" to have one instance instead of even 3 on isolated sounds...especially once you start using other things in addition to Maschine (esp. those using it as a plug-in).

 

The reason is that the effects on re-pitching are an integral part of the SP1200 sound, and you can't replicate this with an insert effect implementation. The only option (or at least the most authentic sounding) was to integrate the algorithm into the sampling engine.

Bear in mind it's a per-voice effect, so at least the CPU load will only increase when a sound is actually playing (unlike an insert effect, which is on all the time).

 

Oh, you mean adding another sample to a sound and not layering a whole sound. The add sample map feature using the browser.

Terminology.

 

Even when there's no signal going into the insert effect? Can't that be optimized? IIRC the Cubase effects only work when there's a signal going in.

 

Fore this and many other reasons, Maschine needs a way to edit all sounds in a group at once.

AKA global program/sound edit.

Currently 16x slower to make an edit across a whole group.

 

So is that just for the beta....or are no longer going to get universal binary support from NI?

 

I have an intel and its not decompressing the zip...any suggestions?

 

Of course; I was just pointing out that using a Vintage mode on loads of sounds isn't such a big deal CPU-wise if they're (for example) short-decay drum sounds that aren't all playing at the same time.

Re: optimization as above, in some cases the problem is that the "check if anything is coming in or still going on inside" code could take as much CPU as the "process this chunk of audio" code. Depends on the effect.
---

delete and download again?

 

Once you download it does the icon look like a blank piece of paper? And does it have this extension... (.mpkg) If so, then you need to right click on that file and use the installer.app And It should work fine from that point

Hope it works for you... The update is nice... You are gonna love it!

 

Hello Everyone!

I'm new to the community! I have a question. I've had Maschine for about two weeks now.. I've been waiting along side you guys for this update as well.. I was seriously stoked about the midi cc and pitchbend features like some others.. But how in the world could NI add it and not allow it to be used on the midi out? I'm referring particularly to sustain pedal work... Am I missing something here? Is there something special that needs to be done in the software to activate on the midi out? It works fine on internal stuff. I need it to work on the midi out though! Any help is much appreciated!

 

I'm wondering the same thing, maybe this needs to be sent in as a bug.

 

Early days and not much chance to test yet - but I have to say this was the most painless update so far. All went very smoothly, and so nice to have a working sustain pedal


Thanks NI!

 

Apparently this new update, in addition to dropping PPC support, also requires at least 10.5 to work. I'm somewhat surprised that my failed attempt at installation is the first I've seen of this information, as it seems pretty important. Surely I'm not the only person still running Tiger...

 

this has been official NI policy since last October, but yes there should be a warning,


to clarify:


1.5 will only install on Intel Macs running 10.5.8 and 10.6.x

sowari

 

Thank you NI!

Can someone please tell me if you can automate mutes and solos in Cubase 5?

 

Sucks to be me, but thanks for taking the time to clarify this.

Have fun with the 1.5 update everybody!

 

Hi

Actually, host automation is provided via the Macro Controls. All Macro Controls have host automation IDs. Therefore, if you want to automate a parameter in your host, you have to assign a macro control to that parameter first.

best

James

 

Fair enough

But I still have no midi out

 

Hey guys, this thread is getting a bit unwieldy and we are mixing up topics all over the place. Please continue with your 1.5-related topics in the designated public beta forum, I am closing this thread now!