MuTools

bibz1st · Post by **bibz1st** » Mon Nov 28, 2016 12:06 pm

Were you using your computer keyboard to play notes at the time or just letting the sequence PLAY, sometimes if using the pc keyboard to play whilst changing values on screen with the mouse can cause that to happen.

pljones · Post by **pljones** » Mon Nov 28, 2016 1:24 pm

Hi,

Here's a strange problem. I've not tried it in earlier versions of MuLab, just 7.2.9.

I have a project with one sequence (32 bars, 1 beat notes ascending over four octaves in semitones, first time at vel=110 second time at vel=44, plus some scattered Foot Controller events at value 64), which is in use on two tracks. The first track targets a rack containing a User MuX preset containing Kontakt 5.6.1; the second track targets a rack containing a User MuX preset containing Sforzando 1.877. (The MuX presets contain two racks containing the sample player plus assorted effects; the only difference in cases is the sample player and this is all likely irrelevant!) Here, I'm using the internal MuX to handle the presets.

Now, I open the sequence in the list editor.

First problem is that it takes up to six seconds to select an event (between clicking the event and it getting highlighted).

The second problem is the context menu in the list editor looks very wrong -- it isn't providing any contextual menu commands for operating on the events, just Part and Sequence level operations. So "Delete" either deletes the entire part or the entire sequence -- not the selected events.

---

Just repeated using Factory New template, creating a sequence containing eight notes and some controller events, then trying to edit in the list editor. Same delay, same context menu problem.

*EDIT*
Using the keyboard to navigate the list does not trigger the delay.

Nychthemeron · Post by **Nychthemeron** » Mon Nov 28, 2016 1:31 pm

bibz1st wrote:Were you using your computer keyboard to play notes at the time or just letting the sequence PLAY, sometimes if using the pc keyboard to play whilst changing values on screen with the mouse can cause that to happen.

No I never use the pc keyboard, the sequence was just playing. there do was an external usb midi keyboard plugged in, within the range of my elbows so it's possible I accidentally hit a key on that while adjusting the value but that's all I can think of. Sorry if I'm not explaining it clearly, maybe I need more examples

pljones · Post by **pljones** » Mon Nov 28, 2016 1:42 pm

Another tiny bug. In the Key Editor, the lower lane defaults to showing Note Velocity. The tooltip for the event "value 2" parameter says "Velocity", too, which is nice. However, if you change over to viewing controller values, the tooltip still says "Velocity"... which is wrong

. (No idea how long this one has been lurking...)

bibz1st · Post by **bibz1st** » Mon Nov 28, 2016 2:28 pm

Nychthemeron wrote:
bibz1st wrote:Were you using your computer keyboard to play notes at the time or just letting the sequence PLAY, sometimes if using the pc keyboard to play whilst changing values on screen with the mouse can cause that to happen.
No I never use the pc keyboard, the sequence was just playing. there do was an external usb midi keyboard plugged in, within the range of my elbows so it's possible I accidentally hit a key on that while adjusting the value but that's all I can think of. Sorry if I'm not explaining it clearly, maybe I need more examples

The explanation is fine, I dont think it happens when using midi keyboard so its probably not that then, one for Jo

Nychthemeron · Post by **Nychthemeron** » Mon Nov 28, 2016 7:04 pm

thanks anyway, it's something I've seen in other daws as well it's nothing huge but sometimes it breaks up my workflow a little. thanks for the quick replies to all of you and I assume the panic button is a good enough 'fix'

MuTools · Post by **MuTools** » Mon Nov 28, 2016 10:27 pm

pljones wrote:First problem is that it takes up to six seconds to select an event (between clicking the event and it getting highlighted).

The issue is that it only gets highlighted after the mouse has moved at least a pixel, due to a recent new bug, which will be fixed asap. Thx for reporting this!

The second problem is the context menu in the list editor looks very wrong -- it isn't providing any contextual menu commands for operating on the events, just Part and Sequence level operations. So "Delete" either deletes the entire part or the entire sequence -- not the selected events.

Indeed there are no context functions for events yet. If you want to deleted the selected events in the Event List press the Delete key or click the Delete button at the bottom.

MuTools · Post by **MuTools** » Mon Nov 28, 2016 11:08 pm

pljones wrote:Another tiny bug. In the Key Editor, the lower lane defaults to showing Note Velocity. The tooltip for the event "value 2" parameter says "Velocity", too, which is nice. However, if you change over to viewing controller values, the tooltip still says "Velocity"... which is wrong . (No idea how long this one has been lurking...)

Thx! Will be fixed in the next version.

MuTools · Post by **MuTools** » Tue Nov 29, 2016 12:06 am

There is a new MuLab 7.2.10 in http://www.mutools.com/galaxa/

What's new:

Event List Editor: Clicking events only highlighted them after the mouse was moved again. Fixed.
Sequence editor: Event Property Panel tooltips were not always the right ones for the selected event type. Fixed.

How to install:

Windows: Put the new .exe and .id files into an existing M7.2 installation folder.
Mac: Put the new .app file into an existing M7.2 installation folder.

Grizzellda · Post by **Grizzellda** » Tue Nov 29, 2016 1:42 pm

Jo, here's a question: when you overhauled the font system for MuLab 7, you didn't include a size parameter for the browser font. Why?

Do you think you can get this in the version 7 development cycle, or will it be later?

MuTools · Post by **MuTools** » Tue Nov 29, 2016 2:27 pm

The reason is because i don't want to invest precious r&d time in a temporary, inconsistent workaround. The real solution on the wishlist is to make the whole UI resizable, which will include all font sizes, everywhere in the UI. I cannot yet give a precise timing on when that will be realized, but it will not yet be for the very near future eventhough i regard it as relative important (together with other important todos) and take it into account while doing any new developments so that the code gets more and more ready to make that jump.

Grizzellda · Post by **Grizzellda** » Wed Nov 30, 2016 12:59 pm

Got it. MuLab sure looks and feels alot better with v7, but that browser font is way to small for such a central, usable region of the program. I'm delighted to hear that you are taking a more solid, long term approach with the whole GUI.

If I'm hearing you correctly we might see some improvement in version 8...I shall be upgrading! Actually, I'll upgrade anyway...

Thanks man

MuTools · Post by **MuTools** » Wed Nov 30, 2016 1:02 pm

Grizzellda wrote:that browser font is way to small for such a central, usable region of the program

FYI: It's the same font as used everywhere in the UI.

Grizzellda · Post by **Grizzellda** » Wed Nov 30, 2016 1:07 pm

Yeah, but the size can't be adjusted, right?

MuTools · Post by **MuTools** » Wed Nov 30, 2016 1:18 pm

Not yet, as explained in that previous post. But it's nothing specific to the browser i mean.

MuTools

KVR Audio

MuLab 7.2.24