View Issue Details

IDProjectCategoryView StatusLast Update
0009981ardourbugspublic2026-03-14 09:37
Reporterpyrotek45 Assigned To 
PriorityhighSeveritymajorReproducibilityhave not tried
Status newResolutionopen 
PlatformGNUOSLinuxOS Version(any)
Product Version8.12 
Summary0009981: automation disappears when zooming in/out
Descriptiontrying to edit automation has been a headache for me. im trying to edit some modwheel automation and for some reason, when adding points to the edge. and then zooming in and out, my automation goes away?

i just wanna work on music but ive been dealing with these little issues the whole time. im not sure why the automation lane here needs to be under a midi clip. when im automating an effect from the mixer strip, it lets me edit the full lane just fine. it would be nice if i could do that for synth parameters as well. ( maybe im missing something here? )
Steps To Reproduceyou can reproduce by opening ardour.
add a new midi instrument.
add a midi clip
add some automation for the modwheel ( controller -> modwheel ) though i think this is a problem with any midi automation ive ran into
draw some automation for it, try to snap to the edge ( right edge in my case ).
zoom in or out

watch it go away.
TagsNo tags attached.

Activities

pyrotek45

2025-08-18 15:51

reporter  

pyrotek45

2025-08-18 16:06

reporter   ~0029394

also, with sections of automation like this. there should be a node at the edges of the automation late for each clip. here it just randomly goes off the side, where i cant grab or edit it.

pyrotek45

2026-03-06 23:25

reporter   ~0030059

any update? this bug was super annoying to work around.

pyrotek45

2026-03-13 23:09

reporter   ~0030107

ok, this is getting ridiculous lmao. again, i asked ai to fix this issue and it did it in less than a minute. its a single line fix. at this point i feel like my bug reports are just being ignored. this was super easy to fix. anyways hope this note helps.
image.png (49,612 bytes)   
image.png (49,612 bytes)   

GhostsonAcid

2026-03-14 09:37

reporter   ~0030110

@pyrotek45
I myself cannot confirm whether or not your three AI-given fixes are solid (i.e. won't interfere with other code elsewhere), but, if they are, it does beg the question: Will Paul or Robin ever utilize the help of AI recommendations for easier (but numerous) bug fixes/requests? Based on their previous sentiments, I would guess not.

Now, in general, they do currently seem to be sidelining about 90% of incoming bug reports, unfortunately. I think mostly because they’re working on bigger things (-like restructuring of the pianoroll, etc.). But you have to remember that they’re basically a *two-person* team, which is incredibly tiny for such a beast of a project and inflow of bugs/requests, -regardless of AI-use or not.


Also, I know from a lot of experience using AI to help with coding, the results given look SUPER convincing ***on the surface***. But, if you do it for long enough, you will discover that the AI (-even one specifically ‘trained’ for your exact software/code/DAW/etc.) is always incredibly *nuclear* in its approach, generally lacking broader awareness, which ends-up making critical errors over and over again with respect to *the larger context* of the codebase/goals. So, all in all, it’s wise to approach any AI ‘solutions’ with *a lot* of caution, instead of ‘oh, it’s totally fixed. all is good! wow, so easy!’, as I did for a long while, until I learned better. : 0 : )

Thanks for reading,
-J

Issue History

Date Modified Username Field Change
2025-08-18 15:51 pyrotek45 New Issue
2025-08-18 15:51 pyrotek45 File Added: Screencast From 2025-08-18 11-43-02_ ardourbug.webm
2025-08-18 16:06 pyrotek45 Note Added: 0029394
2026-03-06 23:25 pyrotek45 Note Added: 0030059
2026-03-13 23:09 pyrotek45 Note Added: 0030107
2026-03-13 23:09 pyrotek45 File Added: image.png
2026-03-14 09:37 GhostsonAcid Note Added: 0030110