|
|
Hmm I cannot reproduce the issue. It works as you expect. Is the region split? Could this just be a visibility issue? eg. The waveform is drawn on top of the region boundaries, and in your case tose are not semi-transparent (so, depending on zoom level and signal level, you can't see the new region boundary)? I'll attach an example screenshot in a moment. |
|
|
invisible_region_bounds.png (2,625 bytes) |
|
|
jhenkins could it be this configuration issue: https://community.ardour.org/node/14221 |
|
|
x42, thanks for posting the screencap. It certainly looks interesting, but in this case the issue I am observing does not manifest like that. mhartzel, no, it does not seem to be related to the issue you described. x42, the issue is definitely there, because in the 5.10.0 version offered by the KXStudio project (as well as the official download), the region split works without an issue. Unfortunately I did not attempt to use the split tool for a while, so I cannot say with clarity with which build it stopped working. I will try to make a little screen recording tonight (never done it before, but I think that this situation warrants something like that) to illustrate this. What I haven't done yet, and will also do tonight, is to go through the build config of 5.10.0 and compare it with my broken build, and possibly doing a rebuild before doing some more testing. I will report back with the results. |
|
|
I downloaded Ardour 5.10.396 from nightly.ardour.org and can not reproduce the issue. Splitting by selecting the cut mode and clicking on an region with the mouse works fine. |
|
|
Also works when selecting multiple tracks and splitting regions on them simultaneously. No problem here. |
|
|
Well, it certainly seems that I created a bug-report for nothing at this point. I did some further testing, and I narrowed down the manifestation of this problem to be consistent with specific recording sessions. I have to conclude that I broke those sessions somehow, and that it is therefore a user issue and not an Ardour issue. If I can prove that this is a *real* Ardour issue, I will do a proper QA-style test-case and log a new issue with visuals. |
- Anonymous
