3.0.12 b6

Hi Nico

sl1200mk2 wrote: @tous,
merci de votre participation

...

@Colin

If a MIDI out is connected, and subs have MIDI control, the normal operation of that sub is impaired

from what you described and from what I've noticed:
if Midi Out is enabled and MidiIn and Out are set to the same way, there's a loop problem.
DL send to midi out submaster's level. as DMX have twice more value than Midi, as soon as sub level is 1% in DL (in fact 3 dmx value), it's converted to 0 in midi level and sended out.
if there's a midi loop, DL also receive 0 for the sub, and so reset sub's level to 0.
thus, if there's a midi loop, a submaster cannot raise.

does it make sense?

++

More experiment shows, that where Multiple MIDI Inputs is selected, there are some Output choices which have the MIDI Loop problem, and some don't

MIDI Sources are

Echo AudioFire 4 Firewirewith MIDI In/Out(connected to BCN-44 C0ntroller)
LoopBe Virtual MIDI Cable
MIDIYoke 1 Virtual MIDI Cable
MIDIYoke 2 Virtual MIDI Cable
rtpMIDI Wireless MIDI Connection
TouchOSC Bridge Wireless MIDI Connection

No Loop Problems (ie Subs, Scene Master etc work OK)

Multiple In - Echo AudioFire Out
Multiple In - rtpMIDI Out
Multiple In - TouchOSC Out

Loop Problems (ie Subs, Scene Master etc DO NOT WORK)

Multiple In - LoopBe Virtual Cable Out
Multiple In - MIDIYoke 1 Virtual Cable Out
Multiple In - MIDIYoke 2 Virtual Cable Out


So the problem seems to be inherent in any Virtual Cable, and indeed LoopBe themselves warn of endless feed back with similar connections

But also, because of the nature of the Wireless MIDI applications, the seem to allow INPUT to DLight, but if they are selected as the OUTPUT, then Subs work ok, but can't use the output to allow monitoring (or, presumably, Motorised Faders)


So, Vive les CHECK BOXES...!!! Please...!!!

will definitely try check boxes for midi.
maybe next week or the week after as I do not have rush any more for 3.0.12

thanx,
++