When a scene is duplicated the osc or midi mapings are not duplicated with it.
Why? Say I create a composition, I then assign all of my controls then I want to duplicate this scene and keep the same controls, I now have to remap 50+ controls for every duplication I make wasting my valuable time that could be spent creating more. This is a massive flaw that prevents me from wanting to make changes and kills my drive to be creative. "global shaders" fix this a little but often times I want controls on individual players not global.
Another problem is:
Above we see that there is no ability to control a specific group but only the most recently selected group. This is totally insane, you expect me to reach for my mouse and scroll through a list of 10+ different groups to click on it so that I am controlling the correct group? I don't want to control a selected group I want to control ::INSERT SEQUENCE HERE::/::INSERT GROUP NAME HERE::
I hope my concerns can be addressed as they are a major deterrent from me wanting to upgrade to a PRO license.
I hope it's just something I am missing and if so I hope that I could get help to be able to fix this, thanks.
-KC
-
Hi Brandon,
- Regarding the first issue, we do understand it's a limitation for certain assignments, especially shader paramaters. It's in our roadmap, it's been kicked out of the shortlist for 2.12 unfortunately but we do intend to implement this in the near future. Sorry for the inconvenience.
- As for the second issue, we wanted to implement a choice at first and let you choose to target the selection or a specific element when you add an assignment, but due to technical reasons it had to be pushed back, so we had to make the choice ourselves. We felt that in the live user projects we had observed, it would allow more flexibility (and use less MIDI buttons) to target the parameter of the selected group. Obviously this cannot cover all use cases, as you're experiencing first hand.
However, we do not "expect [you] to reach for [your] mouse and scroll through a list of 10+ different groups to click on it", you can use assignments to change the selected group via MIDI, OSC, etc.
On a MIDI controller for instance, this usually lets you have a column of buttons to choose the group and the rest of pads to change effects. As for OSC, you could even give both actions to a single button, for instance sending successively/sequences/seq4/groups/group2/select
/sequences/edited/groups/selected/outline/border/toggle
Those are the workarounds at the moment if the default does not fit your setup.
Have a nice day!
0 -
I guess I need to learn about OSC more to be able to do those things.
If you could make the command field editable I would be able to direct my OSC commands within Heavy M"However, we do not "expect [you] to reach for [your] mouse and scroll through a list of 10+ different groups to click on it", you can use assignments to change the selected group via MIDI, OSC, etc."
Just started using the more recent version 2.11.4, this must be a new feature or I missed it in the last one, thanks.
Thank you for you continued support and improvements!!0 -
Hi again Brandon,
Oh yes I should have mentioned that the possibility to select a group via Controls has been added only in 2.11, sorry about that!
You mean "make the Command field editable" so that you could change the target, like chose to write "SelectedSeq / SelectedGroup" instead of "Seq 1 / Group 2" here for instance?
Thanks for the kind words and support, that means a lot.
0 -
Sorry I was in a hurry when I made that screen shot, his is the main issue.
When I assign a shape effect like outline it does not target the sequence or group like it does with the opacity slider.
ie
but since you have added the ability to assign groups this may be my solution. But if I did want direct control the only way I can think to do it is allow me to edit this field directly.Edit: So at present I would have to make a duplicate shape group and assign a slider to the opacity to switch between the two, tanking my performance in the process and adding unnecessary complexity. (this is me still thinking in 2.10 since many things broke when I tried to move to 2.11 I stayed away from it for a while(ndi became disabled when I needed it, I think you have fixed it but have not had an opportunity to test I will get back to that support ticket when I have the chance to verify (my setup is constantly in flux sorry!!)))
0 -
Ok I got it, thanks!
Yes we've fixed an NDI issue in the 2.11 patches. If you have any problem, let us know via a private ticket with your logs and configuration.
Have a nice day!
0 -
Here is a direct example of the problem in action, this time with a midi mapping.
https://drive.google.com/file/d/1UyP1thiPAU9XKsVIB5Tfu_4Nlaj4vvy_/view?usp=sharing
In the above clip Because the MIDI assignment Command assigns to SelectedSeq/SelectedGroup/ I can't map the rotation of 2 separate groups to 2 separate knobs so that I can control their rotations real time separate from each other. :(
0 -
Hi Brandon Wooldridge, not sure if that could help you/save you some time but since you're getting into OSC, we've released 3 ready-to-use TouchOSC templates for HeavyM 2.11 last week.
You'll find them at the top of the OSC API article. They are customizable and made to be easily copy-pasted from, so you can retrieve objects in them to build your own templates.
0
Please sign in to leave a comment.
Comments
7 comments