I’m running self-compile debug from latest master (Increase process-thread stack size (same value as jack2) · Ardour/ardour@bc1d19a · GitHub). I’m repeatdedly runinng into issue where the last region I recorded shows the waveform fine as it is recording, but then when I press stop, the recorded region is replaced by an empty region. I don’t hear that recorded region when I playback.
and I can open those wavs and see my recorded audio in them. So ardour knows to save the audio to a file, but maybe ardour doesn’t properly load the same file back?
Maybe I shouldn’t be using git builds when recording, lol!
And it turns out that that second one shouldn’t be there. And it is actually covering up the real recorded region. Simply clicking on the that extra region and pressing delete, then I can uncover the real recorded region. So the problem is somehow for some mistaken reason, ardour thinks there is an extra region.
But it says created-with="Ardour 6.6" modified-with="Ardour 6.6-102-ge07b3104bb, so maybe I actually wasn’t using the latest git. Sorry.
Well what I think I’ll do is make sure I’m on the latest git and start a fresh session and see if it happens again. It happened a handful of times, so hopefully it will reproduce.
I had simply forgot to ./waf install the compiled build, that is why I wasn’t actually on the latest build.
I’ll try again, this time on the latest
/usr/local/bin/ardour6 --version
bind txt domain [gtk2_ardour6] to /usr/local/share/ardour6/locale
Ardour6.6.250 (built using 6.6-255-gced5918e22 and GCC version 10.2.0)
In general we recommend to just run self-builds of ardour from the source-tree without install:
cd gtk2_ardour/
./ardev
not only does that not clutter up your system’s /usr/, but it’ll also simplify debugging in case something comes up. – The only downside of doing that is that translations won’t work
ok, thanks for the tip. I started on fresh git checkout and used ./ardev to run, and started a fresh project on this latest git… Buy unfortunately I’ve managed to encounter the glitch again.
I’ve also at this moment of encounter the glitch am making a tar.gz of the project, it will be a big file, but let me know if you would like to inspect that.
Just a heads up, I had a quick look, but no explanation for this. Nor can I reproduce it.
The only issue is ambiguous capture alignment (and ambiguous I/O latency) due to parallel port connections (the “No align” button blinks). But that only leads to a region being placed incorrectly after rec-stop.
It would be preferable to file a bug report at tracker.ardour.org about this, The forum is not great to keep track of issues and it’ll likely be forgotten.
–
PS. Can you start ardour from a terminal and check the first few lines it prints. There should be a message:
Ardour: [INFO]: Your system is configured to limit Ardour to 1048576 open files
(for whatever reason, tracker.ardour.org is not sending me an email to confirm my account, and I’ve tried with both a hotmail and gmail address and looked in my spam & junk folders.)