Had a glitchy encoder press on a unit. Fixed itself over time, must have been some mechanical issue like oxidation. Is the encoder being denounced enough if this happens on more units?

_{Sent with GitHawk}

After waiting 10-15 min for ML to reboot after installing "midi" beta, either nodejs app loses connection to the shell script or the shell script still hasn't finished.

Running the software update shell script manually does seem to drop by ssh connection during the install... maybe something there.

@ndonald2 I think this is the only function you should have to fix up... I hope. I don't quite understand how the button logic works, I tried to make it work, but no dice. I think the rest of the flow from User_Interface to Engine should be good to go once you are able to get the Button object working correctly.

The gestures I'm going to do are "hold encoder button, then press Tap or PlayStop button". Right now I only have one special command, to queue a StartTransport at the next Loop start. I'm sure we can come up with something to put in the other gesture... or maybe we just have it do something cheeky like tell a knock knock joke.

Might be nice to have an option to switch the clock to square wave for things that have trouble with 5ms pulse

_{Sent with GitHawk}

In order of importance:

• List stored WiFi creds
• Delete stored AP
• Edit stored password
• Sort by priority

Do some customer research to see if people would find it fun to have the outputs do rhythmic pulses

Don't plug in USB MIDI interface
Boot Missing Link
Press play button to start clock
Plug in USB MIDI interface

Results:
UI input is unresponsive but clock continues to output

Note: v1.08 of missing_link does have this behavior

din sync beta tester mentioned that her sequenced drums were off by enough time that it was noticeable. We need to be able to start the clock ahead of time to get things in sync.

Added status message to let user know PPQN is now 24

Steps:

Hold down PlayStop button

Press the Tap button

Results:

• MIDI StartTransport will trigger at the start of the next loop
• Releasing PlayStop and Tap buttons will not register as Tap or PlayStop commands

When performing with live instruments you need a way to reset the timeline when the live instruments go “off the grid”

Maybe first tap of tap tempo could reset the grid... this would be an optional thing of course. Reset Grid on Tap: yes/no

_{Sent with GitHawk}

Each track has a play/stop button and a plus and minus button to add or remove complexity from the sequence, and a loop size.

Play/Stop and the plus/minus effect the sequence on the next global quantum start.

Stop can stop immediately or at the end of the global quantum.

_{Sent with GitHawk}

If output is set to Clock, parameters are:

• PPQN, any arbitrary non-zero, non-negative int
• Clock type: short pulse, square wave
• Invert output: boolean

If output is set to Reset, parameters are:

• Loop Size, any arbitrary non-zero, non-negative int
• Mode: short pulse, square wave, HIGH while playing
• Invert output: boolean

Update to the latest version of Ableton Link and add support for auto start/stop

If libconfig expects a setting to be of a certain type and it is not that type, ML terminates.

If I don't have my MIDI interface plugged in on boot up, but plug it in after missing_link is already running, missing_link will not use it to output MIDI. Need to set up some kind of periodic scan for MIDI devices or something.

README still references the CHIP build toolchain. We can also eliminate/update the dockcross build scripts while we're at it.

It takes longer than 1 second to draw the scrolling text of a menu label that is longer than four characters. So you may after 1 second realize you want to advance to the next menu, but pressing the encoder button just redraws the same menu label, which may take you more than a second to realize is the same menu... it makes for some slightly awkward menu navigating.

make ch-init.service that will run after the system has fully booted, at the least make sure network is up.

If there’s an Internet connection, download latest application and system zips

If there isn’t internet install local zip from /ch/installers/system and /application

Install contents of zip files to their respective places

Run factory reset script

Run hostname script

Disable the ch-init.service

Reboot

_{Sent with GitHawk}

WIFI
ON
AP
OFF

Write to file and have nodejs look for that and act accordingly.

If set to OFF on boot don’t try to connect or set up AP

If set to AP on boot don’t look for network, just AP mode right away

ON would be current behavior

_{Sent with GitHawk}

For labels that are longer than 4 chars, would be nice if the label scrolled once and then displayed the value it is set to.

Have solder points for the other pins for hacking

_{Sent with GitHawk}

Refactor all the other code to work with a boolean.
Don’t have to worry about direction of knob turn, just toggle when there’s a knob change
Don’t need the switch anymore since it’s a bool

Have four play buttons that can start a clock, trigger sequence, etc

Pressing the play button waits til the next phase start to play its assigned output(s)

_{Sent with GitHawk}

Right now stop stops the clock immediately. It’d be good to have an option where the clock stops at the end of the loop for a more musical ending.

_{Sent with GitHawk}

I'd personally like to see MIDI clock/sync of Missing Link function a little more like it does in most drum machines. For example, this is the behavior that my Digitakt exhibits when acting as Master:

• As long as it is powered on, it is actively sending MIDI clock info to the slave device.
• When you press Play, the device sends a Start command.
• When you press Play again while mid sequence(Pause), the device sends a Stop command. Pressing Play again after being Paused sends a Continue command to resume play from the point at which it was stopped.
• When you Press the Stop button, the device sends a Stop command. Pressing Play from this state sends a Start command which then resets the sequence.

ML crashed when trying to open MIDI Port 1 when MIDI device wasn't connected. If can't open the port, then don't try to do any MIDI releated things in the code.

label: IP Address: 192.168.44.1
menu items:
192.
168.
44.
1

If currPhase - prevPhase is negative and phase is 0, output StartTransport now

_{Sent with GitHawk}