# Issue using RIBN as modulation source in v1.24

**URL:** https://forum.udo-audio.com/t/issue-using-ribn-as-modulation-source-in-v1-24/2840
**Category:** Super Gemini
**Created:** [14 August 2024 20:41 UTC](https://forum.udo-audio.com/t/issue-using-ribn-as-modulation-source-in-v1-24/2840 "2024-08-14T20:41:34Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![0x80](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.udo-audio.com/0x80/32/439_2.png) [@0x80](https://forum.udo-audio.com/u/0x80)
#### Post date: [14 August 2024 20:41 UTC](https://forum.udo-audio.com/t/issue-using-ribn-as-modulation-source-in-v1-24/2840/1 "2024-08-14T20:41:34Z")

</div>

I ran into some unexpected behavior trying to use the ribbon controller as a modulation source.

I would expect:

1. When the source is mapped it should no longer control pitch
2. The upper/lower/both switch next to portamento should not affect the source, because the modulation mappings are already configured explicitly for each layer.

When I turn on the arpeggiator, 1 is no longer true. The ribbon controller goes back to controlling pitch.

2 is not true ever. If I map the controller, the toggle switch will cut out the controller, disabling whatever mapping is active.

I guess that last one could be considered a feature, being able to overrule the mapping with the switch, but I don’t see a practical use for it. I think it would mainly confuse people.
