Some time I will have to explore this more fully, but for the time being here's some footnotes: (1) Confirmed: Changing Channel Assign Dest to ext does make tick 0 visible in the event editor. Example: T02 EVENT <-> 001.01.000 C02 controller # 7 v:68 T02 EVENT <-> 001.01.000 C02 controller # 10 v:71 T02 EVENT <-> 001.01.000 C02 prog:107 m:17 l:1 ll 3 of these were found at tick 0 in the factory sequence RiskyBizness. By the way, the 3rd piece of data is intended for Bank 1 [l:1] of the P2500 ROM [m:17] which would probably confuse any external gear I have. (2) I was under the impression that these tick 0 settings are the "pre-roll" midi data sent; i.e., the data sent when you dial up a pattern or when you RTZ (return to zero) by hitting stop twice. OK--found it in the XL-7 Manual: page 144 of the pdf (Rev. G), corresponding with numbered page 132. Looking at this page, it makes sense that if you want a program change to be sent out at the start of each loop of a pattern, it needs to be at tick 2 as found in the event editor. Otherwise it would only be sent out as "Pre-Sequence Setup Info" [what I meant when I said "pre-roll"]. Intuitively, if any track going to external gear only used one program change command, I assume tick 0* would be OK to use, but not if a pattern or song changed the preset and someone wanted it to change back when the pattern looped. To fully explore the possibilities in the context of a song (that is in song mode), someone should make sure then understood what happens with tick 0* with EVENT SOURCE settings (song events only, 1st pattern only, all patterns, songs & patterns). ------------------------ *Actually tick 0/tick 1 of the "pre-roll" or "pre-sequence setup" data From the manual": The first two ticks (0 & 1) are reserved for pre-sequence setup information. ---Tick 0 is reserved for the internal pre-sequence setup information. ---Tick 1 is used to place your own pre-sequence setup information so that it won't loop and cause timing errors. Events (controller data, program changes, sysex, etc.) are played before Notes, even if they are located on the same numbered Tick. This is done so that volume changes and other programming information will be in place when the notes turn on. When a track is set to "ext" (external transmit only), you will be allowed to see the tick 0 spot for EVENTS. This allows you to remove any presequence setup data (which is stored at Tick 0) left over from when the track may have been internal or both. --- In xl7@yahoogroups.com, craig ward <craigbiz@...> wrote: > > Usually I have to put the program change at .002 as opposed to .001 for the program change to register with external hardware. Hope I'm understanding correctly. Good luck > > Sent from my iPhone > > On 13/06/2013, at 1:51 PM, "steve_the_composer" <smw-mail@...> wrote: > > > Here's one reference on how to get to tick 0. There might be others. > > > > http://launch.groups.yahoo.com/group/xl7/message/19624 > > > > Steve > > > > --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@> wrote: > > > > > > I digging back into the far reaches of my memory, but I seem to recall you need to have the track set to ext to access tick 0. I do believe it has been discussed here and it might be in the manual. I see to recall that Aaron pointed that out. I will try to find the post. > > > > > > --- In xl7@yahoogroups.com, Nathan Steele <XTCaine303@> wrote: > > > > > > > > Hi all. > > > > > > > > I have been trying to embed the program change at tick 1 so I can have > > > > my Electribes switch patterns, but have not been able to get it to work. > > > > I'm no noob, but I really havent messed with PC all that much. I > > > > followed the examples I could find, and PC is enabled on the electribes. > > > > > > > > Can someone who has had this working explain the process to me? has > > > > anyone done this with electribes specifically I need to know if the > > > > pattern will switch on time like it should... > > > > > > > > Thanks all > > > > > > > > > > > >
Message
Re: Tick 0 Tick 1.
2013-06-14 by steve_the_composer
Attachments
- No local attachments were found for this message.