taron's little sessions

[janamdo]

LOL, haha, maybe I should really dive into the docs, because I just accidentally found out that you can double click on the little import nipples on the modules to adjust min/max for each device feed. Nice surprise!

Ehh nipples you said .. where?
you mean in the modular area
Well in the docs is not all functionality of MUlab written unfortanely
So this subject about nipples does maybe not exist ?
Please explain more in detail what you mean

[Taron]

Ehehe, thought it was a fun word to use. The connection points (little triangles (dark blue, light blue and was it red?!)) on each module, or rather the modules that allow event or parameter inputs.

Hook an LFO into an Oscillator's pitch input. Now double click on the input triangle of the Oscillator module, where you've just connected the LFO to. It'll bring up a window that allows you to manipulate the min/max values of that input. If you connect another LFO or an ADSR envelope to that very same input you then get a little menu instead, where you can choose which module's output you want to adjust (min/max).
I think that's pretty nifty! Good stuff, even if neatly hidden, haha.

[MuTools]

LOL, haha, maybe I should really dive into the docs, because I just accidentally found out that you can double click on the little import nipples on the modules to adjust min/max for each device feed. Nice surprise!

Ehh nipples you said .. where?
you mean in the modular area
Well in the docs is not all functionality of MUlab written unfortanely
So this subject about nipples does maybe not exist ?
Please explain more in detail what you mean

http://www.mutools.com/mulab/docs/modular-area.html

[janamdo]

[/quote]


http://www.mutools.com/mulab/docs/modular-area.html[/quote]
Yes there is a lot of information to find there
OSC=>Filter=>AMP = sound

Now i know that you can build a whole new sound in the Modular area
OSC->Filter->AMP = sound ..now i am interesting what can i do more with it in songcomposing ?

A pitch modulation automation of a sound or volume automation to start with..but there must be more?

[Taron]

Yup, that's where the good stuff starts!
It's also not that hard to understand the system, but every synth has its limitations and specialities. Jo's AIPS idea is interesting, but as in so many places I'm missing a bit of visual feedback to get a solid feel on things. Maybe it's just me, but my process of understanding is tremendously boosted by visuals.
MU.LAB seems to be vary careful when it comes to accessing and connecting elements, trying to avoid that users make "mistakes". That's a very good thing on one hand, but a little limiting on the other.
I could already imagine a nice amount of new modules appearing over time.

I wished there was a MIDI module (MIDI splitter?) which would output Velocity and Key (Note), as well as new input accesses to the ADSR module for each important parameter, especially Attack time, Decay time and potentially their levels, but the times would already help to design better performance synths.

But, yeah, it makes a massive difference to be able to create your own sounds, as there's not only a tremendous inspiration factor, but also a far tighter connection to what you want to achieve in your music.

Thanks for the link, Jo. Just to make sure, I wasn't complaining about the surprise, but rather entertained. By now I'm perfectly sure you know how people skim through docs, right, hahaha. Luckily for the most part I only need a light introduction to happily start fiddling about.

I'm having a blast with MU.LAB UL, that's for sure!
(DID I MENTION how much I love the Module Area for the main rack? Awesome! Just makes me feel even more just how much potential your tool has. A simple thing you say? Na ah, that's the stuff that leads to great things!)

[pljones]

OSC=>Filter=>AMP = sound

There are multiple levels you can use the MPA at.

You can use it at a higher level than the racks. If you switch to MPA view, you'll see how the racks are wired up by default. (This is also the hint as to how to get access to stuff in the MPA -- each plugin in the MPA is a target, and a rack is just another plugin in the MPA...)

So the first thing is - it's a way of organising things that maybe you can't do with the "strict" routing of the racks. You can route the output of one rack to many places, more visibly route multiple things into a rack, etc.

The next thing is, if you don't want the racks at all, it's just another - again, more flexible - way of managing your synths and effects. You're not creating new synths or effects, just using the existing ones (like you could in the rack) in new ways.

Then a point of contention... The MUX is a plugin that's much like the MPA. It works a little differently (not much but enough I get confused! -edit-case in point: MUX is for effects; MuSynth is the modular area for synths, as it has voice awareness-/edit-) and is really for creating new plugins - binding together the low level components into a usable tool. You'd then use the MUX patch, either in a rack or in the MPA.

Personally, I wouldn't use the MPA to directly construct "OSC=>Filter=>AMP" arrangements - these would go in a MUX, so they could be re-used.

I'd consider the MPA at the level:
(trigger)=>Multiple Sound Sources=>Complex effects routing = sound
but it's non-linear, of course, as there could be MIDI VST effects prior to the each sound source and possibly cross-modulating other sound sources and effects all over the place. (So long as there's no feedback.)

[MuTools]

MU.LAB seems to be vary careful when it comes to accessing and connecting elements, trying to avoid that users make "mistakes". That's a very good thing on one hand, but a little limiting on the other.

