From: federico <xa...@in...> - 2005-03-09 20:06:47
|
Brian wrote: > JSynthLib does not play nice with having more of one of the same > synthesizer. d'oh! :-O > Menu. This will assign the patch to a different instance of the synth. > However, you would have to do this each time you load a library. yes, it's terrible! :-) > As for your specific case its a little differnt, you don't have three > different synths, but one synth with different midi channels that > you want to use. What is the ID field you are talking about that > contains "MKS-7-B", etc. Is this a part of the actual sysex for the MK-7? no. it is the Synth ID i given to the three instances of driver. the midi channel and the device id are set to the mks's receiving midi channel > Is there someway that it is possible to tell which part > (chord,melody,bass) a patch belongs in based on looking at the patch? as i said, dev_id and midi_ch are set to the same number, which is the midi channel. here is the MKS7 sysex header (one byte per line): F0 <id:roland> <model:mks7> <opcode:param_change/tone_change> <midi channel> <data ...> F7 when you turn on the device, melody is channel 1, bass is channel 2, chord is channel 3 (however you change them with a button) and there isn't other method to distinguish parts. > If so, > maybe you could have the MK7 Device have three drivers each being > identical except having a sysex_id that will only match the > patches which should be for that part? That would be the optimal way > to do it. > uhm i think it is not possible (see above) i thought another approach: make three tabs, one for part. but this would drive into a DOUBLE problem: conceptually doesn't exists anymore the patch, but only the BANK concept, since the driver controls an entire bank (bank on synthesizer, not a jsl's bank); you can't specify three midichannels in the driver's settings. so i decided to abandone this way. the really optimal way would be make possible to have many driver instances (think the surreal situation in which you have 3 synthesizers, same brand, same model ;D) maybe add a column to the patchlib database would solve the prbl, i.e. a field to specify midi channel for a patch (uhm, this may be heavily redundant). otherwise is it possible access FIELD1/FIELD2 from the editor/driver? about the midi problem, i quote here your message: > What platform are you using? (Operating System / Java Version / Midi > Provider? > Linux 2.6 java version "1.4.2-01" Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.4.2-01) Java HotSpot(TM) Client VM (build Blackdown-1.4.2-01, mixed mode) Advanced Linux Sound Architecture Driver Version 1.0.7. Compiled on Mar 5 2005 for kernel 2.6.10-gentoo-r6. i access midi through the /dev/snd/midi* and /dev/midi* devices. -- Federico |