Synth-DIY Yahoo! Groups Archives

Thread

Newbie: understanding Hex & SysEx??????????????

2010-02-23 by Rob

I've only been producing and using the Emu a few months.  I've been reading manuals and everything on the internet I can find. I am starting to understand Hex & have figure out NRPNs and CC.  BUT some SysEx is alien to me.  The Emu manual has things like KK VV XX YY ZZ  NN but  hex is 0 to H. The sysex info seems to have different meanings for different commands for the letters.

8n kk vv is the command for note off.

n = midi number
kk = ?
vv = ?

Is this so standard that all companies shouldn't have to define it and I'm missing some chart on it?

Is 8n kk vv all I enter or do I need more numbers for machine ID, EMU id, on, off, etc?

Most of the tutorial sites treat you like a computer programer not a layman.

Re: [xl7] Newbie: understanding Hex & SysEx??????????????

2010-02-23 by Jack Pratt

Usually the sysex documentation explains for each command what the variables stand for [the letters are just variables to be replaced by a hexadecimal value]. This is so obvious that it always assumed and people who can't figure that out shouldn't bother trying. Hexadecimal is 0 to F [not H].

The pairing of the letters means that they represent an 8 bit value (two hex nibbles). Often the letters are used to have some kind of significance.

In the case of the note on command (which is strictly speaking NOT sysex), 8n means that the hexadecimal nibble pair with an 8 as the first nibble and 'n' as the second (for the midi channel); kk represents the note [a bigger number is a higher pitched note]; and vv represents the velocity [a bigger number is a louder note & a velocity of 00 is the same as note off]. The note on command is one way of switching notes off, but there is also a separate note off command. Sysex is used for more complex things than switching notes on and off.

It seems that you do not have the background to work with sysex, so you should probably give up.

Show quoted textHide quoted text

From: Rob
To: xl7@yahoogroups.com
Sent: Tue, February 23, 2010 11:31:36 AM
Subject: [xl7] Newbie: understanding Hex & SysEx??????????????

I've only been producing and using the Emu a few months. I've been reading manuals and everything on the internet I can find. I am starting to understand Hex & have figure out NRPNs and CC. BUT some SysEx is alien to me. The Emu manual has things like KK VV XX YY ZZ NN but hex is 0 to H. The sysex info seems to have different meanings for different commands for the letters.

8n kk vv is the command for note off.

n = midi number
kk = ?
vv = ?

Is this so standard that all companies shouldn't have to define it and I'm missing some chart on it?

Is 8n kk vv all I enter or do I need more numbers for machine ID, EMU id, on, off, etc?

Most of the tutorial sites treat you like a computer programer not a layman.

Re: [xl7] Newbie: understanding Hex & SysEx??????????????

2010-02-23 by Jane

Hi Rob,

On Feb 23, 2010, at 02:31, Rob wrote:

> I've only been producing and using the Emu a few months.  I've been reading manuals and everything on the internet I can find. I am starting to understand Hex & have figure out NRPNs and CC.  BUT some SysEx is alien to me.  The Emu manual has things like KK VV XX YY ZZ  NN but  hex is 0 to H. The sysex info seems to have different meanings for different commands for the letters.

0-F is just a different representation for the same thing: numbers. base10 uses 0-9. in computing a lot is about bits (0-1, base2) and bytes.
the great thing about hexadecimal (base16) is that you can represent every byte value with just 2 hex literals. eg:
FF = 255 = 1111 1111
0F =  15 = 0000 1111
F0 = 240 = 1111 0000

> 
> 8n kk vv is the command for note off.
> 
> n = midi number
> kk = ?
> vv = ?

n, kk and vv are just placeholders for hex values. that means that you are supposed to replace these with real numbers in form of hex literals.

> 
> Is this so standard that all companies shouldn't have to define it and I'm missing some chart on it?

yes, it's called "MIDI Protocol". :)
http://www.blitter.com/~russtopia/MIDI/~jglatt/tech/midispec.htm

