taron's little sessions

[MuTools]

the controller curves in the sequencer are...uhm...not really helpful, when you've squeezed a parameter mapping into tiny increments between 0.5 and 0.51 for example. I would much prefer to have a 0% - 100% curve that gets interpreted by the synth as opposed to a controller curve in the sequence that wants to show the actual value. Normally it sounds unlike me, since I am somewhat of a control-freak when it comes to music, hehe, or the creation process altogether, but in this case it's a application problem. One can't edit what he can't see.

I'm not sure if i understand what you mean here.

When a meta-parameter is set to e.g. minimum 0.2 and maximum 0.5, then you have the full height of the Event Graph Editor to edit in between this 0.2 - 0.5 range. And the editor shows the actual value i.e. in the middle it gives 0.35. I think this is all good, no?

[janamdo]

How Taron did this pitch modulation in MUlab is for me still a riddle, but if you see the controller lane of the pitch modulation in his session example and you scroll this to maximum size than you see some small tiny chances in value

His idea is to express modulation value in % than it is more visible in the controllerlane ?
In the list editor you see the values of the pitch modulation ranging from 0 % to 2 %

The pitch modulation parameter value is -100 to 100 %
Yes now i do see why the controller curve is in the middle
With -0.1 % as pitch modulation value to start
I think with this small amount of controller data it is better to have a larger graph in the controllerlane

[Taron]

Yup, for a lack of better knowledge I mapped the pitch.modulation directly to the modulation wheel as opposed to going through all the parameter mapping. As a result it recorded the pitch.mod itself and gave me what you can see in the WFT Osci track at the bottom. Not sure how you maximize that?!

[Taron]

Can you explain how you did the automation for the musynth 2 and his WFT oscillator
Unfortanely for me it is not so intuitive that i can figure this out now.. so i ask you

I suppose you mean the flute, right?
The oscillators has pitch modulated by lfo, while the lfo itself swings in automatically, simply because I was too lazy to program the parameters properly. A wobble generator together with a ADSR envelope modulate the AIPS to introduce a blowin change in sound as well as a slight continuing wobble in the character of the sound. Not sure what else to say about it, really. The real trick of the sound is the same LFO hooked into the final amplitude, which creates a tremolo for the noise generator and oscillator at the same time, binding them more closely together. The real fine spice of the sound was the tuning of the filters, though. Just the kind of resonance to just the kind of spectrum or rather frequency for the filters, so that they somehow feel like the two sounds can live together. It's difficult to discribe, really. You can switch into the guts of it and explore a little. This is not a very complex sound. But then they never really are. The simpler a sound contruction, the more control you can keep over it and it works with the nature of the synth. I think one should never fight that nature, but learn to embrace it. But I don't mind fighting for some improvements, hehehe. I'd love to have more intuitive ways to set up modulations and hook them together. It's all still a little...let's say "opaque" to me. But I really have to warm up to its mechanics a bit more before I really start with detailed feedback.

[Taron]

Here's a little experiment with mapping the wheel to the parameter map that maps to the parameter map of the synth core....eh... seems to work that way. I also happily discovered the beautiful simplicity of recording mixer movements! Sweet!

taron-cheese.MuSession

[janamdo]

Here's a little experiment with mapping the wheel to the parameter map that maps to the parameter map of the synth core....eh... seems to work that way. I also happily discovered the beautiful simplicity of recording mixer movements! Sweet!

taron-cheese.MuSession

Thanks.
It seems that altering the padsound (WFT oscillator + pitch Mod) of rack a better can be done via mapping the wheel to the parameter map of the mysynth core and using therefore one of the 16 meta parameters of the padsound patch of the deep editor.
There is a better controllercurve to see now

In your first session example(taron glitter) you mapped the wheel directly to the wft oscillator and his pitch modulation and this gives a another shape of the controllercurve

[Taron]

Correct. I think it feels a bit like a detour that shouldn't have to be necessary, having to map parameters twice or even three times (module to synthcore p.map to synth p.map and then synth mapped parameter to midi) in order to get the proper curve in the sequencer. A min/max on the curve display in the sequencer should be easier, I think. Havn't found that option, yet, in case it already exists?

But again, I've just started on my quest to discover things.

[MuTools]

Correct. I think it feels a bit like a detour that shouldn't have to be necessary, having to map parameters twice or even three times (module to synthcore p.map to synth p.map and then synth mapped parameter to midi) in order to get the proper curve in the sequencer.

You don't have to do it that way, but you can, if you want.

The advantages of using a meta-parameter mapping are:

* You can combine different parameters under 1 meta parameter
* You can define a value range
* MIDI controllers keep their full range which is mapped into the meta-parameter value range!

A min/max on the curve display in the sequencer should be easier, I think. Havn't found that option, yet, in case it already exists?

No it's not there.

