racks have a serial pathway. you cant route the output of a synth to a synth, it needs to be an effect unless the synth is made to pass audio through its architecture.

It's because of the signal flow logic in a rack: it is top down, not parallel.
So the upper instrument receives the note information, but outputs the audio signal,
which can not be used in turn as input for a second instrument.

One solution is to use a send channel to a second rack, then the instrument (below the send). In the second rack you can insert a second (parallel) instrument.
Last edited by Eggu on Tue Jun 19, 2012 11:48 am; edited 1 time in total

I see. Dragging and dropping a second rack onto the same track does not work, either, it simply replaces the old one...
Well, I will find some solution...

Oops, someone has already explained how that works, I will try that.

Use the MUX in the Rack and stack all you need inside it.

If you want to stack sounds (i.e. one note triggers two or more instruments), you need to use MUX to send the MIDI input to both. Only the first plugin in a rack gets the MIDI input, the lower ones process the audio output from there. (IIRC)

Indeed in a rack the audio and MIDI signals travel top down.
Cfr the info on this doc page: http://www.mutools.com/mulab/docs/racks.html

If you put a synth in rack slot 1 and that synth does not have event output then rack slot 2 won't receive events.

If you put a MIDI effect in rack slot 1 then you can still put a synth in rack slot 2 as the events will go from slot 1 to slot 2.

With the previous DAW I used it said in the manual that one should set Windows power to maximum as otherwise Windows' switching between various power states would lead to problems on the DAW.
Does this also apply to Mulab? Since I live in a rather hot region my computer tends to get rather loud and hot when I set its performance to maximum permanently

There is no such recommendation in the MuLab docs. I assume this is very system dependent.

It's not important, but I always have to think twice when using the open and save patch buttons. To me it would be more logical if the down arrow meant open patch and the up arrow meant save patch, like in up and downloading

"Down" almost always means "write to disk", "commit", "save" in all software I've used. As in "download".

I can't remember any other programs with arrow symbols for either, so I can't say anything about other software. It just works against my brain so to speak, but I will get used to it eventually

What I also don't like so much are those rectangular digital numbers in the counters, they are a bit more difficult to read than normal roundish numbers, especially when the counter is running faster. But maybe it is also just a matter of getting used to...

I happened to be using one at the time (Free File Sync - green upward sweeping arrow for load; red downward sweeping arrow for save). Reaper is the similar (a drive with an up arrow for open; down arrow into a drive for close). LibreOffice - rather ambiguous folder with a document sitting in it for open, emphatic green down arrow into a disk for save. Visual Studio and WordPad (and, I guess, other MS stuff) - ambiguous folder with a sideways swept arrow (maybe indicating that the folder is opening) for open and a disk or disks for save. So there you have it, complete UI consistency... or not .

I tend to agree about the seven-segment LCD clocks...

Funny, I was just listening to Wham's Nothing looks the same in the light. They used such few and simple sounds back then and yet it sounded good and charming, more so than most modern music, despite all the sophisticated software we have today
How long do you people spend on programming one sound on average?

On average, i'd say about 15 minutes. I like fairly basic, raw kinds of sounds though and look to automation to provide most of the interest.