5 Dec
2004
5 Dec
'04
7:37 a.m.
Hi!
I've just one important - for me at least - question. Can the jack example
client be used without gui? Can it be used with midi only?
Thanks!
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net - the Linux TextBased Studio guide
5 Dec
5 Dec
10:25 a.m.
On Sunday 05 Dec 2004 11:37, Julien Claassen wrote:
I've just one important - for me at least -
question. Can the jack
example client be used without gui? Can it be used with midi only?
Yes and no. The DSSI JACK host will always try to start a user interface for
each plugin it loads. (It could easily have a command line switch to tell it
not to, but there isn't one at the moment.) However, if no user interface
executable is found, it will continue happily without. So you could make it
never start a UI by simply not installing any UIs. It will still continue to
deliver MIDI and produce audio.
Also, DSSI user interfaces have no obligation to be "graphical". The DSSI UI
mechanism is a simple Open Sound Control protocol, and you can control it
from any OSC client. You can provide many UIs for a single plugin, and the
host will choose one or support many at once -- again, the JACK host is
probably not optimal here as it offers no way for you to specify which UI to
prefer. (I haven't tested it with multiple simultaneous UIs.)
The DSSI package also includes a command-line tool (dssi_osc_send) that you
can use to control the ports, parameters, and configuration of any loaded
DSSI plugin without explicitly using a UI at all.
So most of the bits you need are there, but their organisation can probably be
improved upon. Any suggestions for particular use cases will be warmly
received.
Chris
1:16 p.m.
Hi!
I've taken a short lookat the dssi specs (6. ui section).
To tell the host to use a specific UI one could use the suggested naming
conventions: PLUGIN_UI. One could create the ui-programs: PLUGIN_QT and
PLUGIN_TXT and then tell the host try to find TXT ui with a commandline
switch.
For the uis in general I don't know what you should need. Perhaps things
close to the alsamixer.?
I expect synths have: continuous sliders (show a percentage bar (very rough)
and display value at bottom (or to the left)).
Buttons that change states (int-sliders). Well you could build thejm like
that. They could react to the same keys, they'd only show their current state
and no percentage.
ON/OFF switches. Two thoughts:
1. have an element where you can use tab or something like that, to switch
or
2. display specific keys (i.e.: R=turn off reverb).
Show and hide would have no effect (but they are optional anyway. An
interface like that could be implemented in ncurses or slang.
A totally different (and not SO intuitive way would be: a commandline based
interface (like a shell - see ecasound, fluidsynth...).
I hope these thoughts are not too disorganised and not too far from a way to
do it. Thanks for your help. I'll download dssi in a few days and try it the
way it is now anyway. I'm curious.
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net - the Linux TextBased Studio guide
7288
days inactive
7288
days old
linux-audio-dev@lists.linuxaudio.org
2 comments
2 participants
participants (2)
-
Chris Cannam -
Julien Claassen