> 
> Is 8n kk vv all I enter or do I need more numbers for machine ID, EMU id, on, off, etc?
> 
> Most of the tutorial sites treat you like a computer programer not a layman.


hope this helps,
Jan

RE: [xl7] Newbie: understanding Hex & SysEx??????????????

2010-02-23 by Geert Depuydt

hey sorry, but you should never say to anyone to give up on somethig. there was a time when even you had no single clue, right?

so "the letters are just variables to be replaced by a hexadecimal value" would have done just as well to help the guy, no? ;-)

anyway, your efforts for emu xl-7 project are very much appreciated.

regards,
geert

To: xl7@yahoogroups.com

Show quoted textHide quoted text

From: woodsworth1@...
Date: Mon, 22 Feb 2010 18:35:31 -0800
Subject: Re: [xl7] Newbie: understanding Hex & SysEx??????????????

The pairing of the letters means that they represent an 8 bit value (two hex nibbles). Often the letters are used to have some kind of significance.

It seems that you do not have the background to work with sysex, so you should probably give up.

From: Rob com>
To: xl7@yahoogroups.com
Sent: Tue, February 23, 2010 11:31:36 AM
Subject: [xl7] Newbie: understanding Hex & SysEx??????????????

Gratis verblufffende panoramafoto's maken? Met Photo Gallery is dit zo gebeurd.

Re: [xl7] Newbie: understanding Hex & SysEx??????????????

2010-02-23 by Jack Pratt

well, [you are correct but] if after a few months you've got effectively nowhere [and haven't figured out something so basic that no one ever explains it], how much time are you going to waste?

A better way to learn would be to use midi ox (or equivalent) and just look at the traffic going back and forth, or to use Jane's wonderful prodatum program and not bother with midi or sysex at all.

http://prodatum.sourceforge.net/

Show quoted textHide quoted text

From: Geert Depuydt
To: xl7@yahoogroups.com
Sent: Tue, February 23, 2010 6:49:00 PM
Subject: RE: [xl7] Newbie: understanding Hex & SysEx??????????????

Re: [xl7] Newbie: understanding Hex & SysEx??????????????

2010-02-23 by Paul Vickers

Hexadecimal is a base-16 counting system. In decimal (base 10) we use  
the digits 0-9. The sum 9+1 leads to an answer that cannot be  
expressed in a single digit so we add a '10s' column, put a 1 in it  
and put zero in the units column, hence: 10. Hex, as it is base 16  
needs 16 digits to represent its units, so we have 0-9 which have  
their usual decimal meaning and then A-F for the hex units whose  
decimal values are 10, 11, 12, 13, 14, and 15. So, the sum F+1 is 15+1  
in decimal = 16. As 16 cannot be represented by a single hex digit we  
put a 1 in the 16s column and a zero in the units column to give: 10.  
So 10 in hex is 16 in decimal.

Thus we see that FF in hex is 255 in decimal (15*16 + 15).

Hex is widely used in computing circles because of its ability to  
represent powers of 2 in a few digits. A single 8-bit byte can hold up  
to 256 binary values (from 00000000 to 11111111). As each nybble (4- 
bits, or half a byte) has a maximum value of 15 decimal (1111) then a  
single byte can be represented by a maximum of two hex digits.

Show quoted textHide quoted text

On 23 Feb 2010, at 01:31, Rob wrote:

> I've only been producing and using the Emu a few months. I've been  
> reading manuals and everything on the internet I can find. I am  
> starting to understand Hex & have figure out NRPNs and CC. BUT some  
> SysEx is alien to me. The Emu manual has things like KK VV XX YY ZZ  
> NN but hex is 0 to H. The sysex info seems to have different  
> meanings for different commands for the letters.
>
> 8n kk vv is the command for note off.
>
> n = midi number
> kk = ?
> vv = ?
>
> Is this so standard that all companies shouldn't have to define it  
> and I'm missing some chart on it?
>
> Is 8n kk vv all I enter or do I need more numbers for machine ID,  
> EMU id, on, off, etc?
>
> Most of the tutorial sites treat you like a computer programer not a  
> layman.
>
>
>

