MuLab 7.0.47

[bibz1st]

Oh yes, dont get me wrong, its a great addition to the arsenal

[MuTools]

FR (which is desperately needed but rarely noticed...): When popping up "Couldn't find VST plug-in XXXX", please add a third option: either "Abort" to cancel loading the project entirely or "Ignore All" to ignore all future unfound VSTs. I just loaded a project with well over a hundred VSTs (around 35 tracks, at least 3 VSTs per track) and having to click "ignore" on each (because I really don't want to manually find them right now) is very painful. (Actually, it wasn't that bad -- I just held down "I" in the end.)

Ok implemented in the next version.

[MuTools]

in short I could not find a musynth preset that reproduces exactly what happen with Absynth/Kontakt etc. but I think you can imagine from the sample project.
Even with the Texture preset the clip plays on after the last note/end of clip. Difference to Absynth/Kontakt: at least it stops sometime while the mentioned did not stop at all but just play on endlessly.

I'm sorry but i still don't see/hear the prob. Can you pls be more precise. At what point in time you think there is something wrong?

[MuTools]

Oh yes, dont get me wrong, its a great addition to the arsenal

Do you think something musically essential is missing in the step sequencer/arp? Personally i don't think so, but maybe i'm missing something? If yes pls elaborate.

[bibz1st]

Ok, going back to RandArp and others like it or even simpler ones (like the one on the real Pro One) you just turn them on select up, down or up/down and away you go, the arpeggios follow what you play dynamically, add notes here drop notes there, the key words are play and dynamically, not just pressing one key. Hope I'm making sense

[Taifunk]

I encountered a strange problem in modular area, when you drag a mux or a module from the rack/mux in modular area and vice versa sometimes disappear inputs and outputs of the mux module/mux dragged(This happened with the step sequencer patch posted before),I can not reproduce the error but maybe there is something wrong

other times always in the modular area when you drag a module/mux are selected automatically unintentionally other modules maybe I'm doing something wrong here?

[MuTools]

Ok, going back to RandArp and others like it or even simpler ones (like the one on the real Pro One) you just turn them on select up, down or up/down and away you go, the arpeggios follow what you play dynamically, add notes here drop notes there, the key words are play and dynamically, not just pressing one key. Hope I'm making sense

I do understand that you like the simplicity of those other arps ie. that they instantly generate notes without having to program a pattern. But what i don't understand is what you are missing when inserting the preset i made. That arp preset also gives you an instant typical arp result without having to program anything. Right? And to avoid confusion: i'm not arguing to prove that the m7 arp is good, i'm especially critical about it at this point (still test phase!) and want to double-check with you guys whether it's a good design or whether something is wrong/missing.

[MuTools]

I encountered a strange problem in modular area, when you drag a mux or a module from the rack/mux in modular area and vice versa sometimes disappear inputs and outputs of the mux module/mux dragged(This happened with the step sequencer patch posted before),I can not reproduce the error but maybe there is something wrong. Other times always in the modular area when you drag a module/mux are selected automatically unintentionally other modules maybe I'm doing something wrong here?

Please try to find a repeatable pattern in it, or make a screen video that visualizes the issue. Thx.

[pljones]

Ok implemented in the next version.

Thanks - wasn't a big problem in the end (once I realised I could hold a key down).

Next one... Now the rack has a power button, it would be nice if it was really easy to have "Automatic input focus" select a rack (e.g. when its any of its controls are clicked). At the moment, a track can target a rack but input focus cannot - which isn't consistent with other targets, as far as I've noticed.

What this means is I can't just switch between racks by turning one off and the next on, I have to turn a rack off, collapse it, turn the next on, un-collapse it and click on the first populated rack slot.

[MuTools]

I don't follow. Lets use an example: Pls open demo project AirTime. When you click the rack names, MIDI input focus is auto switched to that rack. Right?

[pljones]

I don't follow. Lets use an example: Pls open demo project AirTime. When you click the rack names, MIDI input focus is auto switched to that rack. Right?

Yes but on a collapsed rack, e.g. "Wide Square Bass Rack", now there are two controls on the top bar, I have "(o) (o) W" visible, with only the "W" (and a few pixels top bar border) that I can click to change input focus. If it was any control, or indeed anywhere on the rack at all, it would make it easier. Very few pixels are left .

It would at least reduce the number of clicks.

[MuTools]

Mmm, i'm not sure if clicking the collapse/expand should focus the track, in fact i think it should not. About the on/off: It would be a bit weird that when switching a rack off it gets MIDI focused, right? So the only option to be evaluated, imho, is whether to auto focus a rack when switching it on. About the 'small amount of pixels' to select a collapsed track: 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?

[Taifunk]

I encountered a strange problem in modular area, when you drag a mux or a module from the rack/mux in modular area and vice versa sometimes disappear inputs and outputs of the mux module/mux dragged(This happened with the step sequencer patch posted before),I can not reproduce the error but maybe there is something wrong.

Please try to find a repeatable pattern in it, or make a screen video that visualizes the issue. Thx.

tried and tried several times the problem does not recur ,I can not replicate the error if it occurs again I'll try to to make a screenshot

Other times always in the modular area when you drag a module/mux are selected automatically unintentionally other modules maybe I'm doing something wrong here?

is automatically selected also the source rack,nothing strange was my mistake forgive me

[bibz1st]

I do understand that you like the simplicity of those other arps ie. that they instantly generate notes without having to program a pattern. But what i don't understand is what you are missing when inserting the preset i made. That arp preset also gives you an instant typical arp result without having to program anything. Right? And to avoid confusion: i'm not arguing to prove that the m7 arp is good, i'm especially critical about it at this point (still test phase!) and want to double-check with you guys whether it's a good design or whether something is wrong/missing.

with the preset you made, by pressing one key the arp runs through each note in the pattern over and over til I take my finger off, what I like with the other arps is, just select which direction to run through, up or down or whatever and it only plays the notes you hold down.
I just think there could/ should be a simpler option as well as the sophisticated one
Wow, I sound like I'm whining but I'm not honestly,

[runaudio]

what would be great on the step seq is give you were able to name the notes like say when you have a drum beat kick snare and so on just saying as a idea sorry just found out how to change things name