Hey everyone,
Our next office hours will be held on Wednesday, October 29th at 2 PM EDT (6 PM UTC).
The meeting will be held on Big Blue Button. Use the following link to join: Spritely Office Hours
If you’d like to queue up something on the agenda ahead of time, please reply in this thread with your topic/question. Otherwise, just drop in and share what you’re interested in when we start the meeting.
These meetings are always a lot of fun and it’s nice to get a chance to talk to everyone.
Hope to see you there!
1 Like
Working on a simple streaming application and I’m not even really sure yet what functionality I will be pushing to a wasm binary, the app will be pulling mp3s from a third party website and sequentially streaming them possibly with some sound analysis or search over sound properties across the set of recordings. Not sure! But I’m sure I will find something to do with Hoot for this project.
1 Like
I won’t be able to join this meeting this time (I’ll be driving on my way to work), but I do wanted to ask.
I’m pretty interesting in working on making Hoot’s backend applicable to more than just WASM, and the first idea I have is to add a command-line option called “ir-dump” that basically dumps out the current state of the bytecode right before it gets transformed into WASM (So CPS already performed on it and stuff)
What part of the code handles that, and how would you go about handling it?
1 Like
Hey @ValorZard. You probably don’t really want to use Hoot itself for that, but rather extract a piece of the compiler pipeline and repurpose it. (hoot library-group) is the module you want to check out. It’s a representation of a Scheme program + its entire dependency graph. It gets lowered to Tree-IL form as a giant letrec.
1 Like
Just a reminder that we’re at that time of the year that daylight saving time can mean the meeting time has shifted a little bit, please remember to double check when it is in your timezone!
Our best meeting yet, IMO! Here’s some notes from the meeting!
- Game jam
- Ridley’s question!
- op:listen, wants-partial?, what’s the deal?
- Projects in development!
- Bloblin
-
Navi
- OCapN
- possible use case for a hoot wasm application
https://xeno-canto.org/
mp3 files primarily, API available
simple js for the UI, WASM hopefully for audio analysis and search
Simple description:
a streaming application that loads birdsong files from xeno canto according to audio properties, think musical qualities, allowing a user to search xeno canto for a speific
kinds of sound files and also share them with others.
Question I came with:
how realistic is it to write the audio analysis algorithms in guile, use hoot to compile these algorithms to a wasm binary so that you are doing audio analysis in the browser without having to hook into ffmpeg or even numpy or something like that. Use case is then essentially:
load webpage and it calls out to xeno-canto’s api, it queues up a number of mp3’s which it would hand off to a wasm binary that can either process it or read a tag that allows it to search over other properties it keeps in a sqlite or something
Resolution to the ocapn conversation:
1. Always share the settled resolution of a promise
2. Always share when a promise is now pointing at another peer (this also allows detecting cycles)
3. This means we can drop `wants-partial?` as a flag altogether
Discussion of OCapN interoperability implementors working group (you have to working on an active interoperable implementation to be speaking at these)