MuTools

MuTools · Post by **MuTools** » Wed Apr 15, 2015 3:39 pm

There is a new MuLab 6.4.19 test version in http://www.mutools.com/forsythia
Changes since M6.4.18:

Fixed an exceptional possible save error.
Event Graph Editor: When clicking a velocity beam while holding Ctrl, this will now do the value line.
Composer: In specific cases looped sequence parts were not drawn right. Fixed.
Sequence part -> Consolidate: In specific cases looped sequence parts could cause a hang. Fixed.
Sequence functions: Quantize, Quantize 50% and Quantize Lengths all take the sequence start locator into account wrt defining the grid.
Sequence editor: When targetting a rack with a synth module that is using note key names, the mouse cursor info display was not showing the key names. Fixed.
Sequence editor: When targetting a rack with a synth module that is using note key names, choosing a mask for the Event Graph Editor didn't show the key names. Fixed.
Several detailed improvements wrt importing/exporting MIDI files.
LFO: Loading projects/presets made with versions prior to M6.4 now properly defaults the new End Fade parameter to the same value as the Start Fade parameter for sound compatibility.

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.

bibz1st · Post by **bibz1st** » Thu Apr 16, 2015 9:35 pm

Thanks for the new update

LYTZ · Post by **LYTZ** » Thu Apr 16, 2015 11:25 pm

Indeed, good job!

tatanka · Post by **tatanka** » Tue Apr 21, 2015 9:09 pm

Hello Joe,

there is still something wrong with memory/loading samples/libraries (kontakt ?). I had the problem versions ago (projects not loading again etc.), now tested with my 6.4.17 then updated to the actual 6.4.19, it is stil the same. I have NO track, NO other VSTi just blank project with one empty track and just the midi input from an external software sequencer (Sundog). Loaded Kontakt with Pentagon library. Switched to second library "panic. cant locate enough memory". Then sound dropped, nothing goes anymore. By the way: the sum of the loaded samples is around 100 mb !

I have for comparison the actuel cubase elements 8. WITH 8 midi tracks, VST (Halion, Groove Agent...) and the same sequencer routed to Pentagon Rack. No problem at all.

What I recognized and maybe there lies the bug: Cubase takes lets say about 10 to 30 seconds to load the samples in Kontakt in Cubase. In Mulab there is just a hush and then the error report. I am sure there is DEFINITELY something wrong (with loading samples in libraries ?) in Mulab, cant say if it is Kontakt specific but you told me that time ago to use STABLE VST LIKE Kontakt.....and could not be the CPU with NOTHING apart from that one Kontakt library.

Kind regards,

Richard

MuTools · Post by **MuTools** » Tue Apr 21, 2015 9:21 pm

Sounds like Kontakt needs more RAM than you have in your system. Can't do anything about that.

PS: Note that using the 64 bit version you can access more RAM. Maybe you're using MuLab 32 bit? If so try MuLab 64 bit.

pljones · Post by **pljones** » Tue Apr 21, 2015 9:50 pm

tatanka wrote: STABLE VST LIKE Kontakt

LOL... I can crash Kontakt in Reaper by opening two instances at the same time. Rock solid in MuLab. NI, of course, say "Not us"...

tatanka · Post by **tatanka** » Tue Apr 21, 2015 10:02 pm

O.k., I am using 32 bit (but thats the same with cubase, 32 bit the same), but I think I have found something mor in detail.

Has nothing to do with ram (I mean I have 8 GB and Kontakt loads 100 mb as I wrote and cubase uses the same ram WITH Halion, Groove agent etc. LOADED....) directly but it seem that pentagon has 512 voices for evry instrument by default and that seems to affect Mulab WHILE it is loading. This time the extern sequencer wasnt even opened but still opening kontakt with that pentagon library in an empty project kills mulab with that "panic...."

When I turn the voices down (with lots of error messages from mulab) at least it works. So maybe there could be something done with managing the loading of the voice setting when they are not even used.

Kind regards,

Richard

MuTools · Post by **MuTools** » Thu Apr 23, 2015 4:19 pm

There is a new MuLab 6.4.21 test version in http://www.mutools.com/forsythia
Changes since M6.4.19:

Finetuned the dialog for the "Sequence -> Change ..." functions: The buttons are replaced by a tree list.
Soloing a rack also takes any racks into account that are sending/outputting to that rack. This is important wrt the use of racks as busses.
Finetuned previewing strategy.
Event Graph Editor: Applying a velocity line was not always working as expected wrt the start and end point of the velocity line. Fixed.
Changed the "Quantize 50%" function to "Quantize %" which uses a popup dialog where you can enter the percent value.

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.

Reincke · Post by **Reincke** » Fri Apr 24, 2015 7:22 am

Thanks for the update, Jo.

mutools wrote:
Event Graph Editor: Applying a velocity line was not always working as expected wrt the start and end point of the velocity line. Fixed.

Similar prob occured (pre 6.4.21) also on curves (e.g. pitch bend). Trying to get a curve from e.g. 0.5 down to 0 often (but not always) results in different values, although 0 was displayed in value preview. Is this fixed too? I often work with pitch bends in the event graph editor.

BTW: Do we really need the "Composer" button? The "Editor" button toggles on/off, so we can switch back to composer by switching off the editor. Do I overlook something?
JR

MuTools · Post by **MuTools** » Fri Apr 24, 2015 8:48 am

There is a new MuLab 6.4.22 release version in http://www.mutools.com/forsythia

Only change since M6.4.21: Finetuned solo behavior for racks.

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.

MuTools · Post by **MuTools** » Fri Apr 24, 2015 8:58 am

Reincke wrote:Similar prob occured (pre 6.4.21) also on curves (e.g. pitch bend). Trying to get a curve from e.g. 0.5 down to 0 often (but not always) results in different values, although 0 was displayed in value preview. Is this fixed too? I often work with pitch bends in the event graph editor.

At the moment the end point of the line is regarded as exclusive = not inclusive. I'll see if i can change that. I agree that would be more relevant from user pov.

Reincke · Post by **Reincke** » Fri Apr 24, 2015 1:50 pm

mutools wrote:... I'll see if i can change that. ...

That would be really great.

Any comments regarding the composer button question?
JR

MuTools · Post by **MuTools** » Fri Apr 24, 2015 1:55 pm

Reincke wrote:Any comments regarding the composer button question?

I'll keep it as is.

pljones · Post by **pljones** » Fri Apr 24, 2015 4:06 pm

The Composer button makes sense depending how you're using docking, IIRC. You can think of the three as "tabs" to switch between rather than the other two as toggles. IIRC...

Reincke · Post by **Reincke** » Sat Apr 25, 2015 6:10 am

Thanks pljones. Just tested again:

"Modular" toggles te modular (floating) window on/off
"Edit" toggles (docked) part editor on/off
"Composer" doesn't toggle at all but brings us "home".

So imho it's a mix of tab and toggle behaviour. I simply didn't understand the need for the "Composer" button.
JR

MuTools

KVR Audio

MuLab 6.4.26 Test