Emu XL-7 & MP-7 User's Group

Just wondering if anyone knows the commands for play and stop on the
CS. I'm setting up for a live configuration, and am trying to program
my remote 25's Play and Stop buttons to control the XL7. It's really
strange though, I even tried different midi monitors, and can't seem
to find the code needed to do this? 
Thanks,
ByronIV

Command Stations can receive and transmit the general start/stop 
MIDI messages. (I have a keyboard with built in basic MIDI functions,
like START/STOP, and it can controll the XX-7 without any synchronizing.)


Searched for a description for general midi sysex commands, I found this:

SysEx Command [Type : String] : SysEx Command to send.
Usage : The SysEx Command string must not contain the SysEx Start (F0) and 
SysEx Stop (F7) bytes which will be automatically added by the MxM.
Hexadecimal characters of the SysEx message must be preceded by the '!' 
character. For example, to send the MIDI Machine Control "Stop" command 
for device 1(F0 7F 00 06 01 F7), type the following string 
:"!7F!00!06!01".


Other way is to midimonitoring that device's output which should controll
the command station.

On Fri, 27 May 2005, funkjunke wrote:

> Just wondering if anyone knows the commands for play and stop on the
> CS. I'm setting up for a live configuration, and am trying to program
> my remote 25's Play and Stop buttons to control the XL7. It's really
> strange though, I even tried different midi monitors, and can't seem
> to find the code needed to do this?
> Thanks,
> ByronIV
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>

Please note that the sysex start and stop bytes are for delineating the 
beginning and end of the sysex message.
They are not the same thing as MIDI sequencer start and stop commands.
The XL-7 sends MIDI start and stop when you press the "play" or "stop" 
buttons.

Szonyi Andras wrote:

>Command Stations can receive and transmit the general start/stop 
>MIDI messages. (I have a keyboard with built in basic MIDI functions,
>like START/STOP, and it can controll the XX-7 without any synchronizing.)
>
>
>Searched for a description for general midi sysex commands, I found this:
>
>SysEx Command [Type : String] : SysEx Command to send.
>Usage : The SysEx Command string must not contain the SysEx Start (F0) and 
>SysEx Stop (F7) bytes which will be automatically added by the MxM.
>Hexadecimal characters of the SysEx message must be preceded by the '!' 
>character. For example, to send the MIDI Machine Control "Stop" command 
>for device 1(F0 7F 00 06 01 F7), type the following string 
>:"!7F!00!06!01".
>
>
>Other way is to midimonitoring that device's output which should controll
>the command station.
>
>
>
>On Fri, 27 May 2005, funkjunke wrote:
>
>  
>
>>Just wondering if anyone knows the commands for play and stop on the
>>CS. I'm setting up for a live configuration, and am trying to program
>>my remote 25's Play and Stop buttons to control the XL7. It's really
>>strange though, I even tried different midi monitors, and can't seem
>>to find the code needed to do this?
>>Thanks,
>>ByronIV
>>
>>    
>>

Right, but Szonyi was illustrating the MMC stop command (which I don't
think the XL-7 supports).  All you need is:
MIDI Song Start (0xFA) - Play from beginning
MIDI Song Continue (0xFB) - Play from current location
MIDI Song Stop (0xFC) - Stop at current location

There's a screen in the MIDI menu to enable/disable the reception of
start/stop that you'll need to enable if it's not already.

-Aaron

--- Greg Waltzer <egwaltzer@...> wrote:
> Please note that the sysex start and stop bytes are for delineating
> the 
> beginning and end of the sysex message.
> They are not the same thing as MIDI sequencer start and stop
> commands.
> The XL-7 sends MIDI start and stop when you press the "play" or
> "stop" 
> buttons.
> 
> Szonyi Andras wrote:
> 
> >Command Stations can receive and transmit the general start/stop 
> >MIDI messages. (I have a keyboard with built in basic MIDI
> functions,
> >like START/STOP, and it can controll the XX-7 without any
> synchronizing.)
> >
> >
> >Searched for a description for general midi sysex commands, I found
> this:
> >
> >SysEx Command [Type : String] : SysEx Command to send.
> >Usage : The SysEx Command string must not contain the SysEx Start
> (F0) and 
> >SysEx Stop (F7) bytes which will be automatically added by the MxM.
> >Hexadecimal characters of the SysEx message must be preceded by the
> '!' 
> >character. For example, to send the MIDI Machine Control "Stop"
> command 
> >for device 1(F0 7F 00 06 01 F7), type the following string 
> >:"!7F!00!06!01".
> >
> >
> >Other way is to midimonitoring that device's output which should
> controll
> >the command station.
> >
> >
> >
> >On Fri, 27 May 2005, funkjunke wrote:
> >
> >  
> >
> >>Just wondering if anyone knows the commands for play and stop on
> the
> >>CS. I'm setting up for a live configuration, and am trying to
> program
> >>my remote 25's Play and Stop buttons to control the XL7. It's
> really
> >>strange though, I even tried different midi monitors, and can't
> seem
> >>to find the code needed to do this?
> >>Thanks,
> >>ByronIV
> >>
> >>    
> >>
> 
> 
> ------------------------ Yahoo! Groups Sponsor
> --------------------~--> 
> In low income neighborhoods, 84% do not own computers.
> At Network for Good, help bridge the Digital Divide!
> http://us.click.yahoo.com/c9hWNA/3MnJAA/n1hLAA/pWZylB/TM
>
--------------------------------------------------------------------~->
> 
> 
>  
> Yahoo! Groups Links
> 
> 
> 
>  
> 
> 
> 
> 

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

Everyone is right!!! And let me add one more piece:

Midi Time Clock (0xF8) accounts for the synchronization betweeen the 
keyboard and the E-Mu.

The keyboard sends out an FA byte to start the clock which starts 
the E-Mu sequencer.  If you have OS2.0 and the E-Mu is set to 
external time clock, it slaves in sync to the midi clock master 
because the keyboard is sending out a stream of F8 bytes. When you 
press STOP, the synth then sends out and FC byte to stop the E-Mu 
sequencer.

The more F8 bytes in the midi stream, the faster the clock. (And 
vice versa: the fast the clock, the more F8 bytes placed into the 
midi stream.)

Midi also includes commands for song select and song position 
pointer, but the E-Mu does not implement those.

If you have two pieces of gear that implement midi time code, both 
should have the ability to be either master or slave. 

As for MMC [Midi Machine Control], I think I tried that (generating 
code from Cakewalk software) and the E-Mu did not respond.  I don't 
know anything about a "25's" (whether it uses MMC or MTC).

Hope this helps.

--Steve