Can you please give an example about this, i.e. where the carefulness is limiting.

[Taron]

Tahahaha, feedback, to name the most risky one of them all!
It's more of a MUX thing, but to make a delay, put it through a filter then one stream into the audio out and another into an amplifier that feeds back into the delay. If that works, it's very pretty!

But no, I meant things such as using audio as signal to put into modulations. It can be used to create very exciting effects. The mod.mapper could be used to modify any single incoming signal, really, which invites even more interesting possibilities, if audio signals could be remapped, then. But all these are wilder examples, I know. As I said in the quote, it's very good on one hand and a little limiting on the other. In other words, it's not the biggest drama, but a MS-20 giggles about those worries.

The other thing is the Midi Event, as it's a combination of note on/off, velocity and key, it is a limitation in itself, since you can't pick out any one of the signals to freely do as you please. One of my main thing is to tie velocity to various other aspects of the sound, particularely ADSR related dynamics. The same goes for key tracking. It's a powerful input to many parameters. Being able to use those things flexibly can make all the difference between a nice little synth and an awesome synth-phenomenon.

As long as the audio signal during the module process remains in percentage before it gets multiplied to the bit depth, it can be one heck of a fantastic source, really. Yielding those things properly you can produce extremely realistic sounds aside from the infinite wackiness you can achieve that way, haha.

Naturally I have some ideas for your Oscillator, too, but I already fear... all this begins to make you twitch a bit here and there, hahaha. Step by step, as you've said. And I'm fully happy to be there for you every step of the way to test, make examples, eventually help you create some presets, of course and we get those of us here, who'd like to, into some really nifty synth programming skills! ...it could become a fearsom crowd with an awesome tool to show for. Fun stuff.
As far as I'm concerned, there's plenty of time. Especially if the will is there.

[pljones]

I would like to see an audio to control plugin... (That way any special care and attention that needs to be applied can be given a home; maybe include a frequency divider, maybe even a limiter/compressor...) And a MIDI to control plugin along the lines Taron mentions (separate control outputs for channel (0% to 100% for 1 to 16), MIDI note number (0% to 100% for 0 to 127), MIDI note gate (0% when off, 100% during note duration), MIDI note velocity (0% to 100% for 0 - or 1? - to 127).

[janamdo]

OSC=>Filter=>AMP = sound

There are multiple levels you can use the MPA at.

Personally, I wouldn't use the MPA to directly construct "OSC=>Filter=>AMP" arrangements - these would go in a MUX, so they could be re-used.

I'd consider the MPA at the level:
(trigger)=>Multiple Sound Sources=>Complex effects routing = sound
but it's non-linear, of course, as there could be MIDI VST effects prior to the each sound source and possibly cross-modulating other sound sources and effects all over the place. (So long as there's no feedback.)

I am looking forwards to study a example of your approach .. it seems it is not the same aproach how MUlab it handles for making a sound(patch) and using the MUX (only for effects: correct me if am wrong)

It is rather suprizing

[MuTools]

Note that the modulation signals (the green jacks) work on a much lower rate than the audio sample rate.

A audio -> modulation converter module is possible,but it will be a kind of envelope follower.

It's on the whishlist/wishlist

And a MIDI to control plugin along the lines Taron mentions (separate control outputs for channel (0% to 100% for 1 to 16), MIDI note number (0% to 100% for 0 to 127), MIDI note gate (0% when off, 100% during note duration), MIDI note velocity (0% to 100% for 0 - or 1? - to 127).

Added to the wishlist!

The channel idea is a bit strange, but hell why not.

Thanks!

[Taron]

Tehehe...the channel thing i don't get either, but haha...sounds interesting.

Reminds me... key zone splitter would rock hard, too! This could probably be accomplished to some degree by dealing with a key tracking output, but it would make a very neat module for organisation. You could not only make great split key sounds, but also fully synth drumkits and the likes.

[Taron]

**********************************
* A new little tune....
**********************************
taron-electile.MuSession muSynth mild techno with muSynth drum fun...no idea how this works with speaker and subwoofer. I tried to be careful.

A quicky right now... just doodling around, playing with the synth, of course.

THIS one feels like it goes well with the rhythm:
**********************************
* A new little tune....
**********************************

[pljones]

Using audio signals as controls is the basis of FM synthesis, of course - FM makes no differentiation between modulator and signal. Of course, you need frequency dividers if you're going to play this game or you've no safe way of having LFOs from your audio signals (I don't trust tuning and getting beat frequencies...). (Envelope followers are different but also interesting! )

The channel idea is a bit strange, but hell why not.

Heh, I've no idea how a CV synth deals with channel, either! So long as it lets you control something that can use it to select zones, it's good. (It's that or 16 copies of the other outputs .)

[liquidsound]

Jo, it sound like you are going to compete (and surpass) Propellerheads's Reason pretty soon... .