#emct

Write up done!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! At 3:27 on a Friday night!!!!!!!!!

Just a couple things I need to take care of now like the video demonstration, readme file, and tidying up the non-presentation view of the patch so it’s up to scratch with other Max for Live devices.

Finalised the UI, really happy with the way it looks now.

Added some nice buttons using the “live.” objects within Max.

As well as a button at the top that flashes when the Markov object bangs, so you can see if the device is functioning while it’s bypassed.

Also labelled everything in the plugin, so users can read what everything does in the help window in Ableton.

Still really behind on the write up - been a rough week.

presentation mode!

added a few quality of life features:

every time the user changes the order of the chain it rebuilds the model, so the flow of audio doesn’t stop

using live.thisdevice to essentially loadbang components when the olugin is turned on/ loaded

added nice live.numbox and live.buttons for the UI in presentation mode

need to add feature where when i clear the model it bypasses the plugin, so audio doesn’t stop while markov model isn’t trained

and still need to sort out the plugin working on multiple tracks 

had a tutorial with atau today,

he pointed out some extra features/ quality of life things that would be good to implement.

firstly was a bypass mode so you can hear the original midi input without having to turn off the device in ableton, was an easy fix with a couple of gswitches.

secondly was the patch’s ability to be active in multiple tracks at the same time, currently its a bit buggy - he suggested using # to assign individual keys to things, but haven’t really figured out what those things are.

last was an ability to store the midi that is coming out of the markov into sort of presets - potentially through writing this data to a midi file

to be honest, i think just setting up a new midi lane in ableton and recording/ resampling the midi from the markov track is a lot more straightforward and intuitive - so i might just leave as is

write-up is currently at 2200 words minus my bibliography

most of the development in max is meeting my expectations of a minimal viable project and I’m pretty happy with it to be honest, potentially I could mess around with the transition matrix to fine tune its output and I definitely need to tweak the UI and get a nice preview mode setup, but. that shouldn’t take long

can now devote some time to the write up, its due in less than a month!

on about 2.6k words right now

Added functionality for transport detection from Live using the plugsync~ object which detects every time playback is stopped/ started in Live, as well as a lot of other useful info -- seems to be a pretty decent solution for now

ok so i think i’ve managed to figure out a solution already! using borax!!! also i wonder what borax means

time delta between note-on values is used to set the timing of the metro object, which then bangs the markov objects, whereas previously the markov objects were being banged every time a new note came in from live

patch now detects multiple midi notes coming through at once

still unhappy with the way notes are being triggered, need to look into detecting note onset values and work it into the model somehow