--- In xl7@yahoogroups.com, Aaron Eppolito <synthesis77@y...> wrote:
> Right, but Szonyi was illustrating the MMC stop command (which I 
don't
> think the XL-7 supports).  All you need is:
> MIDI Song Start (0xFA) - Play from beginning
> MIDI Song Continue (0xFB) - Play from current location
> MIDI Song Stop (0xFC) - Stop at current location
> 
> There's a screen in the MIDI menu to enable/disable the reception 
of
> start/stop that you'll need to enable if it's not already.
> 
> -Aaron
> 
> --- Greg Waltzer <egwaltzer@c...> wrote:
> > Please note that the sysex start and stop bytes are for 
delineating
> > the 
> > beginning and end of the sysex message.
> > They are not the same thing as MIDI sequencer start and stop
> > commands.
> > The XL-7 sends MIDI start and stop when you press the "play" or
> > "stop" 
> > buttons.
> > 
> > Szonyi Andras wrote:
> > 
> > >Command Stations can receive and transmit the general 
start/stop 
> > >MIDI messages. (I have a keyboard with built in basic MIDI
> > functions,
> > >like START/STOP, and it can controll the XX-7 without any
> > synchronizing.)
> > >
> > >
> > >Searched for a description for general midi sysex commands, I 
found
> > this:
> > >
> > >SysEx Command [Type : String] : SysEx Command to send.
> > >Usage : The SysEx Command string must not contain the SysEx 
Start
> > (F0) and 
> > >SysEx Stop (F7) bytes which will be automatically added by the 
MxM.
> > >Hexadecimal characters of the SysEx message must be preceded by 
the
> > '!' 
> > >character. For example, to send the MIDI Machine Control "Stop"
> > command 
> > >for device 1(F0 7F 00 06 01 F7), type the following string 
> > >:"!7F!00!06!01".
> > >
> > >
> > >Other way is to midimonitoring that device's output which should
> > controll
> > >the command station.
> > >
> > >
> > >
> > >On Fri, 27 May 2005, funkjunke wrote:
> > >
> > >  
> > >
> > >>Just wondering if anyone knows the commands for play and stop 
on

> > the
> > >>CS. I'm setting up for a live configuration, and am trying to
> > program
> > >>my remote 25's Play and Stop buttons to control the XL7. It's
> > really
> > >>strange though, I even tried different midi monitors, and can't
> > seem
> > >>to find the code needed to do this?
> > >>Thanks,
> > >>ByronIV

--- steve_the_composer <smw-mail@...> wrote:
> Midi also includes commands for song select and song position 
> pointer, but the E-Mu does not implement those.

It doesn't do song select, but it does recieve and transmit Song
Position Pointer.


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new Resources site
http://smallbusiness.yahoo.com/resources/

Thanks for the correction. I'll have to take another look at that, 
although I can't think  of how I might want to use it.  I have gotten 
out of using my software sequencer in favor of the P2500's sequencer.  

--Steve

--- In xl7@yahoogroups.com, Aaron Eppolito <synthesis77@y...> wrote:

> --- steve_the_composer <smw-mail@p...> wrote:
> > Midi also includes commands for song select and song position 
> > pointer, but the E-Mu does not implement those.
> 
> It doesn't do song select, but it does recieve and transmit Song
> Position Pointer.

I just checked the pdf for the Novation ReMOTE 25. (It looks really 
nifty, btw.) However, I have no experience with it.

I didn't see anywhere that it sends MTC.  I suppose you might be able 
to route it through some software which receives MMC and in turn would 
send out the MTC.  IF you really want to do that.

--Steve

--- In xl7@yahoogroups.com, "funkjunke" <earworm@g...> wrote:

> Just wondering if anyone knows the commands for play and stop on the
> CS. I'm setting up for a live configuration, and am trying to program
> my remote 25's Play and Stop buttons to control the XL7. It's really
> strange though, I even tried different midi monitors, and can't seem
> to find the code needed to do this? 
> Thanks,
> ByronIV

Thanks for all the help guys, I didn't realize I would need to be
sending Midi Clock or time code, I assumed I could program it to just
'play' on command. Alas, it doesn't seem to want to via the remote. I
can't even enter the code '00 FA' unless I enter it as an Nrpn command
strin....the remote25s sysex won't allow any value to be entered in
one bit that equals more than 127 (FA being 250). MidiOX spit out a
different play command however (7F 7F 01 01 60 00 00 00), so I tried
that, and it was wierd, when I would upload the change to the
remote25, it would pass through and the sysex would hit the XL, and it
WOULD start playing, but then after the initial burst, the now
programmed Play button on the remote would do nothing....really odd.
I'm no expert on sysex whatsoever, so maybe I'm missing something, oh
well, lol.

And as for MMC, yeah, the CStations don't respond to that unfortunately.

No big loss, although it would have been nice to work it out like
that. I guess I can just rearrange stuff so that the XL is more hands
accessible when I'm using the remote as well.

BTW Steve, the Remote's are pretty nice, great keys, lots of knobs and
sliders, and even though they can do sysex strings and whatnot, the
capabilities of the peavey pc1600x seem far beyond the Remotes for
string command programming!

Cheers,
ByronIV

--- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@p...> wrote:

> I just checked the pdf for the Novation ReMOTE 25. (It looks really 
> nifty, btw.) However, I have no experience with it.
> 
> I didn't see anywhere that it sends MTC.  I suppose you might be able 
> to route it through some software which receives MMC and in turn would 
> send out the MTC.  IF you really want to do that.
> 
> --Steve
> 
> --- In xl7@yahoogroups.com, "funkjunke" <earworm@g...> wrote:
> > Just wondering if anyone knows the commands for play and stop on the
> > CS. I'm setting up for a live configuration, and am trying to program
> > my remote 25's Play and Stop buttons to control the XL7. It's really
> > strange though, I even tried different midi monitors, and can't seem
> > to find the code needed to do this? 
> > Thanks,
> > ByronIV

I just tested MidiOx and the P2500. MidiOx has both a Midi Sync 
Transport window and a Midi Time Code window.  Midi Sync uses the 
stream of F8 bytes. MTC uses a stream of F1 bytes based on frame 
settings.

The P2500 responds to the MidiOx Sync Transport controls.  I am not 
sure if you can slave MidiOx to the ReMOTE 25 and slave your CS to 
MidiOx.

My reading of the MidiOX help leads me to believe it is worth 
testing if you haven't found another solution yet. There is an 
example of how to slave Cakewalk to the MidiOx Sync Transport.

Then it says:

The [x] Sync and Send MTC concurrently checkbox allows the 
synchronization of MIDI clock and MTC. When it is checked, the MTC 
view will be loaded (with its transport disabled), and both items 
will be controlled by the MIDI sync transport. When play is started, 
both MTC and MIDI Sync will be generated, and both views will stop 
upon pressing Stop.

The question is, can MidiOx be slaved to the ReMOTE? I couldn't find 
how to do that with MidiOx, but perhaps MidiYoke would help. I don't 
have MidiYoke installed, so I couldn't test it out.

Let me know either way if you test it.

Hope this helps.

--Steve
  

