Meaning of errors in the log

merryl0 · May 13, 2023, 10:35am

Good morning @Paul
Can you tell me what these errors mean?

2023-05-13T11:08:22 [INFO]: AlsaAudioBackend: adjusted output channel count to match device.
2023-05-13T11:08:22 [INFO]: AlsaAudioBackend: adjusted input channel count to match device.
2023-05-13T11:08:22 [INFO]: Scanning folders for bundled LV2s: /opt/ARDOUR-7/lib/LV2
2023-05-13T11:08:24 [WARNING]: LV2https://github.com/HiFi-LoFi/KlangFalter: Unsupported required LV2 feature: ‘LV2 Buf Size’.
2023-05-13T11:08:24 [WARNING]: LV2https://www.jahnichen.de/plugins/lv2/BShapr-cv: Port 6 (‘CV Output 1’) has no known data type
2023-05-13T11:08:24 [WARNING]: LV2https://www.jahnichen.de/plugins/lv2/BShapr-cv: Port 7 (‘CV Output 2’) has no known data type
2023-05-13T11:08:24 [WARNING]: LV2https://www.jahnichen.de/plugins/lv2/BShapr-cv: Port 8 (‘CV Output 3’) has no known data type
2023-05-13T11:08:24 [WARNING]: LV2https://www.jahnichen.de/plugins/lv2/BShapr-cv: Port 9 (‘CV Output 4’) has no known data type
2023-05-13T11:08:24 [WARNING]: LV2urn:juce:Vex: Unsupported required LV2 feature: ‘LV2 Buf Size’.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [WARNING]: VST3</usr/lib/vst3/deadlab_bluelab/BL-RebalanceStereo.vst3>: Invalid Module Path
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:25 [INFO]: Cache file is valid and up-to-date.
2023-05-13T11:08:26 [INFO]: harvid version: 901
2023-05-13T11:08:27 [INFO]: Loading menus from /opt/ARDOUR-7/etc/ardour.menus
2023-05-13T11:08:30 [INFO]: Loading user ui scripts file /home/mel/.config/ardour7/ui_scripts
2023-05-13T11:08:30 [INFO]: Loading plugin order file /home/mel/.config/ardour7/plugin_metadata/plugin_order
2023-05-13T11:08:38 [INFO]: Loading history from /home/mel/Music/Audio/day23/day23.history
2023-05-13T11:24:57 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2023-05-13T11:24:57 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2023-05-13T11:24:57 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2023-05-13T11:24:57 [INFO]: Loading user ui scripts file /home/mel/.config/ardour7/ui_scripts
2023-05-13T11:24:57 [INFO]: Loading plugin order file /home/mel/.config/ardour7/plugin_metadata/plugin_order
2023-05-13T11:24:57 [INFO]: Loading history from /home/mel/Music/Audio/120DayPerc/120DayPerc.history
2023-05-13T11:28:06 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2023-05-13T11:28:06 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2023-05-13T11:28:06 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2023-05-13T11:28:08 [INFO]: Loading user ui scripts file /home/mel/.config/ardour7/ui_scripts
2023-05-13T11:28:08 [INFO]: Loading plugin order file /home/mel/.config/ardour7/plugin_metadata/plugin_order
2023-05-13T11:28:16 [INFO]: Loading history from /home/mel/Music/Audio/day23/day23.history

I’m using Ardour 7.4 on AVL 21.3 and I’m finding it very buggy.
Yesterday I posted in uncategorized about unwanted duplicate copies and time stretch crashes.
If I could understand some of the problems, maybe I could do something to workaround them.
Many thanks

x42 · May 13, 2023, 11:04am

Can you double-check Menu > Help > About

The following messages should not be present in 7.4

It seems that you use 7.3 or earlier.

merryl0 · May 13, 2023, 11:10am

Yes Robin, you’re right. Doh! I will start again
Many thanks

merryl0 · May 13, 2023, 11:19am

But Im using 7.4 now and still time stretch is crashing Ardour as soon as i press play after stretching.
Heres 2 screen shots.
I imported 4 bars each of 2 seperate mono precussion tracks recorded at 111bpm, which I then bounced without processing to see if shorter clips worked without crashing. Im using the time tool to make them 4 bars at 120bpm
Heres the timestretch dialog. You will see the percentages are different for the 2 clips?

Defo using 7.4 now

Heres the log at session start
2023-05-13T12:17:29 [INFO]: AlsaAudioBackend: adjusted output channel count to match device.
2023-05-13T12:17:29 [INFO]: AlsaAudioBackend: adjusted input channel count to match device.
2023-05-13T12:17:29 [INFO]: Scanning folders for bundled LV2s: /opt/Ardour-7.4.0/lib/LV2
2023-05-13T12:17:31 [WARNING]: LV2https://github.com/HiFi-LoFi/KlangFalter: Unsupported required LV2 feature: ‘LV2 Buf Size’.
2023-05-13T12:17:31 [WARNING]: LV2https://www.jahnichen.de/plugins/lv2/BShapr-cv: Port 6 (‘CV Output 1’) has no known data type
2023-05-13T12:17:31 [WARNING]: LV2https://www.jahnichen.de/plugins/lv2/BShapr-cv: Port 7 (‘CV Output 2’) has no known data type
2023-05-13T12:17:31 [WARNING]: LV2https://www.jahnichen.de/plugins/lv2/BShapr-cv: Port 8 (‘CV Output 3’) has no known data type
2023-05-13T12:17:31 [WARNING]: LV2https://www.jahnichen.de/plugins/lv2/BShapr-cv: Port 9 (‘CV Output 4’) has no known data type
2023-05-13T12:17:31 [WARNING]: LV2urn:juce:Vex: Unsupported required LV2 feature: ‘LV2 Buf Size’.
2023-05-13T12:17:32 [WARNING]: VST3</usr/lib/vst3/deadlab_bluelab/BL-RebalanceStereo.vst3>: Invalid VST3 Module Path: ‘’
2023-05-13T12:17:32 [INFO]: harvid version: 901
2023-05-13T12:17:33 [INFO]: Loading menus from /opt/Ardour-7.4.0/etc/ardour.menus
2023-05-13T12:17:36 [INFO]: Loading user ui scripts file /home/mel/.config/ardour7/ui_scripts
2023-05-13T12:17:36 [INFO]: Loading plugin order file /home/mel/.config/ardour7/plugin_metadata/plugin_order
2023-05-13T12:17:44 [INFO]: Loading history from /home/mel/Music/Audio/day23/day23.history

peder · May 13, 2023, 11:28am

Unless the plugins causing warnings are an integral part of your workflow I’d start by moving them out of Ardour’s search path, to minimize the chance of one of them being the culprit.
I’d also rename the ~/.config/ardour7 folder to something like ardour7_org just to make sure there aren’t any weird settings there.

It could also be some problem with Ardour’s interaction with the particular Rubberband version in AVL 21.3

merryl0 · May 13, 2023, 11:38am

Thanks Peder. These plugin warnings seem to be hyperlinks. I cant find them in /opt/Ardour7.4/lib/LV2 or ~/.LV2. Can you give me a precise instruction please
Many thanks

peder · May 13, 2023, 11:47am

If you haven’t renamed your ardour7 folder already you should be able to find the LV2 plugins by running something like
grep -iE "KlangFalter|BShapr-cv|Vex" ~/.config/ardour7/plugin_metadata/scan_log | sed 's/ /\n/g' | grep "file:"

The VST3 appears to be in /usr/lib/vst3/deadlab_bluelab , according to the warning.

merryl0 · May 13, 2023, 12:01pm

Thanks Peder
I removed the VST.
I had renamed the config to ardour7_org, so I ran
root@mx:~# grep -iE “KlangFalter|BShapr-cv|Vex” ~/.config/ardour7_org/plugin_metadata/scan_log | sed ‘s/ /\n/g’ | grep “file:”
grep: /root/.config/ardour7_org/plugin_metadata/scan_log: No such file or directory

But no luck.
I will try starting Ardour 7.4 again and see if stretch is still crashing

peder · May 13, 2023, 12:05pm

Weird.
But in any case the plugins are probably in either /usr/lib/lv2 or /usr/local/lib/lv2

Oh, you’re running the grep command as root but your Ardour sessions as user mel.
So run
grep -iE "KlangFalter|BShapr-cv|Vex" ~mel/.config/ardour7/plugin_metadata/scan_log | sed 's/ /\n/g' | grep "file:"

Also you need to rename the ~mel/.config/ardour7 folder.

x42 · May 13, 2023, 12:15pm

You can ignore those Warnings. They just inform you that there are plugins on your system that Ardour cannot use.

Per Plugin Details

BSharpr-cv has CV (control-voltage) ports. They are useful for modular synths, Ardour does not support those.
RebalanceStereo.vst3 does not meet VST3 specs. It is likely a single file, not a bundle.
Klangfalter requires a fixed buffersize - it is an old convolver that requires power of 2 samples every process cycle. Ardour cannot guarantee that (e.g. when automation is used or when looping, there can be multiples partial cycles).

In any case, plugins do not have any effect on the built-in time-stretch tool.

I have just tested a similar scenario: stretching a 120 BPM Beat to a 130 BPM session, and this works and plays just fine.

To get to the bottom of this, please have a look at https://ardour.org/debugging_ardour and file a bug report at tracker.ardour.org.

–

In short: install a debug version of Ardour (e.g. current https://nightly.ardour.org, demo is fine, and can be installed in parallel to distro versions). Launch it inside a debugger from a terminal window

/opt/Ardour-7.4.0/bin/ardour7 --gdb

inside gdb type run (press enter). Do something that crashes Ardour, which returns you to the gdb prompt. then type thread apply all bt (press enter), which can produces many pages of output. Add them to the bug report at tracker.ardour.org

merryl0 · May 13, 2023, 12:17pm

Thanks Peder
I moved the 3 lv2 folders to /usr/BadPlugins.
I started Ardour again and remade the config folder.
Should i now delete the old ardour7_org folder?

peder · May 13, 2023, 12:21pm

Keep it as a backup in case you’ve made specific settings that you’d like to keep.
Starting with a fresh .config/ardour7 is just for debugging purposes.

But as Robin says, there doesn’t seem to be anything inherently wrong with Ardour’s time stretching, so it could be something specific to your particular installation.
You should ping GMac to see if there are any known issues with time stretching in AVL.

merryl0 · May 13, 2023, 12:22pm

Will do thanks Robin and Peder

merryl0 · May 13, 2023, 12:53pm

Hi Robin
I installed the nightly build. Unfortunately I mistakenly pressed Y to uninstalling 7.4.0
Anyway, when I ran the debug instruction:
mel@mx:~
$ /opt/Ardour-7.4.72-dbg/bin/ardour7 --gdb
/opt/Ardour-7.4.72-dbg/bin/ardour7: 49: exec: gdb: not found

The nightly runs when I launch it from the start menu
What should I do now please?

merryl0 · May 13, 2023, 1:05pm

PS
this is what happened when i types the handle command
handle SIG32 noprint nostop
bash: handle: command not found

peder · May 13, 2023, 1:12pm

means that AVL doesn’t have the gdb (Gnu DeBugger) program installed and I’m not sure if there is an easy way to install it but you can try running sudo apt-get install gdb or sudo apt install gdb and hope for the best.

The handle command is something you run inside of gdb , so that’s why it fails.

merryl0 · May 13, 2023, 3:17pm

Good afternoon
I installed gdb
then did the timestretch and then submitted the report
Many thanks for your help

merryl0 · May 13, 2023, 4:10pm

I would just like to add that for changing from 111 to 120bpm, the timestretch percentage shows as 87.1%, which doesn’t make sense. The bar count is 4 exactly, but the sample inside the region is right off time (16th notes) when the original had excellent accuracy:

original sample at 111bpm

timestretched sample at 120bpm.
I used the unpitched percussion setting with minimise time distortion checked

merryl0 · May 13, 2023, 4:37pm

It looks like it is something to do with AVL21.3.
I installed Ardour 7.3 ds0 from the debian repoistory on my laptop running debian12 and timestretch works perfectly.
The percentage is sensible and the stretched sample is nicely in time
@GMaq do you know of anything in AVL which may be causing problems with ardour 7?
Many thanks

merryl0 · May 15, 2023, 9:44am

Having imported the clips I timestretched correctly in Adour7.3 ds0 on debian12, into my current project in Ardour7.4 on AVL21.3, Im finding It crashes within a few seconds of pressing play.
I’m adding the crash data to bug 0009332 in a minute
Many thanks