Hi! I have a problem with routing back data to the Physical Input in the environment. WHAT I WANT TO DO: use an external controller (Doepfer Pocket Dial) to move the Song Position Pointer back and forth. Due to various reasons I have to process the MIDI data in the environment. Finally I get out two controllers: one to move it backwards and one to move it forward. THE PROBLEM: Since there is no meta message to move the SPP directly, I am doing it via a MIDI command (those hotkeys that can also be triggered by MIDI events). I found out that I have to route the data back to the Physical Input, because commands are apparently captured directly from there, not from the Sequencer input. I first specified my own meta message for this purpose, because I wanted to generate something exotic which no other external device could "accidently" generate as well. It did not work, so I guessed that meta messages are filtered out because they cannot really appear at a physical input. Just for testing I generated notes instead and that worked. Great! But these notes now cannot be played anymore. So I changed my events to controllers. Now again, it doesn't work. Why? The controller data simply does not appear at the physical input, although I have cabled it to go there! Any ideas how to solve this? Or maybe an idea for a different approach to achieve this? Thanks, Dennis P.S.: Another annoying fact is that there seems to be no way to grab any data from the PhysIn if it didn't really come in at an input. There are different outputs for every physical port, but no output for data that came in from a virtual cable in the environment. This is not relevant for my problem, but it seems pretty annoying. Or am I wrong somehow?

"travelboy_berlin" <dennis78@...> wrote: >Hi! I have a problem with routing back data to the Physical >Input in the environment. I can't answer your problem directly, but I'm very interested in what you have found because I am doing the same thing except routing the data to a setup of MidiPipe (a separate application) and back into Logic. I did not know that you could cable it into the Physical Input. Indeed I think I tried to do this already using controllers and it did not work, which is when I got MidiPipe to do it for me. But you say Notes work? Hmmm. Why don't you use Notes, but keep them on a Midi channel that you don't use from your master keyboard or other midi devices? You could use a Channel Splitter after the Phys In to make sure no stray notes on that channel get through. It may be, if you have Automation Quick Access enabled, that the controllers are being filtered off before getting to the Phys In? Have you tried Program Change messages? I have a problem in that Logic repeats indefinitely some Midi commands that I send it. "Select Next Track", for example, occasionally sends the selection right down to the bottom track of the arrange window. Some commands, like "Toggle Loop", freeze Logic in a repetitive loop of toggling. You should be OK with your song position commands, though, they seem to work fine. Cheers, Stephen.

Hi Stephen & others, I found a solution now for the problem of not being able to route back data to PhysIn. I am now converting the events to Notes on MIDI channel 16, cabled them back to PhysIn and using them as MIDI commands. It works fine now, I can use one knob on my external controller to move the SPP, another knob to select a tool, another knob select a screenset etc. Neat! :) Stephen <stephband@l...> wrote: > I am doing the same thing except routing the data to MidiPipe Yes, I've thought about it. That would probably have been my last solution too. I just wanted to find a way to do that without the need for external software. It's easier, and it's also less likely to go wrong one day, for example if you want to use the song on a different computer. > Why don't you use Notes, but keep them on a Midi channel that you > don't use from your master keyboard or other midi devices? Thanks, I am doing this now. The reason why I didn't like it is that it would be nicer to use events that never occur "accidently". I don't want a melody to trigger my commands, so controllers would have been better. I don't understand why controllers still don't work (they simply get lost), but notes do work. I used the highest possible notes on channel 16 (that I usually don't play on), so it's still a good solution. Stephen, have you tried it without MidiPipe yet? Dennis

On a fine day, 02-12-2003, travelboy_berlin wrote: >I found a solution now for the problem of not being able to route >back data to PhysIn. The PhysIn-loopback trick is broken, since v6.something I think. So you're right in not understanding why it doesn't work: it actually _should_ work, and _has_ worked. -- Hendrik Jan Veenstra h @ k n o w a r e . n l Omega Art: http://www.omega-art.com/

On Tuesday, Dec 2, 2003, at 04:31 Europe/London, travelboy_berlin wrote: > Thanks, I am doing this now. The reason why I didn't like it is that > it would be nicer to use events that never occur "accidently". I > don't want a melody to trigger my commands, so controllers would > have been better. I don't understand why controllers still don't > work (they simply get lost), but notes do work. I used the highest > possible notes on channel 16 (that I usually don't play on), so it's > still a good solution. > > Stephen, have you tried it without MidiPipe yet? No, but thanks to your insight I will get round to re-programming my environment - this week, hopefully. I think yours is a much better way of doing it. If you have time can you see if you can reproduce my problem of cyclic lockup? I got no response from the list when I posted a couple of weeks ago. Try just setting a Midi Command for "Select Next Track" and press the midi command twenty or so times in the arrange window to see what happens each time. Does it always do what it says? Mine occasionally repeats the Select Next Track until the selected track hits the bottom of the track list. Same problem with "Toggle Loop" and "Enable Record on Current Track", but these two lock Logic indefinitely. Cheers! Stephen.