--- In xl7@yahoogroups.com, "funkjunke" <earworm@g...> wrote:
> Thanks for all the help guys, I didn't realize I would need to be
> sending Midi Clock or time code, I assumed I could program it to 
just
> 'play' on command. Alas, it doesn't seem to want to via the 
remote. I
> can't even enter the code '00 FA' unless I enter it as an Nrpn 
command
> strin....the remote25s sysex won't allow any value to be entered in
> one bit that equals more than 127 (FA being 250). MidiOX spit out a
> different play command however (7F 7F 01 01 60 00 00 00), so I 
tried
> that, and it was wierd, when I would upload the change to the
> remote25, it would pass through and the sysex would hit the XL, 
and it
> WOULD start playing, but then after the initial burst, the now
> programmed Play button on the remote would do nothing....really 
odd.
> I'm no expert on sysex whatsoever, so maybe I'm missing something, 
oh
> well, lol.
> 
> And as for MMC, yeah, the CStations don't respond to that 
unfortunately.
> 
> No big loss, although it would have been nice to work it out like
> that. I guess I can just rearrange stuff so that the XL is more 
hands
> accessible when I'm using the remote as well.
> 
> BTW Steve, the Remote's are pretty nice, great keys, lots of knobs 
and
> sliders, and even though they can do sysex strings and whatnot, the
> capabilities of the peavey pc1600x seem far beyond the Remotes for
> string command programming!
> 
> Cheers,
> ByronIV
> 
> --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@p...> 
wrote:
> > I just checked the pdf for the Novation ReMOTE 25. (It looks 
really 
> > nifty, btw.) However, I have no experience with it.
> > 
> > I didn't see anywhere that it sends MTC.  I suppose you might be 
able 
> > to route it through some software which receives MMC and in turn 
would 
> > send out the MTC.  IF you really want to do that.
> > 
> > --Steve
> > 
> > --- In xl7@yahoogroups.com, "funkjunke" <earworm@g...> wrote:
> > > Just wondering if anyone knows the commands for play and stop 
on the
> > > CS. I'm setting up for a live configuration, and am trying to 
program
> > > my remote 25's Play and Stop buttons to control the XL7. It's 
really
> > > strange though, I even tried different midi monitors, and 
can't seem

> > > to find the code needed to do this? 
> > > Thanks,
> > > ByronIV

Just to be clear, here's a little primer on MIDI sync/control
protocols:

MIDI Song Start/Stop/Continue:
These are all 1 byte system realtime messages.  They're 0xFA, 0xFC, and
0xFB respectively.  These are all you need to start and stop your XL-7.


MIDI Song Position Pointer:
This tells your sequencer where it should start when it receives a
continue (0xFB) message.  It is a three byte message system common
message (0xF2 lsb msb) where msb and lsb are two 7 bit numbers that add
up to a 14 bit song position, measured in 16th notes.


MIDI Clock:
This conveys both tempo and relative position in beats.  It as well is
a 1 byte system realtime message.  It is 0xF8.  Each one that comes in
advances the song by 1/24th of a quarter note.  If you time the
interval between them, you can derive tempo.  The XL-7 uses the
positional information to drive the sequencer and derives tempo for the
tempo-based effects.  (side note: this is why despite the tempo
jittering on the LED display, the sequencer is dead on.  tempo can only
be derived, but position is absolute)


MIDI Time Code (MTC):
This is a different form of synchronization and control that is based
on SMPTE time (i.e. hours, minutes, seconds - not beats).  It is
commonly used with video equipment.  The XL-7 does NOT respond to these
types of messages.  There are actually two types of MTC: full frame
messages and quarter frame messages.

Full frame messages are a 10 byte sysex message (0xF0 0x7F id 0x01 0x01
hr mn sc fr 0xF7) where id is the sysex unit ID and the other 4 are
hours minutes seconds and frames.  It essentially is a locate command,
containing all the data necessary to specify an exact time.

Quarter frame messages are a collection of 2 byte realtime messages. 
They are 0xF1 followed by one of 8 data bytes: 0x0n - 0x7n.  Basically,
this accomplishes a similar thing to MIDI Clock in that it is a quick
message that carries position.  Each one of the 8 different messages
contains half of a byte of the 4 byte location, so, after 8 quarter
frame messages, you know your full location.


MIDI Machine Control (MMC):
This is a large part of the spec that specifies a way for devices to
tell each other to do stuff.  It is a a whole collection of message,
the most simple being a 6 byte sysex message (0xF0 0x7F id 0x06 cmd
0xF7) that can convey simple play, stop, continue, record, etc
(specified in the cmd byte).  There are many other more complicated MMC
commands beside the simple one above.  The XL-7 does NOT support any
MMC messages.

-Aaron

--- steve_the_composer <smw-mail@...> wrote:

> I just tested MidiOx and the P2500. MidiOx has both a Midi Sync 
> Transport window and a Midi Time Code window.  Midi Sync uses the 
> stream of F8 bytes. MTC uses a stream of F1 bytes based on frame 
> settings.
> 
> The P2500 responds to the MidiOx Sync Transport controls.  I am not 
> sure if you can slave MidiOx to the ReMOTE 25 and slave your CS to 
> MidiOx.
> 
> My reading of the MidiOX help leads me to believe it is worth 
> testing if you haven't found another solution yet. There is an 
> example of how to slave Cakewalk to the MidiOx Sync Transport.
> 
> Then it says:
> 
> The [x] Sync and Send MTC concurrently checkbox allows the 
> synchronization of MIDI clock and MTC. When it is checked, the MTC 
> view will be loaded (with its transport disabled), and both items 
> will be controlled by the MIDI sync transport. When play is started, 
> both MTC and MIDI Sync will be generated, and both views will stop 
> upon pressing Stop.
> 
> The question is, can MidiOx be slaved to the ReMOTE? I couldn't find 
> how to do that with MidiOx, but perhaps MidiYoke would help. I don't 
> have MidiYoke installed, so I couldn't test it out.
> 
> Let me know either way if you test it.
> 
> Hope this helps.
> 
> --Steve
>   
> 
> --- In xl7@yahoogroups.com, "funkjunke" <earworm@g...> wrote:
> > Thanks for all the help guys, I didn't realize I would need to be
> > sending Midi Clock or time code, I assumed I could program it to 
> just
> > 'play' on command. Alas, it doesn't seem to want to via the 
> remote. I
> > can't even enter the code '00 FA' unless I enter it as an Nrpn 
> command
> > strin....the remote25s sysex won't allow any value to be entered in
> > one bit that equals more than 127 (FA being 250). MidiOX spit out a
> > different play command however (7F 7F 01 01 60 00 00 00), so I 
> tried
> > that, and it was wierd, when I would upload the change to the
> > remote25, it would pass through and the sysex would hit the XL, 
> and it
> > WOULD start playing, but then after the initial burst, the now
> > programmed Play button on the remote would do nothing....really 
> odd.
> > I'm no expert on sysex whatsoever, so maybe I'm missing something, 
> oh
> > well, lol.
> > 
> > And as for MMC, yeah, the CStations don't respond to that 
> unfortunately.
> > 
> > No big loss, although it would have been nice to work it out like
> > that. I guess I can just rearrange stuff so that the XL is more 
> hands
> > accessible when I'm using the remote as well.
> > 
> > BTW Steve, the Remote's are pretty nice, great keys, lots of knobs 
> and
> > sliders, and even though they can do sysex strings and whatnot, the
> > capabilities of the peavey pc1600x seem far beyond the Remotes for
> > string command programming!
> > 
> > Cheers,
> > ByronIV
> > 
> > --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@p...> 
> wrote:
> > > I just checked the pdf for the Novation ReMOTE 25. (It looks 
> really 
> > > nifty, btw.) However, I have no experience with it.
> > > 
> > > I didn't see anywhere that it sends MTC.  I suppose you might be 
> able 
> > > to route it through some software which receives MMC and in turn 
> would 
> > > send out the MTC.  IF you really want to do that.
> > > 
> > > --Steve
> > > 
> > > --- In xl7@yahoogroups.com, "funkjunke" <earworm@g...> wrote:
> > > > Just wondering if anyone knows the commands for play and stop 
> on the
> > > > CS. I'm setting up for a live configuration, and am trying to 
> program
> > > > my remote 25's Play and Stop buttons to control the XL7. It's 
> really
> > > > strange though, I even tried different midi monitors, and 
> can't seem
> > > > to find the code needed to do this? 
> > > > Thanks,
> > > > ByronIV

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