Re: [xl7] Newbie: understanding Hex & SysEx??????????????

2010-02-23 by D F Tweedie

Paul,

You must be a teacher! What an eloquent explanation.

DF Tweedie

--- On Tue, 2/23/10, Paul Vickers <paul@...> wrote:

Show quoted textHide quoted text

> From: Paul Vickers <paul@...>
> Subject: Re: [xl7] Newbie: understanding Hex & SysEx??????????????
> To: xl7@yahoogroups.com
> Date: Tuesday, February 23, 2010, 4:39 AM
> Hexadecimal is a base-16 counting
> system. In decimal (base 10) we use  
> the digits 0-9. The sum 9+1 leads to an answer that cannot
> be  
> expressed in a single digit so we add a '10s' column, put a
> 1 in it  
> and put zero in the units column, hence: 10. Hex, as it is
> base 16  
> needs 16 digits to represent its units, so we have 0-9
> which have  
> their usual decimal meaning and then A-F for the hex units
> whose  
> decimal values are 10, 11, 12, 13, 14, and 15. So, the sum
> F+1 is 15+1  
> in decimal = 16. As 16 cannot be represented by a single
> hex digit we  
> put a 1 in the 16s column and a zero in the units column to
> give: 10.  
> So 10 in hex is 16 in decimal.
> 
> Thus we see that FF in hex is 255 in decimal (15*16 + 15).
> 
> Hex is widely used in computing circles because of its
> ability to  
> represent powers of 2 in a few digits. A single 8-bit byte
> can hold up  
> to 256 binary values (from 00000000 to 11111111). As each
> nybble (4- 
> bits, or half a byte) has a maximum value of 15 decimal
> (1111) then a  
> single byte can be represented by a maximum of two hex
> digits.
> 
> 
> On 23 Feb 2010, at 01:31, Rob wrote:
> 
> > I've only been producing and using the Emu a few
> months. I've been  
> > reading manuals and everything on the internet I can
> find. I am  
> > starting to understand Hex & have figure out NRPNs
> and CC. BUT some  
> > SysEx is alien to me. The Emu manual has things like
> KK VV XX YY ZZ  
> > NN but hex is 0 to H. The sysex info seems to have
> different  
> > meanings for different commands for the letters.
> >
> > 8n kk vv is the command for note off.
> >
> > n = midi number
> > kk = ?
> > vv = ?
> >
> > Is this so standard that all companies shouldn't have
> to define it  
> > and I'm missing some chart on it?
> >
> > Is 8n kk vv all I enter or do I need more numbers for
> machine ID,  
> > EMU id, on, off, etc?
> >
> > Most of the tutorial sites treat you like a computer
> programer not a  
> > layman.
> >
> >
> > 
> 
> 
> ------------------------------------
> 
> Yahoo! Groups Links
> 
> 
>     xl7-fullfeatured@yahoogroups.com
> 
> 
>

Re: Newbie: understanding Hex & SysEx??????????????

2010-02-24 by Rob

thanks everyone.

--- In xl7@yahoogroups.com, "Rob" <awol9000@...> wrote:

Show quoted textHide quoted text

>
> I've only been producing and using the Emu a few months.  I've been reading manuals and everything on the internet I can find. I am starting to understand Hex & have figure out NRPNs and CC.  BUT some SysEx is alien to me.  The Emu manual has things like KK VV XX YY ZZ  NN but  hex is 0 to H. The sysex info seems to have different meanings for different commands for the letters.
> 
> 8n kk vv is the command for note off.
> 
> n = midi number
> kk = ?
> vv = ?
> 
> Is this so standard that all companies shouldn't have to define it and I'm missing some chart on it?
> 
> Is 8n kk vv all I enter or do I need more numbers for machine ID, EMU id, on, off, etc?
> 
> Most of the tutorial sites treat you like a computer programer not a layman.
>

