MuLab 6.0.35 released

[fluffy_little_something]

That is also why it says in the link "Some applications are available in both installable and portable versions." They exclude each other...

No, they don't. That's poor phrasing and worth editing the page on wikipedia to correct if you feel like quibbling about it.

Poor phrasing because it doesn't confirm your view?
I guess we need an IT expert to clarify...

[MuTools]

Personal view: For me it's an install too. It's not because it's not installed using an installer program that it is no install. Anyway, feel free to have another view/feeling of it, this is no exact science. Luckily whether it's called an install or not we can make music with it

[LunaTech]

Something that I have noticed, cpu load cut in half and I am running this in wine on KX Studio. Jo, did you guys change the Gui and sound engines?

[pljones]

Poor phrasing because it doesn't confirm your view?
I guess we need an IT expert to clarify...

No, because it contradicts itself.

[fluffy_little_something]

Something that I have noticed, cpu load cut in half and I am running this in wine on KX Studio. Jo, did you guys change the Gui and sound engines?

I was playing around yesterday and also thought I noticed a lower CPU load with a fat pad. But I was not sure (the last time I had used it was weeks ago), nor by how much. But certainly not by half. That would be a sensational reduction which he would probably have mentioned in the change log.

There is a note on sound engine optimization leading to fewer dropouts when CPU load is high, though.

[MuTools]

Something that I have noticed, cpu load cut in half and I am running this in wine on KX Studio. Jo, did you guys change the Gui and sound engines?

Yes the audio engine has been optimized and certain improvements may make an important difference on certain systems, maybe especially depending on the operating system (version). It's indeed about that note on the change log. Happy to hear it makes a clearly noticable difference on certain machines.

[fluffy_little_something]

Poor phrasing because it doesn't confirm your view?
I guess we need an IT expert to clarify...

No, because it contradicts itself.

I don't think so. Again, I would like to hear what an IT nerd has to say about it...

Anyway, it is not important, as long as it works. And I will look the other way whenever I read it, and things like Quit without save instead of saving

[fluffy_little_something]

Not really any issue, but I was wondering why it is not possible to drag and drop a synth VST directly from the browser onto an empty track?
One can drag and drop rack presets onto empty tracks, though, although there is no corresponding rack in the mixing desk in that case.
I was just adding new tracks via + and it always was pre-filled with a certain rack preset that I had used before. I personally think a new track should be all empty.

Also, it seems that when I add new tracks via + and then drag and drop a rack preset onto one of them, that rack preset gets propagated to all other tracks as well.

[MuTools]

Not really any issue, but I was wondering why it is not possible to drag and drop a synth VST directly from the browser onto an empty track?

Drag-dropping a VST synth from the browser onto the [+] track button works fine here, it creates a new track and rack with that VST synth plugged in. Anyone else encountering an issue with that?

I was just adding new tracks via + and it always was pre-filled with a certain rack preset that I had used before. I personally think a new track should be all empty.

You're talking about the "Add Track" choice? It indeed presets that new track to the currently focused plugin module. Don't see why that would hurt your workflow cause if it's not what you want you can change it, which you had to do anyway if it was empty.

Also, it seems that when I add new tracks via + and then drag and drop a rack preset onto one of them, that rack preset gets propagated to all other tracks as well.

Did you drop it on a track and then its sub-tracks followed that change?

[fluffy_little_something]

Yes, dropping it on the + works, but not on an existing track. Since there only can be one synth per rack, the newly dropped synth could replace whatever is in the synth slot so to speak. But yes, as I said, it is not issue. I will go the detour

Regarding the third note, no, I had added 4 new tracks, which took over the rack content from before, which is as intended if I got that right.
But those 4 new tracks are not subtracks, but all equal full tracks. And when I drop rack preset x onto the fifth track, the other 4 before also switch to that rack preset. I find that odd.

[MuTools]

Not odd cause all tracks were pointing to the same rack, if i understood you well. So dropping a preset on one of these tracks loads it into that target rack and hence the other tracks (which are pointing to that same rack) also reflect that change.

[fluffy_little_something]

Not odd cause all tracks were pointing to the same rack, if i understood you well. So dropping a preset on one of these tracks loads it into that target rack and hence the other tracks (which are pointing to that same rack) also reflect that change.

So, how do I stop the affiliation with any rack? I mean, when I open 4 new tracks (each of which has the same rack content because rack preset x was focused in the browser while opening those tracks) I naturally want to use them as independent tracks once they exist.

[sbj]

Drag-dropping a VST synth from the browser onto the [+] track button works fine here, it creates a new track and rack with that VST synth plugged in. Anyone else encountering an issue with that?

Works fine here. Win7 64bit. Newest version 6.0.28

[MuTools]

So, how do I stop the affiliation with any rack?

FYI: There is no propagation/affiliation. You're using a single rack, it's all about that same rack.

I mean, when I open 4 new tracks (each of which has the same rack content because rack preset x was focused in the browser while opening those tracks) I naturally want to use them as independent tracks once they exist.

Simple: Use separate racks for these tracks.

[fluffy_little_something]

Well, I thought rack presets are racks as well, so I thought it would make sense to be able to drag and drop rack presets onto tracks individually, rack x on track 3, rack y on track 1 etc., without the other tracks being affected. But again, it seems the detour via dropping racks into the mixind desk and then up on the tracks seems to work...