Sampler, been struggling for years on this one

[nrgskill]

Try this:
Assign two different samples one at Sel 0 and one at Sel 1
Map a rack macro to the selector
Now in the macro type 0.4 > Sel position 0 sounds
Now in the macro type 0.5 > Sel position 1 sounds

This is driving me mad because I am using Push to select samples, and I cannot rely on the sample number on display because the Selector changes samples at half steps.
So, every time I have to adjust the knob just that little bit to change the sample and believe me... this is killing my vibe.

Is this a bug?
Anyone knows how to make sample select in Sampler to work at integer values (ex. 0; 1; 2...) instead of half values (0,5; 1,5; 2,5...)?

[siliconarc]

Pretty sure I've seen this prob reported around here before.
Adjusting the macro with a mouse, using the arrow keys to select the sample, and adding automation all work fine, but as you say, selecting samples with the macro via Push is almost impossible.
I'd report it as a bug to Ableton Support.

[yur2die4]

Does it work better if you limit the range of one or the other?

Not exactly sure if either of them is limited to a 127 or 128 type range. Or both but in different ways? If you limited the range you might be able to have it match, either by skipping Zero or by not going the maximum range for the mapping of the macro to the chain selector.

I might be way off on this but it is what comes to mind. My big disclaimer is that I haven’t attempted to test it

[siliconarc]

They all seem to be out by .5, so setting ranges can't really help.

[Sterioevo]

You could try to map the control via another mapping device that allows you to scale/offset/attenuate. Do you have m4l?

[nrgskill]

You could try to map the control via another mapping device that allows you to scale/offset/attenuate. Do you have m4l?

I don't have other devices (I went full push 2 and got rid of old controllers).
Yes, I do have the Suite with M4L.
On M4L: I was wondering if there is a way to transform the macro values from decimal numbers to integers. That would solve the issue with Push. Didn't try because I still have to learn M4L...

[Sterioevo]

Something like https://maxforlive.com/library/device/4502/multimap-pro might do what you want.

[Matt_Quinn]

I encountered something similar trying to use Expression Control to create a rack for hocket. Like this:

https://sonicbloom.net/instruments-alte ... enmelodie/

I could never get it to advance exactly one chain per note & then wrap around to the start.

A random trick I recently learned that might help is that you can map a macro to a *range* of notes on a controller. So if you have 5 positions you want the macro to snap to, go into mapping mode, hold down the top & bottom notes of a range of 5. When you get out of mapping mode, each of those notes sent from that controller should snap the macro to one of the 5 positions. Not sure it will work for Push though. Maybe in User mode.

[nrgskill]

This is definitely a Sampler bug:
I mapped a M4L "live.numbox" display to a macro, when I was moving the macro the Macro and numbox numbers were aligned.
Then I mapped the Sampler sample selector to the same Macro: not only the sample selector was off, but the numbox numbers too.

I hope my support request will be answered.

[Rivanni]

Try this:
Assign two different samples one at Sel 0 and one at Sel 1
Map a rack macro to the selector
Now in the macro type 0.4 > Sel position 0 sounds
Now in the macro type 0.5 > Sel position 1 sounds

This is driving me mad because I am using Push to select samples, and I cannot rely on the sample number on display because the Selector changes samples at half steps.
So, every time I have to adjust the knob just that little bit to change the sample and believe me... this is killing my vibe.

Is this a bug?
Anyone knows how to make sample select in Sampler to work at integer values (ex. 0; 1; 2...) instead of half values (0,5; 1,5; 2,5...)?

What version of Live are you using?

I tried to replicate this issue in Live 11 and 12, but the macro in Live and on Push only shows integers.
When I enter a decimal value, it is rounded down. So 0.4, 0.6, and 0.9 all become 0.

A Max for Live dial shows that the dial moves in tenths when you hold the Shift key, but it still rounds down, meaning the selector only changes at integer values.
Moving without shift performs whole integer steps.

You can make the macro dial less sensitive by lowering the Max value for the macro. Click the Map button in the rack to see this option.


Edit:
All the above is still right, but the fact that the next sample is selected too early is also an issue in my case.
So, typing 0.5 or 0.8 shows a zero on all locations. However what I hear is the sample on position 1. I noticed it with more distinct samples.
So it's definitely a bug since at least Live 10.

Sorry for the confusion.

[siliconarc]

Did you try on Mac, Rivanni?

[Rivanni]

Did you try on Mac, Rivanni?

MacOS 14.6 and Windows 11 23H2.

I edited my previous post. I can reproduce the issue.

[nrgskill]

what's your experience with support?
I wrote them 4 weeks ago about this bug and still didn't get any reply.

[Rivanni]

what's your experience with support?
I wrote them 4 weeks ago about this bug and still didn't get any reply.

It varies from one day to a few weeks before I get a reply. Four weeks is a long time, though.