+1 for this feature!
4 Likes
+10, I’d say. I really think this feature, quite easy to implement, would open up new worlds in adaptive music. Please make it soon, at least on the volume!
4 Likes
+1 for the feature!
You can currently do this using mixer snapshots but the setup is not as clean as you might want it, since it involves using two windows and you won’t have the benefit of seeing automation curves.
- Under a Music mixer group make a dedicated Return for each track.
- Remove all automation from each track and set each track’s volume to 0.
- Insert a send before each track’s volume and send it to that track’s own Return.
- Create a few mixer snapshots and add those snapshot instruments to each of their corresponding labeled parameters’ stacks.
- On each of those snapshot instruments’ Intensity, add an AHDSR!
There will be a little weirdness with how the snapshots behave while one’s attack fade is fighting against another’s release. If you play with the curves a bit you can get it to behave more as expected. Do your best to ballpark equal-power curves on the attack and release. Only scope in the channels you need to. I feel like I prefer how the Overriding behavior works in this case.
3 Likes
@magomusica, yes, that’s neat (though a bit heavy to implement…). That’s in line with some suggestions I’ve given here, though we were talking about the “submixes” version of vertical adaptive music (this post is more about the “stems” version). However, this upcoming feature would work in every case and make things a lot easier.
The fact is, in my actual projects I don’t need that feature. But… it’s so obvious it would be great, that I request it anyway!
Just to clarify, what you are asking for is property seek speed? So in our terminology, the parameter is the input and the thing that is being automated is the property. Seek speed currently only applies in the parameter space, so to get a smooth change of property you have to transition through all the values of the parameter. If we had property seek speed, you could jump from one parameter value to another and the property values would interpolate.
Labelled / discrete parameters don’t specifically factor into this, internally they are just continuous parameters that report to properties in integer increments. This is why parameter seek speed works with them. If we had property seek speed, I believe you would get the desired result, i.e. jumping from label A to label D cause the property to interpolate between the property values at those two points, rather than going via the values of label B and C.
For your labelled parameter use case, jumping to different EQ values, I believe if the labelled parameter automated a continuous parameter, then that continuous parameter automated the target property you could achieve your goal. The continuous parameter would need seek speed on it to do the smoothing, but it would follow the curve you set.
+1 as well! this would help a lot when you are doing adaptive mixing inside of referenced events within a main event…
1 Like
+1
Yep this is exactly the feature i am looking for too for the same setup with event instruments as you mention.
+1 for this
+1 on this request. Smooth transitions between Discrete parameters would be a game changer. Would make my current project so much more efficient
+1 Yes please, I am building an ambience system as we speak and having this feature would be extremely useful. If I had to do this currently, I would need to map in code which value correspond to which label
+100 yes please would be very welcome
1 Like
Would also be very interested in this!
+1 would be a very nice feature to have
+1 Would definitely be interested in this! Any news about this feature?
Development is ongoing; currently, the changes made as part of this task are being reviewed to try and catch any bugs and issues in the code.
I’ll add your name to the list of people interested in this feature.
I am also interested in this feature
Thanks! I’ll add your name to the list.
+1 for this feature!
Thanks! I’ll add you to the list.