<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>macro controls — BeatMaker Forums</title>
        <link>https://intua.net/forums/index.php?p=/</link>
        <pubDate>Sat, 30 May 2026 22:06:45 +0000</pubDate>
        <language>en</language>
            <description>macro controls — BeatMaker Forums</description>
    <language>en</language>
    <atom:link href="https://intua.net/forums/index.php?p=/discussions/tagged/macro-controls/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>midi controller with Macro control : how avoiding Midi Focus actions downside ?</title>
        <link>https://intua.net/forums/index.php?p=/discussion/7827/midi-controller-with-macro-control-how-avoiding-midi-focus-actions-downside</link>
        <pubDate>Mon, 02 Dec 2019 21:24:56 +0000</pubDate>
        <category>Support</category>
        <dc:creator>cyril777</dc:creator>
        <guid isPermaLink="false">7827@/forums/index.php?p=/discussions</guid>
        <description><![CDATA[<p>Unless I’m mistaken, the problem when  mapping the Macro controls using Midi Focus is that when you switch from one bank to another, the Macro value will « jump » to the one last set by its controller. Because my English sucks and the problem is not easy to describe, here’s an example : let’s say you tweak the Macro 2 on Bank A at a value of 80%. Then, in Bank B you want to tweak its Macro 2. If this one was originally at 0%, as soon as you touch the knob on your midi controller mapped the Macro 2, this one will jump from 0&amp; to 70%, and this problem goes on and on from on bank to another. Since the Macro controls are meant to be used in live situations, you can see the problem. So far I didn’t find any solution to avoid this and there’s still no midi learn for Macro controls.<br />
Any other users concerned by this behavior, any solution to avoid this problem ? Thank you for your help !</p>
]]>
        </description>
    </item>
    <item>
        <title>Increase macro controls to...64 ? At least... :)</title>
        <link>https://intua.net/forums/index.php?p=/discussion/6869/increase-macro-controls-to-64-at-least</link>
        <pubDate>Sun, 22 Jul 2018 18:26:08 +0000</pubDate>
        <category>Feature Requests</category>
        <dc:creator>crony</dc:creator>
        <guid isPermaLink="false">6869@/forums/index.php?p=/discussions</guid>
        <description><![CDATA[<p>Hi,</p>

<p>Ok, Macro controls are massive, but it seems too limited for my needs I'm afraid...</p>

<p>As far as I've understood, if you want to map let's say Ruismaker to a midi controller, you have to select an AUx parameter between the 16 that BM3 can handle (fine for me) , then you assign it to a macro control, then you map the macro to your midi controller. Right ?</p>

<p>I wonder because selecting instruments directly is not a problem, it's assigned with the notes on the midi controller.<br />
But the CC's are not. Right ??<br />
I kind of expected that even with a fix CC into Ruismaker related to BM3, I would have been able to control it directly as the midi controller is well connected as he's sending notes to the instruments...</p>

<p>Am I missing something ?<br />
If it's the normal workflow of BM3, 16 macros are really too few...<br />
I could "live" with 64 macros in that case, but to have some spare, I'd love to have 128...or maybe 96...</p>

<p>Thanks for your comments <img src="https://intua.net/forums/resources/emoji/smile.png" title=":)" alt=":)" height="20" /></p>
]]>
        </description>
    </item>
   </channel>
</rss>
