MuLab 7.0.47

[pljones]

Less pixels than in M6, that's true, but still more pixels to select a collapsed rack than the collapse/expand and on/off controls so it should be ok, UI wise, i think. Right?

They're spread out very, very thinly.

What screen resolution are you on?
I guess the solution will be that the whole UI has a scale factor, right?

1920 x 1080. Adding more pixels would be bad -- that would take up more space on the screen and I have little enough as it is with 35 racks. What's needed is that more of the pixels that are there become useful for selecting the rack -- like the whole of the rack body, not just the title bar excluding the buttons.

ideally, all the racks would have focus

I don't get that. Do you want to play all racks at the same time when playing your MIDI keyboard? That will cause sonic chaos and level overload i assume.

No, I only have one rack switched on, so only one is processing MIDI, using up CPU time and creating audio. Each rack holds one drum kit and its effects. I want to switch between them as quickly, simply and accurately as possible.

[tatanka]

Hi Joe,

I have simplified the project to only one track, simplified the texture synth rack (thrown away the verb and echo modules) and getting a little bit closer to the problem maybe by this. Too much echo/delay etc. and maybe too much cpu use seems to cause the problem.

Now with the simplified version the problem gets smaller but you can still hear the sound starting again after the clip is finished (between beat 18 and 19). It first stops as it should, short silence, then about one beat after the clip has stopped, in the empty part, the sound starts again for a while.

In this project it is just a hint, without Absynth or the kontakt libraries or the complete texture rack with hight cpu use I cant reproduce the never ending sound problem but maybe you can see the direction of the problem.

What worries me is that it is not one VST only, not one Preset only but a lot of VST/Kontakt libraries/patches.

[pquenin]

Dont know if its a bug or not :
- if I select an audio part in the composer and click on the "edit" arrow at the left bottom of the composer, just after the name of the part, it doesn't open the audio lab in a separate window, it has no effect at all. It's OK if it's a sequence part.
Well, this "bug" is also in Mulab 6.

[AndreasD]

Im a bit confused with it, can it also behave like a more 'traditional' ARP, you know, play a chord on my midi keyboard and it plays each note in turn without having to program the steps myself,
maybe its been a long day

For me this setup works more traditional.
This is for 6 notes, if your chords are 3 notes, just use 3 steps.

ARP.jpg

[MuTools]

Thx everyone for the additional thoughts & explorations on the arpeggiator. Happy to see that some more usefulness has been discovered. Atoh i understand that not "everything" is possible with it and i'll reflect on things some more and see if it can be further improved/extended, maybe on short term, otherwise later.

[MuTools]

Hi Joe,

I have simplified the project to only one track, simplified the texture synth rack (thrown away the verb and echo modules) and getting a little bit closer to the problem maybe by this. Too much echo/delay etc. and maybe too much cpu use seems to cause the problem.

Absolutely. It seems you have made a very complex patch using a looped Multi-Point Envelope as 'Main Envelope' in other words the voices of that patch never end.

[MuTools]

What's needed is that more of the pixels that are there become useful for selecting the rack -- like the whole of the rack body, not just the title bar excluding the buttons.

Implemented in the next version.

[MuTools]

Dont know if its a bug or not :
- if I select an audio part in the composer and click on the "edit" arrow at the left bottom of the composer, just after the name of the part, it doesn't open the audio lab in a separate window, it has no effect at all. It's OK if it's a sequence part.
Well, this "bug" is also in Mulab 6.

Fixed in the next version. Thx!

[bibz1st]

Im a bit confused with it, can it also behave like a more 'traditional' ARP, you know, play a chord on my midi keyboard and it plays each note in turn without having to program the steps myself,
maybe its been a long day

For me this setup works more traditional.
This is for 6 notes, if your chords are 3 notes, just use 3 steps.

ARP.jpg

appreciate that Andreas but you are a little late as taifunk has already solved that for me.

[pljones]

Implemented in the next version.

Deeply appreciated! (It had been sufficiently "hard" to click the title bar - even in M6 - I'd not noticed that way of doing it! With the whole rack body clickable, it will be much easier.)

I'm also going to investigate how my idea would work of a single focused module in the session MuX with events through that connected to all the racks. (That's pretty much how my set up in Reaper works but without the flexibility to decide to do it that way.)

[MuTools]

Implemented in the next version.

Deeply appreciated! (It had been sufficiently "hard" to click the title bar - even in M6 - I'd not noticed that way of doing it! With the whole rack body clickable, it will be much easier.)

Hope you gonna like it cause it's only the very background that has been added to the click=select area. New version is expected to be available tomorrow.

[sbj]

Hi Jo

First of all congrats with this update.

I haven't found any bugs but I have two suggestions to modifications
regarding these functions:

1). When I use the new freeze function, it would be nice if I could tell MuLab the lenght of the freeze (e.g According to the loop markers).

2). Would it be possible to modify the Randomizer module, so the 8 different "assignments", would be with individual minimum and maxium values.

Cheers

[Taifunk]

I was able to recreate the error previously reported, this time has not disappeared inputs, but it appeared an input in musynth

[pljones]

Hope you gonna like it cause it's only the very background that has been added to the click=select area. New version is expected to be available tomorrow.

Yes, that's what I was expecting - not the slots, just the background.

Anyway, I put an empty MuX module into the Session MuX and wired its event out to all the rack event ins, focused all input channels to that module and turned off Automatic/Follow focus. Now all I need to do to change kit is turn off/on processing for the racks - very nicely CPU efficient and easy enough, I hope (I'll see over the weekend how it actually turns out when in "proper" use - when I'm actually playing, rather than sitting down in front of my computer).

[bibz1st]

2). Would it be possible to modify the Randomizer module, so the 8 different "assignments", would be with individual minimum and maxium values.

Cheers

I think they are different aren't they ? you can see this if you connect a module that has unipolar and bi-polar parameters, they show differently here unless Im reading it wrong (wont be the first time)