Antoine Colombier

That sounds reasonable. Are we happy with something like this? ```xml ... ... ``` Would be nice to hear your thought @JoergAtGithub and @daschuer

So just two summarise the two suggestion options: ## 1. Mapping define a namespace in manifest This means that two mapping meant to work together (e.g S4Mk3 controller & screen)...

> Thats easy to do if you're the author of both mappings. It's virtually impossible if it would have to match with any other mapping. If you need to share...

I have added namespace restriction. Hopefully this is heading toward the right direction. > I think it would make it more clear how it works While this provide more visibility...

Yeah, that widget definitely would need some refactoring, but I think the deal was to remove it before we merge that feature, and is only here to facilitate testing, thus...

Ah I had misunderstood the plan for that. Sounds good then, I try and see if I can use the effect state indicator used in the effect bar instead of...

Please note that UI changes (1st and 3rd commits) will be moved to https://github.com/mixxxdj/mixxx/pull/13515 once this PR is ready to be merged!

I have removed the UI widget, so this PR should be ready for merge. If you wish to test it with the UI widget, you can use the branch `feat/add-quick-fx-on-stem-with-ui`

> fx standard disabled when a track is loaded I will look into this. There is already a setting for mute/volume, so it makes sense to extend it to FX...

QML GUI integration should be functional and I intend to have it fully usable there, so if it's not, it's a bug that I should fix!