punchdrunk wrote:i think you're a little confused.
set q-link 1's target to TRACK
now when you record a sequence hitting all the pads and moving the qlink everything on the track is affected by the qlink and that qlink data is recorded into the sequence right?
what i am asking for is the ability to specify a value per pad in the program file that would overide the q-link slider's actual value. maybe i didn't make that clear before but storing this value per pad in the program file is what i've been saying this whole time. maybe you didn't catch that from earlier...
the function/ability is there already...
forget about the whole q-link thing you keep mentioning because this has nothing to do with q-link, this is what you really want to be able to do... and remember that all start and end points are used for is specifying the part of the sample that is played.
Method 1 with start and end points saved in the program per layer in a pad:
1) go into program mode.
2) hit A1.
3) select sample1.wav as layer 1's sample.
4) hit the window button.
5) in the play mode window, set layer 1 start point to 0, set layer 1 end point to 100.
6) hit A2.
7) select sample1.wav as layer 1's sample.
8) hit the window button.
9) in the play mode window, set layer 1 start point to 100, set layer 1 end point to 200
What Method 1 Does:
when pad A1 is hit or triggered, rather than use the start and end points specified within sample1.wav, it uses the start and end points specified for layer 1 which is 0 and 100. when pad A2 is hit or triggered, rather than use the start and end points specified within sample1.wav, it uses the start and end points specified for layer 1 which is 100 and 200.
Method 2 with sets of start and end points saved within wav file:
1) go into trim mode
2) select sample1.wav
3) edit->create new end point set (sample1.wav[0] becomes available)
4) select sample1.wav[0]
5) set start point to 0
6) set end point to 100
7) select sample1.wav
8) edit->create new end point set (sample1.wav[1] becomes available)
9) select sample1.wav[1]
10) set start point to 100
11) set end point to 200
12) go into program mode
13) hit A1
14) select sample1.wav[0] as layer1's sample
15) hit A2
16) select sample1.wav[1] as layer1's sample
What Method 2 Does:
when pad A1 is hit or triggered, since sample1.wav[0] had been selected, the sample plays using the first set of start and end points for sample1.wav of 0 and 100. when pad A2 is hit or triggered, since sample1.wav[1] has been selected, the sample plays using the second set of start and end points for sample1.wav of 100 and 200.
both of these methods would allow for you to use sample1.wav, but have two different pads play different parts of the file.
the advantage to Method 2 is that the sets of start and end points are saved within the wav file, which means that you can remove a sample from a pad and then add it back and the end points were retained. also, if that sample was loaded into a new session, all of the sets of end points which you previously saved would be available.
i personally like Method 2 because you could have a break:
break1.wav: boom tick bap tick boom boom bap tick
and you can save different sets of end points within it and end up with all of these samples in your program:
break1.wav: boom tick bap tick boom boom bap tick
break1.wav[0]: boom tick
break2.wav[1]: bap tick
break3.wav[2]: boom boom
break4.wav[3]: bap tick
now if you load break1.wav into a new program, it's just one file but it has 4 different chops within it and each can be assigned to a different pads without having to re-do the chops. now tell me that you wouldn't loooove that.
