Yahoo Groups archive

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

Index last updated: 2026-04-09 23:09 UTC

Message

Re: XL-7 midi woes - Aaron??

2004-03-06 by Justin Grimley

Matt,
Changing presets without leaving mult-mode does not fix it.  I have 
to switch to single mode and back to multi.

As for the stray midi messages.  This is what I originally thought 
was happening as I have a CC#11 at the start of every track on my 
default empty pattern.  This is so that the pattern retains it's 
channel routings when I store it.  However, erasing the tracks 
(holding erase and track number) still does not fix the problem.

I appreciate you trying though.
-Justin


--- In xl7@yahoogroups.com, "Matt Picone" <matman@m...> wrote:
> Hi Justin
> 
> How about changing presets without leaving multi mode? Does that fix
> anything?
> Have you ruled out all stray midi messages by doing an ERASE ALL
> CONTROLLERS on the track?
> 
> -m@
> 
> > -----Original Message-----
> > From: Justin Grimley [mailto:grimley@i...] 
> > Sent: Saturday, March 06, 2004 2:13 PM
> > To: xl7@yahoogroups.com
> > Subject: [xl7] Re: XL-7 midi woes - Aaron??
> > 
> > 
> > Aaron,
> > Do you have any idea what could be going on here?
> > 
> > I have narrowed the problem down by disconnecting the Virus midi 
in 
> > from my midi patchbay altogether (midex 8).
> > I now have the XL-7 midi B connected to the Virus midi in and I 
am 
> > still seeing the problem.  I was convinced this was a Cubase 
problem.
> > 
> > Anyway, playing back a pettern on the XL-7 (just one track output 
to 
> > channel:01B and Dest:both going to Virus) the sound on the Virus 
will 
> > stop.  Preview sound on the Virus will not work (hold Edit and 
Sync), 
> > playing the pads on the XL-7 will make no sounds on the Virus.  
> > Previously I had to reset the Virus to fix the problem.  Changing 
> > presets would have no affect.  However, I just discovered that if 
I 
> > change from multi to single mode and back on the Virus then the 
> > problem is cleared and all is good .... until I start play again 
on 
> > the XL-7.  
> > 
> > I would greatly appreciate any help on this.
> > 
> > -Justin.
> > 
> > 
> > 
> > --- In xl7@yahoogroups.com, erik_magrini@B... wrote:
> > > Good idea.
> > > 
> > > rEalm
> > > 
> > > 
> > > 
> > > 
> > > 
> > > "Justin Grimley" <grimley@i...>
> > > 02/19/2004 01:04 PM
> > > Please respond to xl7
> > > 
> > >  
> > >         To:     xl7@yahoogroups.com
> > >         cc: 
> > >         Subject:        [xl7] Re: Cubase SX / XL-7 midi woes
> > > 
> > > 
> > > Thanks for trying anyway!
> > > This evening I'm going to try hooking up a midi merge box to 
the XL-
> > 7 
> > > and split the output so that it goes to both Cubase and the 
Virus.
> > > Same with the Midex to Virus connection.  That way I can bypass 
> > > Cubase and see if it is a XL-7->Virus issue or a XL7-Cubase-
>Virus 
> > > issue.
> > > -Justin.
> > > 
> > > --- In xl7@yahoogroups.com, erik_magrini@B... wrote:
> > > > Actually for Sounddiver they both need to be set to sysex.  
But
> > it 
> > > looks
> > > > like you have them set right for what I was thinking, no other
> > > ideas what
> > > > could be causing that problem.
> > > > 
> > > > rEalm
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > rAlm,
> > > > Where do I check that?
> > > > In the control menu I can select Midi Control Lo and Hi 
page.  I
> > > have
> > > > it set to LoPage -> Contr and HiPage -> SysEx.  I believe 
these
> > are 
> > > > the settings I need for Emagic SoundDiver.
> > > > 
> > > > -grimley
> > 
> > 
> >  
> >  
> >      
> >  
> >    
> >  
> >  
> > I am having some serious problems using the XL-7 as my 
> > pattern sequencer hooked up to Cubase and was hoping someone 
> > might have an idea of what is going on (sorry for the long post).
> > 
> > First off I will recap my setup as outlined in a previous post:
> > 
> > In Cubase I have a template with 12 midi tracks which map to 
> > tracks 5- 16 from the XL-7. I am using the input transformer 
> > on the tracks in Cubase so that they filter out channels not 
> > assigned for this track. (I'm using a Steinberg Midex8 midi 
> > interface.)
> > 
> > For example:
> > In cubase:
> > Midi Track 1 -> Halion channel 1 <- From XL-7 channel 5
> > Midi Track 2 -> Halion channel 2 <- From XL-7 channel 6
> > Midi Track 3 -> Halion channel 3 <- From XL-7 channel 7
> > Midi Track 4 -> Halion channel 4 <- From XL-7 channel 8
> > Midi Track 5 -> Virusb channel 1 <- From XL-7 channel 9
> > Midi Track 6 -> Virusb channel 2 <- From XL-7 channel 10
> > Midi Track 7 -> Virusb channel 3 <- From XL-7 channel 11
> > Midi Track 8 -> Virusb channel 4 <- From XL-7 channel 12
> > Midi Track 9 -> MS2000r channel 1 <- From XL-7 channel 13
> > Midi Track 10 -> EX5 channel 1 <- From XL-7 channel 14
> > Midi Track 11 -> Juno 106 channel 1 <- From XL-7 channel 15 
> > Midi Track 12 -> Absynth2 channel 1 <- From XL-7 channel 16
> > 
> > Each track in the XL-7 template is storing a CC#11 controller 
> > as the first event so that when I save the template the 
> > channel routings are stored. In the Cubase midi preferences 
> > dialog, I filter out CC##11. I also filter program changes 
> > and SYSEX for both thru and record.
> > 
> > Every time I use this setup, 2 problems occur at intermittent 
> > times, and with no obvious pattern of events:
> > 
> > [1] ... The Access Virus b will not make any sound. Even 
> > doing a patch audition by pressing EDIT & SYNC or choosing 
> > any other patch, will not result in sound. The virus has to 
> > be completely shut down and restarted.
> > 
> > [2] ... The XL-7 will completely lock-up and has to be 
> > restarted. "Local" is on in the XL-7 because I use the pads 
> > to transmit midi to my other devices as well as internal 
> > patches. No tracks in Cubase are being routed back to the 
> > XL-7 so there shouldn't be a midi loopback problem. The only 
> > thing that I can see that the XL-7 receives from Cubase is 
> > midi clock and song pointer info.
> > 
> > Anything else I should look at?
> > Thanks for listening,
> > grimley
> > 
> >  
> > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > The information transmitted is intended only for the person(s)
or
> > > entity
> > > > to which it is addressed and may contain confidential and/or
> > > legally
> > > > privileged material. Delivery of this message to any person 
other
> > > than
> > > > the intended recipient(s) is not intended in any way to waive
> > > privilege
> > > > or confidentiality. Any review, retransmission, dissemination 
or
> > > other
> > > > use of, or taking of any action in reliance upon, this
> > information 
> > > by
> > > > entities other than the intended recipient is prohibited. If 
you
> > > > receive this in error, please contact the sender and delete 
the 
> > > > material from any computer.
> > > > 
> > > > For Translation:
> > > > 
> > > > http://www.baxter.com/email_disclaimer
> > > > 
> > > > 
> > > > [Non-text portions of this message have been removed]
> > > 
> > > 
> > > 
> > >  
> > > Yahoo! Groups Links
> > > 
> > > 
> > > 
> > >  
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > The information transmitted is intended only for the person(s)or
> > entity 
> > > to which it is addressed and may contain confidential and/or
> > legally 
> > > privileged material. Delivery of this message to any person 
other
> > than 
> > > the intended recipient(s) is not intended in any way to waive
> > privilege 
> > > or confidentiality. Any review, retransmission, dissemination or
> > other 
> > > use of, or taking of any action in reliance upon, this 
information
> > by 
> > > entities other than the intended recipient is prohibited. If you
> > > receive this in error, please contact the sender and delete the 
> > > material from any computer.
> > > 
> > > For Translation:
> > > 
> > > http://www.baxter.com/email_disclaimer
> > > 
> > > 
> > > [Non-text portions of this message have been removed]
> > 
> > 
> > 
> >  
> > Yahoo! Groups Links
> > 
> > 
> > 
> >  
> > 
> >

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.