M3 Tests

[MuTools]

He Jo there is one issue I'd like to see if you couldn't help with it might be kinda dicey though I'm not sure... Rhino is in a development phase agian and there have been some changes to the GUI and on M2.7 I was getting crashes when opening Rhino's GUI consistently. Only problem is Rhino was updated to SSE2 and my CPU apparently only has SSE1 instructions (yes i know time for a new pc) so it kind of killed me being able to test it. Although it's now portable and now M3 supports MME so I can take M3 and Rhino to another computer to test as soon as I set Rhino up for relative paths. Would you be willing to work with Tick to try to get this resolved if it persists in M3?

Yes, sure.

Note that if it crashes in Rhino, then Big Tick is the one who should do the debugging as they have the source code so they can see where and why it crashes and resolve the issue.

But if they need something from me, i'm open for email.

[bpblog]

there's a slowdown bug in the value editor. when drawing automation lines, each new line takes more time to be drawn, which after 20 or so lines results in serious hiccups. to repat the bug, just select the pitchbend parameter for example and draw the same line over and over.

btw, the new patch/preset order looks on-spot.

[sorohanro]

About the patch/preset order:

Taken all feedback into account, i think finetuning it this way:



So:

• To avoid confusion between the MuSynth group and MuSynth synth, the group is named "MUTOOLS" now, which indeed tells better what it contains
• The "Templates" subgroup is separated and renamed to "Devices"
• "Patches" are renamed to "Presets"

Sounds ok to you?

NB: The VST library idea is certainly not for M3. I'm happy to hear there is already such tool out there.

Now that's a work of art !!!
You crystallized all the best ideas in the best way. I love it!

[Improviser]

there's a slowdown bug in the value editor. when drawing automation lines, each new line takes more time to be drawn, which after 20 or so lines results in serious hiccups. to repat the bug, just select the pitchbend parameter for example and draw the same line over and over.

I've observed that too. Each successive deletion is a bit slower.

If you go back to the Composer window and select a different part (or composition), and draw automation lines for it, the deletion speed seems to be normal again, but then it too starts to suffer the same type of delay, after successive drawings and deletions.

Les J.

[MuTools]

there's a slowdown bug in the value editor. when drawing automation lines, each new line takes more time to be drawn, which after 20 or so lines results in serious hiccups. to repat the bug, just select the pitchbend parameter for example and draw the same line over and over.

Oops, this bug was already fixed, but due to an 'admin' fault it's still in there, sorry

Tuned in the next version.

[MuTools]

Now that's a work of art !!!
You crystallized all the best ideas in the best way. I love it!

Just want to say i am not 100% convinced myself, but as many people ask the same thing, i want to be flexible.

The reason why i am not convinced is that when you choose Synths -> MUTOOLS -> Devices -> Synthia, then ok you get a Synthia at first, but as soon as you select another patch, this Synthia could become a MuSynth etc. So in fact by separating Synthia, Sampla, MultiSampla and MuSynth into that Devices group, they get too much importance, imho.

But i do understand that putting the 'Devices' inside the presets list could cause some confusion too, as Sampla, MultiSampla, Synthia and MuSynth are not normal presets.

So i feel ok with doing it this new way

[pquenin]

Now that's a work of art !!!
You crystallized all the best ideas in the best way. I love it!

Just want to say i am not 100% convinced myself, but as many people ask the same thing, i want to be flexible.

The reason why i am not convinced is that when you choose Synths -> MUTOOLS -> Devices -> Synthia, then ok you get a Synthia at first, but as soon as you select another patch, this Synthia could become a MuSynth etc. So in fact by separating Synthia, Sampla, MultiSampla and MuSynth into that Devices group, they get too much importance, imho.

But i do understand that putting the 'Devices' inside the presets list could cause some confusion too, as Sampla, MultiSampla, Synthia and MuSynth are not normal presets.

So i feel ok with doing it this new way

It looks very nice and neat ! Bravo !

[pquenin]

Well, there is something that still annoy me about presets : when the plugin is a mulab's one, when you click in the preset name, you have a list of presets : if you choose a preset or click outside this window, it simply disapears and it's fine.
If the plugin is a VST, the window showing the presets has not the same look and must be closed by OK : it's irritating, and even more if you have a shorcut to this window.

[MuTools]

Well, there is something that still annoy me about presets : when the plugin is a mulab's one, when you click in the preset name, you have a list of presets : if you click outside this window, it simply disapears and it's fine.
If the plugin is a VST, the window showing the presets has not the same look and must be closed by OK : it's irritating, and even more if you have a shorcut to open this window.

True. Should be equal behaviour as in Mu plug editors. Will be finetuned.

[sorohanro]

So i feel ok with doing it this new way

Can I say on a public forum that I love you ? can I ? can I ?
Don't worry, I'm a married guy... but still...

[gemada]

Another thing: FILE, EDIT and HELP popup menus should really appear bellow the buttons...i think someone noted that it also happens everywhere (where it has buttons and menus).

100% agreed.

Practical point: We need updated buttons for the main menu, and some other places, as these buttons then need a 'down' state too. And i'm not sure if updating these graphic resources can be realized on short term.

If not, the menus-below-button thing may be put on the whishlist for later implementation.

Couldn't you just update the popup list files?
Maybe it would solve the problem without updating the buttons...

[MuTools]

Not sure what you mean...

[gemada]

Oh..i've found a gui bug...in transport panel, when you press the forward and rewind buttons their layouts don't change.

[gemada]

Not sure what you mean...

I was talking about the file PopupList.txt...i thought the "top position" of the popup menu list could be changed in there. I guess it doesn't work like that...

[liquidsound]

Jo I think the Device/Preset is perfect!
An extra touch to reach heaven:

If each MuLab device has its own little Icon

AND

each preset stored in the Preset folder shows the ICON of the synth

THEN

we can choose by Category and By Synth

WHICH

really helps in narrowing down our choices specially when this thing grows...
<edited> It not true that it's enough just to know that a Preset is a Bass, it is really important to know which Plug-in has created that sound for obvious reasons.

This could be a Very elegant addition to MuLab Simplicity and Effectiveness, beside being very efficient as already is.

This would be really really COOL