MU.LAB: What's next

[MuTools]

I've been thinking more about the next steps in the MUTOOLS story.

First it was my intention to do a poll here on the forum so to learn about your top wishes, but in fact i already have a clear idea of what's to be done next. In one little sentence: Further enhance the MUX in all its aspects.

This main goal incorporates several aspects:

• Merge the MuSynth and the MUX into 1, MuSynthCore will simply become MuSynth.
  This will increase simplicity and transparancy.
• Optimize performance i.e. lower CPU weight.
• Enhance editing comfort in the modular editors + beautify the GUI
• Enrich existing modules + add new modules.
• Expand the patch library with many more synth and effect patches.
• ...

There already are several concrete plans on the table, though i'm not yet going to tell too much now, lets keep the R&D cycle open and lets keep some nice surprises

Next ETA and next version number are not yet defined, this R&D cycle is just about starting, and things must first be researched more. (after a holiday break mid July)

The reason for this next goal is that i'm convinced that we can further gain a lot of workflow comfort by optimizing and expanding the MUX and its preset patch library. And also because it's the most logical step forward towards the MUX VST, which is an important goal too!

The big benefit for newbies will be:

• Simplified and more transparant architecture
• More preset content

The big benefit for power users will also be:

• Optimized performance
• Streamlined workflow in the modular editors
• Extended sonic palette <-> enhanced/more modules

I'm aware there are many other wishes waiting, like finetuned (sub)track management, integrated automation envelopes, specific support for sample loops (REX, stretching, slicing), SFZ support, and so much more.

It has always been my intention to keep MU.LAB simple, light and a joy to use. And i still want to keep that focus.

The MUX is magic power, that's for sure. So lets further polish (simplify and increase) that power as it's the sonic heart of MU.LAB!

Last but not least: Although the essence of this very next step in the MU.LAB story is already quite defined, i continue to be very interested in your wishes.

So feel free to share your MU.LAB Top 3 Wishes here in this topic, it will certainly help in updating the next priorities in the wishlist.

Please think good for yourself which 3 of all the feature requests you have in mind are the most important to yourself. Only the first 3 will be taken into account
Then share them here in a brief post eventually with some brief background info if relevant.

Thanks in advance!

And enjoy the summer of 2010!!

[zappadave]

Simple item fade in/outs seem to be the an obvious thing missing.
I can't see any simple way of fading out an audio item.
May be missing the obvious though, and I'm just using the free version.

[pljones]

My top wish is a 64 bit version (and all that entails) -- because I'm slowly moving towards 64 bit in other tools and I don't want to have to have duplicates of everything.

Multi-core would be nice but I'm happy to see code optimisation above that - and have no problem if "code optimisation" focusses on MUX and its components to start with. (However, I would ideally like to see multi-core tackled alongside this, as I think in itself it could offer some help with restructuring the code base. If this isn't kept in sight, implementing it later could become harder.)

GUI tuning has to also be in my top three. 3.1 has brought the app a long way forward but I'm sure there's more richness that can be added without complexity. It's an area I'd have to think about more, though -- I've very simple requirements from MU.LAB, which makes me familiar with the bits I use and probably unaware of large tracts of the app!

[cytone]

Here's 3 ideas:

1. Loop Mode for the composer. When you press play there is no left to right timeline but sequences get played when you click on them. Each row is independent. Maybe normal click = sequence will loop, CTRL + click = one shot. If record is activated it will go to the currently selected sequence.
Would be good for trying out different variations in an existing composition or to start out building up a track.


2. A method to edit more than one sequence at the same time. Or could simply have shortcuts to jump to the previous/next edited sequence while in the piano roll.

3. Improved cable management for the modules. When you move the mouse over a connection point highlight it with a small circle. The connection can then be either dragged off to remove it or moved to a new connection point. For multiple connections to the same point show multiple connection circles so one can be selected.

[bpblog]

1) multicore support (isn't this also important when it comes to using mux as a vst?)

2) increased control over audio seqences (fading, reversing, merging, ...)

3) timestretching

[MuTools]

Multi-core would be nice but I'm happy to see code optimisation above that - and have no problem if "code optimisation" focusses on MUX and its components to start with. (However, I would ideally like to see multi-core tackled alongside this, as I think in itself it could offer some help with restructuring the code base. If this isn't kept in sight, implementing it later could become harder.)

