Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1114178 > unrolled thread

Bug#1017960: vmpk stopped producing sound

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1017960: vmpk stopped producing sound Ash Joubert <ash@transient.nz> - 2022-08-23 02:30 +0200
    Bug#1017960: vmpk stopped producing sound Ash Joubert <ash@transient.nz> - 2022-08-24 01:30 +0200
    Bug#1017960: libdrumstick 2.7.1-1 causes vmpk to stop making sound Pedro Lopez-Cabanillas <pedro.lopez.cabanillas@gmail.com> - 2022-08-25 11:00 +0200
      Bug#1017960: libdrumstick 2.7.1-1 causes vmpk to stop making sound Ash Joubert <ash@transient.nz> - 2022-08-29 00:00 +0200
        Bug#1017960: libdrumstick 2.7.1-1 causes vmpk to stop making sound Pedro Lopez-Cabanillas <pedro.lopez.cabanillas@gmail.com> - 2022-08-29 01:40 +0200
          Bug#1017960: libdrumstick 2.7.1-1 causes vmpk to stop making sound Pedro Lopez-Cabanillas <pedro.lopez.cabanillas@gmail.com> - 2022-08-29 23:10 +0200
    Bug#1017960: (no subject) snd <snd@y0o.de> - 2022-08-26 14:30 +0200
    Bug#1017960: libdrumstick 2.7.1-1 causes vmpk to stop making sound Pedro Lopez-Cabanillas <pedro.lopez.cabanillas@gmail.com> - 2022-10-01 22:20 +0200

#1114178 — Bug#1017960: vmpk stopped producing sound

Package: vmpk
Version: 0.8.7-1
Severity: important
X-Debbugs-Cc: ash@transient.nz

Dear Maintainer,

some time in the last week, vmpk stopped producing any sound at all. I have not
changed configuration of vmpk, and deleting ~/.config/vmpk.sourceforge.net to
reset the configuration did not resolve the issue.

The expected behaviour is that pressing a piano key results in sound output. No
sound is produced. I can see "FluidSynth output" in the PulseAudio mixer
(pavucontrol) when vmpk is running, and not when it is not running. Other audio
including YouTube in Firefox and MuseScore work fine.

Starting vmpk at the command line results in:

$ vmpk
MIDI Output "Information: Using PulseAudio driver\nError:
fluid_sfloader_load(): Failed to open '': File does not exist.\nError: Unable
to open file ''\nError: ipatch_file_open() failed with error: 'No such file or
directory'\nError: Failed to load SoundFont \"\""

I am on sid. The only thing I see that might be relevant was a libdrumstick
upgrade (2.6.1-1, 2.7.1-1) a few days ago.

Kind regards,
Ash.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages vmpk depends on:
ii  libc6                     2.34-4
ii  libdrumstick-rt-backends  2.7.1-1
ii  libdrumstick-rt2          2.7.1-1
ii  libdrumstick-widgets2     2.7.1-1
ii  libgcc-s1                 12.1.0-8
ii  libqt5core5a              5.15.4+dfsg-5
ii  libqt5dbus5               5.15.4+dfsg-5
ii  libqt5gui5                5.15.4+dfsg-5
ii  libqt5widgets5            5.15.4+dfsg-5
ii  libstdc++6                12.1.0-8

Versions of packages vmpk recommends:
ii  qjackctl  0.9.7-1
ii  qsynth    0.9.7-1

vmpk suggests no packages.

-- no debconf information

[toc] | [next] | [standalone]

#1114292

Downgrading libdrumstick binaries to 2.6.1-1 restores vmpk 
functionality. I downgraded:

drumstick-data
libdrumstick-alsa2
libdrumstick-rt-backends
libdrumstick-rt2
libdrumstick-widgets2

Kind regards,

-- 
Ash Joubert (they/them) <ash@transient.nz>
Director
Transient Software Limited <https://transient.nz/>
New Zealand

[toc] | [prev] | [next] | [standalone]

#1114425 — Bug#1017960: libdrumstick 2.7.1-1 causes vmpk to stop making sound

Hi!

I'm the upstream developer of both libdrumstick and vmpk.

