Hi! I’ve been using Claude for macOS and iOS coding for a while, and it’s mostly great, but it’s always using deprecated APIs, even if I instruct it not to. It will correct the mistake if I ask it to, but then in later iterations, it will sometimes switch back to using a deprecated API. It also produces a lot of code that just doesn’t compile, so a lot of time is spent fixing the made up or deprecated APIs.
The REDS-HEIG version you link to has more development activity, support for a wider variety of FPGAs, and a few other advanced features. My version has some neat features not found in REDS-HEIG fork, and usually aims to keep the interface more beginner-friendly and streamlined for use as student's first-contact with digital circuits.
Nice one. I used to have a large mp3 collection (now replaced by Spotify) and would have loved to use audiostreamer and Waypoint to get to it while at work.
I really like the idea of being able to track your overall progress. I use trello for all my tasks, but it always stays on the granular task level and it's sometimes difficult to see the bigger picture. Maybe you can explore this concept a bit more and work on a polished product?
Meditations actually was originally a Trello board. I built out a frontend that gave made it easier for me to see statistics and manipulate the individual cards (e.g. just click on one to cycle through labels). Eventually it became evident that it needed its own backend, so it's been through a couple large iterations since then.
I don't see it becoming a SAAS-type product, but I would like to make it easy to download and use at some point in the future. I like working on it, but I can only really get into major things when I have time between client projects.
Nice. I was actually looking for a simple image host with an API that I could use for a personal project, and didn't know about Pix. Ended up using Cloudinary, which is way overblown for my needs. Maybe I'll make an iOS port of your app!
That sounds like a great idea. I used to have a decent vinyl collection, and would often forget about some of the good ones I have after not playing them for a while.
There isn't any info on the github page. Could you describe a bit how exactly does it organize the music?
There's no info yet partly because I've been trying a variety of approaches, and I'm not sure yet which approach will work out best. The core of the tool is a scanner which extracts an audio feature vector for each track in your library. Armed with this feature matrix, we can apply clustering algorithms - the most successful so far has been a Gaussian mixture model. I'm currently working on a system which will hopefully improve accuracy by bootstrapping a feature selection model, using metadata tags as an initial ground truth for music similarity, thereby allowing us to reduce the actual number of features which need to be compared.
I started out imagining that this tool would continuously update the contents of my crates, but now I think I want it to be more of a manual process. I'm imagining it as an analysis and reporting tool more than an organizer; I'll ask it to identify the outliers in a given crate, or ask for suggested additions, then choose how to arrange things myself. This way, I can use the manually-curated organization of my library as additional training data for the similarity model.
