On 05/09/2010 12:10 PM, Niels Mayer wrote:
the xg specs actually refers a way for you to query and dump xg device
state, but truth goes like that i always meant my db250xg thingie as
write-only devices and qxgedit acquaints for that neatly :)
i'll have to check that out yet again, 'coz last time i've tried and it
was a long time ago, nothing ever came out from the the hostess
soundcard midi outs on that matter. i suspect there's no db50xg midi
outs at all or at least are not being connected trough the waveblaster
interface to the soundcard's own midi outs.
> (1.1) Alternately, is there a way to extract the sysex/control
not with qxgedit. however you can do something of the sorts with yours
truly qtractor sysex manager ;)
> (1.2) Another alternative -- have qxgedit "track" sysex/control changes
qxgedit can indeed read xg sysex input and react to it. just connect its
midi ins as you do with the midi outs.
> (2) A way of hooking it up to a control surface (but then again, maybe
there's no midi learn nor external midi controller mapping to the
qxgedit gui knobs and stuff, sorry.
> (3) Feature request -- support for db60xg's analog input (e.g. for
i guess that it's already included. the analog input is only about to be
processed through the xg effects section and then mixed down to anolog
outputs from the synths.
there maybe something missing wrt. analog input levels and such... but i
am lacking documentation specifics about the db60xg (i only deal with
rncbc aka Rui Nuno Capela
Linux-audio-user mailing list