Footswitches - Revision history

Edwards: /* Morningstar MC8 */

2026-01-17T19:59:50Z

Morningstar MC8

← Older revision		Revision as of 05:59, 18 January 2026
Line 71:		Line 71:

	== Morningstar MC8 ==		== Morningstar MC8 ==
	This is a capable highly programmable footswitch~~; to use~~ it ~~with Loopy Pro, you need~~ to set it to looper mode as described on the [https://www.morningstar.io/post/looper-mode-for-zero-latency-midi-control Morningstar web site].		This is a capable highly programmable footswitch. For the most flexible, lowest latency behavior, it is recommend to set it to looper mode as described on the [https://www.morningstar.io/post/looper-mode-for-zero-latency-midi-control Morningstar web site] so that it can be used as a fully-momentary footswitch. If you make use of the MC8's internal mapping of double-taps, it will introduce a delay of single taps (an issue that will be true of any device that lets you map mutually exclusive tap and double-tap behaviors).

			'''MIDI FEEDBACK'''. The MC8 does not make use of Loopy Pro's MIDI feedback. Loopy Pro automatically turns off MIDI feedback to the MC8 because many MIDI messages to the MC8 trigger the MC8 itself. A list of the reserved MIDI messages is provided in the MC8's manual.

Edwards: /* Morningstar MC8 */ let to looper mode page

2025-12-08T01:20:09Z

Morningstar MC8: let to looper mode page

← Older revision		Revision as of 11:20, 8 December 2025
Line 71:		Line 71:

	== Morningstar MC8 ==		== Morningstar MC8 ==
	This is a capable highly programmable footswitch; ~~however at this time (November 2025)~~, it ~~has a drawback if you want~~ to ~~use tap and double-tap with no delay off~~ the ~~tap~~. ~~Its internal double~~-~~tap detection prevents double~~-~~taps from being passed through even if you have not programmed a double~~-~~tap into the pedal. If you do program a double~~-~~tap into the pedal, the single tap will be delayed slightly~~.		This is a capable highly programmable footswitch; to use it with Loopy Pro, you need to set it to looper mode as described on the [https://www.morningstar.io/post/looper-mode-for-zero-latency-midi-control Morningstar web site].

Edwards: /* Morningstar MC8 */

2025-11-22T00:21:52Z

Morningstar MC8

← Older revision		Revision as of 10:21, 22 November 2025
Line 71:		Line 71:

	== Morningstar MC8 ==		== Morningstar MC8 ==
	This is a capable highly programmable footswitch; however at this time (November 2025), it has a drawback if you want to use tap and double-tap with no delay ~~on a~~ tap. Its internal double-tap detection prevents double-taps from being passed through even if you have not programmed a double-tap into the pedal. If you do program a double-tap, the single tap will be delayed slightly.		This is a capable highly programmable footswitch; however at this time (November 2025), it has a drawback if you want to use tap and double-tap with no delay off the tap. Its internal double-tap detection prevents double-taps from being passed through even if you have not programmed a double-tap into the pedal. If you do program a double-tap into the pedal, the single tap will be delayed slightly.

Edwards: add MC8 note

2025-11-22T00:21:15Z

add MC8 note

← Older revision		Revision as of 10:21, 22 November 2025
Line 69:		Line 69:
	== Line 6 Helix LT ==		== Line 6 Helix LT ==
	This foot controller does not respond correctly to Loopy Pro’s MIDI Feedback. In Control Settings, find the controller and turn off the Feedback Enabled option.		This foot controller does not respond correctly to Loopy Pro’s MIDI Feedback. In Control Settings, find the controller and turn off the Feedback Enabled option.

			== Morningstar MC8 ==
			This is a capable highly programmable footswitch; however at this time (November 2025), it has a drawback if you want to use tap and double-tap with no delay on a tap. Its internal double-tap detection prevents double-taps from being passed through even if you have not programmed a double-tap into the pedal. If you do program a double-tap, the single tap will be delayed slightly.

Edwards: /* M-Vave Chocolate */

2025-11-14T01:25:56Z

M-Vave Chocolate

← Older revision		Revision as of 11:25, 14 November 2025
Line 42:		Line 42:
	The Chocolate has four switches and a port for an expression or sustain pedal. It has several different modes of operation and can be configured with the free CubeSuite app.		The Chocolate has four switches and a port for an expression or sustain pedal. It has several different modes of operation and can be configured with the free CubeSuite app.

	The quickest way to set up the Chocolate is to choose the '''Manufacturer Control''' mode. No additional set up is required with Cube Suite once that mode is selected. In this mode the four switches send MIDI CC 20 - 23. A press sends cc value 127 (on) and release sends cc value 0 (off).		The quickest way to set up the Chocolate is to launch the CubeSuite app and choose the '''Manufacturer Control''' mode. No additional set up is required with Cube Suite once that mode is selected. In this mode the four switches send MIDI CC 20 - 23. A press sends cc value 127 (on) and release sends cc value 0 (off).

	'''For the fastest pedal response time:''' use the '''Manufacturer Control''' settings mentioned in the previous paragraph or '''Custom Control''' mode (with CC messages). Both of these modes are quick to set up and send an On message on press and Off on release.		'''For the fastest pedal response time:''' use the '''Manufacturer Control''' settings mentioned in the previous paragraph or '''Custom Control''' mode (with CC messages). Both of these modes are quick to set up and send an On message on press and Off on release.

Edwards: add test your controller with video

2025-11-14T01:11:17Z

add test your controller with video

← Older revision		Revision as of 11:11, 14 November 2025
Line 6:		Line 6:
	For musicians whose hands are busy during performance, footswitches/pedals are invaluable for controlling Loopy Pro. This page is a place for tips about using footswitches.		For musicians whose hands are busy during performance, footswitches/pedals are invaluable for controlling Loopy Pro. This page is a place for tips about using footswitches.

	~~'''Basic~~ Setup~~'''.~~ For the best, most flexible behavior you want a foot controller to have full '''momentary''' behavior which means that when a switch is pressed an ON event is sent and when the switch is released an OFF event is immediately sent. An ON message can be a MIDI CC message with value greater than zero or a MIDI Note message with velocity greater than 0. The OFF message would be the same CC or Note number but with a value or velocity of 0. This sort of full momentary behavior is needed for tap/double-tap/hold disambiguation. Hold messages require full momentary behavior.		If you want to make use of tap, double-tap and hold from your footswitch, it must be configured to send MIDI Notes or MIDI CC messages. MIDI Program Change (PC) messages can be used as triggers but cannot be used for hold or double tap.

			Expression pedals that can send a stream of values are useful for controlling controls like faders, knobs and dials that respond to more than simple on/off messages.

			== Full Momentary Setup ==
			For the best, most flexible behavior you want a foot controller to have full '''momentary''' behavior which means that when a switch is pressed an ON event is sent and when the switch is released an OFF event is immediately sent. An ON message can be a MIDI CC message with value greater than zero or a MIDI Note message with velocity greater than 0. The OFF message would be the same CC or Note number but with a value or velocity of 0. This sort of full momentary behavior is needed for tap/double-tap/hold disambiguation. Hold messages require full momentary behavior.

	If a pedal sends ON messages only (such as with pedals that send an ON for press but send no release message), the messages will be seen as HOLD messages when MIDI learning.		If a pedal sends ON messages only (such as with pedals that send an ON for press but send no release message), the messages will be seen as HOLD messages when MIDI learning.

	MIDI ~~Program change~~ messages ~~are less desirable~~ as ~~they don~~'~~t have on~~/~~off values.~~		=== Testing Your Controller ===
			To test your controller, use a MIDI Monitor app. A MIDI Monitor will show you what your pedal is sending. We recommend using a MIDI monitor to see what your controller is sending even if you think you know how it is set up. It is somewhat common for pedals to be sending different messages than one thinks.

			We like the free ShowMIDI app (which can also run as an AUv3 plugin). Here is the procedure.

			* Launch the MIDI Monitor app as a standalone.
			* Press BUT DO NOT RELEASE the first switch and make a note of what message was sent.
			* Release the switch and make a note of what message was sent.
			* Repeat the press/release with the same switch.
			If you did not see the same ON message for each press '''and''' and OFF message for each release, your controller is not set up as a full momentary controller. If the controller is configurable, we recommend that you set it up as a full momentary controller.

			This video walks through the testing process.

			<YouTube>V3jRCKOR8W4</YouTube>

	~~Expression pedals that can send a stream of values are useful for controlling controls like faders, knobs and dials that respond to more than simple on/off messages.~~
	= Particular Controllers =		= Particular Controllers =

Edwards: /* Foot Controllers */

2025-10-03T21:04:08Z

Foot Controllers

← Older revision		Revision as of 07:04, 4 October 2025
Line 6:		Line 6:
	For musicians whose hands are busy during performance, footswitches/pedals are invaluable for controlling Loopy Pro. This page is a place for tips about using footswitches.		For musicians whose hands are busy during performance, footswitches/pedals are invaluable for controlling Loopy Pro. This page is a place for tips about using footswitches.

	'''Basic Setup'''. For ~~simple triggers~~, ~~it is preferred to have the~~ foot controller ~~set up~~ to ~~send~~ an ON ~~message~~ when ~~pressed and~~ an OFF message ~~when released. Typically, these messages will~~ be MIDI CC or MIDI Note ~~messages~~. ~~Other MIDI messages can also~~ be ~~used~~ but ~~offer less flexibility~~. ~~Expression pedals that can send a stream~~ of ~~values are useful~~ for ~~controlling controls like faders, knobs and dials that respond to more than simple on~~/~~off~~ messages.		'''Basic Setup'''. For the best, most flexible behavior you want a foot controller to have full '''momentary''' behavior which means that when a switch is pressed an ON event is sent and when the switch is released an OFF event is immediately sent. An ON message can be a MIDI CC message with value greater than zero or a MIDI Note message with velocity greater than 0. The OFF message would be the same CC or Note number but with a value or velocity of 0. This sort of full momentary behavior is needed for tap/double-tap/hold disambiguation. Hold messages require full momentary behavior.

			If a pedal sends ON messages only (such as with pedals that send an ON for press but send no release message), the messages will be seen as HOLD messages when MIDI learning.

			MIDI Program change messages are less desirable as they don't have on/off values.

			Expression pedals that can send a stream of values are useful for controlling controls like faders, knobs and dials that respond to more than simple on/off messages.
	= Particular Controllers =		= Particular Controllers =

Edwards: /* M-Vave Chocolate */

2025-09-17T21:39:55Z

M-Vave Chocolate

← Older revision		Revision as of 07:39, 18 September 2025
Line 33:		Line 33:
	=== Wired Connections ===		=== Wired Connections ===
	The M-Vave Chocolate (both the plus and non-plus models) can be used wired over USB rather than wireless. Make sure that the M-Vave is turned on. If you connect it without turning it on, the USB connection will be used for charging. You can transfer existing bindings in Control Settings from the Bluetooth device to the wired SINCO device. To do this: go into Control Settings, find the profile that has the binding, view the bindings and tap Transfer to bring up the panel that lets you copy or move the bindings.		The M-Vave Chocolate (both the plus and non-plus models) can be used wired over USB rather than wireless. Make sure that the M-Vave is turned on. If you connect it without turning it on, the USB connection will be used for charging. You can transfer existing bindings in Control Settings from the Bluetooth device to the wired SINCO device. To do this: go into Control Settings, find the profile that has the binding, view the bindings and tap Transfer to bring up the panel that lets you copy or move the bindings.

			'''Low Latency Setup'''. [https://www.youtube.com/watch?v=P1liZOVHqrg This video] walks through setting up the Chocolate for low latency operation that should be on a par with hardware loopers. In the video a wired connection is being used.

	== FCB1010 ==		== FCB1010 ==

Edwards: /* M-Vave Chocolate */ add note about wired connections.

2025-09-11T21:20:13Z

M-Vave Chocolate: add note about wired connections.

← Older revision		Revision as of 07:20, 12 September 2025
Line 29:		Line 29:
	'''Short Tread/Long Tread Mode'''. The Short Tread/Long Tread mode lets you set up a different messages to be sent for short and long press. This can be very convenient to send different message on short and long press, but it is important to understand that the response time is not as fast with this mode as with Manufacturer Control or the options that send an ON message immediately on press. In Short Tread/Long Tread mode, the short press message is sent on '''release''' of the short press. This adds about 120ms of delay to the sending of the press compared to the modes that send one message on press and another on release. The short/long tread mode has the advantage of slightly less delay for hold message than when mapping the same pedal to short and long press in Loopy Pro. When using this mode, you will want to have the short press send both an on and an off message so that Loopy does not interpret the short press as a hold.		'''Short Tread/Long Tread Mode'''. The Short Tread/Long Tread mode lets you set up a different messages to be sent for short and long press. This can be very convenient to send different message on short and long press, but it is important to understand that the response time is not as fast with this mode as with Manufacturer Control or the options that send an ON message immediately on press. In Short Tread/Long Tread mode, the short press message is sent on '''release''' of the short press. This adds about 120ms of delay to the sending of the press compared to the modes that send one message on press and another on release. The short/long tread mode has the advantage of slightly less delay for hold message than when mapping the same pedal to short and long press in Loopy Pro. When using this mode, you will want to have the short press send both an on and an off message so that Loopy does not interpret the short press as a hold.

	Here is a [https://www.youtube.com/watch?v=-rBegPTAGSs video] showing the expected response at a buffer of 256.		'''Expected behavior via Bluetooth'''. Here is a [https://www.youtube.com/watch?v=-rBegPTAGSs video] showing the expected response at a buffer of 256. [https://www.youtube.com/watch?v=i3ouyfAW6io Here] is another quick and dirty demonstration.

			=== Wired Connections ===
			The M-Vave Chocolate (both the plus and non-plus models) can be used wired over USB rather than wireless. Make sure that the M-Vave is turned on. If you connect it without turning it on, the USB connection will be used for charging. You can transfer existing bindings in Control Settings from the Bluetooth device to the wired SINCO device. To do this: go into Control Settings, find the profile that has the binding, view the bindings and tap Transfer to bring up the panel that lets you copy or move the bindings.

	== FCB1010 ==		== FCB1010 ==

Edwards: /* M-Vave Chocolate */ add link to latency demo

2025-09-11T21:07:15Z

M-Vave Chocolate: add link to latency demo

← Older revision		Revision as of 07:07, 12 September 2025
Line 28:		Line 28:

	'''Short Tread/Long Tread Mode'''. The Short Tread/Long Tread mode lets you set up a different messages to be sent for short and long press. This can be very convenient to send different message on short and long press, but it is important to understand that the response time is not as fast with this mode as with Manufacturer Control or the options that send an ON message immediately on press. In Short Tread/Long Tread mode, the short press message is sent on '''release''' of the short press. This adds about 120ms of delay to the sending of the press compared to the modes that send one message on press and another on release. The short/long tread mode has the advantage of slightly less delay for hold message than when mapping the same pedal to short and long press in Loopy Pro. When using this mode, you will want to have the short press send both an on and an off message so that Loopy does not interpret the short press as a hold.		'''Short Tread/Long Tread Mode'''. The Short Tread/Long Tread mode lets you set up a different messages to be sent for short and long press. This can be very convenient to send different message on short and long press, but it is important to understand that the response time is not as fast with this mode as with Manufacturer Control or the options that send an ON message immediately on press. In Short Tread/Long Tread mode, the short press message is sent on '''release''' of the short press. This adds about 120ms of delay to the sending of the press compared to the modes that send one message on press and another on release. The short/long tread mode has the advantage of slightly less delay for hold message than when mapping the same pedal to short and long press in Loopy Pro. When using this mode, you will want to have the short press send both an on and an off message so that Loopy does not interpret the short press as a hold.

			Here is a [https://www.youtube.com/watch?v=-rBegPTAGSs video] showing the expected response at a buffer of 256.

	== FCB1010 ==		== FCB1010 ==