One Synth Challenge #80: MUX by MuTools (Voting Over, preliminary results in)

[Eauson]

Well, I downloaded Mulab (Mac) after all, and must say... it's quite fun. I guess that means I might be in this one, after all.

I did have one question which I'm not sure I've seen so far in this post (forgive me if this is repetition)... although I've not come across any deficiency with the Fx in MUX/Mulab so far, it is still true that we can use freeware VSTs (not part of MUX), yes?

Thanks!

Yes,
as far as I am aware, you are not limited to MUX alone, as PC users are using MUX in their own DAWS.

[bjporter]

Well, I downloaded Mulab (Mac) after all, and must say... it's quite fun. I guess that means I might be in this one, after all.

I did have one question which I'm not sure I've seen so far in this post (forgive me if this is repetition)... although I've not come across any deficiency with the Fx in MUX/Mulab so far, it is still true that we can use freeware VSTs (not part of MUX), yes?

Thanks!

Yes,
as far as I am aware, you are not limited to MUX alone, as PC users are using MUX in their own DAWS.

Yup, though the MuLab key also works for Windows, so you can run MuLab

[TheBellows]

It seems i get the excact same sound no matter how much velocity, is there a way to make it change the volume by velocity?

[bluerobot]

It seems i get the excact same sound no matter how much velocity, is there a way to make it change the volume by velocity?

