MuTools

MuTools · Post by **MuTools** » Sun Mar 08, 2015 6:49 am

Braserox wrote:Have found the problem. By default 6.4.5 is openning modular in floating. Have never used floating frame before.

Whether the modular area is opened docked or in a floating window is defined by the "Docked Modular Area" preference. By default it's "On" = docked. So i assume that preference is "Off" now. You can set it back to "On" if you want.

bibz1st · Post by **bibz1st** » Sun Mar 08, 2015 8:52 pm

bibz1st wrote:I was trying to move those sections that I highlighted a few steps to the right, so it was only sequence data I was moving.
After the crash I could load the project and carry on adding things and it would even play ok but as soon as I tried to move a sequence part it crashed.
Im not at my pc now but will do further testing asap. If nobody else is having this problem it may just be the patches I'm using in Synthmaster that is the issue, too cpu hungry maybe.
Will let you know when I can.

Well I opened the exact same Project today and I'm pleased to say it didnt crash once, so fingers crossed it was just one of those unexplained glitches.

MuTools · Post by **MuTools** » Sun Mar 08, 2015 9:10 pm

Ok, thanks for the update. Lets keep a good eye on that. Thx again.

bibz1st · Post by **bibz1st** » Sun Mar 08, 2015 9:29 pm

Sometimes I think it would be better if there was something obviously wrong, then at least it can be sorted. I'm hoping it was just a CPU issue, at least I can just render the tracks and free it up.
Back to the music

Braserox · Post by **Braserox** » Tue Mar 10, 2015 7:02 pm

Little problem. "Save as" is still saving as *.musession

On next "save" it is overwritten as *.MuProject

I dont know if it is wanted. May creat bugs.

MuTools · Post by **MuTools** » Tue Mar 10, 2015 7:37 pm

Confirmed, will be fixed in the next version. Thanks for reporting this!

MuTools · Post by **MuTools** » Fri Mar 13, 2015 10:38 am

There is a new MuLab 6.4.9 test version in http://www.mutools.com/forsythia/

Changes since M6.4.5:

Greatly improved LFO module:
- All LFO shapes are fully editable now.
- LFO shapes can be saved/retrieved using MuWaveShape preset files.
- LFO now has a Start Phase parameter, which can also be set to Random.
- LFO now both has Start Fade and End Fade parameters, both of which can function as a fade in or fade out. The end fade starts when a note off is received.
- When Start Fade is an immediate fade out, then it is ensured that the LFO will start at the defined start phase on note-off. This way you can do a pure note-off LFO.
- When in Tempo Sync mode, setting the frequency via a dialog bar now also supports a "Bpc" unit suffix meaning Beats Per Cycle. This way the conversion to "Cpb" (Cycles Per Beat) is done for you.
New "Note Dispatcher" module.
This module dispatches the incoming notes (events) to one of the outputs depending on the mode:
Random: Whenever a note-on is received, a random output is selected.
Round Robin: Whenever a note-on is received, the next output is selected. And when a note-on with Special Key is received, the output is reset to the first one.
Keyed: Whenever a note-on with Special Key is received, the next output is selected.
Key Range: The note-ons in the key range from Special Key to Special Key + Num Outs define the output.
MuSynth, MuSampla and MultiSampla are using the new improved LFO.
Some MuSynth patches could contain a pitch/filter LFO with amplitude at 0%. Fixed.
MuSynth: Fixed a problem with the polarity of the amplifiers sustain level.
Finetuned MuSynth UI layout.
Improved time bar and time grid layout for when in real time mode hh:mm:ss.
Parameter editors with only a label (eg in MuSynth) now have a "Edit Value" context menu.
MultiSampla editor: Pitchbend knob had a little vertical offset. Fixed.
Save Project As could still save as a .MuSession file. Fixed.
Pure Delay now has a samplerate-independent maximum delay of 2 seconds.

How to upgrade from MuLab 6.2.x or up:
OSX: Simply replace the MuLab.app by the new version.
Windows: Simply replace the MuLab.exe + MuLab.ID files by the new versions.

As the new LFO is preset file based you also need to add the MuWaveShape folder to MuLab/App/Library
The MuWaveShape is as a zip in http://www.mutools.com/forsythia/

MuTools · Post by **MuTools** » Fri Mar 13, 2015 10:43 am

Info tips:

Both the Start Fade (starts on note-on or when LFO starts) as well as the End Fade (starts on note-off) can both do a fade-in and a fade-out. That's what the smaller than/greater than symbol in the value means: '<' means fade-in, '>' means fade-out.
LFO: Special case: When Start Fade = ">0" = immediate fade out, then End Fade starts as an independent fade.
so it will start with the start phase and start a fade-in from 0% and a fade-out from 100% of the defined amplitude.
When the Start Fade is in this special case, its value is "Inactive".
In all other cases the End Fade will continue fading from where the Start Fade ended.
A wave shape envelope is expressed in frames, but the time positions in a wave shape envelope are simply relative to the loop end point. It is the loop end point that defines the full cycle.
So setting the loop end to eg 360 frames makes it easier for editing as then it matches the 0 - 360 degrees of a waveform.
But you're free to set it as you want. For this reason there is the context function "Resize Shape".
Note however that the size of the shape has no effect on the final quality, the final quality is always perfect.
That's because the wave shape is vectorial using 64 bit floating point values.
Double-click the LFO waveform display to open the editor.
Right-click the LFO waveform display for more options.
In the envelope editor, hovering a point shows the exact time+value of that point in the mouse info display.

Nielzie · Post by **Nielzie** » Fri Mar 13, 2015 10:44 am

mutools wrote: All LFO shapes are fully editable now.

Awesome!

runaudio · Post by **runaudio** » Fri Mar 13, 2015 11:17 am

theres a problem with the new lfo when go into edit mode and take away the loops marker and add another point it crashes and all so if you only want to just pick a lfo shape you cant now before you were able to click left and right to change the shape

MuTools · Post by **MuTools** » Fri Mar 13, 2015 4:31 pm

Indeed, there is a prob as it should not be allowed to remove the loop markers. Will deliver a fix asap. Thx for reporting!

MuTools · Post by **MuTools** » Fri Mar 13, 2015 6:18 pm

There is a new MuLab 6.4.10 test version in http://www.mutools.com/forsythia/

Changes since M6.4.9:

* LFO Wave Shape editor: User could delete the loop start/end markers, which should not be allowed. Fixed.

How to upgrade from MuLab 6.2.x or up:
OSX: Simply replace the MuLab.app by the new version.
Windows: Simply replace the MuLab.exe + MuLab.ID files by the new versions.

AndreasD · Post by **AndreasD** » Fri Mar 13, 2015 7:39 pm

Fully editable LFOs! Great update!!

MuTools · Post by **MuTools** » Fri Mar 13, 2015 8:17 pm

Thx! And not only fully editable, also more creative options on how the LFO evolves, using the Start Fade in/out and End Fade in/out.
And thx to the fact that all parameters in MUX can be set via dialog input, now it's easy to set exact tempo synced values for example 2 Cpb (= Cycles Per Beat)
You can even input "1.5 bpc" (Beat per cycle) which will automatically do the conversion calculation to Cpb. (= 0.66667 Cpb)

Michael L · Post by **Michael L** » Sat Mar 14, 2015 12:07 am

This is a very complete and well thought-out upgrade.
Perhaps we could have a place to upload and share more complex LFO presets. Would that be useful?

MuTools

KVR Audio

MuLab & MUX Modular 6.4.17 Released