jump to beginning show previous Showing Logic-users Thread 98064 of 105816 show next jump to end

Forum Index | Read LUG: Policy/Rules Messages Threads Digests | Post New Message | Search!

From: Hendrik De Clercq <hendrikdeclercq@tiscali.be>
Date: Sun, 5 Nov 2006 at 9:42:03 AM
Subject: SysEx Mapper --> output not what it should be
Message #220709
(I'm a logic pro 7.2.3 user) I connected a button fader to a transformer (set on sysex mapper). The button fader has been set to 'Control', on Ch1. It's sending a value on cc60 (= randomly taken value, as long as it doesn't affect the bytes in my sysex message). In the Sysex mapper, I set following conditions: Status=Control; Channel=1; -1-=All; -2-=All (last two values are set on all, just because I have set the cc of the button to a value that won't affect a byte in the SysEx message I create following Sysex message: $F0 $18 $0F $00 $55 $02 $01 $02 $04 $07 ... and I connect the transformer to an instrument. So far so good ... But when I'm monitoring the output of the transformer with the Event List, when clicking on the button, I'm seeing a different output from what I'd expect: $70 $00 $00 $70 $0F $18 $00 $55 $02 $01 $02 $04 $0C $05 $00 $7F $00 $00 there are some kind of likenesses between the two, but still, it's an invalid message and as a result, my MIDI Hardware doesn't recognize it (but receives it as I see the MIDI led flashing when I hit the button) Is this a Logic bug, or is there something wrong in my thinking? I've tested this in situations in which I actually did change a value, but it had the same result) I'd glad if someone could help my out (I've tested the same situation with a Sysex fader, and it actually worked out well).
Viewed 223 times, 1 reply, 3 messages in thread. Reply to this message.
From: Hendrik De Clercq <hendrikdeclercq@tiscali.be>
Date: Mon, 6 Nov 2006 at 4:02:49 PM
Subject: Re: SysEx Mapper --> output not what it should be
Message #220769
This is a reply to #220709.
OK, maybe this problem isn't that obvious to expect an answer, so I'll ask a different question: Are some of you using the sysex mapper succesfully? If so, can you give a short description how you set it up (input object, sysex message, etc. ...)? At least, I'd like to determine of it's logic bug or if it's me thank you PS: in my original post, I did type a mistake: last byte of my SysEx message is $F7, not $07.
Viewed 225 times, 1 reply, 3 messages in thread. Reply to this message.
From: Hendrik De Clercq <hendrikdeclercq@tiscali.be>
Date: Tue, 7 Nov 2006 at 11:08:38 AM
Subject: Re: SysEx Mapper --> output not what it should be
Message #220789
This is a reply to #220769.
UPDATE I've tested my set-up with a 7.1.1 transformer, and it works. There must be a bug with the 7.2.x SysEx Mapper. Bug Report sent ...
Viewed 206 times, 0 replies, 3 messages in thread. Reply to this message.

Forum Index | Read LUG: Policy/Rules Messages Threads Digests | Post New Message | Search!

Forum Index | Read LUG: Policy/Rules Messages Threads Digests | Post New Message | Search!


© 1994-2008, All Rights Reserved.