Support functions regardless of music sheet complexity - 08/12/22 08:16 AM
When using the functions of TAG, Repeat..., the behavior of certain functions does not always correspond to what one might expect.
For example, the punch-in record doesn't go well with the TAG.
(And in my case, the cursor is positioned in an A region when I record, while the recording is finally made in a B region).
I know that people may object to me completely unfolding my grid (see recording in the DAW), and that's what I'm probably going to end up doing.
But this type of response does not seem very acceptable to me (if we deliver a feature it is not to say not to use it).
I don't understand why not all functions are compatible with TAGs, reapeat, etc.
With BIAB, when you go outside the basic standard path, the user experience can become quite unpleasant, and it does not improve over the versions.
I know life is a big race but it would be nice to finally take the time to stabilize the existing.
For example, the punch-in record doesn't go well with the TAG.
(And in my case, the cursor is positioned in an A region when I record, while the recording is finally made in a B region).
I know that people may object to me completely unfolding my grid (see recording in the DAW), and that's what I'm probably going to end up doing.
But this type of response does not seem very acceptable to me (if we deliver a feature it is not to say not to use it).
I don't understand why not all functions are compatible with TAGs, reapeat, etc.
With BIAB, when you go outside the basic standard path, the user experience can become quite unpleasant, and it does not improve over the versions.
I know life is a big race but it would be nice to finally take the time to stabilize the existing.