@simon @KaraLG84 @BorrisInABox @Bri @FreakyFwoof @TheQuinbox @Scott @pkirn i updated the manual (finally)

@jonathan859 @TheQuinbox @FreakyFwoof @Bri @simon @BorrisInABox @Scott @pkirn

@FreakyFwoof @Bri @TheQuinbox @simon @BorrisInABox @Scott @pkirn :)

@FreakyFwoof @TheQuinbox @simon @BorrisInABox @Scott @pkirn Sleep with your Move and you can update from anywhere!

@TheQuinbox 300% seems low

@pkirn I think it’s also worth noting my philosophy behind this project is to add things to move rather than replace them. We now have access to the buttons, screen, audio, midi etc so we truly could “add eight tracks” but it would mean, rebuilding all of the scaffolding to get there: sets, clips, sequence, automation, etc., etc. I will leave that door open for someone else. :)

@pkirn we’re all in a hacker discord together, back from when extending move started. There was some work to get the M8 launchpad Pro emulator working that works by killing the move and re-launching a new process. Everything just extends that to run code in the same process as the move binary and then all of the techniques to get access to the midi sound and screen. I wouldn’t have got there without them! And yes, branding is a challenge. And yes, branding is a challenge 🥴

@Scott @BorrisInABox @FreakyFwoof @simon @pkirn But, the move does USB-C audio. And before link audio came out I had a proof of concept, pushing multi channel out to a Mac receiver app, but I’m not sure that’s worth the squeeze given where link audio is. It should be trivial to build a desktop link subscriber to reroute to a black hole device for instance, if you wanted to reuse link audio for other DAWs.

@Scott @BorrisInABox @FreakyFwoof @simon @pkirn you really have to think of these like external sound modules connected to your move. Just without the cables. That means that sound wouldn’t get to your door unless you actually record it. I don’t do anything with the live or move project formats, but it will have the midi data in the clips. As far as exporting to other formats… That’s outside the scope of what I’m working on right now.

@pkirn And while I’m still cranking out ai slop ports of synths, there’s an important conversation about how these tools can make some of the work that always gets deprioritized much more accessible (and relatively easy)! An agent doing an accessibility audit and validating string coverage is work a human employee may never get remit to do – and, at least in my conversations with deaf colleagues about transcription for instance, an 80% solution is better than a 0%. Hopefully we can get to 100%.