I am sure it has been mentioned before, but the best solution for
multiple devices all on MIDI channel 1 is a single USB to MIDI adaptor
with multiple MIDI inputs, like the MidiSport 4X4. Each input is named
"A", "B", "C" & "D" and (unless you move your physical MIDI cables) they
will each always relate to the specific keyboard.
For each keyboard in jOrgan you set the device MidiSport-A and its
channel CH1, then for the next you select MidiSport-B and CH1 etc. The
same is true for the console input, however if you are using more than
one device for console input then I suspect you would need more than one
jOrgan "connector" element. I don't know if it is possible to have more
than one "Connector" element referenced to a "Console"? I don't think
jOrgan Merger would work in this instance.
On 30/06/2011 8:37 p, Bernd Casper wrote:
> Hi Sven,
> I withdraw the proposal of a channel filter for the connector element.
> My proposal is hardware-specific. It raised from the fact that my USB
> keyboards revert to channel 1, after every power off. So everything is
> set to channel 1 here, for default. In case of merging those devices
> via MIDI (how it is proposed), I have a constant problem of merging
> everything on channel 1, after powering off.
> I use to power off my electricals, generally, and won't leave this
> Sorry for wasting time.
> Kind Regards
> ----- Folgende Nachricht wurde empfangen -----
> *Absender:* Sven Meier <mailto:sven@...>
> *Empfänger:* jorgan-user <mailto:jorgan-user@...>
> *Zeit:* 2011-06-29, 22:28:50
> *Betreff:* Re: [jOrgan-user] jOrgan 3.14-beta1
> Hi Bernd,
> > export the element names as well as the "name=.." field in the
> next version will use the description name if available, falling
> back to the normal element name.
> > a proposal for the connector element ... to add a channel filter
> A channel filter for each connector? I'll have to think about it
> ... this might be useful.
> Thanks for your feedback
> On 06/28/2011 09:02 AM, Bernd Casper wrote:
>> Hi Sven,
>> many thanks for the new beta. It runs rock-stable on my console.
>> The exporter works fine here when exporting the raw data into a
>> text file, using a viewer which is able to inteprete the
>> invisible symbols alright - like Notepad2 does for default. I
>> also wonder whether the file format should be restricted to
>> Unicode and .txt only.
>> For instance, if I save the list as .doc, OpenOffice does an
>> import when opening the file, asking me in which format I want
>> the symbols to be interpreted as. Here, the default format given
>> by OpenOffice, is "Westeuropa - Windows1252-Latin1", whilst
>> Unicode is the right one.
>> Regarding elements list - it might be useful to export the
>> element names as well as the "name=.." field in the description,
>> perhaps with a separator?
>> For infinite switches, the deactivate-activate message MPL order
>> is correctly inserted here, when using the record function. Great.
>> I've a proposal for the connector element.
>> Would it be possible to add a channel filter here, or enable MPL
>> alternatively? This could reduce cable salad, when connecting
>> e.g. various USB input devices merged into a single USB cable by
>> a hub.
>> Thank you very much, again, especially for exchanging shortcut
>> press and release.
>> Best Regards
>> ----- Folgende Nachricht wurde empfangen -----
>> Absender: Sven Meier
>> Empfänger: jorgan-user
>> Zeit: 2011-06-21, 21:29:31
>> Betreff: [jOrgan-user] jOrgan 3.14-beta1
>> Hi all,
>> I've uploaded Windows installer, Linux package and OS X bundle for
>> jOrgan 3.14-beta1.
>> We have one bug fix for the recorder and a few new features:
>> * message monitor may now skip control messages
>> * activate/deactivate switches on shortcut press (was released)
>> * customizer: set deactivate before activate to allow
>> customizing of
>> infinite switches
>> * recorder: fixed bug for empty tracker not attached
>> * export: new extension
>> * memory: export memory levels
>> Please try it out and give feedback.
>> All of the data generated in your IT infrastructure is seriously valuable.
>> Why? It contains a definitive record of application performance, security
>> threats, fraudulent activity, and more. Splunk takes this data and makes
>> sense of it. IT sense. And common sense.
>> jOrgan-user mailing list
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> jOrgan-user mailing list