Yahoo Groups archive

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

Index last updated: 2026-04-14 00:15 UTC

Message

Re: [xl7] TICK 0 vs TICK 1

2002-04-29 by Aaron Eppolito

Okay, here goes.  Events at tick 0 (01.01.000) are only editable if the
track is set to "ext" only.  You may edit things at that tick, you may
delete things, but you may not add things.  This is because the
sequencer uses tick 0 as the location at which to place its setup info
if the track is "int" or "both".  To prevent user data from being
overwritten, that location is not "add-to-able".  The only reason tick 0
is visible at all for "ext" tracks is so that you can remove data that
might have been written if the track was saved while set to "int" or
"both".

Events (like program changes, etc) at tick 1 play before notes at tick 0
and do not play after the first loop.  This is the place that you should
put setup information for your external gear.  Basically envision tick 0
as the sequencer's private data setup and tick 1 as the user's data
setup.  Also note that this data is played slightly ahead of time when
switching from pattern to pattern.  If that's still not early enough for
your Korg, try moving the first notes targeted to the Korg later in time
so as to give your Korg plenty of time to do its program change.

-Aaron

peebs uk wrote:

> Just a thought, the v1.31 manual says that you can view this tick for
> removing xl7 presequence setup data from external tracks (but doesn't
> mention adding anything in there yourself). Maybe there's a way of
> getting
> some xl7 data in there which can then be changed to an external cc as
> the
> tick only seems visible when there's something already there?
>
> Does that make any sense, and if so can you think how the xl7 data can
> be
> put in there?
>
> PS. Tried controlling the korgs for the first time since the change in
> o/s
> and the prog change events at 001.01.001 are still too late.
>
> >From: "peebs uk" <peebs_uk@...>
> >To: xl7@yahoogroups.com
> >Subject: Re: [xl7] Re: Prog change msgs to another groovebox/pattern
> >
> >Thanks for the advice Mike, I think that would do the trick if... I
> wasn't
> >having the same problem as you! Just tried to add a cc event on an
> external
> >only track and the lowest tick I can use is 001.01.001 (running o/s
> 1.31)
> >
> >As you're experiencing the same problem should I repost this with the
>
> >subject 'Can't enter event at tick 001.01.000' or has this problem
> already
> >been discussed with no solution?
> >
> >
> > >From: "mikexl7" <mikexl7@...>
> > >To: xl7@yahoogroups.com
> > >
> > >Well there is the ability to place cc info on the tick 001.01.000
> in
> > >the list editer but mine has stoped working for some unknown
> > >reason.  Asuming that yours is not doing what mine is just go into
> > >the list editer and press the repeat button and then select the cc
> > >info to send a program change.
> > >
> > >P.s. the track has to be set to external to access the tick
> > >001.01.000.
> > >
> > >I think this will work.
> > >
> > >Mike G

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.