Limitations of the environment?

[Fred B]

I wonder if the environment could be used for selecting a specific track in the arrange window, for example selecting track #n by sending program change #n. Maybe it could be solved with a loop that creates multiple 'select next track' events. But I'm not sure if such loops are possible at all in the environment.

 

Any suggestions?

[shivermetimbers]

I think David made a template that selected the different tracks. Someone wanted to set up a few EXS instruments and be able to select any one at any time.

[Fred B]

Thanks. I'll try to find it...

[David Nahmani]

This one switches the instruments playing, but not the selected track. Not sure if that's what you're looking for? Rather than changing which track is selected, I reassign the selected track to the instrument I want using Meta events. This can be written on an "automation" track or switched live.

 

http://www.logicprohelp.com/viewtopic.php?t=1048

[Fred B]

Thanks David, but actually I'm looking for switching tracks,

in particular folder tracks to control playback of different "mini songs".

 

Maybe the 'touch tracks' feature could be used for this?

[Plowman]

I have never found a way to choose tracks (other than Previous and Next) by MIDI. But it can be done on Logic Control, which is puzzling to me.

 

Since LC's only way to communicate with a computer is via MIDI (even though it's sending its own kind of data), I've been surprised that some kind of MIDI solution or Environment hack hasn't surfaced over the years.

[Fred B]

That's interesting!

I don't have LC but maybe one could monitor LC's output to disclose the secret messages?

[Fred B]

Back to the original question, I'm still curious:

Does anybody know if it's possible in the environment to generate an arbitrary number of identical events?

[David Nahmani]

From what? Surely the environment can't spontaneously generate events, but what kind of event would you be using to translate into a track select?

[Fred B]

Well, of course I mean that it's triggered by some event, for example cc#20 value 7 translates into 7 'select next track' events, and cc#21 value 7 translates into 7 'select previous track' events.

The purpose would be to select a specific track (number) by MIDI.

[David Nahmani]

One way of doing this that comes to mind is to do that with a series of transformers. Transformers can be set to copy an event and process the copy. It might be a little more elegant with a chord memorizer or a delay object.

 

Let me know if you have trouble doing it, but it shouldn't be too difficult. Unless I'm missing something.

[Fred B]

Ok, problem solved. It works well with a serie of transformers, each one decreases the cc value by 1 if greater 0, and generates a 'select next track' event with another common transformer.

 

Thanks David for the hints!

[David Nahmani]

No problem! If you don't mind it would be nice of you to upload that template in the templates section.

 

BTW to have the key commands work, do you send the events to an IAC bus?

[Fred B]

Well, I guess a template is somewhat problematic since so many variables would be hard-coded, eg. number of tranformers, trigger events, key command events. Also, for practical usage a second transformer serie would be needed to generate 'select previous track' events, such that the user can always go back to track 1 (or even virtual track 0) as a starting point.

 

And YES, the generated key command events must be sent to an IAC bus.

 

So overall it's a rather tricky solution. Anyway, I'll think about a template.

[David Nahmani]

When I say template, I mean your file, it doesn't have to be perfect. Maybe just tell us which MIDI key command you used and upload your file, so others can learn from looking at it, and implement the techniques in their own templates.

 

Only if you want to of course.

[editbrain]

it's mine.. mine... allll miiinnnnee...

 

 

just kidding, folks. I have had a ruff day. this popped in my head and made me laugh.

 

ren and stimpy....

 

nothing personal to the OP

[fader8]

I don't have LC but maybe one could monitor LC's output to disclose the secret messages?

 

Fred,

 

The MIDI messages from the LC for track select are nothing more than Note On's. Specifically 24-31. But that doesn't help you as it will only work if there is an LC in the Control Surface Setup telling Logic what it should do with that MIDI info.

 

There is a way around this but it's $40 US. John Pitcairn's LC-Xmu program creates one or more "dummy" LC's which you can then map your own MIDI messages to. So you could set up any MIDI controllers buttons or keys to perform track select. I've heard this software works quite well.

 

http://www.opuslocus.com/lcxmu/index.php

[Fred B]

fader,

 

thanks a lot for the clarification.

I always like to understand what's going on under the hood...

[Fred B]

John Pitcairn's LC-Xmu program creates one or more "dummy" LC's which you can then map your own MIDI messages to. So you could set up any MIDI controllers buttons or keys to perform track select.

Thanks for the hint. So regarding my original question about track selection, I think it doesn't make much sense trying to emulate LC functionality by tricky cabling in the environment.

[fader8]

Thanks for the hint. So regarding my original question about track selection, I think it doesn't make much sense trying to emulate LC functionality by tricky cabling in the environment.

 

Well it never hurts to learn something new, but in this case, I'd go with the packaged solution. It's a good way to take advantage of all the stuff the LC control surface plugin allows you to do so easily. I'm thinking about getting it just to make good use of this old PC1600 fader/button box I have here.