Thanks for the primer. I found it insightful. I had wondered about the 
tempo display jitters; the side note about midi clock reassumed me.

--Steve

--- In xl7@yahoogroups.com, Aaron Eppolito <synthesis77@y...> wrote:
> Just to be clear, here's a little primer on MIDI sync/control
> protocols:

[snip]

Well, my main question left is, does midi clock need to be sent in
order to allow the XL7 to respond to start/stop commands? I assume
naturally not, but still have a problem with the remote25 programming,
since it will not allow me to program a sysex string on its play
button with 'FA' in it, since that is greater than 127....that does
seem to be what it responds to from the PC though, so I guess what I'm
really wondering is if there is a different way to program the command
'00 FA' in sysex? I tried using the same command via NRPN, but unless
I did it wrong, it didn't work. ;p
Cheers
BIV

On 5/29/05, Aaron Eppolito <synthesis77@...> wrote:
> Just to be clear, here's a little primer on MIDI sync/control
> protocols:
> 
> MIDI Song Start/Stop/Continue:
> These are all 1 byte system realtime messages.  They're 0xFA, 0xFC, and
> 0xFB respectively.  These are all you need to start and stop your XL-7.
> 
> 
> MIDI Song Position Pointer:
> This tells your sequencer where it should start when it receives a
> continue (0xFB) message.  It is a three byte message system common
> message (0xF2 lsb msb) where msb and lsb are two 7 bit numbers that add
> up to a 14 bit song position, measured in 16th notes.
> 
> 
> MIDI Clock:
> This conveys both tempo and relative position in beats.  It as well is
> a 1 byte system realtime message.  It is 0xF8.  Each one that comes in
> advances the song by 1/24th of a quarter note.  If you time the
> interval between them, you can derive tempo.  The XL-7 uses the
> positional information to drive the sequencer and derives tempo for the
> tempo-based effects.  (side note: this is why despite the tempo
> jittering on the LED display, the sequencer is dead on.  tempo can only
> be derived, but position is absolute)
> 
> 
> MIDI Time Code (MTC):
> This is a different form of synchronization and control that is based
> on SMPTE time (i.e. hours, minutes, seconds - not beats).  It is
> commonly used with video equipment.  The XL-7 does NOT respond to these
> types of messages.  There are actually two types of MTC: full frame
> messages and quarter frame messages.
> 
> Full frame messages are a 10 byte sysex message (0xF0 0x7F id 0x01 0x01
> hr mn sc fr 0xF7) where id is the sysex unit ID and the other 4 are
> hours minutes seconds and frames.  It essentially is a locate command,
> containing all the data necessary to specify an exact time.
> 
> Quarter frame messages are a collection of 2 byte realtime messages.
> They are 0xF1 followed by one of 8 data bytes: 0x0n - 0x7n.  Basically,
> this accomplishes a similar thing to MIDI Clock in that it is a quick
> message that carries position.  Each one of the 8 different messages
> contains half of a byte of the 4 byte location, so, after 8 quarter
> frame messages, you know your full location.
> 
> 
> MIDI Machine Control (MMC):
> This is a large part of the spec that specifies a way for devices to
> tell each other to do stuff.  It is a a whole collection of message,
> the most simple being a 6 byte sysex message (0xF0 0x7F id 0x06 cmd
> 0xF7) that can convey simple play, stop, continue, record, etc
> (specified in the cmd byte).  There are many other more complicated MMC
> commands beside the simple one above.  The XL-7 does NOT support any
> MMC messages.
> 
> -Aaron
> 
> --- steve_the_composer <smw-mail@...> wrote:
> 
> > I just tested MidiOx and the P2500. MidiOx has both a Midi Sync
> > Transport window and a Midi Time Code window.  Midi Sync uses the
> > stream of F8 bytes. MTC uses a stream of F1 bytes based on frame
> > settings.
> >
> > The P2500 responds to the MidiOx Sync Transport controls.  I am not
> > sure if you can slave MidiOx to the ReMOTE 25 and slave your CS to
> > MidiOx.
> >
> > My reading of the MidiOX help leads me to believe it is worth
> > testing if you haven't found another solution yet. There is an
> > example of how to slave Cakewalk to the MidiOx Sync Transport.
> >
> > Then it says:
> >
> > The [x] Sync and Send MTC concurrently checkbox allows the
> > synchronization of MIDI clock and MTC. When it is checked, the MTC
> > view will be loaded (with its transport disabled), and both items
> > will be controlled by the MIDI sync transport. When play is started,
> > both MTC and MIDI Sync will be generated, and both views will stop
> > upon pressing Stop.
> >
> > The question is, can MidiOx be slaved to the ReMOTE? I couldn't find
> > how to do that with MidiOx, but perhaps MidiYoke would help. I don't
> > have MidiYoke installed, so I couldn't test it out.
> >
> > Let me know either way if you test it.
> >
> > Hope this helps.
> >
> > --Steve
> >
> >
> > --- In xl7@yahoogroups.com, "funkjunke" <earworm@g...> wrote:
> > > Thanks for all the help guys, I didn't realize I would need to be
> > > sending Midi Clock or time code, I assumed I could program it to
> > just
> > > 'play' on command. Alas, it doesn't seem to want to via the
> > remote. I
> > > can't even enter the code '00 FA' unless I enter it as an Nrpn
> > command
> > > strin....the remote25s sysex won't allow any value to be entered in
> > > one bit that equals more than 127 (FA being 250). MidiOX spit out a
> > > different play command however (7F 7F 01 01 60 00 00 00), so I
> > tried
> > > that, and it was wierd, when I would upload the change to the
> > > remote25, it would pass through and the sysex would hit the XL,
> > and it
> > > WOULD start playing, but then after the initial burst, the now
> > > programmed Play button on the remote would do nothing....really
> > odd.
> > > I'm no expert on sysex whatsoever, so maybe I'm missing something,
> > oh
> > > well, lol.
> > >
> > > And as for MMC, yeah, the CStations don't respond to that
> > unfortunately.
> > >
> > > No big loss, although it would have been nice to work it out like
> > > that. I guess I can just rearrange stuff so that the XL is more
> > hands
> > > accessible when I'm using the remote as well.
> > >
> > > BTW Steve, the Remote's are pretty nice, great keys, lots of knobs
> > and
> > > sliders, and even though they can do sysex strings and whatnot, the
> > > capabilities of the peavey pc1600x seem far beyond the Remotes for
> > > string command programming!
> > >
> > > Cheers,
> > > ByronIV
> > >
> > > --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@p...>
> > wrote:
> > > > I just checked the pdf for the Novation ReMOTE 25. (It looks
> > really
> > > > nifty, btw.) However, I have no experience with it.
> > > >
> > > > I didn't see anywhere that it sends MTC.  I suppose you might be
> > able
> > > > to route it through some software which receives MMC and in turn
> > would
> > > > send out the MTC.  IF you really want to do that.
> > > >
> > > > --Steve
> > > >
> > > > --- In xl7@yahoogroups.com, "funkjunke" <earworm@g...> wrote:
> > > > > Just wondering if anyone knows the commands for play and stop
> > on the
> > > > > CS. I'm setting up for a live configuration, and am trying to
> > program
> > > > > my remote 25's Play and Stop buttons to control the XL7. It's
> > really
> > > > > strange though, I even tried different midi monitors, and
> > can't seem
> > > > > to find the code needed to do this?
> > > > > Thanks,
> > > > > ByronIV
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
> 
> 
> 
> 
> Yahoo! Groups Links
> 
> 
> 
> 
> 
> 
> 
> 