Re: Newbie: understanding Hex & SysEx??????????????

2010-02-24 by Rob

Hitting stop twice on my PX-7 causes my Mopho to freeze- stops all sound until I unplug it.  Frustating trying to write tunes.  Midi ox didn't uncover anything unusual.  I was hoping to be able to send a command to fix it, that's what got me into the whole sysex or whatever it's called.

I've since decided to sell my synth module and buy a few more Emu roms, the frustration isn't worth it.  I can see the appeal in with software based producing where you don't have to learn everything, but hardware still has more appeal to me.  I'm really trying to give this a proper go, I'd made a couple of half assed attempts in my twenties.  Maybe the sysex side of things isn't my thing but it seemed important enough to try and learn it.

I look forward to Jane's prodatum program.  thanks.


--- In xl7@yahoogroups.com, "Rob" <awol9000@...> wrote:

Show quoted textHide quoted text

>
> thanks everyone.
> 
> --- In xl7@yahoogroups.com, "Rob" <awol9000@> wrote:
> >
> > I've only been producing and using the Emu a few months.  I've been reading manuals and everything on the internet I can find. I am starting to understand Hex & have figure out NRPNs and CC.  BUT some SysEx is alien to me.  The Emu manual has things like KK VV XX YY ZZ  NN but  hex is 0 to H. The sysex info seems to have different meanings for different commands for the letters.
> > 
> > 8n kk vv is the command for note off.
> > 
> > n = midi number
> > kk = ?
> > vv = ?
> > 
> > Is this so standard that all companies shouldn't have to define it and I'm missing some chart on it?
> > 
> > Is 8n kk vv all I enter or do I need more numbers for machine ID, EMU id, on, off, etc?
> > 
> > Most of the tutorial sites treat you like a computer programer not a layman.
> >
>

Re: Newbie: understanding Hex & SysEx??????????????

2010-03-08 by soundcrafter_23320

Rob,

I might be too late here, but I would say DON'T sell your Mopho just yet!  The Mopho is a relatively new piece of hardware, and you may be experiencing a bug in the OS.  The XL7 spits out a lot of MIDI data when you press stop twice (as I'm sure you're aware from looking at MIDIOx...)  It may just be "confusing" the Mopho.

Look around for a Mopho / DSI group or forum, they may be able to verify and help you out.  

HTH

DTK


--- In xl7@yahoogroups.com, "Rob" <awol9000@...> wrote:

Show quoted textHide quoted text

>
> Hitting stop twice on my PX-7 causes my Mopho to freeze- stops all sound until I unplug it.  Frustating trying to write tunes.  Midi ox didn't uncover anything unusual.  I was hoping to be able to send a command to fix it, that's what got me into the whole sysex or whatever it's called.
> 
> I've since decided to sell my synth module