> The expected behaviour is that pressing a piano key results in sound 
output. No sound is produced. 

You are correct. Anyone installing vmpk should be able to trigger sounds at 
once, without needing to search/download/configure soundfonts or other 
complex tweaks. Congratulations for pointing the bug report to the right 
target as well. In the past many people has complained to me about defects 
in the distribution/packaging, like not producing sound at once.

>  I can see "FluidSynth output" in the PulseAudio mixer (pavucontrol) when 
vmpk is running
> MIDI Output "Information: Using PulseAudio driver\nError:
> fluid_sfloader_load(): Failed to open '': File does not exist.\nError: 
Unable to open file ''\nError: ipatch_file_open() failed with error: 'No 
such file or directory'\nError: Failed to load SoundFont \"\""

When the default output is missing, the program picks the next best option, 
which is FluidSynth. But this synth requires that the user configure a  
soundfont file and some other parameters before producing sound.

That is why the drumstick-rt backend "SonivoxEAS" was included in 2016 
(v1.1.0). This synth is very straightforward, not needing external 
soundfont files and using embedded samples instead, so it is suitable for 
vmpk and other projects. The synth was ported from the Android AOSP 
repository, including the sources inside the drumstick source repository 
and tarballs for simplicity, which is against Debian and other 
distributions best practices and policies.

Last month I've released drumstick v2.7.0 removing the Sonivox sources from 
the drumstick repository and tarballs, but linking to the shared external 
library instead, which is published at GitHub: 
https://github.com/pedrolcl/sonivox 
and some Linux distros have already picked it, but not Debian: 
https://repology.org/project/sonivox/versions.

The sonivox dependency is optional, but in v2.7.1 the packager must opt-out 
explicitly or the build system complains with an error message. And it has 
taken place: https://salsa.debian.org/multimedia-team/libdrumstick/-/
commit/68ab93c0d4603db88d73728068d7876bcb3f1fef

Your workaround is correct: downgrade drumstick to v2.6.1 to restore the 
expected functionality. Other alternatives:

