# MIdi Controls and a Dynamic Marker

**URL:** <https://community.capoapp.com/t/midi-controls-and-a-dynamic-marker/178>\
**Category:** Feedback\
**Tags:** workflow\
**Created:** [September 6, 2022, 3:04pm UTC](https://community.capoapp.com/t/midi-controls-and-a-dynamic-marker/178 "2022-09-06T15:04:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![w1nterl0ng](https://yyz1.discourse-cdn.com/flex007/user_avatar/community.capoapp.com/w1nterl0ng/32/82_2.png) [@w1nterl0ng](https://community.capoapp.com/u/w1nterl0ng)\
**Post date:** [September 6, 2022, 3:04pm UTC](https://community.capoapp.com/t/midi-controls-and-a-dynamic-marker/178/1 "2022-09-06T15:04:13Z")

</div>

In my current workflow, I use Transcribe!. I am trying to find a reasonable transition to Capo where my most used actions in T! are replicated in Capo.  
Here is where I am stuck, it includes the assignable midi commands, and what I can only describe as a dynamic marker.  
While I am transcribing, I have an audio file with the measures and beats marked out. (Capo seems to do a good job of this automatically, big plus). I set my “cursor” at a part I want to start working on. This creates a temporary “marker”. I use 8 buttons on a midi foot controllers for the following actions.

- Button 1 Down: Return to marker and Play, Button 1 up: Pause Playback
- Button 2: Resume Play from where playback cursor is located.
- Btns 3,4,5,6: Next/Prev - Beat/Measure
- Btns 7,8: Speed +/-

I think you get the idea. Some of these are covered but not others.  
I use a “sustain” pedal for button 1, and it is the most used button in my work, and for me the most important.

Thoughts?

---

<div class="post-metadata">

**Author:** ![liscio](https://yyz1.discourse-cdn.com/flex007/user_avatar/community.capoapp.com/liscio/32/3_2.png) [@liscio](https://community.capoapp.com/u/liscio)\
**Post date:** [September 7, 2022, 2:56pm UTC](https://community.capoapp.com/t/midi-controls-and-a-dynamic-marker/178/2 "2022-09-07T14:56:39Z")

</div>

> [@w1nterl0ng](#):
>
> Here is where I am stuck, it includes the assignable midi commands, and what I can only describe as a dynamic marker.

Let me try and improve this situation for you, at least a little bit.

First off, you want to enable the [Transcription Playhead](https://supermegaultragroovy.com/products/capo/help/mac/4.3/advanced-audio-playback/#transcription-playhead) to get your _dynamic marker_ functionality. On the Mac, you can toggle this using ⌘T (or assign a MIDI command to it.) Each time you press the play button, it will start from wherever the Transcription Playhead is located.

Unfortunately, I don’t think you’ll be able to execute these actions right now _exactly as you have them configured_\[1\]. That’s why I’m (very slowly, carefully) [overhauling](https://community.capoapp.com/t/whats-on-my-plate-right-now-improving-custom-controls/35) of this important aspect of Capo’s feature set. When I (eventually) get done with this, you should be able to set it up how you describe above.

* * *

1. Long story short: Capo’s current MIDI implementation is very simple. It ignores message values, so the sustain pedal on/off won’t get treated differently from one another. 😩

---

<div class="post-metadata">

**Author:** ![w1nterl0ng](https://yyz1.discourse-cdn.com/flex007/user_avatar/community.capoapp.com/w1nterl0ng/32/82_2.png) [@w1nterl0ng](https://community.capoapp.com/u/w1nterl0ng)\
**Post date:** [September 7, 2022, 4:23pm UTC](https://community.capoapp.com/t/midi-controls-and-a-dynamic-marker/178/3 "2022-09-07T16:23:40Z")

</div>

Thank you, I will enable the Transcription Playhead for now, I look forward to the other updates.  
Fred