For those of you who went to NSNorth at Chateau Montebello, enjoyed your time there, and are in the market for a resort, this might be an interesting opportunity: https://youtu.be/ZeoNkWbA9nI
Chris Liscio
@liscio
- 232 Followers
- 64 Following
- 120 Posts
I write SuperMegaUltraGroovy software, such as http://capoapp.com. More recently, I'm also a grad student at the University of Waterloo.
YouTube
@amyworrall so very cool. I used to be a huge nerd about this stuff, and definitely burned through lots of wasted paper when I screwed up my settings. Good luck with it!
@schwa 64GB should be enough for anybody…
@schwa I dunno, man. Claude tells me its code is production quality all the time.
Sure, it has a 30GB memory leak at runtime. But I guess since it was trained on all that Electron code, I guess it’s true?
@steve @hikari Yeah—context is everything. A bag of notes, even when you arrange them by “pitch height”, cannot be reliably named. Rootless voicings, dropping the third, and other such changes to chords in practice make this a fool's errand.
FWIW, chord recognition infers symbols within a fixed vocabulary, and your performance/accuracy is helped if you allow it to say "not in the vocab.” A polyphonic note detector that names the output pitches would be painful to use in practice.
@steve @hikari are we talking chord recognition (from audio) or “suggest some nice chords” tools? Both might share some components (e.g., transition probability matrices), but they are applied in very different ways.
I happen to have more experience on the recognition side, but am happy to try and answer questions about either.
(Edit: on second read, it might be neither! 😂)
@chockenberry here’s hoping that you flip the script and kick 2026’s ass.
@gruber @dmd yeah. On iOS those kinds of views *must* be scrollable or else they are completely useless with even one or two bumps to the default text size. And figuring out the “will the content fit without a scroll view” code is highly impractical and prone to introduce other issues. (Not impossible, but hey—one dude here writing and maintaining the code!)
@dmd @gruber I have tried to achieve this "scroll hint" whenever I am faced with such situations. However, it's incredibly difficult to do on iOS because of Dynamic Type. There are some combinations of settings where your content will get clipped *just so* and the scrollability won't be obvious. Add window resizing to the mix on iPad, and various popover quirks, and this feels like an impossible problem to solve globally—especially for a one-person development team.
Full disclosure: If you signed up recently, (a) you probably need to re-sign-up and/or let me know if you still don't have a confirmation email, and (b) you *may* receive the 015 edition newsletter to your inbox in the next day or so.
I'm still working on the email export in my Middleman project, but I wanted to publish ASAP so that my in-app newsletter links don't still point at a page with a 3-year-old "latest post". 😛