Bug#994208: "not implemented" while exporting a track from ardour

[Antoine Beaupré]

On 2022-04-14 10:46:07, Dylan Aïssi wrote:
> Hi Antoine,
>
> Latest pipewire versions fixed several issues with ardour and the "not
> implemented" message.
>
> https://gitlab.freedesktop.org/pipewire/pipewire/-/issues?scope=all=all=ardour+not+implemented
>
> It would be nice, if you could try with a more recent version.

I would be very happy to see those issues fixed, but unfortunately I do
not plan on upgrading to bookworm for at least a few months. We're still
in the middle of a major bullseye upgrade (~50 machines to go) so it
could take a little longer.

-- 
The problem is not a lack of highly educated workers, the problem is a
lack of highly educated workers willing to work for the minimum wage or
lower in the U.S. Costs are driving outsourcing, not the quality of
American schools.   - Scott Kirwin, IT Professionals Association

Bug#994208: "not implemented" while exporting a track from ardour

[Dylan Aïssi]

Hi Antoine,

Latest pipewire versions fixed several issues with ardour and the "not
implemented" message.

https://gitlab.freedesktop.org/pipewire/pipewire/-/issues?scope=all=all=ardour+not+implemented

It would be nice, if you could try with a more recent version.

Best,
Dylan

Bug#994208: "not implemented" while exporting a track from ardour

[Antoine Beaupre]

Package: pipewire
Version: 0.3.19-4
Severity: normal
Control: fixed -1 0.3.35-1 

It seems Ardour can't export tracks when the backend is down. Or, more
specifically, when it doesn't implement a ... certain something? The
actual error I got is this:

sep 13 13:35:38 curie ardour-6.5.0~ds0[232017]: jack-client 0x55e8be5ffaa0: not 
implemented

If I stop Pipewire:

systemctl disable pipewire.socket
systemctl stop pipewire.service

... and then restart Ardour with an ALSA backend, I can actually
export the track.

I originally filed this as #994207 against Ardour because it stumbled
upon a fairly simple job (exporting a track) when running under
pipewire. But considering how Ardour works, I don't think that can be
fixed there.

I'll also note that this doesn't occur in bookworm.

Note that this bug was filed after confirming the former, so the
following metadata will look inaccurate. The version that works is
0.3.35, and the one that *does not* work (and which the bug applies
on) is 0.3.19-4.

A.

-- System Information:
Debian Release: 11.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'), 
(1, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pipewire depends on:
ii  init-system-helpers  1.60
ii  libpipewire-0.3-modules  0.3.35-1
ii  pipewire-bin 0.3.35-1

pipewire recommends no packages.

pipewire suggests no packages.

-- debconf-show failed