Minor bug: Event output naming after Note key splitter

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Hi,

Bought Mux the other day after playing with the free version way to late one night :)

Great stuff, can't believe it's not talked about more!

I won't bother you with feature requests right now (they're coming, hehe) but I did find a very small bug which I suspect come from reusing resources.

After creating and deleting a Note key splitter the names of some of the event outpost get names from the splitter... So I have a rack with C# and a Mux with G#...

Doesn't really matter but thought you should know. Tell me if you need screen shot or want me to try and reproduce the bug... Being a programmer myself I know how hard it can be to track these small bus down... I'm using Reaper btw, 64bit both host and Mux.

Thanks for a great product!
Top

Post

mehum wrote:Bought Mux the other day after playing with the free version way to late one night :)
Great stuff, can't believe it's not talked about more!
Please spread the word! The more MUX Modular is known, the faster development can go.
After creating and deleting a Note key splitter the names of some of the event outpost get names from the splitter... So I have a rack with C# and a Mux with G#...
Doesn't really matter but thought you should know. Tell me if you need screen shot or want me to try and reproduce the bug... Being a programmer myself I know how hard it can be to track these small bus down... I'm using Reaper btw, 64bit both host and Mux.
Yes please any additional details are very welcome, most of all a step-by-step how to reproduce the issue. Thx.
Top

Post

These kind of things tend to happen randomly but this actually seems to happen consistently. Best kind of bug :)

This is what I did to reproduce (again, 64 bit vst effect plugin in Reaper):

1. Start New patch (although it will probably occur if you edit an existing as well)
2. Add module Note Key Splitter
3. Delete Note Key Splitter
4. Add module Rack

First event output is now named A#

5. Add module Mux
Event output is named G, open it to see name in output module.

Uneducated guess is that any module with an event output that is not explicitly named (send outputs in rack are not affected) gets the name of one of the outputs. Next module will get a G# output and so on...
I suppose there's some kind of resource pool being used and that the names for objects are not reset when deleting the key splitter.
Top

Post

Did another little test:

1. Saved the patch with the bug.
2. Removed effect from track
3. Added new Mux on track and loaded patch with bug.

Result:
The Rack's first output is now named E, Event Input output is named D#, Mux output is named Event output 1 again.
So resources seem to be globally shared which means there's no use in sharing a patch where this bug has occured. It needs to be reproduced manually.
Top

Post

Thanks for your reports mehum! That bug is fixed in the next version. Until then: Don't worry it's an innocent little bug, won't cause a crash.
Top

Post

mutools wrote:Thanks for your reports mehum! That bug is fixed in the next version. Until then: Don't worry it's an innocent little bug, won't cause a crash.
Yeah, I realized that :) Though there's always a chance small quirks like this points to other problems so even if the implications are small I thought it'd be good for you to know!
Top

Post

Absolutely! Thx!
Top

Post

How are naming of outputs supposed to work, by the way?

If I name an output Aux 1, for example, it is currently not shown as Aux 1 on the connection point of the Mux module.

Regarding outputs it would be useful to be able to sort the output order. Especially when using the multiple outputs back to the host. When I've renamed them it's a bit hard to remember in which order I've created them :)
Top
Post Reply

Return to “MuTools”