Thanks, MajorTom and speps, but I supposed I should go on record as not being in favor of these shortcuts. The reason is that they obscure the fact that you're using a particular DSSI host to load the plugin. Imagine a novice user starting up jack-keyboard and your /usr/bin/whysynth below, and wondering why they won't talk to each other, and 'man whysynth' doesn't return anything -- frustrating.
Plus, as you've show below, this sort of thing is incredibly easy for the user to create themselves. Personally, I'd just put the following in my .profile:
alias whysynth='DSSI_PATH={$DSSI_PATH:-/usr/lib/dssi} ghostess whysynth.so'
Search Criteria
Package Details: whysynth 20120903-2
Package Actions
| Package Base: | whysynth |
|---|---|
| Description: | A versatile softsynth plugin for the DSSI Soft Synth Interface |
| Upstream URL: | http://www.smbolton.com/whysynth.html |
| Category: | multimedia |
| Licenses: | |
| Submitter: | None |
| Maintainer: | None |
| Last Packager: | None |
| Votes: | 26 |
| First Submitted: | 2007-04-19 07:02 |
| Last Updated: | 2013-04-25 16:00 |
Required by (0)
Sources
Latest Comments
Anonymous comment
Comment by WiZeTeK
I second that request. Similar to hexter, create a file /usr/bin/whysynth
#!/bin/bash
export DSSI_PATH=/usr/lib/dssi
exec jack-dssi-host whysynth.so
Comment by speps
@smbolton
Hi, nice work. Can u also provide a whysynth starter like the xsynth-dssi one? I mean
wget -O - "http://aur.archlinux.org/packages/xsynth-dssi/xsynth-dssi/xsynth-dssi" | sed "s_xsynth-dssi_whysynth_" > whysynth
Thanks