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

Well installing the new OS went perfictly on windows ME using a 
MidiQuest 2Port/SE.  

I have sompthing to ask of ya all though on a different topic. 
Alot of the time the patterns don't glitch now, I know since the 
releace of 1.17 but they still do sometimes.  I have noticed that 
when I am wrighting patterns that do glitch when switching if I turn 
the thing off and back on the patternst switch with no problem. 
What is this all about?
Is it rather anoying to have to reboot the thing just to see if the 
patterns flow smoothly.  I would like to see this worked out.  The 
amount of work being put into the XL/MP's is obvious and verry much 
appreciated but this problem has been dragging on and on from OS to 
OS.  I am a little concerned becouse I think the thing that you guys 
at E-MU are working on now for the most part are the drivers for 
windows to get the USB working.  I hope you have not overlooked this 
problem that is still happening.

Peace 

Mike

On Sunday, December 23, 2001, at 11:02  AM, mikexl7 wrote:

> Alot of the time the patterns don't glitch now, I know since the
> releace of 1.17 but they still do sometimes.  I have noticed that
> when I am wrighting patterns that do glitch when switching if I turn
> the thing off and back on the patternst switch with no problem.
> What is this all about?
> [...]
>  I am a little concerned becouse I think the thing that you guys
> at E-MU are working on now for the most part are the drivers for
> windows to get the USB working.  I hope you have not overlooked this
> problem that is still happening.

We know there are a few remaining 'rough' spots in pattern switching and 
we are actively working on fixing them. (Well most people are off for 
the next few weeks for holidays, but those issues are highest priority 
for when everyone is back). Adding the USB support is not taking 
significant resources away from fixes like this. We know that getting 
sequencer timing right is very important. They are just not as easy to 
fix as some of the other items that were in the recent releases which we 
felt were important to get out as soon as they were resolved.

That being said, I'm not aware of your exact problem description having 
been observed by anyone previously. We are aware that when switching 
patterns in Song mode there is sometimes still a bit of a lag on the 
first note of the switched-to pattern, and a couple of other 
intermittent head-scratchers. But I think the behavior changing over a 
power cycle is news to us. Can you verify this and give us some specific 
steps to reproduce this? (You can send your info to me in offline e-mail 
if you'd like).

You should expect a new release announcement around NAMM time (end of 
January).

Scott

PS: Happy Holidays to everyone on the list!

Thank you for looking at the board on the weekend you must be love 
what you do! :)
well i hope that is the case anyway.

Well as for an example it is as simple as this...
I made a pettern containing quite a bit of info.  There are 11 active 
tracks and five of them have program changes as well as a continuas 
controller send for each of the five that contain program changes to 
set the corect FX send.  All of this info is on 1.00.01 and this i 
thought might be fair to add.  

I then simply took the pattern and copied it to the next empty 
pattern space and when I switch to the newly copied pattern the 
glitch happens.  When I back to the original pattern from the copy 
the glitch is not there.

A couple of weeks ago on impuls I got totaly fed up with this 
happening and turned the thing off and on just to see what would 
happen and the problem was gone.  Switching back and forth was no 
problem.  I totaly don't understand this one, often i have a guess 
but with this I rely don't understand.  Maby I will try reloading the 
1.18 from scratch instead of loading it in on top of 1.17.  Would 
this make any difference?

Thanks again scott.

Happy holidays.

Mike
> 
> We know there are a few remaining 'rough' spots in pattern 
switching and 
> we are actively working on fixing them. (Well most people are off 
for 
> the next few weeks for holidays, but those issues are highest 
priority 
> for when everyone is back). Adding the USB support is not taking 
> significant resources away from fixes like this. We know that 
getting 
> sequencer timing right is very important. They are just not as easy 
to 
> fix as some of the other items that were in the recent releases 
which we 
> felt were important to get out as soon as they were resolved.
> 
> That being said, I'm not aware of your exact problem description 
having 
> been observed by anyone previously. We are aware that when 
switching 
> patterns in Song mode there is sometimes still a bit of a lag on 
the 
> first note of the switched-to pattern, and a couple of other 
> intermittent head-scratchers. But I think the behavior changing 
over a 
> power cycle is news to us. Can you verify this and give us some 
specific 
> steps to reproduce this? (You can send your info to me in offline e-
mail 
> if you'd like).
> 
> You should expect a new release announcement around NAMM time (end 
of 
> January).
> 
> Scott
> 
> PS: Happy Holidays to everyone on the list!

Scott,

This happens to me as well.  Occasionally if I switch patterns while the 
XL-7 is playing (in pattern mode, I never use song more), the next pattern 
will "hiccup" a bit at the beginning.  Usually it's only the first couple 
of beats, but it is noticeable if infrequent.  It seems to happen to me 
the most if I've been working on a new pattern and then start switching 
while it's playing.  If I just turn the XL-7 on and don't do any 
recording/copying, then it doesn't seem to happen.  Like I said it's 
infrequent, but when it does happen it's very noticeable.  I'll try and 
narrow it down some more if I can over the next week.  I'm off work for 
the holidays and plan on spending much of my time with just the XL-7 and 
my new Red Sound Micro Sync :)

rEalm



That being said, I'm not aware of your exact problem description having 
been observed by anyone previously. We are aware that when switching 
patterns in Song mode there is sometimes still a bit of a lag on the first 
note of the switched-to pattern, and a couple of other intermittent 
head-scratchers. But I think the behavior changing over a 
power cycle is news to us.

mikexl7 wrote:

> Well as for an example it is as simple as this...
> I made a pettern containing quite a bit of info.  There are 11 active
> tracks and five of them have program changes as well as a continuas
> controller send for each of the five that contain program changes to
> set the corect FX send.  All of this info is on 1.00.01 and this i
> thought might be fair to add.

The 01.01.001 time location is really only for use with external gear.  All
of the aforementioned things (prog. change, FX settings, etc) are
*automatically* stored at 01.01.000 by the sequencer for "internal" or "both"
tracks.  For those type of tracks, if you store duplicate info, it probably
will only cause problems.  The bottom line is, if you're not using "external"
tracks, you should never have to deal with the event editor to save pattern
state.


> I then simply took the pattern and copied it to the next empty
> pattern space and when I switch to the newly copied pattern the
> glitch happens.  When I back to the original pattern from the copy
> the glitch is not there.

There is a known glitch with the new "edit pattern" feature.  We are working
on this at the moment (well, now that I'm back from vacation =).  If you've
saved the pattern, to get rid of the "editness", revert to the saved version
(but only after you've saved!).  This should remove the glitch.

> A couple of weeks ago on impuls I got totaly fed up with this
> happening and turned the thing off and on just to see what would
> happen and the problem was gone.  Switching back and forth was no
> problem.  I totaly don't understand this one, often i have a guess
> but with this I rely don't understand.

This is because reloading (as accomplished by rebooting in this case) should
fix the problem.  The "revert" solution should do the same thing.


> Maby I will try reloading the
> 1.18 from scratch instead of loading it in on top of 1.17.  Would
> this make any difference?

Nope.  There really is no such thing as loading from scratch.  That's only
for Windows... (and we all know that you never have to reload Windows,
right?)


> Happy holidays.

And a belated wish to you all as well!

-Aaron