If the only usable range for parameter X is between e.g. 30% and 50%, then why not setup a meta-parameter? (cfr the advantages above)

Maybe i'm missing something?

[Taron]

I guess, particularely when one is new to mu.lab, the first way to record a specific parameter in the core of a custom synth with the wheel is to just map the midi to it directly. Often times the wheel is just used for vibrato and maybe some slight adjustments to filter or other parameters. Without thinking much about it, you'd go ahead and use the midi mapping. Adding a new parameter to the mapping seems to be without a problem as there's the "merge" option. So in any quick'n'dirty edit, it seems natural to ignore the parameter up there.

Frankly, I was hoping to find the mapping I had just done on the module up in that parameter list. Seems like it might actually be useful to have this linked into one paradigm. Meaning that you wouldn't offer midi mapping as option on the module's parameters, but parameter mapping. It may seem like a restriction at first, but ultimatively it could well end up clearer that way.

Again, this is just my early encounter with mu.lab speaking. Soon enough I'll adapt to the way things are handled in it and won't even see a problem there anymore. But it's not really a "problem" to begin with. Just something that might be subject to some streamlining... clarity is a big winner everywhere.

Even so...being able to define min/max on sequencer curves is a very, very good solution. I wrote a synth last year that's not realtime, but generates sounds. I conceived its entire editor on the basis of adjusting the display to the existing amplitudes, which makes editing so beautifully clear. I'm also a developer on the animation (and rendering) tool messiah:Studio, which entirely depends on the graph editor section...eh...why am I writing all this, haha... I'm sure you know what I mean. Regardless as to the handling of the synth's inner glory, it's a clever move to implement min/max for the sequencer's curves.

But you can already keep in mind that I'm very happy with what you've got going. It's an exciting exploration for me and I really hope you know that I'm humbly stumbling into things. I know how grinching such first encounters with new users can get, hahaha...

Thanks for checking into it in the first place, too, by the way! Let me know, when I appear to be pulling your arm in any way, please!

[Juan Mendoza]

Hi Taron,

i listened to your tune yesterday night and i've been all this morning with it inside my mind

Also checked your soundclick site and i think i'm becomming one of your incomming fans ... musical soul indeed

[Taron]

Uh that's to my ears!
Thanks, Juan!
It's been so long since I really focused on music again. That's what gets me so excited about mulab right now. Oddly enough, I'm spending the first days with it inside the musynth core as opposed to just making a few tunes, hehe. But well... guess I want to inspect the goods first and then go really at it.

GREAT encouragement, though! Thank you once again!

[Juan Mendoza]

Uh that's to my ears!
Thanks, Juan!
It's been so long since I really focused on music again. That's what gets me so excited about mulab right now. Oddly enough, I'm spending the first days with it inside the musynth core as opposed to just making a few tunes, hehe. But well... guess I want to inspect the goods first and then go really at it.

GREAT encouragement, though! Thank you once again!

Hehe, i'm in the same situation. I've been more than 5 years offline and away from music production and now i'm starting again with the new Mulab, also happy, also excited with it

Also, as you mentioned before, the music i'm writing right now with mulab (mostly with the musynth) has a different feel and taste than the music i made years ago. The same happened when i switched from cubase to muzys years ago. We should thanks to Jo for bringing us a fresh and inspiring air.


Keep on!

Juan

[MuTools]

I guess, particularely when one is new to mu.lab, the first way to record a specific parameter in the core of a custom synth ... Regardless as to the handling of the synth's inner glory, it's a clever move to implement min/max for the sequencer's curves... Let me know, when I appear to be pulling your arm in any way, please!

Thanks for your feedback. There are some notes on the whishlist about the parameter mappings. To be researched more in the future.

[Taron]

A nice "quick" enhancement could be to the right click on a parameter and have "add to parameter map" as option, which would either bring another requester to pick the parameter number of the map to which it should get added to or you have all the parameters listed already in the right click menu and add it and bring you straight to the edit of the parameter map. It would make it a fair bit more intuitive and direct.

Currently the right click shows:
[map MIDI controller]
[Copy as parameter...] (Havn't looked through the docs to know the use of that?!)

Enhancement could be:
...the above+
[add to parameter map]

or
[add to *name of parameter 1]
[add to *name of parameter 2]
[add to *name of parameter 3]
[add to *name of parameter 4]
[add to *name of parameter 5]
[add to *name of parameter 6]
[add to *name of parameter 7]
[...]
[edit parameter map] (for convenience)

Just some ideas...

[Taron]

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!

Anyway, I will from now on update the first post of this thread with new songs. I made an e-guitar like lead and a mini choir bit for the taron-cheese.MuSession. It's updated, so you could download it again, if you wanted to. It's still cheesy, though! ...oh and my first MUX, which is kind of a weird tube/room sort of nutch for the lead.