MuLab 6.5.29 released
- KVRAF
- 3162 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Sorry, I can't at the moment as Imageshack is premium only now. I can email to you if you like, but will have to wait til I have more time, sorry.
One other thing, would it be possible to have a knob for selecting the Note number please?
One other thing, would it be possible to have a knob for selecting the Note number please?
- KVRAF
- 3162 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Ok, I took a screenshot to show part of the problem. I'll email it you now Jo.
EDIT: email sent
EDIT: email sent
- KVRAF
- Topic Starter
- 13866 posts since 24 Jun, 2008 from Europe
Thanks for the screenshot, that helps! That's an unsupported and not recommended situation. Components should not overlap in such way.
- KVRAF
- 3162 posts since 28 Mar, 2008 from a Galaxy S7 far far away
- KVRAF
- 3162 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Also, when rearranging a front panel I found it strange that frames didn't always stay in the background and covered knobs. Forcing me to move the frame to get to the knob underneath. But when the frame is moved it now moves everything it contains. Is there a way round this?
Did you notice my request for a knob for changing the Note Event Pad pitch? It would be useful for testing different pitches without filling the front panel with pads.
Did you notice my request for a knob for changing the Note Event Pad pitch? It would be useful for testing different pitches without filling the front panel with pads.
- KVRAF
- Topic Starter
- 13866 posts since 24 Jun, 2008 from Europe
You're in control over what covers what. If you want a knob to be _on_ a group frame, then drop the knob _on_ the frame.sl23 wrote:Also, when rearranging a front panel I found it strange that frames didn't always stay in the background and covered knobs.
If u don't want a knob to belong to a frame, drag-drop it elsewhere, where u want it.But when the frame is moved it now moves everything it contains. Is there a way round this?
Saw your request but that's not planned. If you want multiple pads with different pitches = keys, then there are 2 options:Did you notice my request for a knob for changing the Note Event Pad pitch? It would be useful for testing different pitches without filling the front panel with pads.
* Use multiple individual pads
* Use a Drum Note Processor. That gives you 12 pads in a single module.
- KVRAF
- 3162 posts since 28 Mar, 2008 from a Galaxy S7 far far away
- KVRAF
- 3162 posts since 28 Mar, 2008 from a Galaxy S7 far far away
I just thought that having one pad and a knob would be useful to both reduce screen space, spacing between pads can't be adjusted in the Drum Note Processor, but also you could then assign a hardware controller to it for quick adjustment/testing.mutools wrote: Saw your request but that's not planned. If you want multiple pads with different pitches = keys, then there are 2 options:
* Use multiple individual pads
* Use a Drum Note Processor. That gives you 12 pads in a single module.
Maybe for a future version?
- KVRAF
- 3207 posts since 17 Apr, 2010 from Slovenia
I would absolutely love it, if you had an easier way to determine the note per pad, that's for sure. Alone having a little interface for the DrumNote module with a note parameter per event out would be awesome for sure!
You know, Jo, over the many years of being an artist I have long since noticed a mean phenomenon: The better you make something, the more you see what's missing. It's totally classical. You are making massive strides in improving MuLab and the requests you're getting now are only a sign that you are doing the right things!

You know, Jo, over the many years of being an artist I have long since noticed a mean phenomenon: The better you make something, the more you see what's missing. It's totally classical. You are making massive strides in improving MuLab and the requests you're getting now are only a sign that you are doing the right things!
- KVRAF
- Topic Starter
- 13866 posts since 24 Jun, 2008 from Europe
I think it's the same thing: You're partially overlapping sibling components which is not supported and not recommended.sl23 wrote:Another glitch, another email
- KVRAF
- Topic Starter
- 13866 posts since 24 Jun, 2008 from Europe
sl23 wrote:I just thought that having one pad and a knob would be useful to both reduce screen space, spacing between pads can't be adjusted in the Drum Note Processor, but also you could then assign a hardware controller to it for quick adjustment/testing. Maybe for a future version?
I don't get it. Why do you want to change the note pad key 'live' while making music. I think it's more a patch design property which is defined during patch creation.Taron wrote:I would absolutely love it, if you had an easier way to determine the note per pad, that's for sure.
- KVRAF
- 3162 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Yes I appreciate that. But due to the size of the module, I had no choice. It is a bit awkward having to try to move it when most of it isn't showing and not simply because other components are in the way but because it's not visible. If it's not visible it can't be clicked on to drag it.
As the only place it can be dragged is from a visible section, this means it can cause confusion about dragging it. Why? Because the visible parts are over other components, hovering over these highlights or focuses that component, NOT the DNP which the cursor is over!
It's not a major thing but just wanted to explain, it doesn't cause too much issue, but may if you inadvertently drop a small component over something and this happens. You may not be able to see it at all or move it. Could be a pain in the arse in certain situations.
You're the dev and if you think it's ok then who am I to judge? Just trying to help

As the only place it can be dragged is from a visible section, this means it can cause confusion about dragging it. Why? Because the visible parts are over other components, hovering over these highlights or focuses that component, NOT the DNP which the cursor is over!
It's not a major thing but just wanted to explain, it doesn't cause too much issue, but may if you inadvertently drop a small component over something and this happens. You may not be able to see it at all or move it. Could be a pain in the arse in certain situations.
You're the dev and if you think it's ok then who am I to judge? Just trying to help
- KVRAF
- 3207 posts since 17 Apr, 2010 from Slovenia
I always have to hook a note modifier between the DrumNoteProcessor and the respective synth, but you always have to open the note modifier to adjust the transpose, which also involves a certain amount of guessing, of course. It would certainly be extremely elegant, if you could set the note it should play explicitly for each pad such as: [C4] [F2] [A2] [G3] [C8]...and so on, you know.
By the way, that's exactly how it works on a midi keyboard with such drum pads.
But, of course, it's in that grey-zone between convenience and need. But so many things are...
By the way, that's exactly how it works on a midi keyboard with such drum pads.
But, of course, it's in that grey-zone between convenience and need. But so many things are...
- KVRAF
- 3162 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Have you used a Korg ER-1? It has a pitch knob. I found this useful not just for patch creation but composition too! It could give some ideas on how to use different pitched drums in a project. Obviously, unless you were really accurate you couldn't record these knob movements, but it could give quick variations without going into depth. Do you see what I mean?mutools wrote: I don't get it. Why do you want to change the note pad key 'live' while making music. I think it's more a patch design property which is defined during patch creation.
- KVRAF
- 3162 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Fulfilling necessity makes a thing good, convenience makes it great!Taron wrote: But, of course, it's in that grey-zone between convenience and need. But so many things are...
