-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Insert a value when deleteing automation on row 0 #99
Comments
I'm not sure what you mean. If you hit I'm not sure why you need to go into the automation in REAPER to create a new initial point. Why can't you just enter it from within HT? I'm not opposed to adding a flag in the config for auto-adding a first point, but what value would that point need to have? I think I don't understand exactly what you mean, and what your intended workflow is. Could you maybe make a short screen recording? |
Yeah sorry I was gonna delete this because I think what I'm doing wrong is creating a media item at the beginning of a project. Otherwise the first point can be deleted without issues. Might also be something in my automation settings or in your settings that pushes media items forwards / backwards. I only suspect this because sometimes Reaper will fail to trigger the first hit of midi in the piano roll when it's the first thing in a project. So it might be a Reaper issue and the workaround is to move items forward a bit which is fine. |
Ah, I have just reproduced that weirdness at time point zero. That is indeed odd. It seems that the automation system returns |
As it is right now, a big issue for me when using the app for automation is if you accidentally hit '.' on row zero. It enters a 00 but Reaper allows automation at the beginning of a section to be absent and simply jumps to the next point. So while I remember you saying that this is a limitation of Reaper, I think the best thing to do would be to force a point to be created the first row. Right now you have to go into the automation in Reaper and create an initial point, then re-launch hacky-tracky to fix it.
The text was updated successfully, but these errors were encountered: