Ardour 8.6 released

Blog
#9

Is that the official binary, a distro version or a self-compiled?

Could it be that the plugin Window opens behind the main Ardour window?

What Desktop environment do you use? If it’s KDE, perhaps try to enable Ardour Preferences > Appearance > Quirks > All floating windows are dialogs.

Is there a message in Ardour Menu > Window > Log ?
…or if you run Ardour from a Terminal Window, any message printed there?

So far indeed only you and an unknown number of others who have not bothered to report it.

#10

Hi,

For the sake of clarification does the official 8.6 release have an issue with the BBT markers?

#11

Try to put a tempo ramp after a BBT marker and see if it works.
I am having also other tempo-related minor problems, in the week-end I’ll try to reproduce and report them.

1 Like
#12

Hi,

Unfortunately I’m not able to work in the Studio right now and have little time for extracurricular testing, I will keep an eye out for your findings and see if any other reports surface… Right now a nightly 8.2.5 is rock solid here…

#13

Thanks for ideas…
It was the official binary from ardour.org.
There were no other windows that opened, even under the main screen.
I’m using Cinnamon (Mint).
Further investigation shows that some UIs do open, but none of the Calf ones. I can edit only with the Generic Controls.

The log does contain errors…

2024-04-17T18:53:27 [WARNING]: LADSPA</usr/lib/ladspa/autotalent.so>: Cannot load module “/usr/lib/ladspa/autotalent.so” (/usr/lib/ladspa/autotalent.so: undefined symbol: __exp_finite)
2024-04-17T18:53:27 [INFO]: Scanning folders for bundled LV2s: /opt/Ardour-8.6.0/lib/LV2
2024-04-17T18:53:28 [WARNING]: LV2http://kxstudio.sf.net/carla/plugins/carlapatchbaycv: Port 7 (‘CV Input 1’) has no known data type
2024-04-17T18:53:28 [WARNING]: LV2http://kxstudio.sf.net/carla/plugins/carlapatchbaycv: Port 8 (‘CV Input 2’) has no known data type
2024-04-17T18:53:28 [WARNING]: LV2http://kxstudio.sf.net/carla/plugins/carlapatchbaycv: Port 9 (‘CV Input 3’) has no known data type
2024-04-17T18:53:28 [WARNING]: LV2http://kxstudio.sf.net/carla/plugins/carlapatchbaycv: Port 10 (‘CV Input 4’) has no known data type
2024-04-17T18:53:28 [WARNING]: LV2http://kxstudio.sf.net/carla/plugins/carlapatchbaycv: Port 11 (‘CV Input 5’) has no known data type
2024-04-17T18:53:28 [WARNING]: LV2http://kxstudio.sf.net/carla/plugins/carlapatchbaycv: Port 12 (‘CV Output 1’) has no known data type
2024-04-17T18:53:28 [WARNING]: LV2http://kxstudio.sf.net/carla/plugins/carlapatchbaycv: Port 13 (‘CV Output 2’) has no known data type
2024-04-17T18:53:28 [WARNING]: LV2http://kxstudio.sf.net/carla/plugins/carlapatchbaycv: Port 14 (‘CV Output 3’) has no known data type
2024-04-17T18:53:28 [WARNING]: LV2http://kxstudio.sf.net/carla/plugins/carlapatchbaycv: Port 15 (‘CV Output 4’) has no known data type
2024-04-17T18:53:28 [WARNING]: LV2http://kxstudio.sf.net/carla/plugins/carlapatchbaycv: Port 16 (‘CV Output 5’) has no known data type
2024-04-17T18:53:29 [INFO]: xjadeo version: 0.8.13
2024-04-17T18:53:30 [INFO]: harvid version: 901
2024-04-17T18:53:30 [INFO]: Loading menus from /opt/Ardour-8.6.0/etc/ardour.menus
2024-04-17T18:53:32 [INFO]: Removing MIDI patch file custom:DrumGizmo:0x7f477e0f3010
2024-04-17T18:53:32 [ERROR]: MidiTimeAxisView: unknown automation child main-out-volume
2024-04-17T18:53:32 [ERROR]: MidiTimeAxisView: unknown automation child main-out-volume
2024-04-17T18:53:32 [INFO]: Loading user ui scripts file /home/graeme/.config/ardour8/ui_scripts
2024-04-17T18:53:32 [INFO]: Loading plugin order file /home/graeme/.config/ardour8/plugin_metadata/plugin_order
2024-04-17T18:53:32 [INFO]: Loading history from /home/graeme/Music/Ardour/bat-2024-04-14/bat-2024-04-14.history
2024-04-17T18:53:40 [ERROR]: failed to instantiate LV2 GUI
2024-04-17T18:53:40 [ERROR]: failed to instantiate LV2 GUI
2024-04-17T18:53:40 [ERROR]: failed to instantiate LV2 GUI

#14

That is expected. Calf uses GTK2, which has been deprecated, see Ardour 8.4 Calf plugins [ERROR]: failed to instantiate LV2 GUI - #4 by x42

1 Like
#15

Ah, that would explain it. Thanks.
Oh well, I guess it’s good bye to Calf. :frowning:

#16

Hmm… I have installed ardour 8.6 and the calf plugins are working fine. I also have no problems with the gui on ubuntu 22.04.

#17

Not using them anymore but just checked it out of curiosity. The GUI doesn’t work on Debian 12 and Ardour 8.6. It complains about g_task_set_name symbol:

suil error: Unable to open UI library /usr/lib/lv2/calf.lv2/calflv2gui.so (/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0: undefined symbol: g_task_set_name)

The calf-plugins package is installed from Debian repository (0.90.3-4). Maybe other builds will work somehow (for now).

#18

Hmm, strange.

Bildschirmfoto zu 2024-04-20 18-09-48
Bildschirmfoto zu 2024-04-20 18-09-481920×1080 230 KB

As I said, the calf plugins run normally.

#19

If your distro still supports the nowadays deprecated GTK2 and Ardour is compiled, either by yourself or by the distro folks, to use the system libraries then it’ll work.
The official Ardour binary is compiled to use its own internal version of GTK2 and that clashes with the system libs that your Calf plugins are using.

If your particular Ardour/Calf combination works; good for you.
If it doesn’t and instead breaks you get to keep both pieces :slight_smile:

1 Like
#20

That is debatable - unless you’re wearing a “more distortion” t-shirt. :slight_smile:

#21

Yeah, I probably should have expressed myself a bit more “nuanced” :smiley:

But who knows; maybe that extra piece of surprise Calf distortion is exactly what’s needed to get the grindcore album you’re mixing to sound better than all other grindcore albums.

#22

Does anybody know if Calf are planning to upgrade the plugins?
Also - can somebody point me to good (free) alternative please? I am on Linux PopOS 22.04
I am only editing sound occasionally so yes - I am pretty much a newbie.
Thank you in advance!

#23

An alternative would be: https://lsp-plug.in/ I’m not sure if the LSP plugins will run on Linux PopOS 22.04.

With musical greetings

Unknown

1 Like
#24

In fact, they are planning to issue a minor bug release:

Regarding the GTK GUI problem, they are preparing some kind of workaround. See this and following posts on their GitHub issue page:

1 Like
#25

Hi! Apparently you guys are messing with the markers, ruler, locations and such… Can you, (by the way ofc) fix the issue, that if I play in loop mode, the playback ALWAYS starts from the beginnig of the loop range instead of the current playhead position? Please…

Tip: If I want, I know how to manually place the playhead at the beginning of the loop. :wink:

#26

At least many people have asked for the opposite …

#27

This is not an answer I would give a heart emoji to. :wink: Thanks anyway for the fastest reply in the world!

#28

Oh that’s why, I was wondering if it was a bug. It was quite useful to check if a section properly loops without having to listen to the whole section like now.

1 Like