MU.LAB: What's next

[robenestobenz]

BTW, a big thx to your logical editor...I had last night a situation, where I had to delete about 2500 "ghost notes" out of a midi file...I didn't got it to work, but now I got it right...a big time saver and a step ahead against your direct competitors in price range...
Trancit

Yeah, I love this feature (and the sequence functions)!

On the subject of sequence functions -- whenever I try to randomise the time of a group of notes, it goes nuts spreading them around -- even with values as small as 0.0000001. Am I putting in the wrong sort of values?

[MuTools]

The time format = Bars.Beats.Ticks

So 0.000001 = 1 beat (the zeroes are irrelevant there)

If you want to randomize for e.g. 20 ticks, input 0.0.20

Hope this helps.

[robenestobenz]

The time format = Bars.Beats.Ticks

So 0.000001 = 1 beat (the zeroes are irrelevant there)

If you want to randomize for e.g. 20 ticks, input 0.0.20

Hope this helps.

Sweet, thank you. Might be an idea to add a note in the docs.

[> DiGiT <]

My 3 requests are in no particular order:

1) prominently displayed easily modified numerical system in the waveform editor. a neat device would be to allow the display to switch from samples to seconds to bars to 16th notes (according to current tempo), for instance, so you could easily dial in the loop times on your samples.

2) ok how about maybe a dedicated button to zoom to the absolute start of a sample? what other point in a sample is more important? maybe make it so you can tab to the loop start point and then the loop end, and of course the sample end... make it easy for those editing sample material. ideally thats where everything ends up before its done anyway right?

3) some sort of switchable response curve option for any modulation destination, live input or otherwise

this not my whole wish list for mu.lab, nor even my deepest darkest desires, just what i think it needs right now before the really good stuff takes center stage.

i wonder if theres an easy way to allow some current standard of modular plugin to operate within mu.labs architecture, maybe midi style too. that would give users something to play with while more native options were coded... arent there some sort of midi plugins out there?

whats the audiomulch guy doing these days? are his creations able to be ported or can they be supported natively?

[> DiGiT <]

whaddya think jo?

[MuTools]

I can only say the M4 design is fixed and i'm concentrated on implementing it. The main focus will be on further evolving & improving the modular system, as indicated at the start of this topic. There are a bunch of other aspects in the M4 design too, but it's still too early to spread details about it. One difficulty with software development is that sometimes unexpected problems popup that ruine the estimated r&d timeline. That's why i prefer to wait until M4 is almost ready for test before spreading details about it. Doing the very best to get M4 ready asap (where the S = soon / stable / streamlined ) Eager to spread it, and to use it! (have been making a lot of music myself too the last 2 months, which is fun (musician) and interesting (developer) at the same time)

NB: I'm not going to comment your concrete WL because if i do it, then i must do it consequently for others too and it's not relevant at this M4 stage (design is fixed, implementing it now), and it will slow down M4 development. A new poll for new/updated wishes is planned when M5 comes into target. Thanks!

[Trancit]

But one big question is left...

Are you any closer to find a solution for multicore support???


Trancit

[MuTools]

Cannot properly answer the question yet i.e. i cannot yet give you an answer which you can build on. (i know it's a top priority issue, at the same time it's also a difficult issue. while intensively making music, i also crossed the limits of my machine many times, wishing there was MC support and/or an easy & flexible freeze tool)(at the same time i was happily surprised with how stable MU.LAB 3.2.3 is and how good it sounds )(so now give us more power, MUTOOLS! )

[Trancit]

so now give us more power, MUTOOLS! )

Yeees, give us more power

But good to see, that you noticed the limits yourself , perhaps that gives you additional motivation and stimulation to get it done...


Trancit

[Trancit]

BTW...even if it is "only" your idea with parralel enviroments, which can use different core each...


Trancit

[jpumphandle]

An alternative to the actual curves would be like the curves in Sony ACID or Reason, for example. If the curves stayed over the parts/track they could be modified so easily!
They could be vectorial. That's a lot more easy to use.
Vector automation is better.

+1 - so easy to work with.

[jamieblac]

A drum pattern grid would be nice.

[dwsel]

As for multicore support - I'd suggest something like Firefox Plugin Container http://support.mozilla.com/en-US/kb/Wha ... -container
Basically to run all vst's as a separate process from the core program, so when they crash they won't close the MU.LAB itself and they would be easy to resume in such case. Running them as a separate process could benefit in speed, I'm not sure though if switching and sending data between processes wouldn't unnecessarily increase latency. Manual complatibility mode for each plugin - tick at the side on the plugins' name to create safe container for faulty older-SynthEdit-compiled VSTs would be great too.

[jamieblac]

Free tutorials on YouTube.

[liquidsound]

It could be useful to be able to have racks in the SMA but not show up in the Racks window (as an option).
This would allow to create additional mixer channels for groups and sends without having a Miracle Mile of racks in the racks window, keeping the essentials visible and the rest in the SMA.
It helps different styles of Mixer templates.