Loopy Pro Wiki - User contributions [en]

Tips For Getting Up To Speed

2026-07-20T23:40:37Z

Edwards:

If you are having trouble getting started with Loopy Pro, here are some tips that we have found effective. Don't try to learn everything at once. People have different learning styles and backgrounds. The path that works for one person might not work for you. There is no one right path to learning how to use it.

* '''Perform the built-in tour''' all the way through — even if you did it at some time in the past. To access the tour, go to Loopy Pro’s Help menu and choose Open Tour. The Help menu is accessed from Loopy Pro’s main menu.
* '''The [[Simple Looper Tutorial Projects|Simple Looper tutorial]]'''. This is a simple tutorial great for getting started recording your first loops if you are feeling intimidated.
* '''Try out the projects''' in Loopy Pro’s [[Sample Projects 2.0|Sample Projects folder]]. The sample projects folder includes projects that demonstrate common workflows as well as some fun ones. You can access them through either the project browser or the Help Menu.
* The Tutorial projects teach essential core concepts and take only a few minutes each to explore. They include some handy widgets you can use in your own projects. They are found in the Sample Project folder’s Tutorial folder.
* '''Tutorial videos''': Check out our performance [[Main Page#Videos and Tutorials|videos and tutorials]] links. There are a number of comprehensive Loopy Pro tutorial series that approach it from different angles. Try a video or two from different series to see whose style you like. [https://www.youtube.com/@loopwithjack '''Loop with Jack'''] and the '''[https://www.youtube.com/@max_yar_guitar/videos Max Yar]''' tutorial series are particularly popular.
* You will find even more by searching for “Loopy Pro” on YouTube and other social media sites.
* '''Manual and wiki''': the Loopy Pro [https://loopypro.com/manual/ manual] is a valuable resource as is this [[Main Page|wiki]].
* '''Communities''': Join one of our fabulous [https://loopypro.com/communities/ communities], ask questions, and see what people are doing.
* '''Projects Ready-to-use:''' Check out the library of Loopy Pro projects and workflows in the [https://patchstorage.com/platform/loopy-pro/ Patchstorage repository].

One last piece of advice: '''ASK QUESTIONS EARLY!!!!'''

Sorry for shouting. If you find yourself frustrated trying to figure something out, contact us at support or ask your question in one of the communities. Ask us before you check with an LLM (AI). AI’s often answer people’s Loopy Pro questions with wrong answers that send them in the wrong direction.

We can usually help you get back on track, and your questions help us refine the documentation, wiki, tutorials, and examples.

[[Category:Getting Started]]

Tips For Getting Up To Speed

2026-07-16T22:57:06Z

Edwards: create page and add categories

If you are having trouble getting started with Loopy Pro, here are some tips that we have found effective. Since people have different ways of learning and different backgrounds, there is no one right path to learning how to use it. Some combination of the following will benefit anyone.

* Perform the built-in tour all the way through — even if you did it at some time in the past. To access the tour, go to Loopy Pro’s Help menu and choose Open Tour. The Help menu is accessed from Loopy Pro’s main menu.
* Try out the projects in Loopy Pro’s [[Sample Projects 2.0|Sample Projects folder]]. The sample projects folder includes projects that demonstrate common workflows as well as some fun ones. You can access them through either the project browser or the Help Menu.
* The Tutorial projects teach essential core concepts and take only a few minutes each to explore. They include some handy widgets you can use in your own projects. They are found in the Sample Project folder’s Tutorial folder.
* The [[Simple Looper Tutorial Projects|Simple Looper tutorial]]. This is a simple tutorial great for getting started recording your first loops if you are feeling intimidated.
* '''Tutorial videos''': Check out our performance [[Main Page#Videos and Tutorials|videos and tutorials]] links. There are a number of comprehensive Loopy Pro tutorial series that approach it from different angles. You will find even more by searching for “Loopy Pro” on YouTube and other social media sites.
* '''Manual and wiki''': the Loopy Pro [https://loopypro.com/manual/ manual] is a valuable resource as is this [[Main Page|wiki]].
* '''Communities''': Join one of our fabulous [https://loopypro.com/communities/ communities], ask questions, and see what people are doing.
* '''Projects Ready-to-use:''' Check out the library of Loopy Pro projects and workflows in the [https://patchstorage.com/platform/loopy-pro/ Patchstorage repository].

One last piece of advice: '''ASK QUESTIONS EARLY!!!!'''

Sorry for shouting. If you find yourself frustrated trying to figure something out, contact us at support or ask your question in one of the communities. Ask us before you check with an LLM (AI). AI’s often answer people’s Loopy Pro questions with wrong answers that send them in the wrong direction.

We can usually help you get back on track, and your questions help us refine the documentation, wiki, tutorials, and examples.

[[Category:Getting Started]]

Tips For Getting Up To Speed

2026-07-16T22:54:52Z

Edwards: Created page with "If you are having trouble getting started with Loopy Pro, here are some tips that we have found effective. Since people have different ways of learning and different backgrounds, there is no one right path to learning how to use it. Some combination of the following will benefit anyone. * Perform the built-in tour all the way through — even if you did it at some time in the past. To access the tour, go to Loopy Pro’s Help menu and choose Open Tour. The Help menu is..."

Tech Note:Active Page

2026-06-17T13:55:21Z

Edwards: Clarity

When MIDI Learning a widget, there is an option to MIDI Learn for ''This Page Only'' or for the ''Active Page a''s explained in the [https://loopypro.com/manual/midi-learn/ Loopy Pro manual].

''This Page Only'' triggers that particular widget on that particular page whenever the triggering MIDI comes in. The binding is to that particular widget. You can change the page's layout and the binding isn't affected because the binding targets the widget via a unique internal ID.

''Active Page'' bindings are based on the widget’s logical position on the page. For this to work, each page’s layout must be identical (or equivalent in terms of widget order). If your pages are not identical, your ''Active Page'' bindings may not work as you expect. ''Active Page'' page bindings trigger a widget on the page that it active when the triggering MIDI comes in. Unlike ''This Page Only'' bindings, the binding is to the widget at particular logical position. If your pages are not (logically) identical, it is possible that different widgets will be triggered by the same MIDI on different pages. For example, if you MIDI Learn a button called ''Play All'' for the ''Active Page'' and ''Play All'' is the first button on the page, you are really MIDI Learning the first button on the page. If your ''Play All'' is not the first button on page 2, it will not be triggered when page 2 is active.

== Active Page Alternative ==
There may be times where the widget positions are different on different pages but you want the same MIDI to trigger the item on that page any way. In this situation, you will create page-specific control profiles that are active only when the page is the current page.

Mixer Tips

2026-06-17T00:45:56Z

Edwards:

[[Category:Tips and Tricks]]
[[Category:Mixer]]

== Setting Up Independent Mixes ==
As of the time of this writing (June 2026), Loopy Pro's Master fader and its effects apply to all hardware outputs. When one wants a separate monitor/headphone mix and mains mix, there are a few ways to handle the situation.

=== Using a monitor bus ===
The most common solution is to set up a bus for the monitor mix whose destination is the hardware output used for monitoring. You use send knobs (which may be pre or post fader depending on one's needs) from each mixer channel that needs monitoring. With this setup, individual channel strips send to the main hardware outputs and the monitoring is handled with send knobs and the monitor bus.

This setup is the simplest to setup. It has the disadvantage that any change to the master fader (since it applies to all hardware destinations) will also change the level of the monitor mix. So, if you change the Master fader, you may have to make a compensating move on the monitor bus.

Another disadvantage of this setup is that effects on the master channel are applied to all hardware outputs. AUv3 plugins that have meters may not display properly in this situation.

=== Using a bus for each output (pair) ===
If you need to have discrete control over different hardware outputs, such as to have different Monitor and Mains (or Front-of-House) mixes with discrete control, you will use buses whose sends are set to After All Effects.

Overview

* Create a bus for each set of hardware outputs you want to be independent.
* Set the bus output destinations to the desired hardware outputs.
* Add sends from each mixer channel.
* Remove hardware destinations from mixer channels since the buses will handle the output.

The result will look something like what is shown below. Notice that only the FOH and MON mixer channels have output destinations. All the hardware inputs and colors and effects buses uses sends to the FOH and MON channels to reach the hardware destinations. In this setup, the Master fader is not used unless you want to make a global adjustment to both the 1+2 and 3+4 output levels.

[[File:Mixer_indepdendent_mixes.jpg|alt=Screenshot showing the setup described this section|frameless|600x600px]]

You can use this technique to have as many independent mixes as you would like.

== Sharing Venue Adjustments Between Projects ==
Performers often find that they need to make per-venue changes to some settings, most commonly EQ, monitor volume, reverb/delay and limiter/compressor.

While Loopy doesn’t, as of June 2026, have cross-project mixer snapshots, you can make use of Loopy Pro’s preset loading mechanisms and the Load Project follow action to make venue-specific changes that are shared by your projects. The basic technique is:

* Use effects plug-ins for any parameter (including level) that might need global updating across projects. This might include using a plugin such as Loopy Pro's Equalizer (with no EQ bands setup) to control a channel's volume.
* Save a preset in Loopy Pro for each per-venue adjustment of each plugin that needs a global adjustment.
* In each project, have a Load Project follow action that selects the per-venue preset for each plugin.
* At the venue, do a sound check in which you adjust the plugins for the venue and re-save the preset after making the changes. Some performers have a designated Soundcheck Project designed to help them set the levels they need — perhaps by using representative pre-recorded clips.
* If you need to make further adjustments, remember to re-save the preset so that your other projects will use them
* For switching projects, consider using the Load Project action with the “Copy Levels” option turned on.

'''Tip''': For setting gain levels, Loopy Pro’s built-in Equalizer plugin is an excellent way to adjust gain levels with or without EQ.

== See also ==
[[Mixer Actions]]

Mixer Tips

2026-06-17T00:16:08Z

Edwards:

[[Category:Tips and Tricks]]
[[Category:Mixer]]

== Setting Up Independent Mixes ==
As of the time of this writing (June 2026), Loopy Pro's Master fader and its effects apply to all hardware outputs. When one wants a separate monitor/headphone mix and mains mix, there are a few ways to handle the situation.

=== Using a monitor bus ===
The most common solution is to set up a bus for the monitor mix whose destination is the hardware output used for monitoring. You use send knobs (which may be pre or post fader depending on one's needs) from each mixer channel that needs monitoring. With this setup, individual channel strips send to the main hardware outputs and the monitoring is handled with send knobs and the monitor bus.

This setup is the simplest to setup. It has the disadvantage that any change to the master fader (since it applies to all hardware destinations) will also change the level of the monitor mix. So, if you change the Master fader, you may have to make a compensating move on the monitor bus.

Another disadvantage of this setup is that effects on the master channel are applied to all hardware outputs. AUv3 plugins that have meters may not display properly in this situation.

=== Using a bus for each output (pair) ===
If you need to have discrete control over different hardware outputs, such as to have different Monitor and Mains (or Front-of-House) mixes with discrete control, you will use buses whose sends are set to After All Effects.

Overview

* Create a bus for each set of hardware outputs you want to be independent.
* Set the bus output destinations to the desired hardware outputs.
* Add sends from each mixer channel.
* Remove hardware destinations from mixer channels since the buses will handle the output.

The result will look something like what is shown below. Notice that only the FOH and MON mixer channels have output destinations. All the hardware inputs and colors and effects buses uses sends to the FOH and MON channels to reach the hardware destinations. In this setup, the Master fader is not used unless you want to make a global adjustment to both the 1+2 and 3+4 output levels.
[[File:Mixer indepdendent mixes.jpg|alt=Screenshot showing the setup described this section|none|thumb]]
You can use this technique to have as many independent mixes as you would like.

== Sharing Venue Adjustments Between Projects ==
Performers often find that they need to make per-venue changes to some settings, most commonly EQ, monitor volume, reverb/delay and limiter/compressor.

While Loopy doesn’t, as of June 2026, have cross-project mixer snapshots, you can make use of Loopy Pro’s preset loading mechanisms and the Load Project follow action to make venue-specific changes that are shared by your projects. The basic technique is:

* Use effects plug-ins for any parameter (including level) that might need global updating across projects. This might include using a plugin such as Loopy Pro's Equalizer (with no EQ bands setup) to control a channel's volume.
* Save a preset in Loopy Pro for each per-venue adjustment of each plugin that needs a global adjustment.
* In each project, have a Load Project follow action that selects the per-venue preset for each plugin.
* At the venue, do a sound check in which you adjust the plugins for the venue and re-save the preset after making the changes. Some performers have a designated Soundcheck Project designed to help them set the levels they need — perhaps by using representative pre-recorded clips.
* If you need to make further adjustments, remember to re-save the preset so that your other projects will use them
* For switching projects, consider using the Load Project action with the “Copy Levels” option turned on.

'''Tip''': For setting gain levels, Loopy Pro’s built-in Equalizer plugin is an excellent way to adjust gain levels with or without EQ.

== See also ==
[[Mixer Actions]]

Mixer Tips

2026-06-17T00:10:45Z

Edwards: Created page with "Category:Tips and Tricks Category:Mixer == Setting Up Independent Mixes == As of the time of this writing (June 2026), Loopy Pro's Master fader and its effects apply to all hardware outputs. When one wants a separate monitor/headphone mix and mains mix, there are a few ways to handle the situation. === Using a monitor bus === The most common solution is to set up a bus for the monitor mix whose destination is the hardware output used for monitoring. You use sen..."

File:Mixer indepdendent mixes.jpg

2026-06-17T00:09:53Z

Edwards:

Screenshot of the Loopy Pro mixer set up to have fully independent monitor and front-of-house mixes.

Mixer Actions

2026-06-16T23:50:18Z

Edwards: tags

__FORCETOC__
This article covers topics related to controlling the mixer with Loopy Pro actions.

== Mutually-Exclusive Inputs ==
if you have instruments or hardware inputs that you want to be mutually exclusive, use a Radio Button grid or Stepped Dial. For each step or radio button, add a ''Mute/Unmute'' action with ''Invert Value'' turned on as the ''Select/Deselect'' action. We use the Invert Value setting so that the selected input is unmuted rather than muted.
{| class="wikitable"
|+
|[[File:Mixer-mutual-exclusive.jpg|alt=Mutually exclusive input example picture|none|thumb|300x300px]]
|[[File:Input Selector Setup.jpg|alt=Input Selector Setup|none|thumb|300x300px]]
|}
The video below shows the steps to set up a mutually-exclusive input selector.
{|style="border-style: none; border-width: 0px"
|-
|<youtube>D9J9li-Xl6U</YouTube>
|}

== Controlling Sends ==
Send knobs are controlled by ''Adjust Parameter'' actions for the mixer channel in which they appear:

* Color Channels: Color Group Actions -> Adjust Parameter
* Hardware inputs and Audio Unit Instruments: Audio Source Actions -> Adjust Parameter
* Buses: Bus Actions -> Adjust Parameter

To add an action to control a send:

* Add an action of the appropriate type. For example to control an audio input's send know, choose Audio Source Actions -> Adjust Parameter.
* In the ''Adjust Parameter'' setup panel, tap on Target and select the mixer channel whose send you want to target.
* After choosing the target, tap on ''Parameter''. A list will appear of that mixer channel's parameters. If the channel has a send, it will be listed.
* Choose the send that you want to adjust.

{|style="border-style: none; border-width: 0px"
|-
|<YouTube>mzSIy18TrAI</YouTube>
|}

[[Category:Tips and Tricks]]
[[Category:Mixer]]

Effective Use of FX and Routing

2026-06-16T23:49:43Z

Edwards: tags

[[Category:Tips and Tricks]]
[[Category:Mixer]]

Loopy Pro offers a robust set of tools for applying and managing effects (FX) and routing audio. Understanding how to effectively use sends, buses, and multiple instances of effects can significantly enhance your audio production capabilities.

= Sends and Buses =
Sends and buses are essential for managing how audio is routed and processed through effects in Loopy Pro.

== Adding a Bus ==
# Open the Mixer view.
# Tap the + button in the corner and select "Add Bus".

== Using Sends ==
# In the Mixer, tap the + button within the Sends area of a channel strip.
# Select the bus you created.
# Adjust the send level using the dial that appears. Swiping vertically adjusts the level, and then dragging out horizontally allows for finer control.

Sends can be positioned at different points in the signal flow:
* '''Before All Effects''': The send occurs before any effects are applied.
* '''Before Fader''': The send occurs after pre-fader effects but before the fader.
* '''After Fader''': The send occurs after the fader but before post-fader effects.
* '''After All Effects''': The send occurs after all effects and the fader.

Long press on a send dial to change its position in the signal flow or to delete it.

= Using Multiple Instances of the Same Effect =
Loopy Pro allows you to use the same effect across multiple channels. This feature is particularly useful when you want to apply a consistent effect setting to multiple audio sources.

== Adding an Effect ==
# In the Mixer, tap the + button in the Effects section of a channel strip.
# Select the desired effect from the list.

== Applying the Same Effect to Multiple Channels ==
# Add the effect to the first channel and configure it as needed.
# Repeat the process for other channels. Loopy Pro will manage multiple hidden instances of the effect, synchronizing their settings to simulate a single, multi-channel plugin.

This approach helps maintain performance efficiency while ensuring consistent effect application across channels.

= Pre-Fader vs Post-Fader Effects =
Choosing between pre-fader and post-fader effects depends on the desired audio outcome.

== Pre-Fader Effects ==
These are applied before the channel's volume fader. They process the full-volume audio and then pass the processed signal through the fader. Use pre-fader effects when you want the effect to be independent of volume changes.

== Post-Fader Effects ==
These are applied after the channel's volume fader. They process the audio after the volume adjustment, meaning the effect's output is influenced by the fader position. Use post-fader effects when you want the effect to be affected by volume changes, such as reverb or delay that should fade out naturally when the volume is reduced.

= Practical Tips for Effective FX and Routing =
* '''Group Effects''': Use buses to group similar channels and apply a single effect to the group, saving processing power and ensuring consistency.
* '''Parallel Processing''': Use sends to create parallel processing

Main Page

2026-05-23T18:59:22Z

Edwards: /* Basics */

Welcome to the Loopy Pro Wiki, your comprehensive resource for everything related to Loopy Pro, the powerful and flexible looping app designed for musicians and performers.

Don't forget to start with the [https://loopypro.com/manual manual], if you haven't already read it.

= Getting Started =
<dynamicpagelist>
category = Getting Started
ordermethod = sortkey
order = ascending

</dynamicpagelist>

= Basics =
<dynamicpagelist>
category = Basics
ordermethod = sortkey
order = ascending
</dynamicpagelist>

= Hardware Integration =
<DynamicPageList>
category = Hardware Integration
ordermethod = sortkey
order = ascending
</DynamicPageList>

= Software Integration =
<DynamicPageList>
category = Software Integration
</DynamicPageList>

= Common Issues and Troubleshooting =
<DynamicPageList>
category = Common Issues and Troubleshooting
ordermethod = sortkey
order = ascending
</DynamicPageList>

= Advanced Features =
<dynamicpagelist>
category = Advanced Features
ordermethod = sortkey
order = ascending
</dynamicpagelist>

= Tips and Tricks =
<dynamicpagelist>
category = Tips and Tricks
ordermethod = sortkey
order = ascending
</dynamicpagelist>

= Community Contributions =
<DynamicPageList>
category = Community Contributions
</DynamicPageList>

= Videos and Tutorials =
<DynamicPageList>
category = Videos and Tutorials
</DynamicPageList>

= Recent Changes =
Keep track of the latest updates and contributions to the Loopy Pro Wiki.
* [[Special:RecentChanges|Recent Changes]]

= About =
This wiki is maintained by the Loopy Pro community. Your contributions and edits are welcome to help make this resource as comprehensive and useful as possible.

For any questions or issues, feel free to reach out to one of our [https://loopypro.com/communities communities]

MIDI Essential Tips and Tricks

2026-05-23T18:59:01Z

Edwards: tags

[[Category:Tips and Tricks]][[Category:Basics]]
This article covers a variety of tips for using MIDI in Loopy Pro.

__TOC__

== MIDI Effect Chains ==
MIDI Effects chains are possible in Loopy Pro by adding MIDI AUv3s to the mixer and chaining them together using the mixer destination slots.
[[File:MIDI Effects Chain Example.jpg|none|thumb|A simple MIDI effect chain: MIDI controller to Streambyter to Mozaic to Bleass Monolit synth.]]
Steps:

* Add each MIDI AUv3 that will be in your chain to Loopy Pro's mixer, by tapping the + in Loopy Pro's mixer and choosing Add MIDI
* Tap in the Destination slot of the mixer to choose where each plug will send its MIDI.

== Audio Instruments and Effects as MIDI Sources ==
Some Audio AUv3 instruments and effects can send MIDI. For example, Animoog Z can send MIDI from its onscreen keyboard. The FAC Envolver audio effect can send MIDI in response to audio input. MIDI Guitar 2 and 3 con convert audio input into MIDI.

To use the MIDI output of audio AU instruments or effects, first load the audio AUv3. Here we have Animoog Z loaded as an instrument.
[[File:Animoog Z in mixer as an audio source.jpg|alt=Animoog Z loaded as an audio source|none|thumb|Animoog Z loaded as an audio source]]
Once the AUv3 has been loaded as an audio source (instrument or effect), open the mixer and tap + to add a channel to the mixer.

Choose Add MIDI.
[[File:Add MIDI menu item.jpg|alt=Add MIDI menu command|none|thumb]]
In the MIDI Source popup that appears instances of Audio Units already in the project will be labeled with a letter. Choose an existing instance.
[[File:MIDI Source Popup.jpg|alt=Already loaded audio AUv3 that can send MIDI are marked with a letter in a circle (the instance identifier).|none|thumb|Already loaded audio AUv3 that can send MIDI are marked with a letter in a circle (the instance identifier).]]
The AU you choose will be added as a MIDI source to your mixer and can now be routed to any destination that can receive MIDI.
[[File:Mixer after MIDI AU Loaded.jpg|alt=The Audio AUv3 has been added as a MIDI Source, too.|none|thumb|The Audio AUv3 has been added as a MIDI Source, too.]]

== Triggering MIDI Bindings with Widgets ==
It is often useful to use widgets to trigger MIDI bindings. To do so. a widget needs to be able to send MIDI that reaches Loopy Pro's MIDI control system. As of Loopy Pro 2.0, there are two primary ways to do this:

* Use a lightweight MIDI AUv3 (such as the free Streambyter or ShowMIDI plugins) to pass MIDI from widgets to the Loopy Pro's MIDI control system.
* Use a MIDI Color to pass the MIDI through to the MIDI control system.

=== AUv3 Passthrough to MIDI Control ===
The simplest way to do this is to use a MIDI AUv3 as an intermediary. Loopy Pro can use MIDI from any loaded AUv3 to trigger MIDI Bindings. To do this:

* Add a MIDI AUv3 to your project that passes MIDI through. Streambyter or ShowMIDI (both free AUv3) work well for this.
* Use the Send MIDI Message action to send MIDI from widgets to the intermediary of your choice.
* Set up your MIDI binding and set the intermediary as the trigger source.

[[File:Streambyter As MIDI Intermediary.jpg|alt=Streambyter loaded as an MIDI source in Loopy Pro's mixer|none|thumb|Streambyter loaded as an MIDI source in Loopy Pro's mixer]]
[[File:Fader to Streambyter.jpg|alt=A fader set up to send MIDI CC 0 to Streambyter so that it can be received by MIDI Bindings|none|thumb|A fader set up to send MIDI CC 0 to Streambyter so that it can be received by MIDI Bindings]]
[[File:Streambyter binding.jpg|alt=A MIDI Binding set up to be triggered by Streambyter. This binding will trigger when the fader shown in the previous picture is moved.|none|thumb|A MIDI Binding set up to be triggered by Streambyter. This binding will trigger when the fader shown in the previous picture is moved.]]

=== Using a MIDI Color for Passthrough to MIDI Control ===
The Send MIDI Message action can send MIDI to a MIDI colour. Make sure that ''Monitor Through'' is turned on in the Send MIDI Message action. The MIDI message can then be used for MIDI bindings. Usually, you will see a MIDI color used for no other purpose than automation and passing messages. You will need to add a MIDI loop or one-shot to the project for the color to be available. Typically, you won't use that clip and will hide it on a page other than the project's main page. The video below demonstrates the setup:

<youtube>l9BA5FMw5zE</youtube>

== Sending Keys and Pads to Different Instruments ==
If you have a controller with keys and pads, you may want to send the keys and pads to different synths.

Steps:

* Use a MIDI monitor to determine which MIDI channel the keys and pads send on. Typically, the keys will send on channel 1 and the pads on channel 10.
* Add your controller to Loopy Pro's mixer if you have not already done so.
* Add the instruments to which you want to send the MIDI as destinations of the controller.
* For each instrument
** Tap on it destination icon to show the destination options
** Set the Channel Filter to the MIDI Channel of the source (either the keys' MIDI Channel or the pads')
** [[File:MIDI Destination Options.jpg|alt=The Channel Filter set to MIDI Channel 1|none|thumb|The Channel Filter set to MIDI Channel 1]]

== Using a passthrough plugin as a MIDI bus ==
Sometimes, you may want multiple MIDI sources to be seen as a single MIDI source so that input from any of them is routed to the same destinations. For instance, you might want an external MIDI keyboard, Launchpad and onscreen keyboard to be routed the same way.

To do this, add a MIDI AUv3 that passes MIDI through automatically. Streambyter and ShowMIDI are free lightweight AUv3 plugins that pass through any MIDI they receive with no detectable latency. Make the passthrough AUv3 the destination of your other MIDI controllers. Use the passthrough as the MIDI source as shown in the picture below.

Note that Streambyter can also be used as a powerful MIDI scripting, filtering and remapping utility in addition to being a handy MIDI monitor.

There are likely other MIDI AUv3 that also can be used.
[[File:VirtualMIDIbus.jpg|alt=A virtual MIDI bus set up in Loopy Pro’s mixer|none|thumb]]

== Synth Routing ==
See [[Synth Routing 2.0]] for ideas about setting up a routing switch for your synths.

Edward's Example Projects

2026-05-19T22:29:48Z

Edwards: /* Visual Metronome */

__FORCETOC__
This page has links to projects that demonstrate useful techniques.

== Clip Sequencing Examples ==

=== Dial Sequencers 1.1 ===
[[File:Dial Sequencer Example Screenshot.jpg|alt=Screenshot of the dial sequencer example|none|thumb]]
This project demonstrates using a stepped dial to sequence clips into a song without need for the timeline. The project demonstrates two ways you might use a dial to sequence a song:

* An automated dial that plays the song from start to finish when triggered
* A 'stepper' dial that advances from one section to the next when triggered.

In your own projects, you can combine the techniques. For example, you might set up a dial to advance through some parts and manually advance for others.

The projects:
* [[Media:EXAMPLE Dial Sequencer iPad 1.1.lpproj.zip|Landscape (iPad) formatted project]]
* [[Media:EXAMPLE Dial Sequencer iPhone 1.1.lpproj.zip|Portrait (iPhone) formatted project]]

== Miscellany ==

=== SMC-Mixer Compatibility ===
This has moved to: [[SMC-Mixer]]

=== Random Triggers ===

==== Random Note Triggers ====
This project uses a Streambyter script to send random triggers. When any MIDI note is sent to Streambyter, Streambyter sends out a MIDI note in the range set up in the plugin. Add the script as a preset in Loopy Pro to use in your own projects.

'''Download''': [[Media:EXAMPLE Random Note Triggers.zip|EXAMPLE Random Note Triggers]]

{|style="border-style: none; border-width: 0px;"|-
|<YouTube width="450>q-WyxawQygo</youtube>
|}

==== Randomize CCs ====
The [[:File:EXAMPLE RANDOMIZE CC.zip|Randomize CC's Project]] contains a Streambyter instance whose script randomizes incoming CC values. Open the Streambyter script and follow the instructions to configure which CCs are randomized and what the randomization range is.

'''Download''': [[Media:EXAMPLE RANDOMIZE CC.zip|Randomize CC's Project]]

=== Visual Metronome ===
[[File:Visual_Metronome_Flasher.jpg|320x320px|Visual Metronome Flasher.jpg]]

This project provides some ideas for creating visual metronomes.

'''DOWNLOAD''':[[Media:EXAMPLE Flashers.zip| EXAMPLE Flashers]]

== Example Projects Listing==
This is a listing of projects categorized as example. Most are also linked to from other wiki pages.

<DynamicPageList>
category = Example
ordermethod = sortkey
order = ascending
</DynamicPageList>

See also: [[:Category:Example|Examples Category]]

== See also ==
[[Templates:Edward's Workbench|Edward’s Workbench]] always has a number of projects worth checking out.

[[Category:Community Contributions]]

Edward's Example Projects

2026-05-19T22:21:18Z

Edwards: /* Visual Metronome */

__FORCETOC__
This page has links to projects that demonstrate useful techniques.

== Clip Sequencing Examples ==

=== Dial Sequencers 1.1 ===
[[File:Dial Sequencer Example Screenshot.jpg|alt=Screenshot of the dial sequencer example|none|thumb]]
This project demonstrates using a stepped dial to sequence clips into a song without need for the timeline. The project demonstrates two ways you might use a dial to sequence a song:

* An automated dial that plays the song from start to finish when triggered
* A 'stepper' dial that advances from one section to the next when triggered.

In your own projects, you can combine the techniques. For example, you might set up a dial to advance through some parts and manually advance for others.

The projects:
* [[Media:EXAMPLE Dial Sequencer iPad 1.1.lpproj.zip|Landscape (iPad) formatted project]]
* [[Media:EXAMPLE Dial Sequencer iPhone 1.1.lpproj.zip|Portrait (iPhone) formatted project]]

== Miscellany ==

=== SMC-Mixer Compatibility ===
This has moved to: [[SMC-Mixer]]

=== Random Triggers ===

==== Random Note Triggers ====
This project uses a Streambyter script to send random triggers. When any MIDI note is sent to Streambyter, Streambyter sends out a MIDI note in the range set up in the plugin. Add the script as a preset in Loopy Pro to use in your own projects.

'''Download''': [[Media:EXAMPLE Random Note Triggers.zip|EXAMPLE Random Note Triggers]]

{|style="border-style: none; border-width: 0px;"|-
|<YouTube width="450>q-WyxawQygo</youtube>
|}

==== Randomize CCs ====
The [[:File:EXAMPLE RANDOMIZE CC.zip|Randomize CC's Project]] contains a Streambyter instance whose script randomizes incoming CC values. Open the Streambyter script and follow the instructions to configure which CCs are randomized and what the randomization range is.

'''Download''': [[Media:EXAMPLE RANDOMIZE CC.zip|Randomize CC's Project]]

=== Visual Metronome ===
[[File:Visual_Metronome_Flasher.jpg|320x320px|Visual Metronome Flasher.jpg]]
This project provides some ideas for creating visual metronomes.

'''DOWNLOAD''':[[Media:EXAMPLE Flashers.zip| EXAMPLE Flashers]]

== Example Projects Listing==
This is a listing of projects categorized as example. Most are also linked to from other wiki pages.

<DynamicPageList>
category = Example
ordermethod = sortkey
order = ascending
</DynamicPageList>

See also: [[:Category:Example|Examples Category]]

== See also ==
[[Templates:Edward's Workbench|Edward’s Workbench]] always has a number of projects worth checking out.

[[Category:Community Contributions]]

Edward's Example Projects

2026-05-19T22:19:20Z

Edwards: Add visual metronome

__FORCETOC__
This page has links to projects that demonstrate useful techniques.

== Clip Sequencing Examples ==

=== Dial Sequencers 1.1 ===
[[File:Dial Sequencer Example Screenshot.jpg|alt=Screenshot of the dial sequencer example|none|thumb]]
This project demonstrates using a stepped dial to sequence clips into a song without need for the timeline. The project demonstrates two ways you might use a dial to sequence a song:

* An automated dial that plays the song from start to finish when triggered
* A 'stepper' dial that advances from one section to the next when triggered.

In your own projects, you can combine the techniques. For example, you might set up a dial to advance through some parts and manually advance for others.

The projects:
* [[Media:EXAMPLE Dial Sequencer iPad 1.1.lpproj.zip|Landscape (iPad) formatted project]]
* [[Media:EXAMPLE Dial Sequencer iPhone 1.1.lpproj.zip|Portrait (iPhone) formatted project]]

== Miscellany ==

=== SMC-Mixer Compatibility ===
This has moved to: [[SMC-Mixer]]

=== Random Triggers ===

==== Random Note Triggers ====
This project uses a Streambyter script to send random triggers. When any MIDI note is sent to Streambyter, Streambyter sends out a MIDI note in the range set up in the plugin. Add the script as a preset in Loopy Pro to use in your own projects.

'''Download''': [[Media:EXAMPLE Random Note Triggers.zip|EXAMPLE Random Note Triggers]]

{|style="border-style: none; border-width: 0px;"|-
|<YouTube width="450>q-WyxawQygo</youtube>
|}

==== Randomize CCs ====
The [[:File:EXAMPLE RANDOMIZE CC.zip|Randomize CC's Project]] contains a Streambyter instance whose script randomizes incoming CC values. Open the Streambyter script and follow the instructions to configure which CCs are randomized and what the randomization range is.

'''Download''': [[Media:EXAMPLE RANDOMIZE CC.zip|Randomize CC's Project]]

=== Visual Metronome ===
This project provides some ideas for creating visual metronomes.

DOWNLOAD:[[MEDIA:EXAMPLE Flashers.zip| EXAMPLE Flashers]]

[[File:Visual Metronome Flasher.jpg|Visual Metronome Flasher.jpg]]

== Example Projects Listing==
This is a listing of projects categorized as example. Most are also linked to from other wiki pages.

<DynamicPageList>
category = Example
ordermethod = sortkey
order = ascending
</DynamicPageList>

See also: [[:Category:Example|Examples Category]]

== See also ==
[[Templates:Edward's Workbench|Edward’s Workbench]] always has a number of projects worth checking out.

[[Category:Community Contributions]]

File:EXAMPLE Flashers.zip

2026-05-19T22:13:12Z

Edwards: Create

Project that demonstrates how to create a visual metronome with sliders and a midi clip.

[[Category:Project]]
[[Category:Example]]

File:EXAMPLE Flashers.zip

2026-05-19T22:08:34Z

Edwards:

Project that demonstrates how to create a visual metronome with sliders and a midi clip.

File:Visual Metronome Flasher.jpg

2026-05-19T22:03:53Z

Edwards:

Screenshot of the visual metronome/flasher example project

Tech Note:Active Page

2026-05-18T23:42:14Z

Edwards:

When MIDI Learn a widget, there is an option to MIDI Learn for ''This Page Only'' or for the ''Active Page''. As explained in the [https://loopypro.com/manual/midi-learn/ Loopy Pro manual].

''This Page Only'' triggers that particular widget on that particular page whenever the triggering MIDI comes in. The binding is to that particular widget. You can change the page's layout and the binding isn't affected because the binding targets the widget via a unique internal ID.

''Active Page'' bindings are based on the assumption that each page has an identical. If your pages are not identical, your ''Active Page'' bindings may not work as you expected. ''Active Page'' page bindings trigger only a widget on the page that it active when the triggering MIDI comes in. Unlike ''This Page Only'' bindings, the binding is to the widget at particular logical position. If your pages are not (logically) identical, it is possible that different widgets will be triggered by the same MIDI on different pages. For example, if you MIDI Learn a button called ''Play All'' for the ''Active Page'' and ''Play All'' is the first button on the page, you are really MIDI Learning the first button on the page. If your ''Play All'' is not the first button on page 2, it will not be triggered when page 2 is active.

== Active Page Alternative ==
There may be times where the widget positions are different on different pages but you want the same MIDI to trigger the item on that page any way. In this situation, you will create page-specific control profiles that are active only when the page is the current page.

MIDI Basics

2026-05-13T17:17:58Z

Edwards:

__FORCETOC__
This article is intended to provide overview of Loopy Pro's 2.0 MIDI looping and routing features to help get you up and running. '''This page is very much in progress.''' Right now it is a bit bare bones but should help you get up and running.

The ''Tutorial Projects'' in Loopy Pro 2.0's [[Sample Projects 2.0|Sample Projects]] provide a quick and essential overview of Loopy Pro's features. The other sample projects can be great starting points for your own projects.

== Intro Tutorials ==
The video tutorials in this section can help you get up and running

<YouTube>Um1NqKgIhzY</YouTube>

<YouTube>9Tv3coXpD3g</YouTube>

<YouTube>3imVjWs0V74</YouTube>

<YouTube>QoGCoQk20OA</YouTube>

== <youtube>0MSO5Mf9Aew</youtube><youtube>kx7qWDAraK4</youtube><youtube>lAT8qcD0GBE </youtube>See Also ==
See [[MIDI Essential Tips and Tricks|Midi Essential Tips and Tricks]] for more helpful information.
[[Category:Getting Started]]
[[Category:Basics]]

MIDI Essential Tips and Tricks

2026-05-13T17:17:09Z

Edwards: add synth routing link

[[Category:Tips and Tricks]]
This article covers a variety of tips for using MIDI in Loopy Pro.

__TOC__

== MIDI Effect Chains ==
MIDI Effects chains are possible in Loopy Pro by adding MIDI AUv3s to the mixer and chaining them together using the mixer destination slots.
[[File:MIDI Effects Chain Example.jpg|none|thumb|A simple MIDI effect chain: MIDI controller to Streambyter to Mozaic to Bleass Monolit synth.]]
Steps:

* Add each MIDI AUv3 that will be in your chain to Loopy Pro's mixer, by tapping the + in Loopy Pro's mixer and choosing Add MIDI
* Tap in the Destination slot of the mixer to choose where each plug will send its MIDI.

== Audio Instruments and Effects as MIDI Sources ==
Some Audio AUv3 instruments and effects can send MIDI. For example, Animoog Z can send MIDI from its onscreen keyboard. The FAC Envolver audio effect can send MIDI in response to audio input. MIDI Guitar 2 and 3 con convert audio input into MIDI.

To use the MIDI output of audio AU instruments or effects, first load the audio AUv3. Here we have Animoog Z loaded as an instrument.
[[File:Animoog Z in mixer as an audio source.jpg|alt=Animoog Z loaded as an audio source|none|thumb|Animoog Z loaded as an audio source]]
Once the AUv3 has been loaded as an audio source (instrument or effect), open the mixer and tap + to add a channel to the mixer.

Choose Add MIDI.
[[File:Add MIDI menu item.jpg|alt=Add MIDI menu command|none|thumb]]
In the MIDI Source popup that appears instances of Audio Units already in the project will be labeled with a letter. Choose an existing instance.
[[File:MIDI Source Popup.jpg|alt=Already loaded audio AUv3 that can send MIDI are marked with a letter in a circle (the instance identifier).|none|thumb|Already loaded audio AUv3 that can send MIDI are marked with a letter in a circle (the instance identifier).]]
The AU you choose will be added as a MIDI source to your mixer and can now be routed to any destination that can receive MIDI.
[[File:Mixer after MIDI AU Loaded.jpg|alt=The Audio AUv3 has been added as a MIDI Source, too.|none|thumb|The Audio AUv3 has been added as a MIDI Source, too.]]

== Triggering MIDI Bindings with Widgets ==
It is often useful to use widgets to trigger MIDI bindings. To do so. a widget needs to be able to send MIDI that reaches Loopy Pro's MIDI control system. As of Loopy Pro 2.0, there are two primary ways to do this:

* Use a lightweight MIDI AUv3 (such as the free Streambyter or ShowMIDI plugins) to pass MIDI from widgets to the Loopy Pro's MIDI control system.
* Use a MIDI Color to pass the MIDI through to the MIDI control system.

=== AUv3 Passthrough to MIDI Control ===
The simplest way to do this is to use a MIDI AUv3 as an intermediary. Loopy Pro can use MIDI from any loaded AUv3 to trigger MIDI Bindings. To do this:

* Add a MIDI AUv3 to your project that passes MIDI through. Streambyter or ShowMIDI (both free AUv3) work well for this.
* Use the Send MIDI Message action to send MIDI from widgets to the intermediary of your choice.
* Set up your MIDI binding and set the intermediary as the trigger source.

[[File:Streambyter As MIDI Intermediary.jpg|alt=Streambyter loaded as an MIDI source in Loopy Pro's mixer|none|thumb|Streambyter loaded as an MIDI source in Loopy Pro's mixer]]
[[File:Fader to Streambyter.jpg|alt=A fader set up to send MIDI CC 0 to Streambyter so that it can be received by MIDI Bindings|none|thumb|A fader set up to send MIDI CC 0 to Streambyter so that it can be received by MIDI Bindings]]
[[File:Streambyter binding.jpg|alt=A MIDI Binding set up to be triggered by Streambyter. This binding will trigger when the fader shown in the previous picture is moved.|none|thumb|A MIDI Binding set up to be triggered by Streambyter. This binding will trigger when the fader shown in the previous picture is moved.]]

=== Using a MIDI Color for Passthrough to MIDI Control ===
The Send MIDI Message action can send MIDI to a MIDI colour. Make sure that ''Monitor Through'' is turned on in the Send MIDI Message action. The MIDI message can then be used for MIDI bindings. Usually, you will see a MIDI color used for no other purpose than automation and passing messages. You will need to add a MIDI loop or one-shot to the project for the color to be available. Typically, you won't use that clip and will hide it on a page other than the project's main page. The video below demonstrates the setup:

<youtube>l9BA5FMw5zE</youtube>

== Sending Keys and Pads to Different Instruments ==
If you have a controller with keys and pads, you may want to send the keys and pads to different synths.

Steps:

* Use a MIDI monitor to determine which MIDI channel the keys and pads send on. Typically, the keys will send on channel 1 and the pads on channel 10.
* Add your controller to Loopy Pro's mixer if you have not already done so.
* Add the instruments to which you want to send the MIDI as destinations of the controller.
* For each instrument
** Tap on it destination icon to show the destination options
** Set the Channel Filter to the MIDI Channel of the source (either the keys' MIDI Channel or the pads')
** [[File:MIDI Destination Options.jpg|alt=The Channel Filter set to MIDI Channel 1|none|thumb|The Channel Filter set to MIDI Channel 1]]

== Using a passthrough plugin as a MIDI bus ==
Sometimes, you may want multiple MIDI sources to be seen as a single MIDI source so that input from any of them is routed to the same destinations. For instance, you might want an external MIDI keyboard, Launchpad and onscreen keyboard to be routed the same way.

To do this, add a MIDI AUv3 that passes MIDI through automatically. Streambyter and ShowMIDI are free lightweight AUv3 plugins that pass through any MIDI they receive with no detectable latency. Make the passthrough AUv3 the destination of your other MIDI controllers. Use the passthrough as the MIDI source as shown in the picture below.

Note that Streambyter can also be used as a powerful MIDI scripting, filtering and remapping utility in addition to being a handy MIDI monitor.

There are likely other MIDI AUv3 that also can be used.
[[File:VirtualMIDIbus.jpg|alt=A virtual MIDI bus set up in Loopy Pro’s mixer|none|thumb]]

== Synth Routing ==
See [[Synth Routing 2.0]] for ideas about setting up a routing switch for your synths.

Tech Note:MIDI Bindings

2026-05-06T19:29:09Z

Edwards: /* Binding Tap/Hold/Double-Tap to the same message */

This page covers helpful details of Loopy Pro's MIDI [https://loopypro.com/manual/#adding-bindings-manually bindings]. MIDI Bindings are what binds (maps) a MIDI Command with the actions triggered by the commands. MIDI Bindings are created when you use MIDI Learn and can be created manually.

== Bindings and Profiles ==
MIDI Bindings are stored in profiles that are listed in the Control Settings panel. Profiles are either local to the project or global. Local/project profiles are stored in the project itself. Global Profiles are stored in the Loopy Pro folder. MIDI bindings can be created manually or with MIDI Learn.

=== MIDI Learn and Profiles ===
When you MIDI Learn, you choose what profile the binding is stored in by using the popup available in the upper-left of the screen.
[[File:MIDI Learn Profile Popup.jpg|none|thumb]]

=== Editing and Viewing Profiles ===
Choose Control Settings to see a listing of the available profiles, both local and global.
[[File:Control Settings W Profiles.jpg|none|thumb]]
Tap on a profile so see the bindings that it contains. Bindings are grouped by the controller to which the actions are bound. Tap '''Clear''' to clear all of the bindings for the controler. Tap '''Transfer''' to copy or move the bindings to another controller. Tap '''Edit''' to enter list-edit mode where you can delete individual bindings. You can swipe left on a binding to delete it.
[[File:Profile Listing.jpg|none|thumb]]

== Additional Binding Topics ==

==== Binding Tap/Hold/Double-Tap to the same message ====
Loopy Pro allows tap, hold and double-tap of the same MIDI message (such as a MIDI CC or MIDI note) sent from a controller.

Normally, if you map tap and hold and/or double-tap to the same controller, the tap binding will be triggered immediately when the "on" message is received. This means that on a double-tap or hold, the tap binding will be triggered in addition to the double-tap or hold. This is unavoidable if you need immediate response to a single tap with no latency.

The ''Preempt Other Actions'' discussed further down the page is also relevant as it can allow a double-tap or hold action to be triggered on a tap.

===== Avoiding False Triggers - Defer Other Actions =====
There is an option that avoids triggering the tap action when double-taps or holds happen. In order to do this, Loopy Pro needs to wait a short while to be sure that a hold or double-tap isn't in process. Double-tap and hold bindings have an option ''Defer Other Actions'' that ensures that the tap will not be triggered if the interaction is a hold or double-tap. This can be turned on in the binding's trigger settings. When actions are deferred, Loopy Pro will try to compensate for the delay. For example when tap is set to record and hold is set to something else, the recording will end up being the same as if there was no delay when deferred action is on even though the on-screen animation is delayed. While the recording will be the same as if the action had not been deferred, playback of the first loop will start from a point that is slightly delayed (the point where Loopy recognized no hold was going to happen).

To access the ''Defer Other Actions'' option, tap on the Trigger section of the binding.
[[File:Triggerbinding.png|none|thumb]]
[[File:Deferactionsoption.png|none|thumb]]

'''Hold delay time''', If there is only a tap and a hold binding, the tap is deferred until the off message is received or until 500 milliseconds have passed. By making short taps, the delay is minimal. The 'on' is processed as soon as you release the trigger (such as footswitch or MIDI pad).

'''Double-tap delay time'''. If tap and double-tap are mapped to the same MIDI message, Loopy Pro waits 250 ms after the on message for a double-tap's second on message.

'''TOUCH NOTE:''' when using touch rather than MIDI, Loopy Pro always delays processing the tap if there are double-tap or long-press gestures defined. It essentially always uses ''Defer Other Actions'' when processing touches.

===== Strategies When Not Deferring Actions =====
You may sometimes need immediate response to the on action but want to avoid the consequences of the false trigger when a double-tap or hold occurs. To do this, you add an action as the start of your double-tap and hold bindings to undo the falsely started action.

Let's say you want tap to toggle record, double-tap to peel (undo) the last overdub and hold to stop. You need to undo/stop the falsely triggered record action (which Loopy will further undo when it realizes that the double-tap or hold was triggered). Your bindings would look something like this:

* Tap: record/stop selected clip
* Double-tap:
** stop record (selected clip) to stop the recording triggered by the tap
** peel (selected clip)
* Hold:
** stop record (selected clip) to stop the recording triggered by the tap
** Stop (Play) (selected clip)

'''See''': [[Templates:One Button Record, Peel, Stop]] for a downloadable example and demonstration.
==== Preempt Other Actions ====
[[File:Preempt other actions.jpg|thumb]]
Recording and play actions have an option called ''Preempt Other Actions'' in MIDI Bindings. By default, this option is on, but you often need to turn this off. ''Preempt other actions'' lets that binding kick in on a single tap even though it is set up as a double-tap or hold. While this behavior is sometimes desirable, it can cause double-taps and holds to kick in prematurely.
[[Category:Tips and Tricks]]
[[Category:Tech Note]]

Edward's Example Projects

2026-04-28T17:44:34Z

Edwards: /* Random Note Triggers */

__FORCETOC__
This page has links to projects that demonstrate useful techniques.

== Clip Sequencing Examples ==

====== Dial Sequencers 1.1 ======
[[File:Dial Sequencer Example Screenshot.jpg|alt=Screenshot of the dial sequencer example|none|thumb]]
This project demonstrates using a stepped dial to sequence clips into a song without need for the timeline. The project demonstrates two ways you might use a dial to sequence a song:

* An automated dial that plays the song from start to finish when triggered
* A 'stepper' dial that advances from one section to the next when triggered.

In your own projects, you can combine the techniques. For example, you might set up a dial to advance through some parts and manually advance for others.

The projects:
* [[Media:EXAMPLE Dial Sequencer iPad 1.1.lpproj.zip|Landscape (iPad) formatted project]]
* [[Media:EXAMPLE Dial Sequencer iPhone 1.1.lpproj.zip|Portrait (iPhone) formatted project]]

== Miscellany ==

==== SMC-Mixer Compatibility ====
This has moved to: [[SMC-Mixer]]

==== Random Triggers ====

===== Random Note Triggers =====
This project uses a Streambyter script to send random triggers. When any MIDI note is sent to Streambyter, Streambyter sends out a MIDI note in the range set up in the plugin. Add the script as a preset in Loopy Pro to use in your own projects.

'''Download''': [[Media:EXAMPLE Random Note Triggers.zip|EXAMPLE Random Note Triggers]]

{|style="border-style: none; border-width: 0px;"|-
|<YouTube width="450>q-WyxawQygo</youtube>
|}

===== Randomize CCs =====
The [[:File:EXAMPLE RANDOMIZE CC.zip|Randomize CC's Project]] contains a Streambyter instance whose script randomizes incoming CC values. Open the Streambyter script and follow the instructions to configure which CCs are randomized and what the randomization range is.

'''Download''': [[Media:EXAMPLE RANDOMIZE CC.zip|Randomize CC's Project]]

== Example Projects Listing==
This is a listing of projects categorized as example. Most are also linked to from other wiki pages.

<DynamicPageList>
category = Example
ordermethod = sortkey
order = ascending
</DynamicPageList>

See also: [[:Category:Example|Examples Category]]

== See also ==
[[Templates:Edward's Workbench|Edward’s Workbench]] always has a number of projects worth checking out.

[[Category:Community Contributions]]

Edward's Example Projects

2026-04-28T17:38:52Z

Edwards: /* Random Note Triggers */

__FORCETOC__
This page has links to projects that demonstrate useful techniques.

== Clip Sequencing Examples ==

====== Dial Sequencers 1.1 ======
[[File:Dial Sequencer Example Screenshot.jpg|alt=Screenshot of the dial sequencer example|none|thumb]]
This project demonstrates using a stepped dial to sequence clips into a song without need for the timeline. The project demonstrates two ways you might use a dial to sequence a song:

* An automated dial that plays the song from start to finish when triggered
* A 'stepper' dial that advances from one section to the next when triggered.

In your own projects, you can combine the techniques. For example, you might set up a dial to advance through some parts and manually advance for others.

The projects:
* [[Media:EXAMPLE Dial Sequencer iPad 1.1.lpproj.zip|Landscape (iPad) formatted project]]
* [[Media:EXAMPLE Dial Sequencer iPhone 1.1.lpproj.zip|Portrait (iPhone) formatted project]]

== Miscellany ==

==== SMC-Mixer Compatibility ====
This has moved to: [[SMC-Mixer]]

==== Random Triggers ====

===== Random Note Triggers =====
This project uses a Streambyter script to send random triggers. When any MIDI note is sent to Streambyter, Streambyter sends out a MIDI note in the range set up in the plugin. Add the script as a preset in Loopy Pro to use in your own projects.

'''Download''': [[Media:EXAMPLE Random Note Triggers.zip|EXAMPLE Random Note Triggers]]

{|style="border-style: none; border-width: 0px"|-
|<youtube>q-WyxawQygo</youtube>
|}

===== Randomize CCs =====
The [[:File:EXAMPLE RANDOMIZE CC.zip|Randomize CC's Project]] contains a Streambyter instance whose script randomizes incoming CC values. Open the Streambyter script and follow the instructions to configure which CCs are randomized and what the randomization range is.

'''Download''': [[Media:EXAMPLE RANDOMIZE CC.zip|Randomize CC's Project]]

== Example Projects Listing==
This is a listing of projects categorized as example. Most are also linked to from other wiki pages.

<DynamicPageList>
category = Example
ordermethod = sortkey
order = ascending
</DynamicPageList>

See also: [[:Category:Example|Examples Category]]

== See also ==
[[Templates:Edward's Workbench|Edward’s Workbench]] always has a number of projects worth checking out.

[[Category:Community Contributions]]

Edward's Example Projects

2026-04-28T17:38:23Z

Edwards: /* Random Note Triggers */

__FORCETOC__
This page has links to projects that demonstrate useful techniques.

== Clip Sequencing Examples ==

====== Dial Sequencers 1.1 ======
[[File:Dial Sequencer Example Screenshot.jpg|alt=Screenshot of the dial sequencer example|none|thumb]]
This project demonstrates using a stepped dial to sequence clips into a song without need for the timeline. The project demonstrates two ways you might use a dial to sequence a song:

* An automated dial that plays the song from start to finish when triggered
* A 'stepper' dial that advances from one section to the next when triggered.

In your own projects, you can combine the techniques. For example, you might set up a dial to advance through some parts and manually advance for others.

The projects:
* [[Media:EXAMPLE Dial Sequencer iPad 1.1.lpproj.zip|Landscape (iPad) formatted project]]
* [[Media:EXAMPLE Dial Sequencer iPhone 1.1.lpproj.zip|Portrait (iPhone) formatted project]]

== Miscellany ==

==== SMC-Mixer Compatibility ====
This has moved to: [[SMC-Mixer]]

==== Random Triggers ====

===== Random Note Triggers =====
This project uses a Streambyter script to send random triggers. When any MIDI note is sent to Streambyter, Streambyter sends out a MIDI note in the range set up in the plugin. Add the script as a preset in Loopy Pro to use in your own projects.

File: [[Media:EXAMPLE Random Note Triggers.zip|EXAMPLE Random Note Triggers]]

{|style="border-style: none; border-width: 0px"|-
|<youtube>q-WyxawQygo</youtube>
|}

===== Randomize CCs =====
The [[:File:EXAMPLE RANDOMIZE CC.zip|Randomize CC's Project]] contains a Streambyter instance whose script randomizes incoming CC values. Open the Streambyter script and follow the instructions to configure which CCs are randomized and what the randomization range is.

'''Download''': [[Media:EXAMPLE RANDOMIZE CC.zip|Randomize CC's Project]]

== Example Projects Listing==
This is a listing of projects categorized as example. Most are also linked to from other wiki pages.

<DynamicPageList>
category = Example
ordermethod = sortkey
order = ascending
</DynamicPageList>

See also: [[:Category:Example|Examples Category]]

== See also ==
[[Templates:Edward's Workbench|Edward’s Workbench]] always has a number of projects worth checking out.

[[Category:Community Contributions]]

Edward's Example Projects

2026-04-28T17:04:00Z

Edwards: /* See also */

__FORCETOC__
This page has links to projects that demonstrate useful techniques.

== Clip Sequencing Examples ==

====== Dial Sequencers 1.1 ======
[[File:Dial Sequencer Example Screenshot.jpg|alt=Screenshot of the dial sequencer example|none|thumb]]
This project demonstrates using a stepped dial to sequence clips into a song without need for the timeline. The project demonstrates two ways you might use a dial to sequence a song:

* An automated dial that plays the song from start to finish when triggered
* A 'stepper' dial that advances from one section to the next when triggered.

In your own projects, you can combine the techniques. For example, you might set up a dial to advance through some parts and manually advance for others.

The projects:
* [[Media:EXAMPLE Dial Sequencer iPad 1.1.lpproj.zip|Landscape (iPad) formatted project]]
* [[Media:EXAMPLE Dial Sequencer iPhone 1.1.lpproj.zip|Portrait (iPhone) formatted project]]

== Miscellany ==

==== SMC-Mixer Compatibility ====
This has moved to: [[SMC-Mixer]]

==== Random Triggers ====

===== Random Note Triggers =====
This project uses a Streambyter script to send random triggers. When any MIDI note is sent to Streambyter, Streambyter sends out a MIDI note in the range set up in the plugin. Add the script as a preset in Loopy Pro to use in your own projects.

[[Media:EXAMPLE Random Note Triggers.zip|EXAMPLE Random Note Triggers]]
{|style="border-style: none; border-width: 0px"|-
|
<youtube>q-WyxawQygo</youtube>
|}

===== Randomize CCs =====
The [[:File:EXAMPLE RANDOMIZE CC.zip|Randomize CC's Project]] contains a Streambyter instance whose script randomizes incoming CC values. Open the Streambyter script and follow the instructions to configure which CCs are randomized and what the randomization range is.

'''Download''': [[Media:EXAMPLE RANDOMIZE CC.zip|Randomize CC's Project]]

== Example Projects Listing==
This is a listing of projects categorized as example. Most are also linked to from other wiki pages.

<DynamicPageList>
category = Example
ordermethod = sortkey
order = ascending
</DynamicPageList>

See also: [[:Category:Example|Examples Category]]

== See also ==
[[Templates:Edward's Workbench|Edward’s Workbench]] always has a number of projects worth checking out.

[[Category:Community Contributions]]

File:Loopypro example pitchbend.zip

2026-04-27T21:44:58Z

Edwards:

Loopy Pro 1.x project demonstrating how to create a pitchbend slider.

This project is outdated and no longer needed.

This file can be deleted.

File:Loopypro example pitchbend.zip

2026-04-27T21:43:53Z

Edwards:

Loopy Pro 1.x project demonstrating how to create a pitchbend slider.

This project is outdated and no longer needed.

Sending Pitchbend

2026-04-27T21:42:32Z

Edwards: update for Loopy Pro 2.0 now that Send MIDI Message can send pitch bend

= Self-Centering Pitch Bend Widget =

* Add a Slider or Knob widget to your layout.
* Add ''Send MIDI Message'' as the widget's value change action.
* Set the message type to Pitch Bend.
* Add ''Trigger Widget'' as the Release action.
* Choose the widget itself as the target
* Set the Trigger Widget's Action to Value Change
* Set the Trigger Widget's Adjustment to Assign Value
* Set the adjustment value to 50%.

The slider or knob will now return to 50% (no pitch bend) when the widget is released.

[[:Category:Advanced Features]]
[[Category:Advanced Features]]

Sample Projects 2.0

2026-04-08T23:41:08Z

Edwards: /* Verse-Chorus Looper */ more details

[[Category:Getting Started]]

Loopy Pro 2.0 includes a number of very helpful sample projects that will help you get up to speed with Loopy Pro. Access them using the ''Sample Projects'' tab in the Help menu or from the project browser. Even if you are an experienced user, there will be something for you. The '''Main Projects''' provide some helpful starting points and make use of some advanced features. The '''Tutorial Projects''' are small projects that demonstrate essential Loopy Pro concepts and provide some useful widgets you may want to use in your own projects.

'''See also''': The [[MIDI Basics]] page has resources to help you get up to speed with Loopy Pro 2.0's new MIDI features.

== Main Projects ==

=== Demo ===
Introductory demo project (by Dub Fx). A fun phase-locked looper project from [https://dubfx.com Dub FX].
[[File:Demo Project Dub FX.jpg|alt=Demo project by Dub FX|none|thumb]]
'''Key features''': X-Y Pad controlling a Low-Pass filter. Clip slicer. Reverb on a send/bus, controlled by a slider and throw button. Four one-shots and five loops with which to experiment.

=== Simple Scenes Example 1 ===
A simple example of scenes using Play Groups. This example uses mutually-exclusive, ''all loops play together'' play groups to create scenes. A scene can be triggered by pressing its button or by re-triggering any loop in a scene. Features two independent loops that can play at any time without interfering with the play groups.
[[File:Simple Scenes Example 1.jpg|alt=Simple Scenes 1 sample project|none|thumb]]

'''Key features''': all loops play together play group option, mutually exclusive play groups.

See the project's tutorial widgets for more details.

=== Simple Scenes Example 2 ===
A simple example of scenes using Solo actions. This scene looks identical to ''Simple Scenes Example 1'' but it behaves differently. Unlike Example 1, the groups are set up so that the clips play independently rather than play/stop together. The groups are also not mutually exclusive as they are in Example 1.

You can trigger a scene with its button, but the clips can play independently. So, you can turn clips off in a scene without stopping the scene, and you can trigger clips from other scenes. If you have turned off any of a scene's clips while the scene was playing, re-triggering the scene will trigger just the clips that were playing.

See the project's tutorial widgets for more details.

=== 5x5 Scenes ===
A 5x5 grid with scene buttons and a row of independent clips. Each scene row is a mutually exclusive play group that is set to let the clips play independently. You can turn clips on and off in a scene. Retriggering a scene plays just the clips that were last playing in the scene. The purple clips at the bottom are unaffected by scene playback. The Scene buttons use the Solo/Un-Solo action targeted that the row's play group.
[[File:5X5 Scenes.jpg|alt=Screenshot of the 5x5 scenes sample project|none|thumb]]

=== LP 707 ===
Inkie's RC-505-style template with extended functionality. This is a five-track looper reminiscent of the RC-505 with integrated effects (via 3rd Party AUv3). The project has an on-screen tour. Inkie has created a video tutorial that explains it all.

The template makes use of some 3rd-party plugins. You can substitute your own effects if you wish.

* BLEASS [https://apps.apple.com/us/app/bleass-samplewiz-2/id1501504776 Sample Wiz 2]
* Sugar Bytes' [https://apps.apple.com/us/app/turnado/id614418823 Turnado]
* Caelum Audio's [https://apps.apple.com/us/app/flux-pro/id1611411940 Flux Pro]
[[File:Inkie's LP 707 Template.jpg|alt=Screenshot of Inkie's LP 707 Sample Project|none|thumb|450x450px]]
{|style="border-style: none; border-width: 0px"
|-
|<YouTube width="450">cUkTYg4OAQM</youtube>
|}
=== Verse-Chorus Looper ===
Get the Dec 2025 updated version [[Templates:Edward's Workbench#Verse-Chorus Looper Improved (Sept 2025)|here]].

A 4-pedal Verse-Chorus looper, inspired by the VL3. This looper features mutually exclusive verse and chorus loops and an independent groove clip. This project makes use of follow actions (more on that below). This is a good starter project for building serial loopers. The project also features a fun trick for using a two-pedal combination to clear the project.

'''Key features''': When a clip is playing, queuing playback or record of the other clip lets the current clip complete its cycle. If a groove clip has been recorded, verse and chorus recording is quantized to multiples of the groove length. Retrospective recording button.

Designed as a pedal looper with 4-switch operation. Pedal 1 - verse. Pedal 2 - chorus. Pedal 3 - groove. Pedal 4 - mode switch.

In record mode:

* Pedal tap toggles between play and overdub when a clip is playing. Plays the clip if it is stopped.
* Double-tap stops the clip at the end of its cycle)
* Hold clears the clip

In play mode:

* Pedal tap toggles between play and stop. Plays the clip if it is stopped.
* Double-tap immediate overdub switch.
* Hold clears the clip

The project is pre-configured with the MIDI CCs used by the iRig Blueboard or the M-Vave Chocolate in Manufacturer Control mode: MIDI CC's 20-23 for buttons 1 through 4.
[[File:Verse-Chorus Looper Screenshot.jpg|alt=A screenshot of the Verse-Chorus Looper sample project|none|thumb]]'''To add more mutually exclusive clips,''' use the following steps so that new clips will have the follow actions needed for well-behaved serial looping.

* Copy the verse clip
* Paste the copied clip
* Add the clip to play group 1 (the only play group)

==== How It Works ====
There are a few settings worth knowing about if you want to get the same behavior in your own projects. Because we want to support verses and choruses that are different lengths, phase-lock is turned off. For slightly complicated reasons, we use Master for the play/stop quantization setting rather than Loop. When the verse and chorus loops play, they set the master cycle length to their length. The result is that they behave as if loop play quantization is on.

'''Follow Actions'''. The verse clip has play follow actions: Copy Master Length from This Clip and Phase Align Clock. On Clear Clip, the master cycle length is set to the groove clip length. The chorus clip has Begin Initial Record follow actions: Copy Master Length from Groove (which ensures that the chorus is a multiple of the groove clip), Phase Align Clock. Its play follow actions are the same as the verse clip's: Copy Master Length from This Clip and Phase Align Clock.

'''Copy Master/Phase Align Clock'''. These two actions are used together to ensure that the clips and the master clock are the same length and lined up. This makes it possible to use actions like quantized retrospective recording that require alignment with the master clock and ensures that play and stop start and stop in synch with the master clock.

The project assumes that the groove clip is recorded first and the verse is recorded next. With slight modifications of the project, it would be possible to record the clips in any order.

==== Video Demonstration ====
{|style="border-style: none; border-width: 0px"
|-
|<YouTube width="450">3WaXknJB4fA</YouTube>
|}

=== MIDI Showcase ===
A showcase of Loopy Pro 2.0's new MIDI capabilities. This project introduces some of Loopy Pro 2.0's new MIDI system.
[[File:MIDI Showcase screenshot.jpg|alt=Screenshot of the MIDI Showcase sample project|none|thumb]]
'''Key features''':

* MIDI Looping
* Using MIDI to polyphonically play audio one-shots and loops
* Playing/recording MIDI from widgets with Send MIDI Actions
* Using MIDI loops to record and play back effect parameter automation
* Loopy's new onscreen keyboard widget

=== Simple 4 Track Looper ===
Adam Searan - A Chewie Monsta-inspired simple 4-track looper. An easy-to-use 4-track looper with phase-locked loops.
[[File:Searan Simple 4 Track Screenshot.jpg|alt=Screenshot of the Simple 4 Track Looper|none|thumb]]Adam has posted a few helpful videos to go with the project

* Adam's [https://www.youtube.com/watch?v=T_dn0wA_SK0 YouTube template walkthrough/explainer].
* [https://www.youtube.com/watch?v=uVUKSQRTcnM Performance example and overview]. Skip straight to the performance by clicking [https://www.youtube.com/watch?v=uVUKSQRTcnM&t=277 here]

=== Inby's 2.0 Template ===
From [https://www.youtube.com/@inbar.heyman Inby]. This is a great template for exploring some of Loopy Pro 2.0's new features and some great features you may want to incorporate into your own projects. Check out the [https://www.youtube.com/watch?v=_ztu8iE6Ps8 YouTube guide] for this template.
[[File:Inby's Template.jpg|alt=Inby's Loopy Pro 2.0 Template|none|thumb]]

== Tutorials ==
These projects explain demonstrate key Loopy Pro concepts. A little bit of time spent with these lessons will increase your productivity immensely.

=== Master Clock Length ===
The Master Clock Length is often used to start and stop recording. Explore this project to experiment with master clock.

'''See also''': The [[Simple Looper Tutorial Projects#Simple Looper 01 Two Loops|Simple Looper tutorial]] shows the master cycle in action and shows how you might use it in real life.

=== Phase-Locked vs Free Loops ===
A demonstration of Phase Locked and Free clips. This is one of the key concepts in Loop Pro. Phase-locked loops have an always moving playhead even when the loop isn't playing, making it easy to drop in and out of loops while staying in sync. Free loops always start from the beginning when you start them playing -- perfect when working with loops and song sections of different lengths.

'''See also''': [[Phase-Lock and Free Loops]]

=== Record Count-in and Out ===
Record count-in and count-out settings determine the length of clips and when recording starts. Loopy is flexible in how you can set it up. Recording can be tied to the master cycle or use a fixed custom length. Clips can automatically record a set length or record until you trigger the stop.

'''Other key features''': The project makes use of the new Assign Settings action that lets you change the settings used by a clip, a color or all clips.

=== Simple MIDI Example - Loopy Pro as polyphonic sampler ===
This project demonstrates how Loopy Pro can be a polyphonic, MPE-capable sampler by targeting clips as MIDI targets. In this project, an audio clip is set as a destination of a MIDI color in the mixer. Sending MIDI to the color or playing a MIDI clip plays the audio clip polyphonically.

=== Simple MIDI Example 2 ===
A simple example of a MIDI clip driving an AUv3 instrument.

=== MIDI Switcher Example ===
This project demonstrates how to use the ''Enable/Disable MIDI Destination'' action which is an essential tool for realtime MIDI routing -- allowing you to switch your MIDI controller targets on-the-fly.
[[File:Midi switcher sample project.png|alt=Midi switcher sample project screenshot|none|thumb]]

=== MIDI Clip Automation Example ===
This project has an XY-Pad set up to control the cutoff and Q parameters of a low-pass filter. The XY-Pad sends MIDI messages to the Blue MIDI color to be recorddd. When the blue clip plays, it re-triggers the XY-Pad with the recorded automation.
[[File:MIDI Clip Automation Example.jpg|alt=MIDI Automation Example layout|none|thumb]]

==== How it works ====
This project demonstrates the best-practices for setting up MIDI CC automation recording and playback. The main elements are:

* '''A widget:''' A widget (the XY pad) that performs actions (in this case adjust a filter) and sends MIDI messages to a MIDI Color. In most cases, MIDI Through should be turned off in the widget's Send MIDI action.
* '''Clip(s)''': A MIDI clip or clips whose color matches the widget's Send MIDI action. The automation will be recorded in these clips.
* '''Bindings''': MIDI bindings in a project profile that mirror the widget's bindings. Typically, the MIDI bindings will retrigger the widget that sent the automation MIDI.

==== Element Setup ====
{|
![[File:XY Pad Actions Automation Example.jpg|alt=The actions for the XY-Pad|thumb|299x299px]]
![[File:Send MIDI Message.jpg|alt=Send MIDI Message action setup|thumb|256x256px]]
![[File:Automation Example Control Settings.jpg|alt=Binding setup for the automation example|thumb|316x316px]]
!
|-
|XY-Pad Action Setup
|Send MIDI Message setting
|The MIDI Bindings from the Blue color back to the widget
|
|}
'''Send MIDI Message'''. The widget's Send MIDI Message action should generally have the ''Monitor Through'' option turned off to prevent MIDI feedback and redundant MIDI events. The ''Takeover'' option should generally be turned on. It allows you to use the widget during playback and have the interaction take over from the automation. Turning ''Takeover'' off can be fun, too -- allowing you to fight with the automation for stuttering effects.

'''The MIDI Bindings.''' The MIDI bindings can be set up to retrigger the widget that sent the MIDI or to perform the same actions performed by the widget. Generally, the first method is simplest.

==== MIDI Automation Setup Tutorial ====

{|style="border-style: none; border-width: 0px"
|-
|
<youtube>lAT8qcD0GBE</youtube>
|}

=== CircleSongs Tutorial ===
Jonas Viatte - A vocal live-looping tutorial

== Others ==

=== KAVES (COTCD) ===

=== RC-505-Esque ===

=== SHAMANIC's Live Production Template ===

=== Simpler LoopMachine ===

[[Category:Basics]]

Tech Note:Follow Actions

2026-04-08T23:08:45Z

Edwards:

This article discusses details of follow actions not covered in the Loopy Pro [https://loopypro.com/manual/#follow-actions manual].

== Follow Action Order ==

=== Record Then Play ===
When and new clip is recorded with ''After Recording'' set to ''Play'', the follow action order is:

When recording starts, the follow action order is:

* Begin Record
* Begin Initial Record

When recording ends, the triggered actions, in order, are:

* Finish Record
* Finish Initial Record
* Play Clip

=== Record Then Overdub ===
When and new clip is recorded with ''After Recording'' set to ''Overdub'', the follow action order is:
When recording starts:

* Begin Record
* Begin Initial Record

When recording ends, loop playback and overdub start:

* Finish Initial Record
* Play Clip
* Begin Record
* Begin Overdub

When overdub ends, the clip is already playing. The triggered follow actions are:

* Finish Record
* Finish Overdub

=== Recording a clip when another clip is recording ===
If simultaneous recording is off, recording a clip will end the recording of any clip that is recording. The follow action order may be a little surprising. Let's say Clip A is recording and you start recording Clip B. The Begin Record/Begin Initial Record follow actions of Clip B are triggered before Clip A's Finish Record/Finish Initial Record.

If Clip A's finish record follow actions could possibly conflict with Clip B's begin record follow actions, you should slightly delay the actions so that they happen after the clip A's actions.

Tech Note:Follow Actions

2026-04-08T19:34:46Z

Edwards: create

This article discusses details of follow actions not covered in the Loopy Pro [https://loopypro.com/manual/#follow-actions manual].

Sample Projects 2.0

2026-04-07T21:54:42Z

Edwards: /* Verse-Chorus Looper */

[[Category:Getting Started]]

Loopy Pro 2.0 includes a number of very helpful sample projects that will help you get up to speed with Loopy Pro. Access them using the ''Sample Projects'' tab in the Help menu or from the project browser. Even if you are an experienced user, there will be something for you. The '''Main Projects''' provide some helpful starting points and make use of some advanced features. The '''Tutorial Projects''' are small projects that demonstrate essential Loopy Pro concepts and provide some useful widgets you may want to use in your own projects.

'''See also''': The [[MIDI Basics]] page has resources to help you get up to speed with Loopy Pro 2.0's new MIDI features.

== Main Projects ==

=== Demo ===
Introductory demo project (by Dub Fx). A fun phase-locked looper project from [https://dubfx.com Dub FX].
[[File:Demo Project Dub FX.jpg|alt=Demo project by Dub FX|none|thumb]]
'''Key features''': X-Y Pad controlling a Low-Pass filter. Clip slicer. Reverb on a send/bus, controlled by a slider and throw button. Four one-shots and five loops with which to experiment.

=== Simple Scenes Example 1 ===
A simple example of scenes using Play Groups. This example uses mutually-exclusive, ''all loops play together'' play groups to create scenes. A scene can be triggered by pressing its button or by re-triggering any loop in a scene. Features two independent loops that can play at any time without interfering with the play groups.
[[File:Simple Scenes Example 1.jpg|alt=Simple Scenes 1 sample project|none|thumb]]

'''Key features''': all loops play together play group option, mutually exclusive play groups.

See the project's tutorial widgets for more details.

=== Simple Scenes Example 2 ===
A simple example of scenes using Solo actions. This scene looks identical to ''Simple Scenes Example 1'' but it behaves differently. Unlike Example 1, the groups are set up so that the clips play independently rather than play/stop together. The groups are also not mutually exclusive as they are in Example 1.

You can trigger a scene with its button, but the clips can play independently. So, you can turn clips off in a scene without stopping the scene, and you can trigger clips from other scenes. If you have turned off any of a scene's clips while the scene was playing, re-triggering the scene will trigger just the clips that were playing.

See the project's tutorial widgets for more details.

=== 5x5 Scenes ===
A 5x5 grid with scene buttons and a row of independent clips. Each scene row is a mutually exclusive play group that is set to let the clips play independently. You can turn clips on and off in a scene. Retriggering a scene plays just the clips that were last playing in the scene. The purple clips at the bottom are unaffected by scene playback. The Scene buttons use the Solo/Un-Solo action targeted that the row's play group.
[[File:5X5 Scenes.jpg|alt=Screenshot of the 5x5 scenes sample project|none|thumb]]

=== LP 707 ===
Inkie's RC-505-style template with extended functionality. This is a five-track looper reminiscent of the RC-505 with integrated effects (via 3rd Party AUv3). The project has an on-screen tour. Inkie has created a video tutorial that explains it all.

The template makes use of some 3rd-party plugins. You can substitute your own effects if you wish.

* BLEASS [https://apps.apple.com/us/app/bleass-samplewiz-2/id1501504776 Sample Wiz 2]
* Sugar Bytes' [https://apps.apple.com/us/app/turnado/id614418823 Turnado]
* Caelum Audio's [https://apps.apple.com/us/app/flux-pro/id1611411940 Flux Pro]
[[File:Inkie's LP 707 Template.jpg|alt=Screenshot of Inkie's LP 707 Sample Project|none|thumb|450x450px]]
{|style="border-style: none; border-width: 0px"
|-
|<YouTube width="450">cUkTYg4OAQM</youtube>
|}
=== Verse-Chorus Looper ===
Get the Dec 2025 updated version [[Templates:Edward's Workbench#Verse-Chorus Looper Improved (Sept 2025)|here]].

A 4-pedal Verse-Chorus looper, inspired by the VL3. This looper features mutually exclusive verse and chorus loops and an independent groove clip. This project makes use of follow actions (more on that below). This is a good starter project for building serial loopers. The project also features a fun trick for using a two-pedal combination to clear the project.

'''Key features''': When a clip is playing, queuing playback or record of the other clip lets the current clip complete its cycle. If a groove clip has been recorded, verse and chorus recording is quantized to multiples of the groove length. Retrospective recording button.

Designed as a pedal looper with 4-switch operation. Pedal 1 - verse. Pedal 2 - chorus. Pedal 3 - groove. Pedal 4 - mode switch.

In record mode:

* Pedal tap toggles between play and overdub when a clip is playing. Plays the clip if it is stopped.
* Double-tap stops the clip at the end of its cycle)
* Hold clears the clip

In play mode:

* Pedal tap toggles between play and stop. Plays the clip if it is stopped.
* Double-tap immediate overdub switch.
* Hold clears the clip

The project is pre-configured with the MIDI CCs used by the iRig Blueboard or the M-Vave Chocolate in Manufacturer Control mode: MIDI CC's 20-23 for buttons 1 through 4.
[[File:Verse-Chorus Looper Screenshot.jpg|alt=A screenshot of the Verse-Chorus Looper sample project|none|thumb]]
'''How it works'''. The clips make use of follow actions that change the master cycle length and realign the clock when a part starts playing even if the parts are different lengths.

'''To add more mutually exclusive clips,''' use the following steps so that new clips will have the follow actions needed for well-behaved serial looping.

* Copy the verse clip
* Paste the copied clip
* Add the clip to play group 1 (the only play group)

{|style="border-style: none; border-width: 0px"
|-
|<YouTube width="450">3WaXknJB4fA</YouTube>
|}

=== MIDI Showcase ===
A showcase of Loopy Pro 2.0's new MIDI capabilities. This project introduces some of Loopy Pro 2.0's new MIDI system.
[[File:MIDI Showcase screenshot.jpg|alt=Screenshot of the MIDI Showcase sample project|none|thumb]]
'''Key features''':

* MIDI Looping
* Using MIDI to polyphonically play audio one-shots and loops
* Playing/recording MIDI from widgets with Send MIDI Actions
* Using MIDI loops to record and play back effect parameter automation
* Loopy's new onscreen keyboard widget

=== Simple 4 Track Looper ===
Adam Searan - A Chewie Monsta-inspired simple 4-track looper. An easy-to-use 4-track looper with phase-locked loops.
[[File:Searan Simple 4 Track Screenshot.jpg|alt=Screenshot of the Simple 4 Track Looper|none|thumb]]Adam has posted a few helpful videos to go with the project

* Adam's [https://www.youtube.com/watch?v=T_dn0wA_SK0 YouTube template walkthrough/explainer].
* [https://www.youtube.com/watch?v=uVUKSQRTcnM Performance example and overview]. Skip straight to the performance by clicking [https://www.youtube.com/watch?v=uVUKSQRTcnM&t=277 here]

=== Inby's 2.0 Template ===
From [https://www.youtube.com/@inbar.heyman Inby]. This is a great template for exploring some of Loopy Pro 2.0's new features and some great features you may want to incorporate into your own projects. Check out the [https://www.youtube.com/watch?v=_ztu8iE6Ps8 YouTube guide] for this template.
[[File:Inby's Template.jpg|alt=Inby's Loopy Pro 2.0 Template|none|thumb]]

== Tutorials ==
These projects explain demonstrate key Loopy Pro concepts. A little bit of time spent with these lessons will increase your productivity immensely.

=== Master Clock Length ===
The Master Clock Length is often used to start and stop recording. Explore this project to experiment with master clock.

'''See also''': The [[Simple Looper Tutorial Projects#Simple Looper 01 Two Loops|Simple Looper tutorial]] shows the master cycle in action and shows how you might use it in real life.

=== Phase-Locked vs Free Loops ===
A demonstration of Phase Locked and Free clips. This is one of the key concepts in Loop Pro. Phase-locked loops have an always moving playhead even when the loop isn't playing, making it easy to drop in and out of loops while staying in sync. Free loops always start from the beginning when you start them playing -- perfect when working with loops and song sections of different lengths.

'''See also''': [[Phase-Lock and Free Loops]]

=== Record Count-in and Out ===
Record count-in and count-out settings determine the length of clips and when recording starts. Loopy is flexible in how you can set it up. Recording can be tied to the master cycle or use a fixed custom length. Clips can automatically record a set length or record until you trigger the stop.

'''Other key features''': The project makes use of the new Assign Settings action that lets you change the settings used by a clip, a color or all clips.

=== Simple MIDI Example - Loopy Pro as polyphonic sampler ===
This project demonstrates how Loopy Pro can be a polyphonic, MPE-capable sampler by targeting clips as MIDI targets. In this project, an audio clip is set as a destination of a MIDI color in the mixer. Sending MIDI to the color or playing a MIDI clip plays the audio clip polyphonically.

=== Simple MIDI Example 2 ===
A simple example of a MIDI clip driving an AUv3 instrument.

=== MIDI Switcher Example ===
This project demonstrates how to use the ''Enable/Disable MIDI Destination'' action which is an essential tool for realtime MIDI routing -- allowing you to switch your MIDI controller targets on-the-fly.
[[File:Midi switcher sample project.png|alt=Midi switcher sample project screenshot|none|thumb]]

=== MIDI Clip Automation Example ===
This project has an XY-Pad set up to control the cutoff and Q parameters of a low-pass filter. The XY-Pad sends MIDI messages to the Blue MIDI color to be recorddd. When the blue clip plays, it re-triggers the XY-Pad with the recorded automation.
[[File:MIDI Clip Automation Example.jpg|alt=MIDI Automation Example layout|none|thumb]]

==== How it works ====
This project demonstrates the best-practices for setting up MIDI CC automation recording and playback. The main elements are:

* '''A widget:''' A widget (the XY pad) that performs actions (in this case adjust a filter) and sends MIDI messages to a MIDI Color. In most cases, MIDI Through should be turned off in the widget's Send MIDI action.
* '''Clip(s)''': A MIDI clip or clips whose color matches the widget's Send MIDI action. The automation will be recorded in these clips.
* '''Bindings''': MIDI bindings in a project profile that mirror the widget's bindings. Typically, the MIDI bindings will retrigger the widget that sent the automation MIDI.

==== Element Setup ====
{|
![[File:XY Pad Actions Automation Example.jpg|alt=The actions for the XY-Pad|thumb|299x299px]]
![[File:Send MIDI Message.jpg|alt=Send MIDI Message action setup|thumb|256x256px]]
![[File:Automation Example Control Settings.jpg|alt=Binding setup for the automation example|thumb|316x316px]]
!
|-
|XY-Pad Action Setup
|Send MIDI Message setting
|The MIDI Bindings from the Blue color back to the widget
|
|}
'''Send MIDI Message'''. The widget's Send MIDI Message action should generally have the ''Monitor Through'' option turned off to prevent MIDI feedback and redundant MIDI events. The ''Takeover'' option should generally be turned on. It allows you to use the widget during playback and have the interaction take over from the automation. Turning ''Takeover'' off can be fun, too -- allowing you to fight with the automation for stuttering effects.

'''The MIDI Bindings.''' The MIDI bindings can be set up to retrigger the widget that sent the MIDI or to perform the same actions performed by the widget. Generally, the first method is simplest.

==== MIDI Automation Setup Tutorial ====

{|style="border-style: none; border-width: 0px"
|-
|
<youtube>lAT8qcD0GBE</youtube>
|}

=== CircleSongs Tutorial ===
Jonas Viatte - A vocal live-looping tutorial

== Others ==

=== KAVES (COTCD) ===

=== RC-505-Esque ===

=== SHAMANIC's Live Production Template ===

=== Simpler LoopMachine ===

[[Category:Basics]]

Sample Projects 2.0

2026-04-07T21:52:21Z

Edwards: /* Verse-Chorus Looper */ link to updated vc looper

[[Category:Getting Started]]

Loopy Pro 2.0 includes a number of very helpful sample projects that will help you get up to speed with Loopy Pro. Access them using the ''Sample Projects'' tab in the Help menu or from the project browser. Even if you are an experienced user, there will be something for you. The '''Main Projects''' provide some helpful starting points and make use of some advanced features. The '''Tutorial Projects''' are small projects that demonstrate essential Loopy Pro concepts and provide some useful widgets you may want to use in your own projects.

'''See also''': The [[MIDI Basics]] page has resources to help you get up to speed with Loopy Pro 2.0's new MIDI features.

== Main Projects ==

=== Demo ===
Introductory demo project (by Dub Fx). A fun phase-locked looper project from [https://dubfx.com Dub FX].
[[File:Demo Project Dub FX.jpg|alt=Demo project by Dub FX|none|thumb]]
'''Key features''': X-Y Pad controlling a Low-Pass filter. Clip slicer. Reverb on a send/bus, controlled by a slider and throw button. Four one-shots and five loops with which to experiment.

=== Simple Scenes Example 1 ===
A simple example of scenes using Play Groups. This example uses mutually-exclusive, ''all loops play together'' play groups to create scenes. A scene can be triggered by pressing its button or by re-triggering any loop in a scene. Features two independent loops that can play at any time without interfering with the play groups.
[[File:Simple Scenes Example 1.jpg|alt=Simple Scenes 1 sample project|none|thumb]]

'''Key features''': all loops play together play group option, mutually exclusive play groups.

See the project's tutorial widgets for more details.

=== Simple Scenes Example 2 ===
A simple example of scenes using Solo actions. This scene looks identical to ''Simple Scenes Example 1'' but it behaves differently. Unlike Example 1, the groups are set up so that the clips play independently rather than play/stop together. The groups are also not mutually exclusive as they are in Example 1.

You can trigger a scene with its button, but the clips can play independently. So, you can turn clips off in a scene without stopping the scene, and you can trigger clips from other scenes. If you have turned off any of a scene's clips while the scene was playing, re-triggering the scene will trigger just the clips that were playing.

See the project's tutorial widgets for more details.

=== 5x5 Scenes ===
A 5x5 grid with scene buttons and a row of independent clips. Each scene row is a mutually exclusive play group that is set to let the clips play independently. You can turn clips on and off in a scene. Retriggering a scene plays just the clips that were last playing in the scene. The purple clips at the bottom are unaffected by scene playback. The Scene buttons use the Solo/Un-Solo action targeted that the row's play group.
[[File:5X5 Scenes.jpg|alt=Screenshot of the 5x5 scenes sample project|none|thumb]]

=== LP 707 ===
Inkie's RC-505-style template with extended functionality. This is a five-track looper reminiscent of the RC-505 with integrated effects (via 3rd Party AUv3). The project has an on-screen tour. Inkie has created a video tutorial that explains it all.

The template makes use of some 3rd-party plugins. You can substitute your own effects if you wish.

* BLEASS [https://apps.apple.com/us/app/bleass-samplewiz-2/id1501504776 Sample Wiz 2]
* Sugar Bytes' [https://apps.apple.com/us/app/turnado/id614418823 Turnado]
* Caelum Audio's [https://apps.apple.com/us/app/flux-pro/id1611411940 Flux Pro]
[[File:Inkie's LP 707 Template.jpg|alt=Screenshot of Inkie's LP 707 Sample Project|none|thumb|450x450px]]
{|style="border-style: none; border-width: 0px"
|-
|<YouTube width="450">cUkTYg4OAQM</youtube>
|}
=== Verse-Chorus Looper ===
Get the Dec 2025 updated version [[Templates:Edward's Workbench#Verse-Chorus Looper Improved (Sept 2025)|here]].

A 4-pedal Verse-Chorus looper, inspired by the VL3. This looper features mutually exclusive verse and chorus loops and an independent groove clip. This project makes use of follow actions (more on that below). This is a good starter project for building serial loopers. The project also features a fun trick for using a two-pedal combination to clear the project.

'''Key features''': When a clip is playing, queuing playback or record of the other clip lets the current clip complete its cycle. If a groove clip has been recorded, verse and chorus recording is quantized to multiples of the groove length. Retrospective recording button.

Designed as a pedal looper with 4-switch operation. Pedal 1 - verse. Pedal 2 - chorus. Pedal 3 - groove. Pedal 4 - mode switch.

In record mode:

* Pedal tap toggles between play and overdub when a clip is playing. Plays the clip if it is stopped.
* Double-tap stops the clip at the end of its cycle)
* Hold clears the clip

In play mode:

* Pedal tap toggles between play and stop. Plays the clip if it is stopped.
* Double-tap immediate overdub switch.
* Hold clears the clip

The project is pre-configured with the MIDI CCs used by the iRig Blueboard or the M-Vave Chocolate in Manufacturer Control mode: MIDI CC's 20-23 for buttons 1 through 4.
[[File:Verse-Chorus Looper Screenshot.jpg|alt=A screenshot of the Verse-Chorus Looper sample project|none|thumb]]
'''How it works'''. The clips make use of follow actions that change the master cycle length and realign the clock when a part starts playing even if the parts are different lengths.

'''To add more mutually exclusive clips,''' use the following steps so that new clips will have the follow actions needed for well-behaved serial looping.

* Copy the verse clip
* Paste the copied clip
* Add the clip to play group 1 (the only play group)

{|style="border-style: none; border-width: 0px"
|-
<YouTube width="450">3WaXknJB4fA</YouTube>
|}

=== MIDI Showcase ===
A showcase of Loopy Pro 2.0's new MIDI capabilities. This project introduces some of Loopy Pro 2.0's new MIDI system.
[[File:MIDI Showcase screenshot.jpg|alt=Screenshot of the MIDI Showcase sample project|none|thumb]]
'''Key features''':

* MIDI Looping
* Using MIDI to polyphonically play audio one-shots and loops
* Playing/recording MIDI from widgets with Send MIDI Actions
* Using MIDI loops to record and play back effect parameter automation
* Loopy's new onscreen keyboard widget

=== Simple 4 Track Looper ===
Adam Searan - A Chewie Monsta-inspired simple 4-track looper. An easy-to-use 4-track looper with phase-locked loops.
[[File:Searan Simple 4 Track Screenshot.jpg|alt=Screenshot of the Simple 4 Track Looper|none|thumb]]Adam has posted a few helpful videos to go with the project

* Adam's [https://www.youtube.com/watch?v=T_dn0wA_SK0 YouTube template walkthrough/explainer].
* [https://www.youtube.com/watch?v=uVUKSQRTcnM Performance example and overview]. Skip straight to the performance by clicking [https://www.youtube.com/watch?v=uVUKSQRTcnM&t=277 here]

=== Inby's 2.0 Template ===
From [https://www.youtube.com/@inbar.heyman Inby]. This is a great template for exploring some of Loopy Pro 2.0's new features and some great features you may want to incorporate into your own projects. Check out the [https://www.youtube.com/watch?v=_ztu8iE6Ps8 YouTube guide] for this template.
[[File:Inby's Template.jpg|alt=Inby's Loopy Pro 2.0 Template|none|thumb]]

== Tutorials ==
These projects explain demonstrate key Loopy Pro concepts. A little bit of time spent with these lessons will increase your productivity immensely.

=== Master Clock Length ===
The Master Clock Length is often used to start and stop recording. Explore this project to experiment with master clock.

'''See also''': The [[Simple Looper Tutorial Projects#Simple Looper 01 Two Loops|Simple Looper tutorial]] shows the master cycle in action and shows how you might use it in real life.

=== Phase-Locked vs Free Loops ===
A demonstration of Phase Locked and Free clips. This is one of the key concepts in Loop Pro. Phase-locked loops have an always moving playhead even when the loop isn't playing, making it easy to drop in and out of loops while staying in sync. Free loops always start from the beginning when you start them playing -- perfect when working with loops and song sections of different lengths.

'''See also''': [[Phase-Lock and Free Loops]]

=== Record Count-in and Out ===
Record count-in and count-out settings determine the length of clips and when recording starts. Loopy is flexible in how you can set it up. Recording can be tied to the master cycle or use a fixed custom length. Clips can automatically record a set length or record until you trigger the stop.

'''Other key features''': The project makes use of the new Assign Settings action that lets you change the settings used by a clip, a color or all clips.

=== Simple MIDI Example - Loopy Pro as polyphonic sampler ===
This project demonstrates how Loopy Pro can be a polyphonic, MPE-capable sampler by targeting clips as MIDI targets. In this project, an audio clip is set as a destination of a MIDI color in the mixer. Sending MIDI to the color or playing a MIDI clip plays the audio clip polyphonically.

=== Simple MIDI Example 2 ===
A simple example of a MIDI clip driving an AUv3 instrument.

=== MIDI Switcher Example ===
This project demonstrates how to use the ''Enable/Disable MIDI Destination'' action which is an essential tool for realtime MIDI routing -- allowing you to switch your MIDI controller targets on-the-fly.
[[File:Midi switcher sample project.png|alt=Midi switcher sample project screenshot|none|thumb]]

=== MIDI Clip Automation Example ===
This project has an XY-Pad set up to control the cutoff and Q parameters of a low-pass filter. The XY-Pad sends MIDI messages to the Blue MIDI color to be recorddd. When the blue clip plays, it re-triggers the XY-Pad with the recorded automation.
[[File:MIDI Clip Automation Example.jpg|alt=MIDI Automation Example layout|none|thumb]]

==== How it works ====
This project demonstrates the best-practices for setting up MIDI CC automation recording and playback. The main elements are:

* '''A widget:''' A widget (the XY pad) that performs actions (in this case adjust a filter) and sends MIDI messages to a MIDI Color. In most cases, MIDI Through should be turned off in the widget's Send MIDI action.
* '''Clip(s)''': A MIDI clip or clips whose color matches the widget's Send MIDI action. The automation will be recorded in these clips.
* '''Bindings''': MIDI bindings in a project profile that mirror the widget's bindings. Typically, the MIDI bindings will retrigger the widget that sent the automation MIDI.

==== Element Setup ====
{|
![[File:XY Pad Actions Automation Example.jpg|alt=The actions for the XY-Pad|thumb|299x299px]]
![[File:Send MIDI Message.jpg|alt=Send MIDI Message action setup|thumb|256x256px]]
![[File:Automation Example Control Settings.jpg|alt=Binding setup for the automation example|thumb|316x316px]]
!
|-
|XY-Pad Action Setup
|Send MIDI Message setting
|The MIDI Bindings from the Blue color back to the widget
|
|}
'''Send MIDI Message'''. The widget's Send MIDI Message action should generally have the ''Monitor Through'' option turned off to prevent MIDI feedback and redundant MIDI events. The ''Takeover'' option should generally be turned on. It allows you to use the widget during playback and have the interaction take over from the automation. Turning ''Takeover'' off can be fun, too -- allowing you to fight with the automation for stuttering effects.

'''The MIDI Bindings.''' The MIDI bindings can be set up to retrigger the widget that sent the MIDI or to perform the same actions performed by the widget. Generally, the first method is simplest.

==== MIDI Automation Setup Tutorial ====

{|style="border-style: none; border-width: 0px"
|-
|
<youtube>lAT8qcD0GBE</youtube>
|}

=== CircleSongs Tutorial ===
Jonas Viatte - A vocal live-looping tutorial

== Others ==

=== KAVES (COTCD) ===

=== RC-505-Esque ===

=== SHAMANIC's Live Production Template ===

=== Simpler LoopMachine ===

[[Category:Basics]]

Sample Projects 2.0

2026-04-07T21:49:40Z

Edwards: /* Verse-Chorus Looper */ video link

[[Category:Getting Started]]

Loopy Pro 2.0 includes a number of very helpful sample projects that will help you get up to speed with Loopy Pro. Access them using the ''Sample Projects'' tab in the Help menu or from the project browser. Even if you are an experienced user, there will be something for you. The '''Main Projects''' provide some helpful starting points and make use of some advanced features. The '''Tutorial Projects''' are small projects that demonstrate essential Loopy Pro concepts and provide some useful widgets you may want to use in your own projects.

'''See also''': The [[MIDI Basics]] page has resources to help you get up to speed with Loopy Pro 2.0's new MIDI features.

== Main Projects ==

=== Demo ===
Introductory demo project (by Dub Fx). A fun phase-locked looper project from [https://dubfx.com Dub FX].
[[File:Demo Project Dub FX.jpg|alt=Demo project by Dub FX|none|thumb]]
'''Key features''': X-Y Pad controlling a Low-Pass filter. Clip slicer. Reverb on a send/bus, controlled by a slider and throw button. Four one-shots and five loops with which to experiment.

=== Simple Scenes Example 1 ===
A simple example of scenes using Play Groups. This example uses mutually-exclusive, ''all loops play together'' play groups to create scenes. A scene can be triggered by pressing its button or by re-triggering any loop in a scene. Features two independent loops that can play at any time without interfering with the play groups.
[[File:Simple Scenes Example 1.jpg|alt=Simple Scenes 1 sample project|none|thumb]]

'''Key features''': all loops play together play group option, mutually exclusive play groups.

See the project's tutorial widgets for more details.

=== Simple Scenes Example 2 ===
A simple example of scenes using Solo actions. This scene looks identical to ''Simple Scenes Example 1'' but it behaves differently. Unlike Example 1, the groups are set up so that the clips play independently rather than play/stop together. The groups are also not mutually exclusive as they are in Example 1.

You can trigger a scene with its button, but the clips can play independently. So, you can turn clips off in a scene without stopping the scene, and you can trigger clips from other scenes. If you have turned off any of a scene's clips while the scene was playing, re-triggering the scene will trigger just the clips that were playing.

See the project's tutorial widgets for more details.

=== 5x5 Scenes ===
A 5x5 grid with scene buttons and a row of independent clips. Each scene row is a mutually exclusive play group that is set to let the clips play independently. You can turn clips on and off in a scene. Retriggering a scene plays just the clips that were last playing in the scene. The purple clips at the bottom are unaffected by scene playback. The Scene buttons use the Solo/Un-Solo action targeted that the row's play group.
[[File:5X5 Scenes.jpg|alt=Screenshot of the 5x5 scenes sample project|none|thumb]]

=== LP 707 ===
Inkie's RC-505-style template with extended functionality. This is a five-track looper reminiscent of the RC-505 with integrated effects (via 3rd Party AUv3). The project has an on-screen tour. Inkie has created a video tutorial that explains it all.

The template makes use of some 3rd-party plugins. You can substitute your own effects if you wish.

* BLEASS [https://apps.apple.com/us/app/bleass-samplewiz-2/id1501504776 Sample Wiz 2]
* Sugar Bytes' [https://apps.apple.com/us/app/turnado/id614418823 Turnado]
* Caelum Audio's [https://apps.apple.com/us/app/flux-pro/id1611411940 Flux Pro]
[[File:Inkie's LP 707 Template.jpg|alt=Screenshot of Inkie's LP 707 Sample Project|none|thumb|450x450px]]
{|style="border-style: none; border-width: 0px"
|-
|<YouTube width="450">cUkTYg4OAQM</youtube>
|}
=== Verse-Chorus Looper ===
A 4-pedal Verse-Chorus looper, inspired by the VL3. This looper features mutually exclusive verse and chorus loops and an independent groove clip. This project makes use of follow actions (more on that below). This is a good starter project for building serial loopers. The project also features a fun trick for using a two-pedal combination to clear the project.

'''Key features''': When a clip is playing, queuing playback or record of the other clip lets the current clip complete its cycle. If a groove clip has been recorded, verse and chorus recording is quantized to multiples of the groove length. Retrospective recording button.

Designed as a pedal looper with 4-switch operation. Pedal 1 - verse. Pedal 2 - chorus. Pedal 3 - groove. Pedal 4 - mode switch.

In record mode:

* Pedal tap toggles between play and overdub when a clip is playing. Plays the clip if it is stopped.
* Double-tap stops the clip at the end of its cycle)
* Hold clears the clip

In play mode:

* Pedal tap toggles between play and stop. Plays the clip if it is stopped.
* Double-tap immediate overdub switch.
* Hold clears the clip

The project is pre-configured with the MIDI CCs used by the iRig Blueboard or the M-Vave Chocolate in Manufacturer Control mode: MIDI CC's 20-23 for buttons 1 through 4.
[[File:Verse-Chorus Looper Screenshot.jpg|alt=A screenshot of the Verse-Chorus Looper sample project|none|thumb]]
'''How it works'''. The clips make use of follow actions that change the master cycle length and realign the clock when a part starts playing even if the parts are different lengths.

'''To add more mutually exclusive clips,''' use the following steps so that new clips will have the follow actions needed for well-behaved serial looping.

* Copy the verse clip
* Paste the copied clip
* Add the clip to play group 1 (the only play group)

{|style="border-style: none; border-width: 0px"
|-
<YouTube width="450">3WaXknJB4fA</YouTube>
|}

=== MIDI Showcase ===
A showcase of Loopy Pro 2.0's new MIDI capabilities. This project introduces some of Loopy Pro 2.0's new MIDI system.
[[File:MIDI Showcase screenshot.jpg|alt=Screenshot of the MIDI Showcase sample project|none|thumb]]
'''Key features''':

* MIDI Looping
* Using MIDI to polyphonically play audio one-shots and loops
* Playing/recording MIDI from widgets with Send MIDI Actions
* Using MIDI loops to record and play back effect parameter automation
* Loopy's new onscreen keyboard widget

=== Simple 4 Track Looper ===
Adam Searan - A Chewie Monsta-inspired simple 4-track looper. An easy-to-use 4-track looper with phase-locked loops.
[[File:Searan Simple 4 Track Screenshot.jpg|alt=Screenshot of the Simple 4 Track Looper|none|thumb]]Adam has posted a few helpful videos to go with the project

* Adam's [https://www.youtube.com/watch?v=T_dn0wA_SK0 YouTube template walkthrough/explainer].
* [https://www.youtube.com/watch?v=uVUKSQRTcnM Performance example and overview]. Skip straight to the performance by clicking [https://www.youtube.com/watch?v=uVUKSQRTcnM&t=277 here]

=== Inby's 2.0 Template ===
From [https://www.youtube.com/@inbar.heyman Inby]. This is a great template for exploring some of Loopy Pro 2.0's new features and some great features you may want to incorporate into your own projects. Check out the [https://www.youtube.com/watch?v=_ztu8iE6Ps8 YouTube guide] for this template.
[[File:Inby's Template.jpg|alt=Inby's Loopy Pro 2.0 Template|none|thumb]]

== Tutorials ==
These projects explain demonstrate key Loopy Pro concepts. A little bit of time spent with these lessons will increase your productivity immensely.

=== Master Clock Length ===
The Master Clock Length is often used to start and stop recording. Explore this project to experiment with master clock.

'''See also''': The [[Simple Looper Tutorial Projects#Simple Looper 01 Two Loops|Simple Looper tutorial]] shows the master cycle in action and shows how you might use it in real life.

=== Phase-Locked vs Free Loops ===
A demonstration of Phase Locked and Free clips. This is one of the key concepts in Loop Pro. Phase-locked loops have an always moving playhead even when the loop isn't playing, making it easy to drop in and out of loops while staying in sync. Free loops always start from the beginning when you start them playing -- perfect when working with loops and song sections of different lengths.

'''See also''': [[Phase-Lock and Free Loops]]

=== Record Count-in and Out ===
Record count-in and count-out settings determine the length of clips and when recording starts. Loopy is flexible in how you can set it up. Recording can be tied to the master cycle or use a fixed custom length. Clips can automatically record a set length or record until you trigger the stop.

'''Other key features''': The project makes use of the new Assign Settings action that lets you change the settings used by a clip, a color or all clips.

=== Simple MIDI Example - Loopy Pro as polyphonic sampler ===
This project demonstrates how Loopy Pro can be a polyphonic, MPE-capable sampler by targeting clips as MIDI targets. In this project, an audio clip is set as a destination of a MIDI color in the mixer. Sending MIDI to the color or playing a MIDI clip plays the audio clip polyphonically.

=== Simple MIDI Example 2 ===
A simple example of a MIDI clip driving an AUv3 instrument.

=== MIDI Switcher Example ===
This project demonstrates how to use the ''Enable/Disable MIDI Destination'' action which is an essential tool for realtime MIDI routing -- allowing you to switch your MIDI controller targets on-the-fly.
[[File:Midi switcher sample project.png|alt=Midi switcher sample project screenshot|none|thumb]]

=== MIDI Clip Automation Example ===
This project has an XY-Pad set up to control the cutoff and Q parameters of a low-pass filter. The XY-Pad sends MIDI messages to the Blue MIDI color to be recorddd. When the blue clip plays, it re-triggers the XY-Pad with the recorded automation.
[[File:MIDI Clip Automation Example.jpg|alt=MIDI Automation Example layout|none|thumb]]

==== How it works ====
This project demonstrates the best-practices for setting up MIDI CC automation recording and playback. The main elements are:

* '''A widget:''' A widget (the XY pad) that performs actions (in this case adjust a filter) and sends MIDI messages to a MIDI Color. In most cases, MIDI Through should be turned off in the widget's Send MIDI action.
* '''Clip(s)''': A MIDI clip or clips whose color matches the widget's Send MIDI action. The automation will be recorded in these clips.
* '''Bindings''': MIDI bindings in a project profile that mirror the widget's bindings. Typically, the MIDI bindings will retrigger the widget that sent the automation MIDI.

==== Element Setup ====
{|
![[File:XY Pad Actions Automation Example.jpg|alt=The actions for the XY-Pad|thumb|299x299px]]
![[File:Send MIDI Message.jpg|alt=Send MIDI Message action setup|thumb|256x256px]]
![[File:Automation Example Control Settings.jpg|alt=Binding setup for the automation example|thumb|316x316px]]
!
|-
|XY-Pad Action Setup
|Send MIDI Message setting
|The MIDI Bindings from the Blue color back to the widget
|
|}
'''Send MIDI Message'''. The widget's Send MIDI Message action should generally have the ''Monitor Through'' option turned off to prevent MIDI feedback and redundant MIDI events. The ''Takeover'' option should generally be turned on. It allows you to use the widget during playback and have the interaction take over from the automation. Turning ''Takeover'' off can be fun, too -- allowing you to fight with the automation for stuttering effects.

'''The MIDI Bindings.''' The MIDI bindings can be set up to retrigger the widget that sent the MIDI or to perform the same actions performed by the widget. Generally, the first method is simplest.

==== MIDI Automation Setup Tutorial ====

{|style="border-style: none; border-width: 0px"
|-
|
<youtube>lAT8qcD0GBE</youtube>
|}

=== CircleSongs Tutorial ===
Jonas Viatte - A vocal live-looping tutorial

== Others ==

=== KAVES (COTCD) ===

=== RC-505-Esque ===

=== SHAMANIC's Live Production Template ===

=== Simpler LoopMachine ===

[[Category:Basics]]

Sample Projects 2.0

2026-04-05T15:37:40Z

Edwards: How to access info added

[[Category:Getting Started]]

Loopy Pro 2.0 includes a number of very helpful sample projects that will help you get up to speed with Loopy Pro. Access them using the ''Sample Projects'' tab in the Help menu or from the project browser. Even if you are an experienced user, there will be something for you. The '''Main Projects''' provide some helpful starting points and make use of some advanced features. The '''Tutorial Projects''' are small projects that demonstrate essential Loopy Pro concepts and provide some useful widgets you may want to use in your own projects.

'''See also''': The [[MIDI Basics]] page has resources to help you get up to speed with Loopy Pro 2.0's new MIDI features.

== Main Projects ==

=== Demo ===
Introductory demo project (by Dub Fx). A fun phase-locked looper project from [https://dubfx.com Dub FX].
[[File:Demo Project Dub FX.jpg|alt=Demo project by Dub FX|none|thumb]]
'''Key features''': X-Y Pad controlling a Low-Pass filter. Clip slicer. Reverb on a send/bus, controlled by a slider and throw button. Four one-shots and five loops with which to experiment.

=== Simple Scenes Example 1 ===
A simple example of scenes using Play Groups. This example uses mutually-exclusive, ''all loops play together'' play groups to create scenes. A scene can be triggered by pressing its button or by re-triggering any loop in a scene. Features two independent loops that can play at any time without interfering with the play groups.
[[File:Simple Scenes Example 1.jpg|alt=Simple Scenes 1 sample project|none|thumb]]

'''Key features''': all loops play together play group option, mutually exclusive play groups.

See the project's tutorial widgets for more details.

=== Simple Scenes Example 2 ===
A simple example of scenes using Solo actions. This scene looks identical to ''Simple Scenes Example 1'' but it behaves differently. Unlike Example 1, the groups are set up so that the clips play independently rather than play/stop together. The groups are also not mutually exclusive as they are in Example 1.

You can trigger a scene with its button, but the clips can play independently. So, you can turn clips off in a scene without stopping the scene, and you can trigger clips from other scenes. If you have turned off any of a scene's clips while the scene was playing, re-triggering the scene will trigger just the clips that were playing.

See the project's tutorial widgets for more details.

=== 5x5 Scenes ===
A 5x5 grid with scene buttons and a row of independent clips. Each scene row is a mutually exclusive play group that is set to let the clips play independently. You can turn clips on and off in a scene. Retriggering a scene plays just the clips that were last playing in the scene. The purple clips at the bottom are unaffected by scene playback. The Scene buttons use the Solo/Un-Solo action targeted that the row's play group.
[[File:5X5 Scenes.jpg|alt=Screenshot of the 5x5 scenes sample project|none|thumb]]

=== LP 707 ===
Inkie's RC-505-style template with extended functionality. This is a five-track looper reminiscent of the RC-505 with integrated effects (via 3rd Party AUv3). The project has an on-screen tour. Inkie has created a video tutorial that explains it all.

The template makes use of some 3rd-party plugins. You can substitute your own effects if you wish.

* BLEASS [https://apps.apple.com/us/app/bleass-samplewiz-2/id1501504776 Sample Wiz 2]
* Sugar Bytes' [https://apps.apple.com/us/app/turnado/id614418823 Turnado]
* Caelum Audio's [https://apps.apple.com/us/app/flux-pro/id1611411940 Flux Pro]
[[File:Inkie's LP 707 Template.jpg|alt=Screenshot of Inkie's LP 707 Sample Project|none|thumb|450x450px]]
{|style="border-style: none; border-width: 0px"
|-
|<YouTube width="450">cUkTYg4OAQM</youtube>
|}
=== Verse-Chorus Looper ===
A 4-pedal Verse-Chorus looper, inspired by the VL3. This looper features mutually exclusive verse and chorus loops and an independent groove clip. This project makes use of follow actions (more on that below). This is a good starter project for building serial loopers. The project also features a fun trick for using a two-pedal combination to clear the project.

'''Key features''': When a clip is playing, queuing playback or record of the other clip lets the current clip complete its cycle. If a groove clip has been recorded, verse and chorus recording is quantized to multiples of the groove length. Retrospective recording button.

Designed as a pedal looper with 4-switch operation. Pedal 1 - verse. Pedal 2 - chorus. Pedal 3 - groove. Pedal 4 - mode switch.

In record mode:

* Pedal tap toggles between play and overdub when a clip is playing. Plays the clip if it is stopped.
* Double-tap stops the clip at the end of its cycle)
* Hold clears the clip

In play mode:

* Pedal tap toggles between play and stop. Plays the clip if it is stopped.
* Double-tap immediate overdub switch.
* Hold clears the clip

The project is pre-configured with the MIDI CCs used by the iRig Blueboard or the M-Vave Chocolate in Manufacturer Control mode: MIDI CC's 20-23 for buttons 1 through 4.
[[File:Verse-Chorus Looper Screenshot.jpg|alt=A screenshot of the Verse-Chorus Looper sample project|none|thumb]]
'''How it works'''. The clips make use of follow actions that change the master cycle length and realign the clock when a part starts playing even if the parts are different lengths.

'''To add more mutually exclusive clips,''' use the following steps so that new clips will have the follow actions needed for well-behaved serial looping.

* Copy the verse clip
* Paste the copied clip
* Add the clip to play group 1 (the only play group)

=== MIDI Showcase ===
A showcase of Loopy Pro 2.0's new MIDI capabilities. This project introduces some of Loopy Pro 2.0's new MIDI system.
[[File:MIDI Showcase screenshot.jpg|alt=Screenshot of the MIDI Showcase sample project|none|thumb]]
'''Key features''':

* MIDI Looping
* Using MIDI to polyphonically play audio one-shots and loops
* Playing/recording MIDI from widgets with Send MIDI Actions
* Using MIDI loops to record and play back effect parameter automation
* Loopy's new onscreen keyboard widget

=== Simple 4 Track Looper ===
Adam Searan - A Chewie Monsta-inspired simple 4-track looper. An easy-to-use 4-track looper with phase-locked loops.
[[File:Searan Simple 4 Track Screenshot.jpg|alt=Screenshot of the Simple 4 Track Looper|none|thumb]]Adam has posted a few helpful videos to go with the project

* Adam's [https://www.youtube.com/watch?v=T_dn0wA_SK0 YouTube template walkthrough/explainer].
* [https://www.youtube.com/watch?v=uVUKSQRTcnM Performance example and overview]. Skip straight to the performance by clicking [https://www.youtube.com/watch?v=uVUKSQRTcnM&t=277 here]

=== Inby's 2.0 Template ===
From [https://www.youtube.com/@inbar.heyman Inby]. This is a great template for exploring some of Loopy Pro 2.0's new features and some great features you may want to incorporate into your own projects. Check out the [https://www.youtube.com/watch?v=_ztu8iE6Ps8 YouTube guide] for this template.
[[File:Inby's Template.jpg|alt=Inby's Loopy Pro 2.0 Template|none|thumb]]

== Tutorials ==
These projects explain demonstrate key Loopy Pro concepts. A little bit of time spent with these lessons will increase your productivity immensely.

=== Master Clock Length ===
The Master Clock Length is often used to start and stop recording. Explore this project to experiment with master clock.

'''See also''': The [[Simple Looper Tutorial Projects#Simple Looper 01 Two Loops|Simple Looper tutorial]] shows the master cycle in action and shows how you might use it in real life.

=== Phase-Locked vs Free Loops ===
A demonstration of Phase Locked and Free clips. This is one of the key concepts in Loop Pro. Phase-locked loops have an always moving playhead even when the loop isn't playing, making it easy to drop in and out of loops while staying in sync. Free loops always start from the beginning when you start them playing -- perfect when working with loops and song sections of different lengths.

'''See also''': [[Phase-Lock and Free Loops]]

=== Record Count-in and Out ===
Record count-in and count-out settings determine the length of clips and when recording starts. Loopy is flexible in how you can set it up. Recording can be tied to the master cycle or use a fixed custom length. Clips can automatically record a set length or record until you trigger the stop.

'''Other key features''': The project makes use of the new Assign Settings action that lets you change the settings used by a clip, a color or all clips.

=== Simple MIDI Example - Loopy Pro as polyphonic sampler ===
This project demonstrates how Loopy Pro can be a polyphonic, MPE-capable sampler by targeting clips as MIDI targets. In this project, an audio clip is set as a destination of a MIDI color in the mixer. Sending MIDI to the color or playing a MIDI clip plays the audio clip polyphonically.

=== Simple MIDI Example 2 ===
A simple example of a MIDI clip driving an AUv3 instrument.

=== MIDI Switcher Example ===
This project demonstrates how to use the ''Enable/Disable MIDI Destination'' action which is an essential tool for realtime MIDI routing -- allowing you to switch your MIDI controller targets on-the-fly.
[[File:Midi switcher sample project.png|alt=Midi switcher sample project screenshot|none|thumb]]

=== MIDI Clip Automation Example ===
This project has an XY-Pad set up to control the cutoff and Q parameters of a low-pass filter. The XY-Pad sends MIDI messages to the Blue MIDI color to be recorddd. When the blue clip plays, it re-triggers the XY-Pad with the recorded automation.
[[File:MIDI Clip Automation Example.jpg|alt=MIDI Automation Example layout|none|thumb]]

==== How it works ====
This project demonstrates the best-practices for setting up MIDI CC automation recording and playback. The main elements are:

* '''A widget:''' A widget (the XY pad) that performs actions (in this case adjust a filter) and sends MIDI messages to a MIDI Color. In most cases, MIDI Through should be turned off in the widget's Send MIDI action.
* '''Clip(s)''': A MIDI clip or clips whose color matches the widget's Send MIDI action. The automation will be recorded in these clips.
* '''Bindings''': MIDI bindings in a project profile that mirror the widget's bindings. Typically, the MIDI bindings will retrigger the widget that sent the automation MIDI.

==== Element Setup ====
{|
![[File:XY Pad Actions Automation Example.jpg|alt=The actions for the XY-Pad|thumb|299x299px]]
![[File:Send MIDI Message.jpg|alt=Send MIDI Message action setup|thumb|256x256px]]
![[File:Automation Example Control Settings.jpg|alt=Binding setup for the automation example|thumb|316x316px]]
!
|-
|XY-Pad Action Setup
|Send MIDI Message setting
|The MIDI Bindings from the Blue color back to the widget
|
|}
'''Send MIDI Message'''. The widget's Send MIDI Message action should generally have the ''Monitor Through'' option turned off to prevent MIDI feedback and redundant MIDI events. The ''Takeover'' option should generally be turned on. It allows you to use the widget during playback and have the interaction take over from the automation. Turning ''Takeover'' off can be fun, too -- allowing you to fight with the automation for stuttering effects.

'''The MIDI Bindings.''' The MIDI bindings can be set up to retrigger the widget that sent the MIDI or to perform the same actions performed by the widget. Generally, the first method is simplest.

==== MIDI Automation Setup Tutorial ====

{|style="border-style: none; border-width: 0px"
|-
|
<youtube>lAT8qcD0GBE</youtube>
|}

=== CircleSongs Tutorial ===
Jonas Viatte - A vocal live-looping tutorial

== Others ==

=== KAVES (COTCD) ===

=== RC-505-Esque ===

=== SHAMANIC's Live Production Template ===

=== Simpler LoopMachine ===

[[Category:Basics]]

Main Page

2026-04-04T03:22:54Z

Edwards: /* Tips and Tricks */

RECIPE: Row-Based Footswitch Setup

2026-04-03T19:00:44Z

Edwards: /* See Also */

[[File:Row-Based Template Picture.jpg|alt=a row/scene based template|thumb|In this template, footswitch 1 will control the first clip of the active row; switch 2 will control clip 2 of the row, and switch 3 will control clip 3.]]For scene-based workflows, it is handy to have switches for the first, second, third, etc. clips of the active scene/row. One way of accomplishing this is to have one control profile per row with a radio button to make a row the active scene.

=== Overview ===

* Create a profile to control the clips in row 1.
* Set up the MIDI bindings for the row’s clips.
* Duplicate the new profile for use with another row and update the targets.
* Set up a radio button group to switch profiles and make a row active.

=== Create the Profile for Row 1 ===
A project can have many profiles in it. We will leave the default profile alone so that it can be used for bindings that aren’t row-specific. I rename mine to ''Always'' to remind myself that it is always active. We use MIDI Learn mode for creating the profiles in this tutorial, but you can use the Control Settings panel if you prefer.

* Choose MIDI Learn from the main menu.
* In the upper-left corner is the profiles popup that shows which profile the bindings will be saved in.<br />[[File:MIDI Learn Profile Name Display.jpg|195x195px]]
* Tap on the pop down and rename the ''Default'' profile to ''Always''. This is where you will have bindings that are always active. You don’t have to rename it, but it will make things easier to keep track of.
* Choose ''New Profile'' from the Project Profiles section.
* Give the new profile the name ''Row 1''.
* Tap on the first clip in the row, tap your foot controller to learn it.
* Learn all the other clips in that row.
* ''Optional'': Set up any double-tap and hold bindings for the clips.
* Leave MIDI Learn mode.
* View the profile that you just created by choosing ''Control Settings'' from the main menu.
* The profile should look something like this:
[[File:Row 1 Profile Listing.jpg|492x492px]]

=== Create Profiles for The Remaining Rows ===
Create profiles for the remaining rows as you did for Row 1. I suggest naming them Row 2, Row 3, etc.

An alternate method is to duplicate the Row 1 profile in the ''Control Settings'' panel and update the targets for the bindings in the duplicated profiles. The MIDI Learn method is probably faster.

Whichever method you use, you should end up with a series of profiles as shown below:

[[File:Profile Listing After Completion.jpg|alt=profile listing once this stage has been completed|400x400px]]

=== Create Scene/Profile Selector ===
Now that we have profiles that map the footswitches to particular rows, we need create a radio button group to handle the profile switching.

* Go into layout edit mode by tapping the lower tools' pencil icon.
* Create a new radio button group.
[[File:Radiobutton picker.png|frameless]]
* Tap on the radio buttons to pop up the editor.
* Tap on the + next to ''Items Source''
* Choose the action ''Select Controller Profile''. This makes the chosen profiles the source for the radio buttons.
* Tap ''List''
* Tap ''Project''. You will see a list of the project profiles.
* Uncheck any non-row profiles. Only the row profiles should be selected.
[[File:Profile list.jpg|alt=profile list for radio buttons|frameless]]
* Resize the radio button group so that it is one button high. Adjust the width as preferred. You should be able to resize it so that the buttons line up with your rows.
You now have radio buttons that switch the profile for the desired row.

'''Test that everything is set up correctly'''. Tap on a row and press a footswitch button. It should activate only a clip in the selected row.

=== Bells and Whistles ===
What we have done so far lets you change the row targeted by the footswitch by selecting a radio button. Depending on your workflow, there are a number of ways you might enhance the workflow:

* '''Add a row selecting MIDI Binding'''. I create a MIDI Binding in the ''Always'' profile to nudge the row selector. This lets me use my footswitch to advance the selected row. You may also want to add a HOLD action for the same MIDI message that selects the first row. That way you can easily jump to the first row. When you set up that binding turn on the option to defer other actions.
* You might add an action to the scene buttons to select that scene’s row selector when the scene is triggered

== See Also ==
These YouTube videos from Michael may also be of interest:

Four Buttons to rule them all:
<YouTube>ScxELIJHinE</YouTube>

One Button, Many Pages:
<YouTube>ojchzpuJevI</YouTube>

[[Category:Tips and Tricks]]

RECIPE: Row-Based Footswitch Setup

2026-04-03T19:00:24Z

Edwards:

RECIPE: Row-Based Footswitch Setup

2026-04-03T18:58:57Z

Edwards: /* Create Scene/Profile Selector */

RECIPE: Row-Based Footswitch Setup

2026-04-03T18:58:05Z

Edwards:

[[File:Row-Based Template Picture.jpg|alt=a row/scene based template|thumb|In this template, footswitch 1 will control the first clip of the active row; switch 2 will control clip 2 of the row, and switch 3 will control clip 3.]]For scene-based workflows, it is handy to have switches for the first, second, third, etc. clips of the active scene/row. One way of accomplishing this is to have one control profile per row with a radio button to make a row the active scene.

=== Overview ===

* Create a profile to control the clips in row 1.
* Set up the MIDI bindings for the row’s clips.
* Duplicate the new profile for use with another row and update the targets.
* Set up a radio button group to switch profiles and make a row active.

=== Create the Profile for Row 1 ===
A project can have many profiles in it. We will leave the default profile alone so that it can be used for bindings that aren’t row-specific. I rename mine to ''Always'' to remind myself that it is always active. We use MIDI Learn mode for creating the profiles in this tutorial, but you can use the Control Settings panel if you prefer.

* Choose MIDI Learn from the main menu.
* In the upper-left corner is the profiles popup that shows which profile the bindings will be saved in.<br />[[File:MIDI Learn Profile Name Display.jpg|195x195px]]
* Tap on the pop down and rename the ''Default'' profile to ''Always''. This is where you will have bindings that are always active. You don’t have to rename it, but it will make things easier to keep track of.
* Choose ''New Profile'' from the Project Profiles section.
* Give the new profile the name ''Row 1''.
* Tap on the first clip in the row, tap your foot controller to learn it.
* Learn all the other clips in that row.
* ''Optional'': Set up any double-tap and hold bindings for the clips.
* Leave MIDI Learn mode.
* View the profile that you just created by choosing ''Control Settings'' from the main menu.
* The profile should look something like this:
[[File:Row 1 Profile Listing.jpg|492x492px]]

=== Create Profiles for The Remaining Rows ===
Create profiles for the remaining rows as you did for Row 1. I suggest naming them Row 2, Row 3, etc.

An alternate method is to duplicate the Row 1 profile in the ''Control Settings'' panel and update the targets for the bindings in the duplicated profiles. The MIDI Learn method is probably faster.

Whichever method you use, you should end up with a series of profiles as shown below:

[[File:Profile Listing After Completion.jpg|alt=profile listing once this stage has been completed|400x400px]]

=== Create Scene/Profile Selector ===
Now that we have profiles that map the footswitches to particular rows, we need create a radio button group to handle the profile switching.

* Go into layout edit mode by tapping the lower tools' pencil icon.
* Create a new radio button group. [[File:Radiobutton picker.png|frameless]]
* Tap on the radio buttons to pop up the editor.
* Tap on the + next to ''Items Source''
* Choose the action ''Select Controller Profile''. This makes the chosen profiles the source for the radio buttons.
* Tap ''List''
* Tap ''Project''. You will see a list of the project profiles.
* Uncheck any non-row profiles. Only the row profiles should be selected.
[[File:Profile list.jpg|alt=profile list for radio buttons|frameless]]
* Resize the radio button group so that it is one button high. Adjust the width as preferred. You should be able to resize it so that the buttons line up with your rows.
You now have radio buttons that switch the profile for the desired row.

'''Test that everything is set up correctly'''. Tap on a row and press a footswitch button. It should activate only a clip in the selected row.

=== Bells and Whistles ===
What we have done so far lets you change the row targeted by the footswitch by selecting a radio button. Depending on your workflow, there are a number of ways you might enhance the workflow:

* '''Add a row selecting MIDI Binding'''. I create a MIDI Binding in the ''Always'' profile to nudge the row selector. This lets me use my footswitch to advance the selected row. You may also want to add a HOLD action for the same MIDI message that selects the first row. That way you can easily jump to the first row. When you set up that binding turn on the option to defer other actions.
* You might add an action to the scene buttons to select that scene’s row selector when the scene is triggered

== See Also ==
These YouTube videos from Michael may also be of interest:

Four Buttons to rule them all:
<YouTube>ScxELIJHinE</YouTube>

One Button, Many Pages:
<YouTube>ojchzpuJevI</YouTube>

RECIPE: Row-Based Footswitch Setup

2026-04-03T18:56:17Z

Edwards: /* Create Scene/Profile Selector */

[[File:Row-Based Template Picture.jpg|alt=a row/scene based template|thumb|In this template, footswitch 1 will control the first clip of the active row; switch 2 will control clip 2 of the row, and switch 3 will control clip 3.]]For scene-based workflows, it is handy to have switches for the first, second, third, etc. clips of the active scene/row. One way of accomplishing this is to have one control profile per row with a radio button to make a row the active scene.

=== Overview ===

* Create a profile to control the clips in row 1.
* Set up the MIDI bindings for the row’s clips.
* Duplicate the new profile for use with another row and update the targets.
* Set up a radio button group to switch profiles and make a row active.

=== Create the Profile for Row 1 ===
A project can have many profiles in it. We will leave the default profile alone so that it can be used for bindings that aren’t row-specific. I rename mine to ''Always'' to remind myself that it is always active. We use MIDI Learn mode for creating the profiles in this tutorial, but you can use the Control Settings panel if you prefer.

* Choose MIDI Learn from the main menu.
* In the upper-left corner is the profiles popup that shows which profile the bindings will be saved in.<br />[[File:MIDI Learn Profile Name Display.jpg|195x195px]]
* Tap on the pop down and rename the ''Default'' profile to ''Always''. This is where you will have bindings that are always active. You don’t have to rename it, but it will make things easier to keep track of.
* Choose ''New Profile'' from the Project Profiles section.
* Give the new profile the name ''Row 1''.
* Tap on the first clip in the row, tap your foot controller to learn it.
* Learn all the other clips in that row.
* ''Optional'': Set up any double-tap and hold bindings for the clips.
* Leave MIDI Learn mode.
* View the profile that you just created by choosing ''Control Settings'' from the main menu.
* The profile should look something like this:
[[File:Row 1 Profile Listing.jpg|492x492px]]

=== Create Profiles for The Remaining Rows ===
Create profiles for the remaining rows as you did for Row 1. I suggest naming them Row 2, Row 3, etc.

An alternate method is to duplicate the Row 1 profile in the ''Control Settings'' panel and update the targets for the bindings in the duplicated profiles. The MIDI Learn method is probably faster.

Whichever method you use, you should end up with a series of profiles as shown below:

[[File:Profile Listing After Completion.jpg|alt=profile listing once this stage has been completed|400x400px]]

=== Create Scene/Profile Selector ===
Now that we have profiles that map the footswitches to particular rows, we need create a radio button group to handle the profile switching.

* Go into layout edit mode by tapping the lower tools' pencil icon.
* Create a new radio button group. [[File:Radiobutton picker.png|frameless]]
* Tap on the radio buttons to pop up the editor.
* Tap on the + next to ''Items Source''
* Choose the action ''Select Controller Profile''. This makes the chosen profiles the source for the radio buttons.
* Tap ''List''
* Tap ''Project''. You will see a list of the project profiles.
* Uncheck any non-row profiles. Only the row profiles should be selected. [[File:Profile list.jpg|alt=profile list for radio buttons|frameless]]
* Resize the radio button group so that it is one button high. Adjust the width as preferred. You should be able to resize it so that the buttons line up with your rows.
You now have radio buttons that switch the profile for the desired row.

'''Test that everything is set up correctly'''. Tap on a row and press a footswitch button. It should activate only a clip in the selected row.

=== Bells and Whistles ===
What we have done so far lets you change the row targeted by the footswitch by selecting a radio button. Depending on your workflow, there are a number of ways you might enhance the workflow:

* '''Add a row selecting MIDI Binding'''. I create a MIDI Binding in the ''Always'' profile to nudge the row selector. This lets me use my footswitch to advance the selected row. You may also want to add a HOLD action for the same MIDI message that selects the first row. That way you can easily jump to the first row. When you set up that binding turn on the option to defer other actions.
* You might add an action to the scene buttons to select that scene’s row selector when the scene is triggered

== See Also ==
These YouTube videos from Michael may also be of interest:

Four Buttons to rule them all:
<YouTube>ScxELIJHinE</YouTube>

One Button, Many Pages:
<YouTube>ojchzpuJevI</YouTube>

File:Profile list.jpg

2026-04-03T18:45:22Z

Edwards:

profile list

File:Radiobutton picker.png

2026-04-03T18:41:30Z

Edwards:

Radio Button picker

RECIPE: Row-Based Footswitch Setup

2026-04-03T18:38:36Z

Edwards:

RECIPE: Row-Based Footswitch Setup

2026-04-03T18:34:44Z

Edwards: Created page with "In this template, footswitch 1 will control the first clip of the active row; switch 2 will control clip 2 of the row, and switch 3 will control clip 3.For scene-based workflows, it is handy to have switches for the first, second, third, etc. clips of the active scene/row. One way of accomplishing this is to have one control profile per row with a radio button to make a row the active scene...."

File:Profile Listing After Completion.jpg

2026-04-03T18:29:56Z

Edwards:

A listing of the control profiles once you have gotten to this stage.

File:Row 1 Profile Listing.jpg

2026-04-03T18:25:51Z

Edwards:

The binding listing for the Row 1 Profile

Tech Note:Active Page

2026-04-03T18:21:23Z

Edwards:

When MIDI Learn a widget, there is an option to MIDI Learn for ''This Page Only'' or for the ''Active Page''. As explained in the Loopy Pro manual.

''This Page Only'' triggers that particular widget on that particular page whenever the triggering MIDI comes in. The binding is to that particular widget. You can change the page's layout and the binding isn't affected because the binding targets the widget via a unique internal ID.

''Active Page'' bindings are based on the assumption that each page has an identical. If your pages are not identical, your ''Active Page'' bindings may not work as you expected. ''Active Page'' page bindings trigger only a widget on the page that it active when the triggering MIDI comes in. Unlike ''This Page Only'' bindings, the binding is to the widget at particular logical position. If your pages are not (logically) identical, it is possible that different widgets will be triggered by the same MIDI on different pages. For example, if you MIDI Learn a button called ''Play All'' for the ''Active Page'' and ''Play All'' is the first button on the page, you are really MIDI Learning the first button on the page. If your ''Play All'' is not the first button on page 2, it will not be triggered when page 2 is active.

== Active Page Alternative ==
There may be times where the widget positions are different on different pages but you want the same MIDI to trigger the item on that page any way. In this situation, you will create page-specific control profiles that are active only when the page is the current page.

File:MIDI Learn Profile Name Display.jpg

2026-04-03T18:17:27Z

Edwards:

MIDI Learn Profile Name Display