You have to drill into the module editor, into the synth module (polysynth if you're using that one), down to the oscillator itself and there you can adjust velocity sensitivity... Seems to be 0% by default.

[TheBellows]

It seems i get the excact same sound no matter how much velocity, is there a way to make it change the volume by velocity?

You have to drill into the module editor, into the synth module (polysynth if you're using that one), down to the oscillator itself and there you can adjust velocity sensitivity... Seems to be 0% by default.

Thanks, i thought i'd looked everywhere.

Honestly i find this synth to be very tedious and ineffective to work with. It's almost like creating synths in Synthedit, only with polished graphics, every time you want to make a new sound.
It's also crashed Renoise and the GUI stops responding sometimes, if you have certain module windows open and click outside it, it disappears and i have to minimize my DAW just to get to the module.
You can't change parameters while holding a key and you have to click outside the module windows just to get to play a note to hear how it sounds like.
I'd rather work with GUIs like ZynAddSubFX to be honest. Much work for very little, i whish it was more like drag and drop instead of the boring process of right clicking, searching through a boring menu, selecting the module you want, connecting the module correctly, opening the module, editing it, closing it and then clicking outside of the menu just to heart how it sounds like.
It sounds pretty good though, even though i haven't been able to create any ground breaking sounds with it.

[bluerobot]

Can I get an official ruling on VSTs that were once free but not now?

Examples:

1. Replika was once free but now must be purchased (I've been told before that this one is not ok).

2. Single Mault SE from Fxpansion... this used to be free and is simply no longer available... is this one ok?

Is this a reasonable distinction? Or do they all have to be free and available today?

[Dee.P.Tree]

It seems i get the excact same sound no matter how much velocity, is there a way to make it change the volume by velocity?

You have to drill into the module editor, into the synth module (polysynth if you're using that one), down to the oscillator itself and there you can adjust velocity sensitivity... Seems to be 0% by default.

Thanks, i thought i'd looked everywhere.

Honestly i find this synth to be very tedious and ineffective to work with. It's almost like creating synths in Synthedit, only with polished graphics, every time you want to make a new sound.

In my opinion, this is great synth, and specially for sound designers and enthusiasts.

But...for me, who is not conversant with this modular concept of synthesis: here comes "MuSynth" - the life saver. Most of the problems faced by me got solved when changed my way from creating something from very basic. I only know VA/Subtractive synthesis.

I think some of tedious-ness of yours will go away with MuSynth. You should try this. I got same suggestion here when I felt confused. I am now playing around this one.

I have took this as a real challenge for myself to get the most out of this opportunity. I may have never tried modular synthesis, if this was not OSC. For me, this is one more learning.

I am suggesting you the same.

Best of luck.

[TheBellows]

Musynth seems allright, i find it difficult to make some nice sounding drums with it, but i worked a bit on the kick patch posted here earlier and made some quite nice ones. Anyway, here's my track:

DAW: Renoise
13 instances of MUX
Internal DSPs: Multitap Delay, Convolver and EQ5
Free VSTs: Vlad. G. Molot/Nova67P/Limiter6, FerricTDS and OTT


https://soundcloud.com/thebellows/4-on- ... itor-osc80

1 play and 21 likes, yeah right, i hate those bots!

[BbluntProductions]

https://soundcloud.com/bblunt-productio ... ed-osc-mux

KVR OSC MUX

Title: Muxed

Synth: MUX (x25)

DAW: Programmed in Reaper v5.0rc14b/x64, mixed and mastered in Ardour 3

All factory presets Tweaked

Plugins:
Calf Equalizer
Calf Compressor
Calf Saturation
Calf Limiter
Calf Filter
Calf Bass Enhancer
Calf Multiband Compressor
Hard Limiter
Transient Mangler
Guitarix Distortion
TAP AutoPanner
Calf Vintage Delay
Calf Reverb

Thanks!

[ontrackp]

FUNKY ISSUES WITH MuLAB on Mac

My strategy was to create one big MUX synth -- my version of a super synth and use that as the starting point for all the sound design. This worked out well -- it's actually really cool - 3 oscillators, (2 standard and 1 multi) each with their own multi-seg envelopes and filters, a couple of additional master filters, a bunch of LFO's to modulate pitch, filter, noise generators with dedicated envelopes and filters, etc... Fantastic how easy it is to build a customized synth and even make a convenient front end. If there was an AU version of this that I could use in Logic I would buy it right away.

I've run into some issues though with sequencing. One is that when I've opened a third party VST (the free version of Eventide Channel Strip) it leaves a big white square on the screen when I close it and it stays in front of everything unless I close and then open MuLab. I haven't tried anything else yet mostly because I don't have many free VST effects but I was going to download some as I don't love the built in compressor. I assigned some shortcuts which have suddenly stopped working. Even closing and opening the program does not bring them back -- this is a pain. I'm going to restart to see if that helps, but it was inconvenient to say the least and it interferes with workflow. Also, the shortcuts will only do one function so it's not possible to set the space bar to jump back to the last point that I played from and start again, which is kind of aggravating.

Anyway, it's been a really fun program to use, but these issues are beginning to stand in the way of being able to focus on getting a piece finished.

Anyone else having these issues?

Thanks.

[psmacmur]

FUNKY ISSUES WITH MuLAB on Mac

My strategy was to create one big MUX synth -- my version of a super synth and use that as the starting point for all the sound design. This worked out well -- it's actually really cool - 3 oscillators, (2 standard and 1 multi) each with their own multi-seg envelopes and filters, a couple of additional master filters, a bunch of LFO's to modulate pitch, filter, noise generators with dedicated envelopes and filters, etc... Fantastic how easy it is to build a customized synth and even make a convenient front end. If there was an AU version of this that I could use in Logic I would buy it right away.

I've run into some issues though with sequencing. One is that when I've opened a third party VST (the free version of Eventide Channel Strip) it leaves a big white square on the screen when I close it and it stays in front of everything unless I close and then open MuLab. I haven't tried anything else yet mostly because I don't have many free VST effects but I was going to download some as I don't love the built in compressor. I assigned some shortcuts which have suddenly stopped working. Even closing and opening the program does not bring them back -- this is a pain. I'm going to restart to see if that helps, but it was inconvenient to say the least and it interferes with workflow. Also, the shortcuts will only do one function so it's not possible to set the space bar to jump back to the last point that I played from and start again, which is kind of aggravating.

Anyway, it's been a really fun program to use, but these issues are beginning to stand in the way of being able to focus on getting a piece finished.

Anyone else having these issues?

Thanks.

There is much trickery with MuLab. Haven't tried 3rd party VSTs, but earlier in this thread, someone pointed to a thread in the MuTools forum that mentioned you can edit a file
MuLab (64 bit)\User\Settings\MainSetup.Txt

add the line
SupportMultiFuncShortcuts=1

Then you can fix the spacebar. Works like a charm.

[psmacmur]

Can I get an official ruling on VSTs that were once free but not now?

Examples:

1. Replika was once free but now must be purchased (I've been told before that this one is not ok).

2. Single Mault SE from Fxpansion... this used to be free and is simply no longer available... is this one ok?

Is this a reasonable distinction? Or do they all have to be free and available today?

Well, consider the spirit of the rule: if there's doubt about some patch in your project, bjporter can request your project file. He'd need to be able to play it back, so would need legit access to all the VSTs you use. Thus, only currently-free and readily-available VSTs are allowed. There might be some leeway on readily available, e.g. if it's in archive.org or something, I suppose, but in previous contests we've had this discussion and Replika and similar temporary giveaways are no-gos.

[z.prime]

Can I get an official ruling on VSTs that were once free but not now?

Examples:

1. Replika was once free but now must be purchased (I've been told before that this one is not ok).

2. Single Mault SE from Fxpansion... this used to be free and is simply no longer available... is this one ok?

Is this a reasonable distinction? Or do they all have to be free and available today?

Well, consider the spirit of the rule: if there's doubt about some patch in your project, bjporter can request your project file. He'd need to be able to play it back, so would need legit access to all the VSTs you use. Thus, only currently-free and readily-available VSTs are allowed. There might be some leeway on readily available, e.g. if it's in archive.org or something, I suppose, but in previous contests we've had this discussion and Replika and similar temporary giveaways are no-gos.

Correct, basically ALL plugins should be *currently* freely available. If it's no longer available, that doesn't qualify as 'available'; no longer free doesn't qualify as 'free'.

[mehum]

But concept is ready in mind. "Gandhi Meets Mandela" (amalgamation of Indian raga based melody and african / tribal rhythm). Let me try, How much I can get close to complete it, only coming days can tell.

This is going to be interesting to hear!
I suppose you're familiar with Ten Ragas to a Disco Beat?

https://www.youtube.com/playlist?list=P ... B4FDC11841

[rghvdberg]

Decided to skip this one.
Other musical projects take to much time and have higher priorities (i.e. I get paid for them ).