-- 
For your electronik listening pleasures 
http://www.limbikfreq.com
---
Mindset Studio Music and Media
http://www.mindsetstudio.com

I am not sure about your first question. (See explanation below.)  
But just to clarify a few basics:

Midi sysex strings start with F0 and end with F7.
FA, FB, and FC are not part of any sysex strings. They are 1-byte 
sysex commands.

Sysex command bytes go from 128 (0x80 in hex, 10000000 in binary) 
through 255 (0xFF in hex, 11111111 in binary). Sysex data--the stuff 
that is packaged within the F0 . . . F7 string--needs to be less 
than 128 (0x80).

So, you cannot send the FA, FB, or FC via sysex.  Nor can you send 
them via NRPN command.

Now to your first question: I used the MidiOx Sync Transport to 
start my E-Mu sequencer (using OS 2.0)when it was NOT set to ext.  
The MidiOx Transport successfully started, stopped, and continued 
the sequencer which played at the internal tempo.  The MidiOx 
Transport was sending out midi clocks (F8 bytes), but the E-Mu 
ignored them.

So, IF (and that's a big IF) you can manage to get the ReMOTE to 
send out just the single byte transport commands (FA, FB, and FC), 
you could do what I think you are trying to do.  However, when I 
looked at the ReMOTE pdf, I didn't see a way to do that.  Try 
Novation tech support.

Also, I have been playing around with MidiYoke in MidiOx and have 
not yet found a work around.  Based on Aaron's primer, I don't think 
it will work.  If ReMOTE only transmits MMC (not Midi Sync or MTC) 
and MidiOX only handles Midi Sync and MTC, you can't do it.

Hope this helps.

--Steve


--- In xl7@yahoogroups.com, ByronIV <earworm@g...> wrote:
> Well, my main question left is, does midi clock need to be sent in
> order to allow the XL7 to respond to start/stop commands? I assume
> naturally not, but still have a problem with the remote25 
programming,
> since it will not allow me to program a sysex string on its play
> button with 'FA' in it, since that is greater than 127....that does
> seem to be what it responds to from the PC though, so I guess what 
I'm
> really wondering is if there is a different way to program the 
command
> '00 FA' in sysex? I tried using the same command via NRPN, but 
unless

> I did it wrong, it didn't work. ;p
> Cheers
> BIV

0xFA is not 00 FA.  The "0x" is just to show that it's a hex number,
not decimal.  0x00 0xFA wouldn't be a valid MIDI command.  As far as
what the remote25 can send, it seems that it can't do system realtime
messages.  Okay, I just read through the 25's manual.  It doesn't do
system realtime or common (see implementation chart on pg 51).  It also
has a bunch of typos too (pg 34 about sysex(!), pg 41 charging, etc).

And yes, if you're not synced to MIDI Clock (i.e. your tempo isn't set
to external) you don't need to send 0xF8s to start and stop, just
0xFA/0xFB/0xFC.

I'd write Novation and ask that they allow mapping of the transport to
simple MIDI start/stop/continue messages.  It's trivial for them and
I'm surprised they didn't do it already.  Until they do, you'll have to
route the Novation's output through MIDIOx or something to convert it
into something the XL-7 understands.

-Aaron

--- ByronIV <earworm@...> wrote:

