billp Posted May 15, 2021 Share Posted May 15, 2021 Maybe I don't understand the otherwise excellent new tempo map. Any ideas on why a "delete hole" would behave like this? Sorry for the big images. 1 Link to comment Share on other sites More sharing options...
David Baay Posted May 15, 2021 Share Posted May 15, 2021 Looks like a bug. Try enabling Ripple Edit All. Link to comment Share on other sites More sharing options...
billp Posted May 15, 2021 Author Share Posted May 15, 2021 Thanks David. I'll set that and see if I run into it next time. I've subsequently noticed that the markers did not reposition either, even though they were selected in the delete options. Link to comment Share on other sites More sharing options...
msmcleod Posted May 15, 2021 Share Posted May 15, 2021 @billp - thanks for pointing this one out. It's been fixed and will be included in the official release. Link to comment Share on other sites More sharing options...
billp Posted May 16, 2021 Author Share Posted May 16, 2021 Thanks Mark. Looks like the Aim Assist was fixed as well. Link to comment Share on other sites More sharing options...
Tez Posted May 16, 2021 Share Posted May 16, 2021 @msmcleod Not sure if this is a bug but, in the Tempo inspector if there's just the initial tempo node (M.B.T 1:01:000) and a later node is added for the same tempo value, just that single node appears, but if the tempo value is different 2 nodes appear 1 at the desired M.B.T. and 1 at the end of the project. This seems like odd behavior? Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now