MuLab 7.0.47

[MuTools]

I'm afraid there is another issue that has to be fixed, this time indeed in the arpegiator. Another consequence of that change in M7.0.33. An update will be available asap. No video necessary. Thx.

[MuTools]

There is a new M7.0.36 update available on http://www.mutools.com/mulab-downloads.html

This new version fixes an issue in the step sequencer arpegiator mode.

If you already have installed the MuLab 7.0.32 package or up, then you can apply this quick app patch:
http://www.mutools.com/mulab/app-patch/index.html

[magicmusic]

Now the arp work good, but i am not shure if it is plan as this. but if it is plan, its best arp, but can get confusing if not know. it is easy possible to change order which row play which key. Because in the lane setting can change the note number. so if set 1. row to c4, 2. row to c#4, 3. row to d4 then play order is as expectet. 1. row play lowest key 3. row play highest key. but when change 1. row to d4 and 3. row to c4 then lowest key play 3. row highest key 1. row.

i do not see how i can switch with midi key the pattern. Is this possible ?. Good is that pattern is play until end and then switch when press GUI button >.
functions i not see, how i can save all 12 note settings in left side, because then can load settings for drum notes easy or try out arp variations by load . etc

[AndreasD]

i do not see how i can switch with midi key the pattern. Is this possible ?. Good is that pattern is play until end and then switch when press GUI button >.
functions i not see, how i can save all 12 note settings in left side, because then can load settings for drum notes easy or try out arp variations by load . etc

You need to send midi note 0, 1, 2, etc.
I can't remember if this is c0 or c-2 or something.
I usually press the 'octave down' button on my keyboard until i can change the patterns. And you have to have 2 saved patterns before you see a change

[magicmusic]

I try too lowest octave before, but it start play sequence(very low note of course) so i guess this not change pattern. But thanks, now i do a closer look on pattern name. and i see it change pattern. but i think the keys that change pattern should not trigger sequence

edit: I see in arpegiator off this is work usefull, because when i press key for pattern a then it is play non transpose good for drum patterns. but with arp mode on, this play very low notes. I test some sounds. the I like moog sound for example play at this very low notes

[fluffy_little_something]

Noticed something strange: the shortcuts in Sylenth1 don't work unless I click the menu button in the Sylenth1 display first. Once I have done that, the shortcuts work, but only as long as Sylenth1 is displayed. When I switch to Chrome and then back to the DAW, the shortcuts don't work anymore, even if I click on the Sylenth1 window in order to focus it.
In my other DAW that is not the case, so it seems to be a Mulab issue.

[heks]

Just loaded 7.0.36 this morning and I've lost my "spacebar" start/stop play function. I messed around with the add short cuts and can only seem the get it to start, but not stop. Don't know why its just changed, but how do I get that function back?
Thanks

[MuTools]

Noticed something strange: the shortcuts in Sylenth1 don't work unless I click the menu button in the Sylenth1 display first. Once I have done that, the shortcuts work, but only as long as Sylenth1 is displayed. When I switch to Chrome and then back to the DAW, the shortcuts don't work anymore, even if I click on the Sylenth1 window in order to focus it.

That's where Sylenth goes wrong, imho, because when a VST editor gets a mouse click and it it is relevant for that VST editor to have keyboard focus, it should take keyboard focus upon mouse click. The host has no idea at all of how the VST editor is structured. That said i already conceded (in some previous M6 update) in adding some code lines that automatically try to force keyboard focus to the VST editor upon opening a VST editor. Now this enforcement was indeed not yet repeated when switching between other windows. In the next version it is. But whether that works or not still is dependent on the VST plugin's editor internals ie. it still is a rather ugly programming patch, probably the same as what other hosts are doing. VST editors should handle keyboard focus themselves.

[MuTools]

Just loaded 7.0.36 this morning and I've lost my "spacebar" start/stop play function. I messed around with the add short cuts and can only seem the get it to start, but not stop. Don't know why its just changed, but how do I get that function back?

Can't repeat that, start-stop still working fine. Anyone else?

[heks]

Just loaded 7.0.36 this morning and I've lost my "spacebar" start/stop play function. I messed around with the add short cuts and can only seem the get it to start, but not stop. Don't know why its just changed, but how do I get that function back?
Thanks

Sorted it out got start/stop back, just didn't see it in the list of short cut targets. Tell you what I think may have happened, I quickly looked on the forum the other night and downloaded the full .35 version and replaced the files in MuLab folder. I didn't have time to have a look at it and then next thing I saw was a .36 version which I just passed in the exe and ID files. All I can think is the .35 may have changed the short cut. Anyway, all is fine here. Thanks

[fluffy_little_something]

Noticed something strange: the shortcuts in Sylenth1 don't work unless I click the menu button in the Sylenth1 display first. Once I have done that, the shortcuts work, but only as long as Sylenth1 is displayed. When I switch to Chrome and then back to the DAW, the shortcuts don't work anymore, even if I click on the Sylenth1 window in order to focus it.

That's where Sylenth goes wrong, imho, because when a VST editor gets a mouse click and it it is relevant for that VST editor to have keyboard focus, it should take keyboard focus upon mouse click. The host has no idea at all of how the VST editor is structured. That said i already conceded (in some previous M6 update) in adding some code lines that automatically try to force keyboard focus to the VST editor upon opening a VST editor. Now this enforcement was indeed not yet repeated when switching between other windows. In the next version it is. But whether that works or not still is dependent on the VST plugin's editor internals ie. it still is a rather ugly programming patch, probably the same as what other hosts are doing. VST editors should handle keyboard focus themselves.

OK No idea how that works, or should work...
So, don't waste your time on fixing VST's deficits

[MuTools]

[pljones]

Very good intro video - nice and easy to follow. And thank you for putting the audio limiters in - the red lining was irritating .

[heks]

Being new to MuLab I found that video informed me of basic work flow things I had not known (compaired to my other DAW's), very good. Only thing I found annoying was the info box's were not on the screen long enough. I had to stop, go back and freeze to take in what they said. But I'm old, so maybe its just me.
I do think the video medium as above is more educational and accessible than trawling though the MuTools Doc's.

[Michael L]

maybe its just me.

No, many tutorials are as information-dense so I learn to keep my cursor on the transport button and rewind when needed. I really like this 'workflow' video style because it shows how to efficiently use each feature, and its fun to follow along with your creative process.