> Well, my main question left is, does midi clock need to be sent in
> order to allow the XL7 to respond to start/stop commands? I assume
> naturally not, but still have a problem with the remote25
> programming,
> since it will not allow me to program a sysex string on its play
> button with 'FA' in it, since that is greater than 127....that does
> seem to be what it responds to from the PC though, so I guess what
> I'm
> really wondering is if there is a different way to program the
> command
> '00 FA' in sysex? I tried using the same command via NRPN, but unless
> I did it wrong, it didn't work. ;p
> Cheers
> BIV
> 
> On 5/29/05, Aaron Eppolito <synthesis77@...> wrote:
> > Just to be clear, here's a little primer on MIDI sync/control
> > protocols:
> > 
> > MIDI Song Start/Stop/Continue:
> > These are all 1 byte system realtime messages.  They're 0xFA, 0xFC,
> and
> > 0xFB respectively.  These are all you need to start and stop your
> XL-7.
> > 
> > 
> > MIDI Song Position Pointer:
> > This tells your sequencer where it should start when it receives a
> > continue (0xFB) message.  It is a three byte message system common
> > message (0xF2 lsb msb) where msb and lsb are two 7 bit numbers that
> add
> > up to a 14 bit song position, measured in 16th notes.
> > 
> > 
> > MIDI Clock:
> > This conveys both tempo and relative position in beats.  It as well
> is
> > a 1 byte system realtime message.  It is 0xF8.  Each one that comes
> in
> > advances the song by 1/24th of a quarter note.  If you time the
> > interval between them, you can derive tempo.  The XL-7 uses the
> > positional information to drive the sequencer and derives tempo for
> the
> > tempo-based effects.  (side note: this is why despite the tempo
> > jittering on the LED display, the sequencer is dead on.  tempo can
> only
> > be derived, but position is absolute)
> > 
> > 
> > MIDI Time Code (MTC):
> > This is a different form of synchronization and control that is
> based
> > on SMPTE time (i.e. hours, minutes, seconds - not beats).  It is
> > commonly used with video equipment.  The XL-7 does NOT respond to
> these
> > types of messages.  There are actually two types of MTC: full frame
> > messages and quarter frame messages.
> > 
> > Full frame messages are a 10 byte sysex message (0xF0 0x7F id 0x01
> 0x01
> > hr mn sc fr 0xF7) where id is the sysex unit ID and the other 4 are
> > hours minutes seconds and frames.  It essentially is a locate
> command,
> > containing all the data necessary to specify an exact time.
> > 
> > Quarter frame messages are a collection of 2 byte realtime
> messages.
> > They are 0xF1 followed by one of 8 data bytes: 0x0n - 0x7n. 
> Basically,
> > this accomplishes a similar thing to MIDI Clock in that it is a
> quick
> > message that carries position.  Each one of the 8 different
> messages
> > contains half of a byte of the 4 byte location, so, after 8 quarter
> > frame messages, you know your full location.
> > 
> > 
> > MIDI Machine Control (MMC):
> > This is a large part of the spec that specifies a way for devices
> to
> > tell each other to do stuff.  It is a a whole collection of
> message,
> > the most simple being a 6 byte sysex message (0xF0 0x7F id 0x06 cmd
> > 0xF7) that can convey simple play, stop, continue, record, etc
> > (specified in the cmd byte).  There are many other more complicated
> MMC
> > commands beside the simple one above.  The XL-7 does NOT support
> any
> > MMC messages.
> > 
> > -Aaron
> > 
> > --- steve_the_composer <smw-mail@...> wrote:
> > 
> > > I just tested MidiOx and the P2500. MidiOx has both a Midi Sync
> > > Transport window and a Midi Time Code window.  Midi Sync uses the
> > > stream of F8 bytes. MTC uses a stream of F1 bytes based on frame
> > > settings.
> > >
> > > The P2500 responds to the MidiOx Sync Transport controls.  I am
> not
> > > sure if you can slave MidiOx to the ReMOTE 25 and slave your CS
> to
> > > MidiOx.
> > >
> > > My reading of the MidiOX help leads me to believe it is worth
> > > testing if you haven't found another solution yet. There is an
> > > example of how to slave Cakewalk to the MidiOx Sync Transport.
> > >
> > > Then it says:
> > >
> > > The [x] Sync and Send MTC concurrently checkbox allows the
> > > synchronization of MIDI clock and MTC. When it is checked, the
> MTC
> > > view will be loaded (with its transport disabled), and both items
> > > will be controlled by the MIDI sync transport. When play is
> started,
> > > both MTC and MIDI Sync will be generated, and both views will
> stop
> > > upon pressing Stop.
> > >
> > > The question is, can MidiOx be slaved to the ReMOTE? I couldn't
> find
> > > how to do that with MidiOx, but perhaps MidiYoke would help. I
> don't
> > > have MidiYoke installed, so I couldn't test it out.
> > >
> > > Let me know either way if you test it.
> > >
> > > Hope this helps.
> > >
> > > --Steve
> > >
> > >
> > > --- In xl7@yahoogroups.com, "funkjunke" <earworm@g...> wrote:
> > > > Thanks for all the help guys, I didn't realize I would need to
> be
> > > > sending Midi Clock or time code, I assumed I could program it
> to
> > > just
> > > > 'play' on command. Alas, it doesn't seem to want to via the
> > > remote. I
> > > > can't even enter the code '00 FA' unless I enter it as an Nrpn
> > > command
> > > > strin....the remote25s sysex won't allow any value to be
> entered in
> > > > one bit that equals more than 127 (FA being 250). MidiOX spit
> out a
> > > > different play command however (7F 7F 01 01 60 00 00 00), so I
> > > tried
> > > > that, and it was wierd, when I would upload the change to the
> > > > remote25, it would pass through and the sysex would hit the XL,
> > > and it
> > > > WOULD start playing, but then after the initial burst, the now
> > > > programmed Play button on the remote would do nothing....really
> > > odd.
> > > > I'm no expert on sysex whatsoever, so maybe I'm missing
> something,
> > > oh
> > > > well, lol.
> > > >
> > > > And as for MMC, yeah, the CStations don't respond to that
> > > unfortunately.
> > > >
> > > > No big loss, although it would have been nice to work it out
> like
> > > > that. I guess I can just rearrange stuff so that the XL is more
> > > hands
> > > > accessible when I'm using the remote as well.
> > > >
> > > > BTW Steve, the Remote's are pretty nice, great keys, lots of
> knobs
> > > and
> > > > sliders, and even though they can do sysex strings and whatnot,
> the
> > > > capabilities of the peavey pc1600x seem far beyond the Remotes
> for
> > > > string command programming!
> > > >
> > > > Cheers,
> > > > ByronIV
> > > >
> > > > --- In xl7@yahoogroups.com, "steve_the_composer"
> <smw-mail@p...>
> > > wrote:
> > > > > I just checked the pdf for the Novation ReMOTE 25. (It looks
> > > really
> > > > > nifty, btw.) However, I have no experience with it.
> > > > >
> > > > > I didn't see anywhere that it sends MTC.  I suppose you might
> be
> > > able
> > > > > to route it through some software which receives MMC and in
> turn
> > > would
> > > > > send out the MTC.  IF you really want to do that.
> > > > >
> > > > > --Steve
> > > > >
> > > > > --- In xl7@yahoogroups.com, "funkjunke" <earworm@g...> wrote:
> > > > > > Just wondering if anyone knows the commands for play and
> stop
> > > on the
> > > > > > CS. I'm setting up for a live configuration, and am trying
> to
> > > program
> > > > > > my remote 25's Play and Stop buttons to control the XL7.
> It's
> > > really
> > > > > > strange though, I even tried different midi monitors, and
> > > can't seem
> > > > > > to find the code needed to do this?
> > > > > > Thanks,
> > > > > > ByronIV
> > 
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam protection around
> > http://mail.yahoo.com
> > 
> > 
> > 
> > 
> > Yahoo! Groups Links
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> 
> 
> -- 
> For your electronik listening pleasures 
> http://www.limbikfreq.com
> ---
> Mindset Studio Music and Media
> http://www.mindsetstudio.com
> 
> 
> ------------------------ Yahoo! Groups Sponsor
> --------------------~--> 
> Has someone you know been affected by illness or disease?
> Network for Good is THE place to support health awareness efforts!
> http://us.click.yahoo.com/pKxVKC/UOnJAA/n1hLAA/pWZylB/TM
>
--------------------------------------------------------------------~->
> 
> 
>  
> Yahoo! Groups Links
> 
> 
> 
>  
> 
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

BTW, have you thought about using foot switches (or a foot 
controller) to start and stop the E-Mu?  Hmmmmm,  Having said that, 
I am wondering if you can program the ReMOTE's Transport buttons to 
serve the same function as foot controllers.

ReMOTE pdf (page 43):
The transport buttons may defined in the same manner as any of the 
other programmable buttons in Template Edit Mode. However, they are 
ideally suited to controlling sequencers or recording device. 
Therefore, they can alternatively be assigned to transmit MIDI MMC 
(MIDI Machine Control) commands. Each one of the 64 Template 
memories can hold its own set of definitions for these five buttons.
The details of assigning MMC to these buttons and the range of MMC 
commands available is described in detail on page 32.
Some sequencers (such as Cubase) Use other types of MIDI message for 
remote control purposes such as MIDI Note messages. The TRANSPORT 
buttons can of course be configured to transmit these instead
of MMC in the normal way. Consult your sequencer documentation for 
full details of the MIDI messages used for remote control purposes.

See "GIVE THIS A TRY FIRST" below!!

