Background: https://bugs.archlinux.org/task/21031
Dieter's workflow involves the following: * jack * rosegarden * fluidsynth For a week or so, Dieter did not touch these. He had: * jack-0.118.0 * fluidsynth-1.1.1 * rosegarden-10.04 In that week, among the kernel and other system software updates a (bleeding-edge) Linux system typically has, he ended up with: * fluidsynth-1.1.2 Suddenly, Dieter could not resume his workflow. Fluidsynth's playback ports refused to show up in jackd's connections. Obviously, troubleshooting standards dictate that he fall back to the previously-working version of the program: * fluidsynth-1.1.1 Unfortunately, this did not solve the issue. The next possible culprit was the kernel, so he installed an older kernel. Again, this did nothing and the output ports still refused to show up. Aside from all this, to prove that there is no issue with jack, generic programs like mplayer and timidity work fine. However, timidity cannot be a replacement in this workflow as it has its own problems. The following is the most obvious error from jackd: subgraph starting at fluidsynth timed out (subgraph_wait_fd=9, status = 0, state = Triggered, pollret = 0 revents = 0x0) And a verbose log: http://sprunge.us/gXIP This did not get filed as a bug report for fluidsynth yet because there is no case against it. If 1.1.1 worked, there would be a case against 1.1.2. Unfortunately, 1.1.1 (which used to work) does not work anymore. As such, I would really appreciate some help in debugging this. Thanks! -- GPG/PGP ID: B42DDCAD _______________________________________________ fluid-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/fluid-dev
