From b8622829c166c3b88445693b7ecdec53ed77af57 Mon Sep 17 00:00:00 2001 From: Albert Graef Date: Mon, 24 Sep 2018 22:05:09 +0200 Subject: [PATCH] Text and comment changes. --- examples/README.md | 4 ++-- examples/XTouchONE2.midizaprc | 8 +++++--- examples/nanoKONTROL2.midizaprc | 8 +++++--- 3 files changed, 12 insertions(+), 8 deletions(-) diff --git a/examples/README.md b/examples/README.md index cd88704..e65fbac 100644 --- a/examples/README.md +++ b/examples/README.md @@ -13,13 +13,13 @@ This folder contains a couple of sample midizap configurations for different con - [XTouchONE.midizaprc](XTouchONE.midizaprc): map the SCRUB key to the more important SHIFT key which the X-Touch ONE lacks -- [XTouchONE2.midizaprc](XTouchONE2.midizaprc): an improved config for the X-Touch ONE which turns the SCRUB key into an internal shift key, showing how to assign arbitrary MCP key combinations to the shifted keys +- [XTouchONE2.midizaprc](XTouchONE2.midizaprc): an improved config for the X-Touch ONE which turns the SCRUB key into an internal shift key, and offers more advanced configuration options Other interesting items: - [midizap.xml](midizap.xml): ready-to-use QjackCtl patchbay for all the sample configurations, auto-connects to Ardour - Installation: Open QjackCtl's Patchbay dialog, load the midizap.xml file and activate the patchbay. + Installation: Open QjackCtl's Patchbay dialog, load the midizap.xml file and activate the patchbay. To connect with Ardour, you also need to enable the Mackie control surface in Ardour's preferences dialog. - [x-touch-one.device](x-touch-one.device): X-Touch ONE device description for Ardour 5.12 (this is basically the X-Touch description with a bank size of 1, so that all tracks become accessible) diff --git a/examples/XTouchONE2.midizaprc b/examples/XTouchONE2.midizaprc index 86a9edf..8134b64 100644 --- a/examples/XTouchONE2.midizaprc +++ b/examples/XTouchONE2.midizaprc @@ -63,9 +63,9 @@ F8 SHIFT ^F8 RELEASE SHIFT ^F8 # bound these functions to the shifted bank and channel keys here, but of # course you can change them to anything you want. -# NOTE: You should configure a bank size of 1 for the ONE, so that all tracks -# become accessible. At least that's necessary in Ardour; a suitable device -# description for Ardour is included (see x-touch-one.device). +# NOTE: You might have to configure a bank size of 1 for the ONE, so that all +# tracks become accessible. A suitable device description for Ardour is +# included (see x-touch-one.device). ^A#3 A#3 C2 # BANK< SELECT ^B3 B3 C2 # BANK> SELECT @@ -113,6 +113,8 @@ F8 SHIFT ^F8 RELEASE SHIFT ^F8 # Experiment with shifted controls. This remaps the shifted fader, encoder and # jog wheel on the ONE to CC1..CC3. As these controls aren't used by MCP, they # can be assigned freely, e.g., to some plugin parameters, using MIDI learn. +# (To make this work in Ardour, you have to connect midizap's midi_out port to +# Ardour's MIDI control in port, in addition to the Mackie control in port.) # NOTE: Touching the fader also emits a note message (G#8), which will get in # the way with MIDI learn, so we disable it here. diff --git a/examples/nanoKONTROL2.midizaprc b/examples/nanoKONTROL2.midizaprc index e71cb80..70b7a76 100644 --- a/examples/nanoKONTROL2.midizaprc +++ b/examples/nanoKONTROL2.midizaprc @@ -16,9 +16,11 @@ JACK_PORTS 2 # Pass everything through (including feedback), except for the mappings below. PASSTHROUGH -# NOTE: This assumes that you run the nanoKONTROL2 in Cubase mode. Use Korg's -# editor application to enter that mode, or hold the SET and << keys when -# plugging in the device. +# NOTE: This assumes that you run the nanoKONTROL2 in *Cubase* mode. Use +# Korg's editor application to enter that mode, or hold the SET and << keys +# when plugging in the device. (Note that Ardour also has support for the +# nanoKONTROL2 as a generic MIDI device, in which case you can leave the +# device in its default CC mode and midizap isn't required.) [Ardour] ^ardour_ardour$