Got a wild hair and adapted the excellent Tablatorium ensemble from the NI user library and turned it into a weird glitchbient percussion beat box thingie. Or something like that.

Anyway, peep Glitchatorium from my Reaktor ensembles page:

http://www.spiritcanyonaudio.com/reaktor.php

Requires R5 ...

so, how does it sound then?
any sound clipps?

Downloading now, along with some other tidbits from your site. Thankyouverymuch!

David

www.davidlinn.com

HelIo dburgan, I downloaded all your wicked ens goodies and I´m having a bit of a problem here. I get instant processor overload with 90% of them. Tried everything from setting the sample rate to tweaking my system, nothing works. Someone here mentioned that running them through Cubase solves the problem, but unfortunately I don't have it. Tried running them through Fruity 5 and Audiomulch though, and it didn't help. I could really use some help here. Thanks.

System specs:
P4 2,4 ghz
512 ram
Win 2000 pro
Creative Audigy
kX driver
Reaktor 5

Yeah the ensembles are all pretty much pigs as far as CPU goes. One thing that doesn't make sense is why some computers can't run them and others can. For example, I designed the ensembles on a laptop with specs not too different from yours. But if I run the ensembles on my desktop machine, which is ostensibly more powerful, I get CPU overload. Weird.

Anyway, the one thing to try is to reduce the sample rate drastically, for example down to 22KHz or even less. See if that makes a difference. If not, then unfortunately I don't have any real suggestions.

Any Reaktor gurus who can explain what's going on and maybe offer some helpful hints? I understand why an ensemble can be a cpu hog, but I don't understand why it can behave so radically different on different machines with similar (or better) capabilities.

ooh r5 you say

Disable midi-out on all instruments/macros that are not sending signals to others. You're running into an issue where the automaters embedded are sending out thousands of unfiltered midi signals per cycle, which is what slams down sequencers. You can also try using step-filters in the randomizing macros if you wanna get your hands dirty, but there would be a lot to adjust if I remember correctly. When I made adjustments for this, a few of those older ensembles I made alonside yours saw a reduced CPU consumption by more than 75%.

You can easily observe this behavior by routing your ensemble through 'midi-mon' in a host like eXT.

Interesting ... I'll give it a try mon ... !

But make sure also that you disable midi-out on the host instrument anyways. If you have an auto-ambient instrument running that's driven by several of these automaters, there's really no reason for the tangle of even the filtered midi signals to pass beyond the instrument itself. Keep it internalized and your CPU will be much lower.

ciao,
D

glitchtastic
gimme a day or so