# Using Bitwig’s On-Screen Grid with Scaler 3 – Best Routing?

**URL:** <https://forum.scalermusic.com/t/using-bitwig-s-on-screen-grid-with-scaler-3-best-routing/22657>\
**Category:** Scaler 3 General Discussion\
**Created:** [June 4, 2025, 4:10am UTC](https://forum.scalermusic.com/t/using-bitwig-s-on-screen-grid-with-scaler-3-best-routing/22657 "2025-06-04T04:10:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![daisy](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@daisy](https://forum.scalermusic.com/u/daisy)\
**Post date:** [June 4, 2025, 4:10am UTC](https://forum.scalermusic.com/t/using-bitwig-s-on-screen-grid-with-scaler-3-best-routing/22657/1 "2025-06-04T04:10:15Z")

</div>

Hey all!

So I’m experimenting with Bitwig’s on-screen isomorphic keyboard grid (super fun to play with), and I’m trying to route it into **Scaler 3** to generate chords, then have those go into something like **Pigments** or **Polymer**.

I’ve got it kinda working using MIDI routing between tracks — on-screen keys → Scaler 3 → synth track — but I’m wondering if there’s a smoother or more elegant way to do this inside Bitwig. Maybe with a Note FX Layer? Or is that overkill?

Would love to hear how others are doing it — this feels like a fun combo that could become part of my main workflow.

Thanks! 🙌