what do you mean by more point details? we can set specific value for any point via inspector panel. the only thing missing is ability to also set specific time-wise value for the point, but it’s mostly due to the fact that other points may collide with this setting, so the solution would be to set up a vertical snapping grid corresponding to time division you want, considering that 1 unit in Segments corresponds to chosen timebase (be it bar, second, millisecond, etc), so you divide that accordingly.
Great question.
So in the current interface you can select a point and in the inspector specify a specific y value percentage value to 1 decimal point. I would suggest to have the same for the x value.
In addition, I’d like to be able to see the display in millseconds, both on the graph and in the inspector. It would change when BPM or time division changes.
When the modulator is directly connected to a target, it would be nice if the display could show appropriate units. An example is that when connecting an MSEG to pitch modulation on a sine, and setting the amount to 120st then every 10% in the y value turns out to be an octave. This is great, but is not clear at all in the interface. Then if you change 120st to say 95st you have to make inconvenient calculations in the MSEG for percent to some semitone value.
It seems all this could be switchable in the UI since internally, those conversions are already happening.
perhaps it would be convenient if it relayed selected timebase to the editor for X axis, so it’s more apparent at glance what 1 unit stands for.
as for editing timing of the point, perhaps they had some dificulty dynamically clamping min-max range of the value according to points around the selection, but still they should implement this, as this already exists for automation editing.
as for value units on the y axis of the graph, I’m afraid that wouldn’t work, because modulators can be mapped to anything at the same time dynamically, so what would it supposed to display then as a point value? again, as a workaround you can simply use grid snap settings that would reflect the set range in appropriate steps, and additionally when you edit the value of the point, you can do the calculation on the spot by inputing simple equation as a value.
But I guess once solution could be to have a drop-down box beside value input to select desired value type and then select source for the range from established modulation routings. could be a pain in the ass to implement though for devs, but it’s an idea worth considering.