MuTools

MuTools · Post by **MuTools** » Fri Mar 20, 2015 2:45 pm

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

Changes since M6.4.11:

Export Tracks As Audio Files: When multiple main tracks were connected to the same rack/module/plugin, only the last such track was available as an audio file. Fixed.
Export Tracks As Audio Files: When a main track did not contain parts but its sub-tracks did, the main track was not exported. Fixed.
Composition: Insert/Delete Time Slice function now also takes the tempo track and markers into account.

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.

mickwest1 · Post by **mickwest1** » Fri Mar 20, 2015 2:53 pm

flipping 'ell Jo - that's amazing!!
thank you so much

AndreasD · Post by **AndreasD** » Fri Mar 20, 2015 10:48 pm

runaudio wrote:there's got to be a way that it can suite everybody's needs

Leave things as they are. I'm very happy with the way Mulab behaves with all the racks and tracks.

dakkra · Post by **dakkra** » Fri Mar 20, 2015 10:58 pm

AndreasD wrote:
runaudio wrote:there's got to be a way that it can suite everybody's needs
Leave things as they are. I'm very happy with the way Mulab behaves with all the racks and tracks.

+1

runaudio · Post by **runaudio** » Sat Mar 21, 2015 12:06 am

i Disagree with this

dakkra · Post by **dakkra** » Sat Mar 21, 2015 1:17 am

FLStudio for example:

All racks are already made. You can't add or delete any. You can assign multiple tracks to each rack. When you delete a track you don't delete the rack.

Only difference between Mulab and FLS in that aspect is that Mulab provides the ability to delete racks which makes for a cleaner work space IMO.

Granted most other daws have 1:1 connection between track and rack and do multi-audio via sends/receives but i much prefer how Mulab handles it. My biggest reason: Session MUX. I use it all the time while mixing/mastering.

It all depends on the DAW and users. DAWs like FLS and Mulab don't have 1:1 relationships. DAWs like Studio One and Bitwig do.

mgiambro · Post by **mgiambro** » Sat Mar 21, 2015 9:04 am

dakkra wrote:FLStudio for example:

All racks are already made. You can't add or delete any. You can assign multiple tracks to each rack. When you delete a track you don't delete the rack.

Only difference between Mulab and FLS in that aspect is that Mulab provides the ability to delete racks which makes for a cleaner work space IMO.

Granted most other daws have 1:1 connection between track and rack and do multi-audio via sends/receives but i much prefer how Mulab handles it. My biggest reason: Session MUX. I use it all the time while mixing/mastering.

It all depends on the DAW and users. DAWs like FLS and Mulab don't have 1:1 relationships. DAWs like Studio One and Bitwig do.

I agree nothing should be changed. But the addition of handling 1:1 relationships would save clicks. Another possibility would be something like Sonar's Instrument Tracks, so you choose what type of track you want at the point of creating i.e. if you create a regular track you get what you have now. If you create an Instrument/1:1 track, the track and rack are bound together. The flexibility MuLab provides with the many-to-many track relationship is great, but I think having the option of quicker 1:1 handling would be appealing to a lot of users, especially for those who rarely use the same sound for multiple parts and refugees from other DAWS.

MuTools · Post by **MuTools** » Sat Mar 21, 2015 9:50 am

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

Changes since M6.4.12:

Tuned a couple of code points where the term "Audio File" was still used, now changed to "Audio Stream".
Legato function now works to the next note anyway, independent whether the next note is selected or not.
A rack's own note key names now have priority on the note key names of the first synth in that rack.

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.

Hermu · Post by **Hermu** » Sat Mar 21, 2015 10:29 am

thanks, for MuLabs simplest note key names handling

MuTools · Post by **MuTools** » Sat Mar 21, 2015 12:01 pm

The MUX Modular 6.4.14 test version is available too: http://www.mutools.com/forsythia/

paradiddle · Post by **paradiddle** » Sat Mar 21, 2015 4:39 pm

Thanks for the mux update Jo, this is great!

MuTools · Post by **MuTools** » Tue Mar 24, 2015 10:39 pm

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

Changes since M6.4.14:

Inputting certain parameter values (eg Multi Mode Filter Resonance) was not working correct. Fixed.
New preference "Auto Loop Recorded Sequences".
"Edit Tempo Changes" now is a shortcuttable context function.

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.

runaudio · Post by **runaudio** » Tue Mar 24, 2015 11:03 pm

it would be better if you were able to drag out non recorded loops i mean loops from sample packs

bibz1st · Post by **bibz1st** » Wed Mar 25, 2015 10:10 am

Thanks again Jo, the auto loop pref is welcomed

mickwest1 · Post by **mickwest1** » Wed Mar 25, 2015 10:19 am

Thanks very much Jo - great work

MuTools

KVR Audio

MuLab & MUX Modular 6.4.17 Released