Home | News | Products | Support | Download | Sales | library | Guests | Contact | WebCam | Links
CDS Logo LanBox-Talk mail archive
 

By date: Prev | Next | Index By thread: Prev | Next | Index

SubjectRe: [LCtalk] LCX problem
FromMichael Lohrengel
DateWed, 17 Mar 2004 15:22:26 +0100


Hi Fokko

Fokko wrote:
AFAIK this has nothing to do with speed, but not keeping together controller messages 21, 53 and 86 when you use multiple MIDI channels (layers).

As the LanBox-LCX and LCM have dynamic layering (you can change the layer order on the fly), keeping these controller messages together is far more critical then for the old LC+.

That makes sense - but it means a hell of a lot of work for me !! Go back to something like 150 logic songs and change each and every one on the computer, then convert it to a midifile and store it back into the midiplayer. Is there anyway to achieve a working system without that hassle ? I mean, I could do without the dynamic layers for my purpose? You know, that's why I asked before: can I use the LCX like the LC+ ? On the other hand, I understand, you can not forsee every situation. Any smart solution at hand ?
If not, I want to make shure what exactly "keeping together" stands for. Each midifile has quite a few commands for the Lanbox at the beginning, I will list them here to see in which order exactly all these commands have to be and how much time ( midiclicks ) have to be in between: ( normally in my Logic SOngs, every engine has it's own track, here I have merged them all so you can see a typical opening string. I hope you are familiar with Logic, if not I can send a second mail with explanation )


1 1 1 1   Control 1  21  1   ctrl 21
1 1 1 1   Control 3  21  1   ctrl 21
1 1 1 1   Control 15 21  0   ctrl 21
1 1 1 3   Control 15 53  25 (#21 LSB)
1 1 1 5   Control 1  53  97 (#21 LSB)
1 1 1 5   Control 3  53  97 (#21 LSB)
1 1 1 5   Control 15 86  11  ctrl 86
1 1 1 7   Control 1  86  11  ctrl 86
1 1 1 9   Control 11 21  0   ctrl 21
1 1 1 10  Control 3  86  12  ctrl 86
1 1 1 12  Control 11 53  1  (#21 LSB)
1 1 1 18  Control 1  73  1  attack time
1 1 1 20  Control 5  73  1  attack time
1 1 1 22  Control 7  73  1  attack time
1 1 1 23  Control 11 73  1  attack time
1 1 1 25  Control 15 73  1  attack time
1 1 1 184 Control 11 86  35  ctrl 86
1 1 2 18  Control 1  73  127  attack time
1 1 2 20  Control 5  73  127  attack time
1 1 2 22  Control 7  73  127  attack time
1 1 2 23  Control 11 73  127  attack time
1 1 2 25  Control 15 73  127  attack time
1 1 1 18  Control 1  65  65  portamento
1 1 2 28  Control 5  65  65  portamento
1 1 2 31  Control 7  65  65  portamento
1 1 2 38  Control 11 65  65  portamento
1 1 2 40  Control 15 65  65  portamento
1 2 2 4   Note    11 F4  90  - 1 0 0

The string starts by setting the used engines to the right cuelist and as you can see, I never bothered about the order as it was always working fine. Control 73 stops running mode, in case the song before was not played to the end and some engines might still run, shortly after they are set back to running mode for the now playing song. Control 65 sends ignoire note off and the note will make a slide projektor go to the right slide, after the command in engine G (midichannel 11) has faded the slideprojektor down. The other midichannbels stend for:
15 = engine A
1 = engine B
3 = engine C
7 = engine E


How should the perfect order be ? Can the controlls for one engine/cuelist be all at the same time or is it better to stagger them like I did ? Are controll 73 and 65 allowed to came in between the cuelist commands )
And one more request: There should be a way, to have the LCX start with ignore note off setting by default - it can store other midisettings like the engine to midichannel setting, couldn't it store that too ?


Two more things I wonder about:
If I add a static text in the fixture definition, the intensity indicators are not available anymore ?? Why ??

Intensity must be the first panel, see also tutorial.

Well, yes, bu you would expect static text to be treated different than a actual controlpanel. I put the static text in to have the fixture have a name in the controlwindow.



I understand, that making a group will merge panels as far as possible - quite often that's a handy feature. But sometimes I would rather have the chance to see e.g. two fixtures in the controlwindow with individuel panels: e.g. I have two Robocolours, that dont always work parallel. It would be a lot more convinient to programm them if I could see both of them with individuel panels in the controlwindow. So, is there a command to show two or more fixtures in the controlwindow without merging the panels ?

Yes, but it is an unsupported, secret, feature! (tip: in the group setup panel option (alt) click below the left list, and a popup will appear. Try "concatenate" ;-)

Great!!


Regards, Michael Lohrengel

By date: Prev | Next | Index By thread: Prev | Next | Index