Your message dated Tue, 15 Nov 2022 13:41:21 -0500 with message-id <[email protected]> and subject line Re: "not implemented" while exporting a track from ardour has caused the Debian Bug report #994208, regarding "not implemented" while exporting a track from ardour to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 994208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994208 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---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
--- End Message ---
--- Begin Message ---Control: fixed -1 0.3.59-1+b1 On 2022-04-14 10:46:07, Dylan Aïssi wrote: > Latest pipewire versions fixed several issues with ardour and the "not > implemented" message. > > https://gitlab.freedesktop.org/pipewire/pipewire/-/issues?scope=all&state=all&search=ardour+not+implemented > > It would be nice, if you could try with a more recent version. I finally lay my hands on an upgraded bookworm machine, and I can confirm this bug is indeed fixed, thanks! a. -- We are discreet sheep; we wait to see how the drove is going, and then go with the drove. - Mark Twain
--- End Message ---
_______________________________________________ Pkg-utopia-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
