whysynth doesn't work
by Florin Andrei
I got whysynth-dssi-20060122-7.src.rpm from here:
http://people.redhat.com/green/FE/devel/
I rebuilt it on FC6 without problems. The thing is, the GUI doesn't show
up. The program appears to be working, I see the outputs being
automatically routed in qjackctl, but there's no GUI anywhere!
###############################################
$ jack-dssi-host whysynth.so
jack-dssi-host: Warning: DSSI path not set
jack-dssi-host: Defaulting to
"/usr/local/lib/dssi:/usr/lib/dssi:/home/florin/.dssi"
jack-dssi-host: OSC URL is:
osc.udp://rivendell.home.local:15040/dssi/whysynth/WhySynth/chan00
host: Ready
WhySynth_gtk starting (pid 4305)...
###############################################
--
Florin Andrei
http://florin.myip.org/
16 years, 10 months
- 6
- 16
jack and /etc/security/limits.conf
by Anthony Green
One of the annoying things about running qjackctl on a fresh Fedora
install is that you have to remember to edit /etc/security/limits.conf
as per /usr/share/doc/jack-audio-connection-kit-0.102.20/README.Fedora
or else it doesn't work at all. I'm wondering if there's something we
can do to make this easier.
One idea is to wrap qjackctl in a script that essentially parses
limits.conf to see that everything is set up properly for $USER. If
not, it pops up a dialog box explaining the problem and offering to edit
it for $USER. If the user agrees, it runs a consolehelper app to fix up
limits.conf and continues on with qjackctl.
I just can't imagine how a new user gets anything running without
stumbling upon that README.Fedora file or searching for help on the web.
Good idea? Bad idea? Suggestions?
AG
16 years, 11 months
- 5
- 9
- ← Newer
- 1
- Older →