Yahoo Groups archive

Analogue-sequencer

Index last updated: 2026-04-28 23:15 UTC

Message

Re: [analogue-sequencer] Pattern copy, remain "linked"?

2006-01-29 by Martin Naef

Hi Paul

Paul Nagle wrote:
>> Now I'm trying to edit a track in part 3 - I want to create a variation 
>> of what is in part 2. Now whatever I edit is applied to both part 2 and 
>> part 3 -> in other words, it seems as if part copy doesn't actually copy 
>> the tracks, but simply sets a pointer to the data from track 2. Why is that?
>>
> Because the part does not contain any data except track, playlist, 
> transpose, FTS etc. settings. Each track still has as many patterns as 
> it has, put in whatever order the playlist deems. If you are in 6 bank 
> mode you have 8 patterns in each track to play with, which is quite a 
> lot.. :)

Ok, I think I get it now. I was missing the crucial distinction between 
*pattern* and part. Until now, I used them interchangeably.

>> What's the proper way to copy a part so I can create a variation of it?
> Do you mean copy a pattern? I tend to do this from playlist edit. Func 
> and the track button - then you can see which patterns run in which 
> order - the playlist. From there I tend to edit patterns - so might edit 
> pattern1, save the results to pattern 2,edit pattern2 save the results 
> to pattern 3 and so on. When you've created a selection of different 
> patterns, string them together by holding down the range of pattern 
> buttons. Lovely innit?

Yup - lovely, once you get it. I *think* I do now. Thanks for the 
explanation, I now know what part of the manual I have to read again.

Bye
Martin

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.