Re: Mopho Lock Up Issue (was Re: Newbie: understanding Hex & SysEx??????????????

2010-03-08 by steve_the_composer

I just took a quick look at the Mopho manual (v1.2 I think). Some diaghnostic questions:

(1) Does the lock-up occur when you press stop once or only when you press stop twice?
(2) Does the lock-up occur when you dial up a new pattern before pressing play, or stop?
(3) How are the two wired in terms of midi i/o?
(4) Which is providing midi clock? Are you using one as a slave? Do you have the right clock settings in the PX7 and the Mopho to do what you want?
(5) Does sending bank switching/program change commands to the mopho cause it to lock up? 

I am not sure of your answers to these questions, but if I had the gear, I would try to isolate the cause of the problem by first setting the PX-7 as clock master and the Mopho as slave. Depending on whether or not the lock-up happens, I'd switch the two and retest.

I would be surprised if the Mopho was confused by the E-Mu sysex data. If that is the source of the problem, I assume DSI would be interested to know that. I'd rule out other possible cuases first.

It looks like a nice module. Hope you can get it working right with your Command Station.

--Steve






--- In xl7@yahoogroups.com, "soundcrafter_23320" <aurastar@...> wrote:

Show quoted textHide quoted text

>
> Rob,
> 
> I might be too late here, but I would say DON'T sell your Mopho just yet!  The Mopho is a relatively new piece of hardware, and you may be experiencing a bug in the OS.  The XL7 spits out a lot of MIDI data when you press stop twice (as I'm sure you're aware from looking at MIDIOx...)  It may just be "confusing" the Mopho.
> 
> Look around for a Mopho / DSI group or forum, they may be able to verify and help you out.  
> 
> HTH
> 
> DTK
> 
> 
> --- In xl7@yahoogroups.com, "Rob" <awol9000@> wrote:
> >
> > Hitting stop twice on my PX-7 causes my Mopho to freeze- stops all sound until I unplug it.  Frustating trying to write tunes.  Midi ox didn't uncover anything unusual.  I was hoping to be able to send a command to fix it, that's what got me into the whole sysex or whatever it's called.
> > 
> > I've since decided to sell my synth module
>

Mopho Lock Up Issue (was Re: Newbie: understanding Hex & SysEx??????????????

2010-03-08 by Rob

I did sell the Mopho last week

(1) twice, one is fine
(2) no
(3) PX7 midi out A to Mopho
(4) The Command Station is providing the clock.  I thought you couldn't use the PX7 as a sequencer and use the Mopho as the clock.
(5) I don't know how to send bank changes from the PX7 but I send bank & pattern changes from my Novation Remote and the Mopho is fine.

If I hold the "push it" button on the Mopho (causes it to sound) while pushing stop twice (on PX7) the Mopho doesn't freeze.  I did sell the Mopho last week.

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

Show quoted textHide quoted text

>
> I just took a quick look at the Mopho manual (v1.2 I think). Some diaghnostic questions:
> 
> (1) Does the lock-up occur when you press stop once or only when you press stop twice?
> (2) Does the lock-up occur when you dial up a new pattern before pressing play, or stop?
> (3) How are the two wired in terms of midi i/o?
> (4) Which is providing midi clock? Are you using one as a slave? Do you have the right clock settings in the PX7 and the Mopho to do what you want?
> (5) Does sending bank switching/program change commands to the mopho cause it to lock up? 
> 
> I am not sure of your answers to these questions, but if I had the gear, I would try to isolate the cause of the problem by first setting the PX-7 as clock master and the Mopho as slave. Depending on whether or not the lock-up happens, I'd switch the two and retest.
> 
> I would be surprised if the Mopho was confused by the E-Mu sysex data. If that is the source of the problem, I assume DSI would be interested to know that. I'd rule out other possible cuases first.
> 
> It looks like a nice module. Hope you can get it working right with your Command Station.
> 
> --Steve
> 
> 
> 
> 
> 
> 
> --- In xl7@yahoogroups.com, "soundcrafter_23320" <aurastar@> wrote:
> >
> > Rob,
> > 
> > I might be too late here, but I would say DON'T sell your Mopho just yet!  The Mopho is a relatively new piece of hardware, and you may be experiencing a bug in the OS.  The XL7 spits out a lot of MIDI data when you press stop twice (as I'm sure you're aware from looking at MIDIOx...)  It may just be "confusing" the Mopho.
> > 
> > Look around for a Mopho / DSI group or forum, they may be able to verify and help you out.  
> > 
> > HTH
> > 
> > DTK
> > 
> > 
> > --- In xl7@yahoogroups.com, "Rob" <awol9000@> wrote:
> > >
> > > Hitting stop twice on my PX-7 causes my Mopho to freeze- stops all sound until I unplug it.  Frustating trying to write tunes.  Midi ox didn't uncover anything unusual.  I was hoping to be able to send a command to fix it, that's what got me into the whole sysex or whatever it's called.
> > > 
> > > I've since decided to sell my synth module
> >
>

Mopho Lock Up Issue (was Re: Newbie: understanding Hex & SysEx??????????????

2010-03-08 by Rob

I'm was using OS 1.3, the latest.

Re: [xl7] Mopho Lock Up Issue (was Re: Newbie: understanding Hex & SysEx??????????????

2010-03-09 by Aaron Eppolito

Hmm, I wonder if you had the Mo:Pho responding to song start/stop, causing the internal arps/beats stuff to activate...

Show quoted textHide quoted text

----- Original Message ----
From: Rob <awol9000@...>
To: xl7@yahoogroups.com
Sent: Mon, March 8, 2010 3:56:24 PM
Subject: [xl7] Mopho Lock Up Issue (was Re: Newbie: understanding Hex & SysEx??????????????

I did sell the Mopho last week

(1) twice, one is fine
(2) no
(3) PX7 midi out A to Mopho
(4) The Command Station is providing the clock.  I thought you couldn't use the PX7 as a sequencer and use the Mopho as the clock.
(5) I don't know how to send bank changes from the PX7 but I send bank & pattern changes from my Novation Remote and the Mopho is fine.

If I hold the "push it" button on the Mopho (causes it to sound) while pushing stop twice (on PX7) the Mopho doesn't freeze.  I did sell the Mopho last week.

--- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@...> wrote:
>
> I just took a quick look at the Mopho manual (v1.2 I think). Some diaghnostic questions:
> 
> (1) Does the lock-up occur when you press stop once or only when you press stop twice?
> (2) Does the lock-up occur when you dial up a new pattern before pressing play, or stop?
> (3) How are the two wired in terms of midi i/o?
> (4) Which is providing midi clock? Are you using one as a slave? Do you have the right clock settings in the PX7 and the Mopho to do what you want?
> (5) Does sending bank switching/program change commands to the mopho cause it to lock up? 
> 
> I am not sure of your answers to these questions, but if I had the gear, I would try to isolate the cause of the problem by first setting the PX-7 as clock master and the Mopho as slave. Depending on whether or not the lock-up happens, I'd switch the two and retest.
> 
> I would be surprised if the Mopho was confused by the E-Mu sysex data. If that is the source of the problem, I assume DSI would be interested to know that. I'd rule out other possible cuases first.
> 
> It looks like a nice module. Hope you can get it working right with your Command Station.
> 
> --Steve
> 
> 
> 
> 
> 
> 
> --- In xl7@yahoogroups.com, "soundcrafter_23320" <aurastar@> wrote:
> >
> > Rob,
> > 
> > I might be too late here, but I would say DON'T sell your Mopho just yet!  The Mopho is a relatively new piece of hardware, and you may be experiencing a bug in the OS.  The XL7 spits out a lot of MIDI data when you press stop twice (as I'm sure you're aware from looking at MIDIOx...)  It may just be "confusing" the Mopho.
> > 
> > Look around for a Mopho / DSI group or forum, they may be able to verify and help you out.  
> > 
> > HTH
> > 
> > DTK
> > 
> > 
> > --- In xl7@yahoogroups.com, "Rob" <awol9000@> wrote:
> > >
> > > Hitting stop twice on my PX-7 causes my Mopho to freeze- stops all sound until I unplug it.  Frustating trying to write tunes.  Midi ox didn't uncover anything unusual.  I was hoping to be able to send a command to fix it, that's what got me into the whole sysex or whatever it's called.
> > > 
> > > I've since decided to sell my synth module
> >
>




------------------------------------

Yahoo! Groups Links

Mopho Lock Up Issue (was Re: Newbie: understanding Hex & SysEx??????????????

2010-03-09 by Rob

On the Mopho I turned off Sysex - no difference.  I also tried changes which parameters were being recieved (NRPN, CC, ALL, OFF).  I also tried limiting what midi the PX7 was sending.


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

Show quoted textHide quoted text

>
> Hmm, I wonder if you had the Mo:Pho responding to song start/stop, causing the internal arps/beats stuff to activate...
> 
> 
> ----- Original Message ----
> From: Rob <awol9000@...>
> To: xl7@yahoogroups.com
> Sent: Mon, March 8, 2010 3:56:24 PM
> Subject: [xl7] Mopho Lock Up Issue (was Re: Newbie: understanding Hex & SysEx??????????????
> 
> I did sell the Mopho last week
> 
> (1) twice, one is fine
> (2) no
> (3) PX7 midi out A to Mopho
> (4) The Command Station is providing the clock.  I thought you couldn't use the PX7 as a sequencer and use the Mopho as the clock.
> (5) I don't know how to send bank changes from the PX7 but I send bank & pattern changes from my Novation Remote and the Mopho is fine.
> 
> If I hold the "push it" button on the Mopho (causes it to sound) while pushing stop twice (on PX7) the Mopho doesn't freeze.  I did sell the Mopho last week.
> 
> --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@> wrote:
> >
> > I just took a quick look at the Mopho manual (v1.2 I think). Some diaghnostic questions:
> > 
> > (1) Does the lock-up occur when you press stop once or only when you press stop twice?
> > (2) Does the lock-up occur when you dial up a new pattern before pressing play, or stop?
> > (3) How are the two wired in terms of midi i/o?
> > (4) Which is providing midi clock? Are you using one as a slave? Do you have the right clock settings in the PX7 and the Mopho to do what you want?
> > (5) Does sending bank switching/program change commands to the mopho cause it to lock up? 
> > 
> > I am not sure of your answers to these questions, but if I had the gear, I would try to isolate the cause of the problem by first setting the PX-7 as clock master and the Mopho as slave. Depending on whether or not the lock-up happens, I'd switch the two and retest.
> > 
> > I would be surprised if the Mopho was confused by the E-Mu sysex data. If that is the source of the problem, I assume DSI would be interested to know that. I'd rule out other possible cuases first.
> > 
> > It looks like a nice module. Hope you can get it working right with your Command Station.
> > 
> > --Steve
> > 
> > 
> > 
> > 
> > 
> > 
> > --- In xl7@yahoogroups.com, "soundcrafter_23320" <aurastar@> wrote:
> > >
> > > Rob,
> > > 
> > > I might be too late here, but I would say DON'T sell your Mopho just yet!  The Mopho is a relatively new piece of hardware, and you may be experiencing a bug in the OS.  The XL7 spits out a lot of MIDI data when you press stop twice (as I'm sure you're aware from looking at MIDIOx...)  It may just be "confusing" the Mopho.
> > > 
> > > Look around for a Mopho / DSI group or forum, they may be able to verify and help you out.  
> > > 
> > > HTH
> > > 
> > > DTK
> > > 
> > > 
> > > --- In xl7@yahoogroups.com, "Rob" <awol9000@> wrote:
> > > >
> > > > Hitting stop twice on my PX-7 causes my Mopho to freeze- stops all sound until I unplug it.  Frustating trying to write tunes.  Midi ox didn't uncover anything unusual.  I was hoping to be able to send a command to fix it, that's what got me into the whole sysex or whatever it's called.
> > > > 
> > > > I've since decided to sell my synth module
> > >
> >
> 
> 
> 
> 
> ------------------------------------
> 
> Yahoo! Groups Links
>

Mopho Lock Up Issue (was Re: Newbie: understanding Hex & SysEx??????????????

2010-03-09 by steve_the_composer

Since you sold the DSI MoPho, there's probably no way to narrow the source of the problem down further. Maybe someone else will come along with trying to slave a MoPho to a Command Station. In any case, I enjoyed browsing through the manual. 
--Steve





--- In xl7@yahoogroups.com, "Rob" <awol9000@...> wrote:

Show quoted textHide quoted text

>
> On the Mopho I turned off Sysex - no difference.  I also tried changes which parameters were being recieved (NRPN, CC, ALL, OFF).  I also tried limiting what midi the PX7 was sending.
> 
> 
> --- In xl7@yahoogroups.com, Aaron Eppolito <synthesis77@> wrote:
> >
> > Hmm, I wonder if you had the Mo:Pho responding to song start/stop, causing the internal arps/beats stuff to activate...
> > 
> > 
> > ----- Original Message ----
> > From: Rob <awol9000@>
> > To: xl7@yahoogroups.com
> > Sent: Mon, March 8, 2010 3:56:24 PM
> > Subject: [xl7] Mopho Lock Up Issue (was Re: Newbie: understanding Hex & SysEx??????????????
> > 
> > I did sell the Mopho last week
> > 
> > (1) twice, one is fine
> > (2) no
> > (3) PX7 midi out A to Mopho
> > (4) The Command Station is providing the clock.  I thought you couldn't use the PX7 as a sequencer and use the Mopho as the clock.
> > (5) I don't know how to send bank changes from the PX7 but I send bank & pattern changes from my Novation Remote and the Mopho is fine.
> > 
> > If I hold the "push it" button on the Mopho (causes it to sound) while pushing stop twice (on PX7) the Mopho doesn't freeze.  I did sell the Mopho last week.
> > 
> > --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@> wrote:
> > >
> > > I just took a quick look at the Mopho manual (v1.2 I think). Some diaghnostic questions:
> > > 
> > > (1) Does the lock-up occur when you press stop once or only when you press stop twice?
> > > (2) Does the lock-up occur when you dial up a new pattern before pressing play, or stop?
> > > (3) How are the two wired in terms of midi i/o?
> > > (4) Which is providing midi clock? Are you using one as a slave? Do you have the right clock settings in the PX7 and the Mopho to do what you want?
> > > (5) Does sending bank switching/program change commands to the mopho cause it to lock up? 
> > > 
> > > I am not sure of your answers to these questions, but if I had the gear, I would try to isolate the cause of the problem by first setting the PX-7 as clock master and the Mopho as slave. Depending on whether or not the lock-up happens, I'd switch the two and retest.
> > > 
> > > I would be surprised if the Mopho was confused by the E-Mu sysex data. If that is the source of the problem, I assume DSI would be interested to know that. I'd rule out other possible cuases first.
> > > 
> > > It looks like a nice module. Hope you can get it working right with your Command Station.
> > > 
> > > --Steve
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > --- In xl7@yahoogroups.com, "soundcrafter_23320" <aurastar@> wrote:
> > > >
> > > > Rob,
> > > > 
> > > > I might be too late here, but I would say DON'T sell your Mopho just yet!  The Mopho is a relatively new piece of hardware, and you may be experiencing a bug in the OS.  The XL7 spits out a lot of MIDI data when you press stop twice (as I'm sure you're aware from looking at MIDIOx...)  It may just be "confusing" the Mopho.
> > > > 
> > > > Look around for a Mopho / DSI group or forum, they may be able to verify and help you out.  
> > > > 
> > > > HTH
> > > > 
> > > > DTK
> > > > 
> > > > 
> > > > --- In xl7@yahoogroups.com, "Rob" <awol9000@> wrote:
> > > > >
> > > > > Hitting stop twice on my PX-7 causes my Mopho to freeze- stops all sound until I unplug it.  Frustating trying to write tunes.  Midi ox didn't uncover anything unusual.  I was hoping to be able to send a command to fix it, that's what got me into the whole sysex or whatever it's called.
> > > > > 
> > > > > I've since decided to sell my synth module
> > > >
> > >
> > 
> > 
> > 
> > 
> > ------------------------------------
> > 
> > Yahoo! Groups Links
> >
>