MuLab 6.0.35 released

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Michael L wrote:Another: When I click on a Track + Add Instrument Track, and then Devices>Instruments>MuSampla, and OK, it adds a Track. However, when I click on a Track + Add MuSampla Track, and OK, nothing happens.
So "Add MuSampla Track" doesn't work on your system? It does work fine here. Also double-checked it on OSX. When doing "Add MuSampla Track" you should get a dialog where you can choose the sample file to be used. Note that you can also drag-drop files on that Sample file field. Then on OK this is what's done all in that 1 step:

* A new track is created
* A new rack is created and assigned to that new track
* A new MuSample is put in that new rack
* The sample file is loaded into that MuSampla
* MIDI focus is switched to that MuSampla rack.

Now all is ready to rock that sample.

Post

mutools wrote:
fluffy_little_something wrote:There seems to be a problem with Cakewalk's Studio Instruments. When I open two instances of the string module, there is terrible noise and Mulab finally overloads even without playing anything. Maybe a Cakewalk thing, dunno... Just tried it in M5, same thing, so obviously nothing to do with M6 as such, but either a Cakewalk issue or a general Mulab issue.
Can you repeat this with other VST plugins?
No, only happens with that Cakewalk stuff. Both in M5 and M6. Since those modules are basically romplers, maybe a memory issue...

Post

mutools wrote:
fluffy_little_something wrote:There is quite some noise when pulling the pre/post fader selector while something is playing.
Can't repeat that noise. When changing the pre-post, sound is muted/reset for a moment, but that's unavoidable.
Yes, with track racks there is a pause, but with the master rack there is noise instead.

Post

sl23 wrote:Amazing how these minor things have made such an impact overall.
I agree.

Maybe M6 does not feature spectacular big new features, but it's rather a rich collections of small and medium-size new and improved features that all together seriously improve the usability and workflow of MuLab.

I could have waited longer before sharing this version and add more and more features just to blow up the release text. But i'm convinced that this is an interesting and very usable update and so i preferred sharing it now already and then continue working on other new and improved features for the next versions.

Also thanks for all your suggestions sl23. Though i only reply on some of them, i've read them all.
I thought that these buttons could do with having icons to save space:
Compose = This could have an icon consisting of several varying-length horizontal bars.
Edit = A simple page and pencil icon.
ModArea = Use the icon from the Front Panels.
Yes though of that too, but i think the Compose / Edit / Modular texts make things more clear than icons atm. And about your point wrt sizes: Replacing those texts by icons will only gain a small amount of pixels. Also note that some of you are on relative small screens, some on big screens with all the top panels only taking half of the screenwidth! I'll continue looking for methods to mak MuLab more flexible to adapt to different screensizes. I'm taking that into account all the time during development and we're getting close to the point where you'll be able to scale MuLab in some way.
Mouse Scrolling in the ModArea scrolls Horizontally by default, can this be changed?
No. But i understand your point, taken note, will reflect on that.
Certain menu items have unnecessary text. More text = longer read time = slower workflow. Removing these superfluous words doesn't remove the actual meaning of the menu item, the meaning remains intact and obvious.
Some good suggestions in there, will give it some thought.

Thanks.

Post

J4ck Fl4sh wrote:Hi Jo,
I love that you can now see the MuDrum instrument name in the piano roll editor, but suggest these be repeated across all octaves in the editor as some of my projects have a range that does not begin at C3.
I understand your request, but that will make the mudrum key name list less clear, much more bloated. At the same time i also have this idea that the other octaves on a MuDrum will use the same sounds but pitched to that relative octave. So the C3 octave at original pitch, C2 octave = same 12 sounds but one octave down, C4 octave = same 12 sounds but one octave up, etc. So i would recommend to stay in the C3 octave anyway. You could assign a shortcut to the Transpose function so it's quick and easy to transpose notes. As a compromise i could also add 2 new shortcuttable functions: "Transpose Octave Up" and "Transpose Octave Down" so that will make it even more easy as there is no dialog involved. What do you think?

Post

fluffy_little_something wrote:
mutools wrote:
fluffy_little_something wrote:There is quite some noise when pulling the pre/post fader selector while something is playing.
Can't repeat that noise. When changing the pre-post, sound is muted/reset for a moment, but that's unavoidable.
Yes, with track racks there is a pause, but with the master rack there is noise instead.
Are you using VSTs after the pre-post point? If yes which VSTs?

Post

I followed your instructions to navigate to a sample before OK to Add MuSampla Track (I was still thinking drag & drop). Works perfectly. Very thoughtful workflow improvement!
On my OSX system, when I click Replace on a Device anywhere in an existing Rack (not on the rack name), and then click on a replacement VST or Instrument, the Rack still disappears.
F E E D
Y O U R
F L O W

Post

sbj wrote:I noticed though that when I load a sample with MuSampla and then make a subtrack to automate for example the filter cut of a crash happens when I try to extend (drag) the automation file backwards
Please mail me a simple session (without VSTs) + step-by-step for how to repeat this crash. Can't repeat it yet here.

Post

Michael L wrote:I followed your instructions to navigate to a sample before OK to Add MuSampla Track (I was still thinking drag & drop).
Note that you can drag-drop a file on the file field too in that dialog!
On my OSX system, when I click Replace on a Device anywhere in an existing Rack (not on the rack name), and then click on a replacement VST or Instrument, the Rack still disappears.
Where exactly are you right-clicking? Are you clicking on a black plugin slot? or somewhere else?

Post

blackbaron1 wrote:I have purchased MuLab UL 5 the last year (23 February) and I am asking if there is the possibility of a future upgrade from MuLab UL 5 to MuLab UL 6 without to pay the whole price again.
Of course there will be a gentle upgrade path. No way you would have to pay it all over again. It's not yet 100% decided but it will definitely be below 20 euro.

Post

Ah, I was clicking on the arrow next to the name in the plugin slot (old habit). When I clicked inside the slot, all is well! No bugs for me.
F E E D
Y O U R
F L O W

Post

Well i do understand the confusion and will tune that anyway.

Post

mutools wrote:
fluffy_little_something wrote:
mutools wrote:
fluffy_little_something wrote:There is quite some noise when pulling the pre/post fader selector while something is playing.
Can't repeat that noise. When changing the pre-post, sound is muted/reset for a moment, but that's unavoidable.
Yes, with track racks there is a pause, but with the master rack there is noise instead.
Are you using VSTs after the pre-post point? If yes which VSTs?
Doesn't matter, even without anything in the master rack slots there is that noise, but also with TAL's chorus (I just picked any random effect to try it).

Post

Could you perhaps make it possible in a future test release to let us unlock to full version with our M5 key or a temporary M6 key? I'd like to test while also continue working on some of my current M5 projects and templates which exceed the limits of the free version :)
No band limits, aliasing is the noise of freedom!

Post

Nielzie wrote:Could you perhaps make it possible in a future test release to let us unlock to full version with our M5 key or a temporary M6 key? I'd like to test while also continue working on some of my current M5 projects and templates which exceed the limits of the free version :)
Come on, that is not the purpose of the demo version :) You can test basically any features with the current test version.
I hope we will be able to buy the upgrade soon, though...

Post Reply

Return to “MuTools”