1) multicore support (isn't this also important when it comes to using mux as a vst?)

I did not explicitly mention multicore support in the message because i want to stay careful about it, don't want to make any false promises. But be sure i take it constantly into account, and when i'll be focussing on optimizing things i will certainly further research multicore support. No doubt it's a top wish of many of us, including myself. I did already research it, and parts of the puzzle are done. Also certain relevant aspects (threading aspects) of the code base have already been reorganized in order to be multicore ready. So that's all done. Now hopefully i'll be able to solve the last parts of the puzzle. It's like a difficult sudoku

[Calum]

My 3 wishes:

To be honest I would forego all other feature requests just to get Audio Unit support in MULAB and not just for the obvious reason - helping to address the inequality balance of VST plugins available for PCs compared to MACs. I have noticed recently that there are quite a few plugins for MACS that are only available as Audio Units which I would love to use in MULAB. It also seems a shame not to give MULAB access to the AU plugins already built into OSX. Most of all I want AU support to give me access to the Quicktime Music Synthesizer through the DLSMusicDevice so I have a GM soundset to hand, something that was relatively easy to achieve in Muzys. Of course, the icing on the cake would be an AU version of the MUX when the VST version is released.

I can't really prioritise my second or third wishes. i have lots of little wishes which have all been mentioned already but I am patient and I am sure they will all eventually make there way into MULAB. I do however think it would be a good idea to try to match the feature set of the MULAB competition. Without naming names, I think a dedicated drum sampler, arpeggiator and soundfont/REX support should be fairly high up the priority list.

Finally, I 100% agree with your wish to develop the patch library. I keep a portable MAC/PC versions of MULAB FREE with me at all times, kept on a memory stick (along with Audacity and TUX Guitar) ready to plug into any MAC or PC I have access to. Not only does this serve as my musical sketch pad but I can also use the setup to demonstrate the power and simplicity of MULAB to potential users. In a bid to keep the portable setup simple (unlike my home setup), I live without any VST plugins, so a developed, MULAB dedicated, patch/sample library would make my portable setup even more versatile and impressive.

[TheGuysanIdiot]

Hi All,

If I put my sales and marketing hat on three good selling points to add to MULAB would be.

1) Multi-core support (and 64bit)
2) Time stretch
3) MP3 import/export

The above three are complex and will probably find there way into MULAB as time goes by. Some may need third party software licences (MP3 etc).

For me they are NOT essential but will need to be addressed at some point in the evolution of any DAW.

I tend to agree that first MULAB needs to optimise its workflow and CPU usage along the lines Jo has already mentioned and while he is doing that keep an eye on how to add multi-core support into the new optimised MULAB code.

Ultimately Jo needs to keep MULAB user friendly and clean and simple. There are many DAWs out there packed full of features but none have the unique workflow and design of MULAB.

What follows is my own personal list of 3 wishes. I am already happy with how MULAB 3.x.x basically works. The first two wishes would add to the "fun" part of MULAB.

1) An arpeggiator and combined step sequencer module. Some time ago I sent Jo a number of presets and was very pleased to see him include them in M3. While Jo's synths sound great the lack of an arpeggiator/step sequencer module meant I could not emulate synth presets that are found in say Sylenth1. Download the demo of Sylenth1 and take a close look at the arpeggiator and combined step sequencer it has.

2) A dedicated drum sampler like Reasons Redrum or like the one in Ableton Live. Pretty much all my songs use drums so I would like a dedicated drum machine/pattern module. Hopefully you know what I mean here.

3) I would like the option to be able to see the note names on the drawn notes when zoomed in. I know I can hover over each individually and see the name in the mouse display. All DAWs I have used in the past have this and it fits in how I like to work.

4) I know it should only be 3 wishes, how about a trancegate module like Vanguard has.

Well there you go.

OZ

[aMUSEd]

Multicore and 64bit - I only have 2 really

[S.HUSH]

Please ignore this post if live performance features are not in the plans for MU.LAB.

There are so many host options out there but none really have catered to the DJ market. Even Ableton Live lost it's touch in this area and are predominantly focusing on the recording aspects of their program. They have live features but nowhere near the ease of use that other applications made specifically for DJing offer.

To consider the live performer/DJ market is a big plus because:

1. The obvious reason of catering to a whole new market means more money

2. Most DJs would consider recording software (remixes etc.) but fail to dive in because it can get a bit intimidating with the learning curves associated with many of the recording software on the market. If a program (such as MU.LAB) offers simple (user friendly, self explanatory etc.) live performance capabilities, this could entice the DJ/live performer to consider utilizing said program for live purposes, yet still have the option for advanced recording needs if and when necessary. It's a win/win situation.

It has always been my intention to keep MU.LAB simple, light and a joy to use. And i still want to keep that focus.

It is for this reason that I am making the following live performance feature requests to MUTOOLS. That, and of course, I have used MU.LAB a bit and like the ease of it.

One last important consideration before making the feature requests:
What is the advantage of utilizing a recording/sequencing software for DJ use vs. an application made specifically for such purposes? The answer is **Multi tracks**.
All software made for the DJ market work with the intention that stereo files are being utilized.
For a multi track program to offer DJ capabilities allows more freedom in live performance. With that being said, the requests:

Note that there will be [CC/Keystroke] placed at certain parts of the requests. All this is asking for is the ability to set feature to it's own MIDI cc and/or Keystroke for optimal live control options.

QUANTIZE LOOP

Allows any part of the song to be looped without any timing inaccuracies.
The duration of the loop can be quantized to 1 bar, 1/2, 1/4, 1/8, 1/16, 1/32, and 1/64 [separate CC/Keystroke for *each* quantize option].
There are 2 loop options [CC/Keystroke] in regards to where playback resumes once loop mode is deactivated:

1. Once loop mode is deactivated, playback resumes at loop point (play cursor stays within loop while in loop mode. Song continues playback from the loop point once loop mode is deactivated).
2. Once loop mode is deactivated, playback resumes at play cursor (play cursor continues down the song timeline while loop mode is on. Song continues playback from wherever the play cursor is down the timeline once loop mode is deactivated.

So there would be 2 loop mode buttons made for the above 2 options.

Advanced option: Have the ability to select only certain tracks to be affected by loop mode. So say, as an example, within a total of 8 tracks, 1,2 and 5 are selected to loop while 3,4,6,7,and 8 continue playing down the timeline. Insane.




BEATSLICE

The tracks slice according to the "quantize loop" settings. So if quantize loop is set to 1/2, all the tracks will get sliced every 1/2 bar throughout the whole song.
A random button [CC/Keystroke] rearranges all the slices, once random is deactivated, all slices resort back to their original positions. This done all in realtime without stopping playback.
There should also be a button which gives one the option to keep the current random setting [CC/Keystroke].

Advanced option: Have the ability to select certain tracks to be beatsliced.




MULTI-SESSION

EDIT: it was brought to my attention that MU.LAB does offer multi session (called compositions). Here are some requests for optimal live performance:

Important [CC/Keystroke] request: Have the ability to *select* each instance/session with CC and/or keystroke. Whichever session is active is the one that will be affected by any MIDI controller(s).
I'm thinking once a new session is loaded, a tab appears at the bottom of the screen (like Microsoft Excel) so one can select that session by clicking on the tab. Right click on the tab to rename and set to a CC/keystroke.
Since we are talking DJing, another cool option by right clicking on the tab, is to select whether or not a composition follows another composition's transport settings. This way both compositions (songs) play simultaneously. You can even select what transport functions a composition will follow (playback, loop, beatslice, BPM etc.). Very cool.


Well, those are the requests. Believe it or not, these additions will win you a whole new market. This will make MU.LAB an easy to use live application along with being a host for recording needs. One can use it simply for live purposes and/or for recording/remixing.

Someone already mentioned Time Stretching and this is absolutely essential for live applications. Set the BPM counter to a CC and time stretch [a time stretch button which can be set to CC/Keystroke] or deselect time stretch to alter the pitch (ala DJ turntables/CD players).

-Regards

[MuTools]

Thanks for your ideas so far!

FYI: I'm not yet replying in detail now as this topic is more regarded as an idea collector until the next MU.LAB X R&D cycle starts, that is at the end of july. Then i'll step thru all your posts again. Thanks again!

[Caco]

My three MU.LAB wishes are:

MSEG: An MSEG module for the Mux would be awesome as they are extremely powerful for sound design, allowing long evolving soundscapes, trancegates etc.

CPU Efficiency: The modularity of MUX, MuSynth etc is fantastic and I love using it but it does seems to be quite CPU heavy. I appreciate that the modularity and flexibility will always bring higher CPU usage but even so, at the moment it still seems higher than I expected.

More Audio Control: Would be really nice to drop wav files into the composer and be able to timestretch them to fit. It doesn't have to be expensive for Jo either as there are options like using the soundtouch library, which is available under an LGPL license so is free to use. Would also like to be able to add fades to audio as well.

[Bonteburg]

1) as soon as a sample isn't used by any instrument, it automatically dissappears from the project.

2) Sample prelisten has customizable volume or defaults to a much lower volume.

3) Straightforward OS-Style saving functionality.

[bpblog]

MULTI-SESSION

Have multiple "instances" (called sessions) within MU.LAB each with their own tracks. These multiple sessions can be treated like "decks" (using DJ terminology).

i'm not sure if i understand this part of your post correctly, but MULAB does have a similar feature already. each project file can have multiple 'compositions' inside it. these are made/toggled by right-clicking an empty space in the composer area and choosing 'select next composition'.
again, i'm not sure if this is what you need actually.

[Nielzie]

1) Multi-core support (and 64bit) / cpu optimization
2) Some fast and simple way to dial in midi fx plugins routing without having to dive in the modular area, preferably in the way it's done in Reaper
3) Some sort of internal drum synth/sequencer with quantization and humanization features.

Oh and a VST version of MU.LAB!! (but i've read somewhere that this is in the pipeline already)