On 11/14/14, 12:00 PM, "Francesco Ariis" <fa...@ariis.it> wrote:
>On Thu, Nov 13, 2014 at 09:28:23PM +0100, Francesco Ariis wrote: >> Now to the problem; when I try to use fluidsynth instead of qsynth, MIDI >> events are recognised (I can see them with -v option), but no sound >>comes >> out of the speakers. > >I think I found the problem: I will answer myself in case someone >experience >the same behaviour. > >Apparently, qsynth spawns an instance of jackd which isn't killed when you >quit the program (I don't really know why). >Killing the process (jack) and starting fluidsynth does it. > > >-- >To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org >with a subject of "unsubscribe". Trouble? Contact >listmas...@lists.debian.org >Archive: https://lists.debian.org/20141114200051.ga28...@x60s.casa I had just installed timidity, when I saw this post, and decided to take a look at these tools. What I found shows both qsynth and fluidsynth depend on jackd, since I did not have jackd installed and both refused to run, with the same error message, to the effect that "jackd could not be found or started." It would seem that these two packages should depend on the jackd package, but don't. I also discovered that neither of them seem to work with jackd2, they only seem to work with jackd1. However, since I could not get jackd2 to run at all, via qjackctl, the issue is probably not with qsynth/fluidsynth. I'm on Debian wheezy (7.7, according /etc/debian_version). Bob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/d08bac3e.6834%bob_mcgo...@symantec.com