I would encourage you to take Aaron's suggestion and suggest to 
Novation they implement Start/Continue/Stop as a control type for the 
transport buttons. (But don't bug them about the typos.) They may not 
have wanted to implement a master clock on that model, but even with 
that, they should still be able to set up a Transport Control Type.  
(Do they have a higher cost version that does have a built in midi 
clock generator?)

In the meantime, you can program the transport buttons as CCs.

WAIT A SEC!!!!!

I discovered some undocumented E-Mu remote control commands.  One of 
them is Play/Continue. (I have done anything with those in quite a 
while.)

Hmmmmm. You would have to use one button to open E-Mu's remote control 
mode, one button for the E-Mu remote control start command, and one 
button to close E-Mu's remote control mode.

But wait!!!  GIVE THIS A TRY FIRST:

The picture on page 34 shows the cursor under the 0 in the F0.  Can 
you change that to an FA and only have one byte?  If so, you maye be 
in luck.

The manual states: "If all 18 bytes of the System Exclusive message 
are used the F7 end of message value will be automatically inserted." 
Maybe that means if you only use 1 byte (FA) the F7 will NOT be 
inserted.

Good luck!

--- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@p...> wrote:
> BTW, have you thought about using foot switches (or a foot 
> controller) to start and stop the E-Mu?

[snip]

I am not sure if the GIVE THIS A TRY suggestion will work.  It cannot 
be done with the template editor. I just played with it and the F0 and 
F7 bytes are not stored in the template. There's no way to trick the 
template editor, so I'm not sure if you can trick the hardware itself. 
But who knows.

--- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@p...> wrote:
> See "GIVE THIS A TRY FIRST" below!!

[snip]

Thanks to a typo while trying to test the play command, I discovered a 
new one (not previously on my chart)--the record button command which 
rotates through the 4 record modes!!

Unfortunately it is not useful yet, because although I have the record 
and play buttons, I don't have the stop button.

Just discovered what turns on trigger button 1, too.

Steve and everyone else...great work with this remote control investigation.
Will you be able to summarize all of these commands and put them in a file
for our file sections...reference for future generations (or even ourselves
when we are ready to do the remote control thing...)

Thanks
Bob
Corona/Riverside, CA


----- Original Message -----

From: "steve_the_composer" <smw-mail@...>
To: <xl7@yahoogroups.com>
Sent: Sunday, May 29, 2005 5:23 PM
Subject: [xl7] More Undocumented Remote Control Sysex Commands


> Thanks to a typo while trying to test the play command, I discovered a
> new one (not previously on my chart)--the record button command which
> rotates through the 4 record modes!!
>
> Unfortunately it is not useful yet, because although I have the record
> and play buttons, I don't have the stop button.
>
> Just discovered what turns on trigger button 1, too.
>
>
>
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>

Wow, holy feedback....thanks guys! So far nothing has worked though.
Using the PC as a translator isn't really useful either, seeing as
that I won't have my PC with me when I'm playing live, which is why I
even bought an XL.

Also, there is no way to trick the hadrware into using FA as a
command....in fact, the only commands that start with an F that I can
enter, at any bit spot, are F7 and F0...actually, F0 is always there,
and not editable.

I do intend to contact Novation however, this remote was actually a
close friends originally, and when he first started editing, he
suggested to them that they allow multiple steps to be programmed for
incremental CC# sending, and they added that to the next OS. So,
perhaps all may be well in the end :)

I tried the bit with the foot controllers too, about all I can do with
the remote, is set the CC# to the same # as the foot controllers, but,
it didn't work?

>>"I discovered some undocumented E-Mu remote control commands.  One of
>>them is Play/Continue. (I have done anything with those in quite a
>>while.)"

Where did you find this? :)

Cheers, and thanks for the help again guys!
BIV



-- 
For your electronik listening pleasures 
http://www.limbikfreq.com
---
Mindset Studio Music and Media
http://www.mindsetstudio.com

It is very tedious work and still rather incomplete.  It is all 
trial and error--which is only limited by what I decide to try. (It 
represents work spanning a couple of years.)

For example, I had been working in pattern mode and found what I 
considered to be oddities. For example, I found a command that 
starts the sequencer via remote and a command that would stop the 
sequencer via remote--but only if it had been started from the front 
panel.  In other words, no stop via remote if it had been started by 
remote.

Well, when I tried it in song mode (which I hardly use), IT 
WORKED!!!!  (Byron--If you need the ReMOTE 25 to start and stop the 
E-Mu in song mode only, I may have some sysex commands for you. I 
will test it some more before posting.

Keep in mind, these work only when the E-Mu is in remote control 
mode. When in remote control mode, the E-Mu also sends remote 
control sysex. If you have the E-Mu's midi out going to other gear, 
it will receive the sysex (which may or may not be a problem).

More to follow.

Aaron, any caveats or warnings regarding the use of E-mu's remote 
control?  (Or any insights into the logic behind it, what the code 
is of the tap button, etc.)

PS: I did find the command that turns XMIX on.



--- In xl7@yahoogroups.com, "Bob S." <tttsystems@e...> wrote:
> Steve and everyone else...great work with this remote control 
investigation.
> Will you be able to summarize all of these commands and put them 
in a file
> for our file sections...reference for future generations (or even 
ourselves
> when we are ready to do the remote control thing...)
> 
> Thanks
> Bob
> Corona/Riverside, CA
> 
> 
> ----- Original Message -----
> From: "steve_the_composer" <smw-mail@p...>
> To: <xl7@yahoogroups.com>
> Sent: Sunday, May 29, 2005 5:23 PM
> Subject: [xl7] More Undocumented Remote Control Sysex Commands
> 
> 
> > Thanks to a typo while trying to test the play command, I 
discovered a
> > new one (not previously on my chart)--the record button command 
which
> > rotates through the 4 record modes!!
> >
> > Unfortunately it is not useful yet, because although I have the 
record

> > and play buttons, I don't have the stop button.
> >
> > Just discovered what turns on trigger button 1, too.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >

--- In xl7@yahoogroups.com, ByronIV <earworm@g...> wrote:

> I do intend to contact Novation however, this remote was actually a
> close friends originally, and when he first started editing, he
> suggested to them that they allow multiple steps to be programmed
> for incremental CC# sending, and they added that to the next OS.
> So, perhaps all may be well in the end :)

This is fantastic that they are so responsive to customer input!!
> 
> I tried the bit with the foot controllers too, about all I can do
> with the remote, is set the CC# to the same # as the foot
> controllers, but, it didn't work?

Ooops. I meant using foot switches going to the CS directly. Via 
midi all you can do is CCs. To do stuff with the transport, you need 
to use the CS footswitch jacks.  (The P2500 has them; I hope the 
others do, too.)

> 
> >>"I discovered some undocumented E-Mu remote control commands. 
> >> One of them is Play/Continue. (I have done anything with those
> >> in quite a while.)"
> 
> Where did you find this? :)

See pp. 36-39 in the Proteus Family Sysex Manual v. 2.2 for the 
basics on Remote Control Sysex.  However, there is much that is not 
there.

Also, search the archives for "remote control." I am sure I wrote 
about it a few times. Keep pressing next (to search backwards for 
earlier posts). I think it was over a year ago.

Notes: 
--Sysex Device ID is assumed as 00 in my examples.
--Sysex is given in hex.
--works on my P2500 with OS2.0
--There are no guarantees.
====================================== 
OPEN/CLOSE REMOTE CONTROL SESSION
====================================== 
Open Remote Control Session:
F0 18 0F 00 55 40 10 F7 

Close Remote Control Session
F0 18 0F 00 55 40 11 F7
=====================================
MODE/VIEW BUTTONS
====================================== 
Song Mode View On:
F0 18 0F 00 55 40 20 46 00 00 F7 

Pattern Mode View On:
F0 18 0F 00 55 40 20 05 00 00 F7 

Preset View Toggle (on/off):
F0 18 0F 00 55 40 20 15 00 00 F7 

Mix View Toggle (on/off):
F0 18 0F 00 55 40 20 25 00 00 F7 

====================================== 
TRANSPORT BUTTONS (use in SONG MODE!)
====================================== 
Play/Continue:
F0 18 0F 00 55 40 20 42 00 00 F7

Stop:
F0 18 0F 00 55 40 20 32 00 00 F7 
 
