On 05/09/2010 12:10 PM, Niels Mayer wrote: > On Sat, May 8, 2010 at 10:59 AM, Rui Nuno Capela wrote: > >> On 05/08/2010 05:03 PM, Niels Mayer wrote: >> http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&Item=200469896509&Category=3701&_trkparms=algo%3DLVI%26its%3DI%26otn%3D1#ht_1151wt_1029 >> http://qxgedit.sourceforge.net . > > speaking of which, had you any success? > > Yes! > > I just got the DB-60XG yesterday, and today it's plugged into a Dynex > DX-SC51 running on Fedora12 alongside qxgedit and rosegarden. > > Oh, and the qchord works beautifully with it too. (It never sounded so > good, with the ability to warp out the sounds via qxgedit). > > qxgedit works well but needs a few features: (or I need a clue). > (1) Can qxgedit "read" the db50xg values so as to set all it's dials and > voice presets to whatever is currently setup on the DB50XG card? > (There's probably no "dump" on the card, right, is there even a MIDI > output??) 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 > information from an XG MIDI file (e.g. if I want to copy the "voicing" > of an existing song) so that qxgedit can be set to edit the values that > are playing? 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 > from the ALSA midi source. I.e. if I sent rosegarden output to qxgedit > input, the presets should set to whatever's in the track, and the dials > should track whatever changes are going on in the track.... from their > given positions "riding" the playing midi file, they can be grabbed, > which overrides what they're "reading" and instead outputs a midi change. 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 so magic I missed in hooking up the ALSA midi in of qxgedit??). > SInce there's so > many things to control, a way of automapping s.t. you can click-and-hold > a control, while jiggling a slider on the control surface. Once that's > done, you've bound the slider to the qxgedit control parameter.... 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 > vocoding, or using voice to modulate parameters) > http://www.studio4all.de/htmle/main96.html http://electro-music.com/forum/topic-21634-175.html > 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 db50xg, remember?). cheers -- rncbc aka Rui Nuno Capela rncbc@xxxxxxxxx _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
