As a possible solution for the sounds not triggering where you want them to: As you've explained now, you're only using one Velocity value per sample to select it with. What if you gave all the samples a Velocity Range that is the same as the Range for that sample in the Sample Select editor. In other words, following your example, the Velocity Values of 0 to 15 select the first sample, then the Velocity Values from 16 to 31 select sample 2, etc... In the Velocity Device, you then also need to set the minimum to 0 again; and in the Macro Mapping you also need to make it go from 0 to 127. My thinking is that with your method, Ableton divides the Macro Knob into 7 steps, and only changes the selection when that certain step is reached (which will always be at the end of the step. I say 7 steps because you already start at 0 which is the first sample of your 8 samples.
Hey thank you for sharing! Your solution is very insightful and yes I do believe that would work! The main concern at that point would be the volume the samples play at will be lower/louder depending on the Velocity zone that’s set (which was also an issue with the method in the video as well). I haven’t taken the time to work that part out fully yet but I do believe the method you mentioned would work to get the select/velocity zones to match!
@@IntempusMusic Then maybe here's another idea: what if you used your method of assigning individual velocity values but added a 9th sample (with its own velocity value) at the end that is actually a duplicate of the 8th sample. So, in this case it would go from 119 to 127. This way, the knob would be divided in 8 segments, but you're still using only slight differences in velocity, so the loudness won't be so different, and because this 9th sample is the same as the 8th sample, the sample won't change if you're at 127.
Awesome video Intempus! Really clever work arounds u figured out. That glitch seems more a good thing than bad. Look forward to trying out ur advise when im back. You da man. thx for the next level.
@@IntempusMusic I finally figured out away to use ur method to make it work with my set up! it took me sometime because i had to redesign a new drum rack. I put all my drum hits in on wave file, one sound per second, for about a minute. This saves load time for the computer to read the same sample across up to 128 zones. Then the velocity can be linked to the sample selector with the hi and lo out beginning with 1 going up to 127. This really helped man. Going to have to see where it goes next. Really dig ur channel.
Informative for sure but I had a follow up question. What if you had the same note (let's say C) coming into the sampler and we had 12 different samples loaded into it where they are distributed equally across the "Sel" range (0 to 127). And then let's say we map the "Sel" slider to a midi knob, Is there a way we can have the Sampler change its view depending on where the knob is i.e. which sample is being selected?
As a possible solution for the sounds not triggering where you want them to: As you've explained now, you're only using one Velocity value per sample to select it with. What if you gave all the samples a Velocity Range that is the same as the Range for that sample in the Sample Select editor. In other words, following your example, the Velocity Values of 0 to 15 select the first sample, then the Velocity Values from 16 to 31 select sample 2, etc...
In the Velocity Device, you then also need to set the minimum to 0 again; and in the Macro Mapping you also need to make it go from 0 to 127.
My thinking is that with your method, Ableton divides the Macro Knob into 7 steps, and only changes the selection when that certain step is reached (which will always be at the end of the step. I say 7 steps because you already start at 0 which is the first sample of your 8 samples.
Hey thank you for sharing! Your solution is very insightful and yes I do believe that would work! The main concern at that point would be the volume the samples play at will be lower/louder depending on the Velocity zone that’s set (which was also an issue with the method in the video as well). I haven’t taken the time to work that part out fully yet but I do believe the method you mentioned would work to get the select/velocity zones to match!
@@IntempusMusic Then maybe here's another idea: what if you used your method of assigning individual velocity values but added a 9th sample (with its own velocity value) at the end that is actually a duplicate of the 8th sample. So, in this case it would go from 119 to 127. This way, the knob would be divided in 8 segments, but you're still using only slight differences in velocity, so the loudness won't be so different, and because this 9th sample is the same as the 8th sample, the sample won't change if you're at 127.
Awesome video Intempus! Really clever work arounds u figured out. That glitch seems more a good thing than bad. Look forward to trying out ur advise when im back. You da man. thx for the next level.
No problem man! Cheers. Let me know if it works out for you
@@IntempusMusic I finally figured out away to use ur method to make it work with my set up! it took me sometime because i had to redesign a new drum rack. I put all my drum hits in on wave file, one sound per second, for about a minute. This saves load time for the computer to read the same sample across up to 128 zones. Then the velocity can be linked to the sample selector with the hi and lo out beginning with 1 going up to 127. This really helped man. Going to have to see where it goes next. Really dig ur channel.
Informative for sure but I had a follow up question.
What if you had the same note (let's say C) coming into the sampler and we had 12 different samples loaded into it where they are distributed equally across the "Sel" range (0 to 127). And then let's say we map the "Sel" slider to a midi knob, Is there a way we can have the Sampler change its view depending on where the knob is i.e. which sample is being selected?