====================================== 
MUTE BUTTONS (various modes)
====================================== 
Notes:
--In Edit Preset Mode Mute Buttons
select edit parameter menus (groups and
pages within groups).
--In Track Mute Mode (both song mode and
pattern mode) Mute Buttons toggle tracks
(on/off).
--In other modes the buttons do other things.
--Some of the buttons also work with different
values in the byte before the F7. Most (not all)
work with 00 and 01. For consistency, I have set
them all to 02.
Button 1:
F0 18 0F 00 55 40 20 03 00 02 F7
Button 2:
F0 18 0F 00 55 40 20 13 00 02 F7
Button 3:
F0 18 0F 00 55 40 20 23 00 02 F7
Button 4:
F0 18 0F 00 55 40 20 33 00 02 F7
Button 5:
F0 18 0F 00 55 40 20 43 00 02 F7 
Button 6:
F0 18 0F 00 55 40 20 02 00 02 F7 
Button 7:
F0 18 0F 00 55 40 20 12 00 02 F7 
Button 8:
F0 18 0F 00 55 40 20 22 00 02 F7 
Button 9:
F0 18 0F 00 55 40 20 32 00 02 F7 
Button 10:
F0 18 0F 00 55 40 20 31 00 02 F7 
Button 11:
F0 18 0F 00 55 40 20 41 00 02 F7 
Button 12:
F0 18 0F 00 55 40 20 00 00 02 F7 
Button 13:
F0 18 0F 00 55 40 20 10 00 02 F7 
Button 14:
F0 18 0F 00 55 40 20 20 00 02 F7 
Button 15:
F0 18 0F 00 55 40 20 30 00 02 F7 
Button 16:
F0 18 0F 00 55 40 20 40 00 02 F7 
==========================================================
There's tons more. This is just the tip of the iceberg.
Hope it helps. (Also, let me know if there are any typos.)

--Dr. Steve
==========================================================

Hey Byron.  Using The ReMOTE Editor (version 1.1) I created a test 
template.  I wasn't sure if you were using USB, Midi 1, or Midi 2, 
so I left all of them enabled. I used sysex ID = 0.

The functions I set up are as follows:

FF - opens the E-Mu Remote Control Session
RWN - closes it
REC - puts the unit in Song Mode View
Play - Plays or continues the current sequence (use in SONG MODE!!)
Stop - Stops the current sequence (use in SONG MODE!!)

I set up the 1st 3 buttons on the top left as track mutes.

If you try the template, let me know if it works.  (Be sure to save 
your current settings first!!!!!)

Its in the files section of the group.

Hope it helps.

Addendum # 1: If you want a button to simulate rotating the big data 
knob, try the following:

Increase value at cursor by 1 (+1):
F0 18 0F 00 55 40 22 01 00 01 00 F7

Decrease value at cursor by 1 (-1):
F0 18 0F 00 55 40 22 01 00 7F 7F F7 

So, if you are in the Song Mode View
and the transport is stopped 
and the cursor is under the song number (eg, 020^00) 
to select the next song, press a button to send +1.

Hey, thanks Steve, you must be pretty bored! In any case, I'm not
really intending to use song mode for much of anything on the XL7
(thats what my PC is for hehe), but I did try these in pattern mode
too, and the rewind and FF work as you stated mostly (dont always seem
to go in and out of the remote mode) but once into the remote mode,
the play will work one time, or vice versa, the stop will work one
time. Then I have to exit the remote mode by triple pressing stop on
the EMU, and then the play or stop will work once again. Record goes
directly into song mode and just sits there.

Definately very interesting regardless, I'm going to have to play
around with this after I have some coffee in me :)

ByronIV

-- 
For your electronik listening pleasures 
http://www.limbikfreq.com
---
Mindset Studio Music and Media
http://www.mindsetstudio.com

Yeah, I really should invest in some footswitches...I could use a few
for a multitude of things. I mostly blew all my cash on this XL7 and a
soon to be here jomox Airbase...all to better my live capabilities
really....it will be a must before I'm doing many shows though I
think.
ByronIV

On 5/30/05, steve_the_composer <smw-mail@...> wrote:
> --- In xl7@yahoogroups.com, ByronIV <earworm@g...> wrote:
> 
> > I do intend to contact Novation however, this remote was actually a
> > close friends originally, and when he first started editing, he
> > suggested to them that they allow multiple steps to be programmed
> > for incremental CC# sending, and they added that to the next OS.
> > So, perhaps all may be well in the end :)
> 
> This is fantastic that they are so responsive to customer input!!
> >
> > I tried the bit with the foot controllers too, about all I can do
> > with the remote, is set the CC# to the same # as the foot
> > controllers, but, it didn't work?
> 
> Ooops. I meant using foot switches going to the CS directly. Via
> midi all you can do is CCs. To do stuff with the transport, you need
> to use the CS footswitch jacks.  (The P2500 has them; I hope the
> others do, too.)
> 
> >
> > >>"I discovered some undocumented E-Mu remote control commands.
> > >> One of them is Play/Continue. (I have done anything with those
> > >> in quite a while.)"
> >
> > Where did you find this? :)
> 
> See pp. 36-39 in the Proteus Family Sysex Manual v. 2.2 for the
> basics on Remote Control Sysex.  However, there is much that is not
> there.
> 
> Also, search the archives for "remote control." I am sure I wrote
> about it a few times. Keep pressing next (to search backwards for
> earlier posts). I think it was over a year ago.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Yahoo! Groups Links
> 
> 
> 
> 
> 
> 
> 


-- 
For your electronik listening pleasures 
http://www.limbikfreq.com
---
Mindset Studio Music and Media
http://www.mindsetstudio.com

Not bored, just avoiding work I SHOULD be doing!!  ;-) 

I am aware of the problems you mentioned with the transport commands 
in pattern mode. Wish the whole thing was docemented and accessible!!

I need to catch up on other projects. Let me know if other sysex 
commands might better meet your needs.

--Steve

--- In xl7@yahoogroups.com, ByronIV <earworm@g...> wrote:
> Hey, thanks Steve, you must be pretty bored! In any case, I'm not
> really intending to use song mode for much of anything on the XL7
> (thats what my PC is for hehe), but I did try these in pattern mode
> too, and the rewind and FF work as you stated mostly (dont always 
seem
> to go in and out of the remote mode) but once into the remote mode,
> the play will work one time, or vice versa, the stop will work one
> time. Then I have to exit the remote mode by triple pressing stop 
on
> the EMU, and then the play or stop will work once again. Record 
goes

> directly into song mode and just sits there.
> 
> Definately very interesting regardless, I'm going to have to play
> around with this after I have some coffee in me :)
> 
> ByronIV
> 
> -- 
> For your electronik listening pleasures 
> http://www.limbikfreq.com
> ---
> Mindset Studio Music and Media
> http://www.mindsetstudio.com

Damn, you're a trooper, Steve!  For your edification, the remote panel
sysex stuff was a vestige from the Proteus 2000 (which itself was a
holdover from the E4 for use with EOSLink).  I'm not sure we ever got
it fully functional with the XL-7.  At one point, I was using it when I
was prototyping XL-7 sequencer code on the P2K and didn't have any
buttons.  It probably hasn't been used (or tested) since.

I'll try and dig up all the button codes; they're around here
somewhere.  In the meantime, the reason you're getting play/stop button
oddities is that there's both button down AND up messages.  You need to
send both.  There's a state associated with the play button (it needs
to know if you're holding play when you hit rec or stop to go to grid
or restart respectively).  There should be a way to get the XL-7 to
SEND the buttons via sysex too so you could see what it's doing.

-Aaron

--- steve_the_composer <smw-mail@...> wrote:
> I am aware of the problems you mentioned with the transport commands 
> in pattern mode. Wish the whole thing was docemented and accessible!!

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com