MuLab 6.0.35 released

[MuTools]

Well, I thought rack presets are racks as well

Not exactly the same. Compare it like a synth and a patch/program: A program is not a synth, it's loaded into the synth.

But you have the choice how to use these rack presets: If you drop a preset on an existing rack it will load into that rack, if you drop it on the [+] track button MuLab creates a new track+rack with that preset. If you drop it on the [+] rack button MuLab creates a new rack with that preset.

[runaudio]

you say u can not rewire have more than two inputs and out puts and more than 8 plugins well i can still do all that in free mode rewired to ableton

[MuTools]

It is possible to do so with the free version but then you'll hear a soft noise from time to time.
That's because MuLab Free also functions as a demo for MuLab Unlimited.

[Hermu]

if Session is out of Composer Window, Rewind to Composition Start will not bring back the Session to Composer Window

i have loaded AudioDropOutLoopPlay.MuSession with 4 beats and 3 markers.
after 5x press forward [->] Session is out of Composer Window.
after 5x press rewind [<-] Session stays always out of Composer Window, although song position is on composition start.
Goto Composition start didn't help, Session must be moved back with the horizontal scroll bar.
i would expect, that rewind to start will bring back Session to Composer Window.

i have sent AudioDropOutLoopPlay.MuSession as attachement to mutools.com

[MuTools]

It works fine here but note that i most probably have another screen resolution so i don't have the same visual setup.
Note that the "Auto Scroll" function only works when the play cursor is crossing the border i.e. it is visible and the next animation cycle it's not visible. So it will not auto scroll once the play cursor is not visible.

[MuTools]

Ok, could repeat it. It's most probably when you're stepping to the very end of the composition view, which is just outside the visual region of the composition as the end point is exclusive. Note that the very end of the composition view is further than the real end of your composition ie the last part's end. So if you want to auto scroll to that point put a marker there.

[Hermu]

Ok, could repeat it. It's most probably when you're stepping to the very end of the composition view, which is just outside the visual region of the composition as the end point is exclusive. Note that the very end of the composition view is further than the real end of your composition ie the last part's end. So if you want to auto scroll to that point put a marker there.

I don't want to autoscroll to that point outside of the composition, but it happens if [->] key was pressed one time to much.
it's very interresting, that the marker outside of the composition on the same position as before, changes the auto scroll behaviour.
also, if i stop playing outside on the same position of the composition as before, auto scroll works without a marker outside of the composition

[MuTools]

I explained the technical reason above. Tip: Put a marker at the real end of your composition, eventualy name it "END" maybe that helps. And in the next version that exclusive end point is not included in the forward function anymore. (but that next version may only come after release i.e. M6.1, it depends)

[fluffy_little_something]

Strange, for the first time in a really long time Mulab crashed on me. I had two synths open, trying to recreate one patch on the other. So I was switching back and forth between the two repeatedly. Suddenly, Mulab's GUI ceased to be responsive, while I could still play the sound of the selected synth.

So I tried to close it, which oddly opened a new Mulab window. So I had two two Mulab instances simultaneously. But neither made a sound. I could close the new instance, but when I closed the first instance, Windows said it crashed.

I assume it had to do with repeatedly selecting synths via their respective windows. I have occasionally noticed before (with various versions) that sometimes clicking on a VST window does not select that VST, but that instead another VST continues to be active.

[MuTools]

Strange, for the first time in a really long time Mulab crashed on me. I had two synths open

VST synths? If yes which ones?

[fluffy_little_something]

Strange, for the first time in a really long time Mulab crashed on me. I had two synths open

VST synths? If yes which ones?

Oh, you think it was the VSTs' fault? Well, maybe, I can't prove the opposite. So you are off the hook, if that is what you want

[MuTools]

I was just asking a question in order to know what tech area this is about.
VSTs are a separate world so if it's about VSTs i need to know.
But it seems to be the case, based on your reply.
Which VSTs?
Is it a repeatable problem?
Is it also repeatable with other VSTs?

[fluffy_little_something]

The same ones I have been using in Mixcraft for over a year without any problems. (Mature Superwave ones.)

Maybe Mulab simply doesn't like SynthEdit. That is however what I use almost all the time because I have zillions of patches for them.
Actually, I use hardly any non-SE plugins at the moment. Except for the Cakewalk Studio Instruments, which, as I have reported earlier, also show problems when using more than one instance in Mulab.

Which plugins do you use when testing Mulab's third-party compatibility?

[MuTools]

A variety, nothing particular, but with an emphasys on the 'major' ones.
Is the problem you're experiencing repeatable?
Is it also repeatable with other VSTs?

[fluffy_little_something]

A variety, nothing particular, but with an emphasys on the 'major' ones.
Is the problem you're experiencing repeatable?
Is it also repeatable with other VSTs?

The crash has not been repeatable so far, as I said it was the first crash of that kind.
Some plugins becoming irresponsive for some time has happened before, yes. But I don't know what to do in order to "achieve" that on purpose And after a while, they become responsive again.