MuTools

fluffy_little_something · Sat Jun 23, 2012 7:52 pm

Me too, I need about a dozen universal staple sounds. With pads merely changing the cutoff often creates new pads. I suppose that is what you do by automation.

15 mins, that's fast

In Mulab it takes me longer as there are so many modules and parameters, one is always tempted to try something else. And I sometimes lose track of parameters because of all the windows and controls looking all the same somehow. I've been trying to create realistic brass sounds for days now, without much success, it's all too soft, doesn't cut enough

I guess for such sounds I will simply use my other synth plugins, that have 24 db filters.

robenestobenz · Post by **robenestobenz** » Sat Jun 23, 2012 9:21 pm

I should have said though, that is very often using external plugins that I've had for years, know inside out and so can get close to the sounds I want pretty quickly.

AndreasD · Post by **AndreasD** » Sun Jun 24, 2012 9:28 am

try to put 2 filter in series (24dB) with cutoff at 0.8..1. Drag each filters frequency knob to one of the MUX meta params, so that you can control both filters with one knob.
If 24dB doesn't cut it, try 3 filters, or 4 ...

fluffy_little_something · Sun Jun 24, 2012 10:31 am

AndreasD wrote:try to put 2 filter in series (24dB) with cutoff at 0.8..1. Drag each filters frequency knob to one of the MUX meta params, so that you can control both filters with one knob.
If 24dB doesn't cut it, try 3 filters, or 4 ...

I have already tried that of course, but it did not really sound like the way I wanted it to and like the way my external plugin with dedicated 24 db filters sounds. I did some research about that topic and found several articles clearly saying that simply cascading two 12 db filters does not result in a 24 db filter. It has to do with poles and stuff. Dunno...

AndreasD · Post by **AndreasD** » Sun Jun 24, 2012 1:33 pm

What is it that you miss?

If you need resonance in your patch, play with resonance.
First LP Q=0.7, second LP Q=1.5 or so.
Or the other way around, which could sound better.
If you need 'dirt' put a Tanh between the 2 filter and drive it with a higher Q in the first filter.

Mulab's modules are more 'textbook'. Everything special you have to do yourself, which is the fun part for me.

fluffy_little_something · Sun Jun 24, 2012 3:50 pm

I sometimes get error messages like this when Mulab is running for hours, especially when I don't do anything in Mulab for some time:

"Internal thread loop time-out error @ AAE[227]"

fluffy_little_something · Sun Jun 24, 2012 3:59 pm

AndreasD wrote:What is it that you miss?

If you need resonance in your patch, play with resonance.
First LP Q=0.7, second LP Q=1.5 or so.
Or the other way around, which could sound better.
If you need 'dirt' put a Tanh between the 2 filter and drive it with a higher Q in the first filter.

Mulab's modules are more 'textbook'. Everything special you have to do yourself, which is the fun part for me.

Thanks for the tip. Still, it just doesn't sound like metal to me.
Never mind, managed to get some acceptable horns out of Noisemaker meanwhile

Sure, if you are a sound designer, Mulab might be fun for you, but I just want to get the sound programming behind me asap so I can make music

MuTools · Post by **MuTools** » Sun Jun 24, 2012 5:55 pm

fluffy_little_something wrote:I sometimes get error messages like this when Mulab is running for hours, especially when I don't do anything in Mulab for some time:"Internal thread loop time-out error @ AAE[227]"

That's strange. Can you please give as much details as possible about the circumstances when this error pops up.

fluffy_little_something · Sun Jun 24, 2012 8:58 pm

It has happened three times recently, I guess it started when I updated to the latest version. I didn't think much of it, programs do crash sometimes...
Today I had opened a new session, opened one MUX patch and one instance of Noisemaker, nothing else. I had not recorded anything, was just comparing and editing two sounds.
When I got back (after about an hour) Mulab did not respond to my MIDI keyboard anymore and when I tried to close and restart it, I got that error message.

Maybe my copy of Mulab contains a download error. When I downloaded it and tried to open a previous session, I got a number of error messages saying this and that could not be found. I remembered reading about upgrading sessions, so I tried that, same thing, could not find all kinds of drum sounds and stuff, so I clicked skip or ignore all, don't remember what the button was called. Since it was just a nonsense test session I did not really care it was gone.

I will watch it more closely in the future as it will probably happen again.

MuTools · Post by **MuTools** » Mon Jun 25, 2012 7:16 am

fluffy_little_something wrote:It has happened three times recently, I guess it started when I updated to the latest version. I didn't think much of it, programs do crash sometimes...
Today I had opened a new session, opened one MUX patch and one instance of Noisemaker, nothing else. I had not recorded anything, was just comparing and editing two sounds.
When I got back (after about an hour) Mulab did not respond to my MIDI keyboard anymore and when I tried to close and restart it, I got that error message.

What audio device & driver type are you using?

Maybe my copy of Mulab contains a download error. When I downloaded it and tried to open a previous session, I got a number of error messages saying this and that could not be found.

I doubt that is a download error.
Did you update your User settings after upgrading?
Cfr http://www.mutools.com/mulab/docs/installation.html

I will watch it more closely in the future as it will probably happen again.

Ok, thanks.
If it happens again, try to start playing back the composition and see if the position line starts moving. I assume it won't. That would mean that there your audio engine stopped running for some reason in the system.

fluffy_little_something · Mon Jun 25, 2012 11:40 am

By audio device you mean sound card? I use an Asus Xonar DX and the ASIO driver that came with it.

Of course I updated my user settings as described in the docs.

As I said there was no composition to play back as I had not recorded a single note, I was just editing a sound.

MuTools · Post by **MuTools** » Sat Jun 30, 2012 10:22 am

Atm i have no idea why this alert pops up. Is there anyone else seeing this alert?

fluffy_little_something · Wed Jul 04, 2012 1:01 pm

I have used Mulab little these days, but today I was just programming a patch and Mulab crashed again. Exactly the same error message, including the number.
I had just opened Mulab, had been running for 5 minutes or so. I only had one instance of Noisemaker open, nothing else. I wonder if it has to do with that synth, would be a pity

It is by far my favorite synth, I use hardly anything else anymore.

MuTools · Post by **MuTools** » Wed Jul 04, 2012 1:10 pm

Just checking: That alert came when you closed your MuLab session or quitted MuLab, right?

I plugged in NoiseMaker in MuLab, tweaked it a bit and quitted MuLab, no such alert here.

Is that alert also coming when you don't use NoiseMaker at all? Can you please test that?

fluffy_little_something · Wed Jul 04, 2012 1:25 pm

Exactly, when closing Mulab in order to restart it again.

Maybe it is an error in Noisemaker, dunno. With some patches the Mulab CPU bar returns to almost zero after releasing the keys, but with others the bar stays in the middle. Actually, it already rises to the middle when selecting certain patches, before hitting the first key. I don't know if it is possible to send patches, if so, I could send you one of those.

PS: I just checked some presets that come with Noisemaker, there are some in there which also show that behavior, like ARP Danger Dance TUC. I will play around with it (volume at zero of course, I hate factory presets

) for a while to see if Mulab or the plugin stops again...

MuTools

KVR Audio

Just a few remarks from a Mulab newbie...