* The deb-multimedia repo (https://deb-multimedia.org/) has full/correct  
packages for drumstick, sonivox and vmpk among others.
* My AppImage from SourceForge: https://sourceforge.net/projects/vmpk/
files/vmpk/0.8.7/
* FlatPak: https://flathub.org/apps/details/net.sourceforge.VMPK

In a few days I will publish a new VMPK v0.8.8 with some fixes, and it will 
loudly complain at startup when the default output backend is missing.

Regards,
Pedro

[toc] | [prev] | [next] | [standalone]

#1115276 — Bug#1017960: libdrumstick 2.7.1-1 causes vmpk to stop making sound

Pedro,

thank you for your detailed explanation.

I can confirm that, after upgrading libdrumstick packages to 2.7.1-1, 
configuring a FluidSynth MIDI connection restores functionality. The 
missing step was to configure a sound font: the default "default.sf2" 
does not exist. You might consider enhancing VMPK by changing the 
default or autodetecting or even recommending a well-known sound font 
package.

For the benefit of other users:

- I had installed fluid-soundfont-gm and thus had symlinks including:

     /usr/share/sounds/sf2/default-GM.sf2 -> 
/etc/alternatives/default-GM.sf2
     /etc/alternatives/default-GM.sf2 -> 
/usr/share/sounds/sf2/FluidR3_GM.sf2

- For this test, I started from a clean installation, but this step may 
not be necessary:

     rm -rf ~/.config/vmpk.sourceforge.net

- I pressed Edit / MIDI Connections / MIDI Out Driver (now automatically 
set to "FluidSynth") and then "..." to configure and saw:

     Audio Driver: pulseaudio
     [...]
     Sound Font: default.sf2 (which does not exist)
     FluidSynth Version: 2.2.8
     Initialization Status: Failed

- I changed sound font with "..." to:

     Sound Font: /usr/share/sounds/sf2/default-GM.sf2

- I pressed OK and status changed to:

     Initialization Status: Ready

VMPK functionality was then restored.

Kind regards,

-- 
Ash Joubert (they/them) <ash@transient.nz>
Director
Transient Software Limited <https://transient.nz/>
New Zealand

[toc] | [prev] | [next] | [standalone]

#1115278 — Bug#1017960: libdrumstick 2.7.1-1 causes vmpk to stop making sound

On domingo, 28 de agosto de 2022 23:52:09 (CEST) Ash Joubert wrote:
> I can confirm that, after upgrading libdrumstick packages to 2.7.1-1,
> configuring a FluidSynth MIDI connection restores functionality. The
> missing step was to configure a sound font: the default "default.sf2"
> does not exist. You might consider enhancing VMPK by changing the
> default or autodetecting or even recommending a well-known sound font
> package.

The name "default.sf2" is the default value of a setting from the 
fluidsynth synthesizer:
https://www.fluidsynth.org/api/settings_synth.html#settings_synth_default-soundfont

This setting can be changed at fluidsynth build time, and Debian sets it to 
"/usr/share/sounds/sf3/default-GM.sf3". Upon installing the libfluidsynth3 
library there is a dependency on the package "timgm6mb-soundfont" which 
installs "/usr/share/sounds/sf2/TimGM6mb.sf2", so maybe you shouldn't need 
to look for more soundfonts after all. But all this smells like another 
different issue that we need to examine in detail.

The idea behind the name "default.sf2" was to be a symlink (created by the 
users, the admins, or the packagers) to some real soundfont file installed 
on the system. There are a few sf2 files available in Debian:

https://packages.debian.org/search?
suite=sid&arch=any&searchon=contents&keywords=sf2

My favorite would be "GeneralUser-v1.47.sf2" ( https://
schristiancollins.com/generaluser.php ) because the small size (only 30Mb) 
and high sound quality. In Debian it is installed by a package named 
"minuet-data", and placed at "/usr/share/minuet/soundfonts/". You may 
observe that there is little consistency in locations between several 
packages. I am not inclined to implement any kind of autodetection. And 
recommendations are managed by the distribution, like the integration 
between components.

Regards,
Pedro

[toc] | [prev] | [next] | [standalone]

#1115403 — Bug#1017960: libdrumstick 2.7.1-1 causes vmpk to stop making sound

On lunes, 29 de agosto de 2022 1:35:22 (CEST) Pedro Lopez-Cabanillas wrote:
> On domingo, 28 de agosto de 2022 23:52:09 (CEST) Ash Joubert wrote:
> > I can confirm that, after upgrading libdrumstick packages to 2.7.1-1,
> > configuring a FluidSynth MIDI connection restores functionality. The
> > missing step was to configure a sound font: the default "default.sf2"
> > does not exist. You might consider enhancing VMPK by changing the
> > default or autodetecting or even recommending a well-known sound font
> > package.
> 
> The name "default.sf2" is the default value of a setting from the
> fluidsynth synthesizer:
> https://www.fluidsynth.org/api/settings_synth.html#settings_synth_default
> -soundfont
> 
> This setting can be changed at fluidsynth build time, and Debian sets it
> to "/usr/share/sounds/sf3/default-GM.sf3". Upon installing the
> libfluidsynth3 library there is a dependency on the package
> "timgm6mb-soundfont" which installs
> "/usr/share/sounds/sf2/TimGM6mb.sf2", so maybe you shouldn't need to
> look for more soundfonts after all. But all this smells like another
> different issue

It is a bug in drumstick-rt-fluidsynth. Upstream ticket:
https://sourceforge.net/p/drumstick/bugs/46/

Regards,
Pedro

[toc] | [prev] | [next] | [standalone]

#1114595 — Bug#1017960: (no subject)

Hey guys,

I already filed an ITP bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018164 and packaged 
sonivox here https://salsa.debian.org/multimedia-team/sonivox
anyways, it will take some time before it comes to sid, because first 
someone needs to review and then it will land in NEW for a while.

Best regards,
Dennnis

[toc] | [prev] | [next] | [standalone]

#1119508 — Bug#1017960: libdrumstick 2.7.1-1 causes vmpk to stop making sound

upstream ticket: https://sourceforge.net/p/drumstick/bugs/46/
fixed and closed in release 2.7.2

Regards,
Pedro

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web