Right now it creates one frame per second (red dotFPS ??? Please explain once again exactly what it means.![]()
Right now it creates one frame per second (red dotFPS ??? Please explain once again exactly what it means.![]()
You can adjust the Speed x. For example, at x4 speed, one step equals 0.25 seconds.Right now it creates one frame per second (red dot), is it possible to have more red dots per second, 2 or 3 for example?
![]()
Thank you!You can adjust the Speed x. For example, at x4 speed, one step equals 0.25 seconds.
There was a minor hiccup for me when updating from V0.4:14mhz updated MultiCurveMapper with a new update entry:
MultiCurveMapper v0.6 20260713
Read the rest of this update entry...
Thanks, I will check it out later! Looks very good, and scrubbing with the mouse is going to be very useful as well!@babul , The implementation of precise mouse picking synchronization between graphs has been completed.
When the plugin is in a disabled state, mouse events do not work and therefore none of the functions operate, which is the expected behavior.@14mhz: I had a small issue with V0.6: The "Set filter" and "Set target" buttons won´t work if the plugin is disabled. All other buttons in the tab work as intened.
Agreed, I think that would be consistent.When the plugin is in a disabled state, mouse events do not work and therefore none of the functions operate, which is the expected behavior.
On the contrary, if events are processed by the Graph while the plugin is disabled, that is an abnormal condition.
How about modifying it so that, when in the disabled state, the Graph does not receive events at all?
The issue where files saved with Save Function do not reappear when saved again using Save Function is actually a chronic problem of the VAM API I use, namely SuperController.singleton.fileBrowserUI. In my other plugins I worked around it by forcing a refresh, but I hadn’t applied that trick in MultiCurveMapper.Agreed, I think that would be consistent.
That said, I am very happy with the plugin as is...
By the way, it seems that VAM does not show a plugin tab preset that was saved just before.
In order to display the preset for loading, I have to jump to the folder above and back, to force a refresh of the folder containing the presets.