291–300 of 1001 posts
I'm working on a voice cloning version of my TTS model, a highly upgraded VITS: https://x.com/ZDi____/status/2013655958027669958 Right now, I only have single speaker checkpoints (as per the old video). That will change soon.
As many here, I've found that a single text file is all that I really need, but found that it makes it difficult to keep track of a variety of things. I was also trying to use the file as a simple project tracker, adding some tags like [BUG-N], and updating them by hand. Eventually, it became difficult to track the progress of things, since I had to jump around the file to look for updates.. or use grep.
I condensed the idea to just that - a very simple tool which manages "trackers", and has a simple filtering built in to "trace" the updates. I've been using it, since I've added the BE, and dogfooding it a bunch. Would love for fellow note takers to take a look. It's not perfect, but I'm keeping it around for myself :)
Creating my own models in Blender for 3D printing. Currently creating replacement wings for a hummingbird whirligig yard decoration that broke a couple years ago. It’s a sentimental gift and I’ve hated the idea of throwing it away. Physical engineering is a huge welcome transition for me from what coding has become in the last couple years. There’s something nice about the realities of creating a model, then printing…
^^ project with my daughter
Parallel agents debate your ideas/work: https://murderboards.ai
^^ solo project / code review agents for non-coders / inspired by Compound Engineering plugin’s code review flow
Im building https://trypixie.com to legally employ my 7 year old child, save on taxes and contribute to her Roth IRA. Im also building https://www.keepfiled.com , a microsaas to save emails (or email attachments) to google drive I almost forgot, I also built https://statphone.com - One emergency number that rings your whole family and breaks through DND. I love building. I built all these for myself. unfortunately I…
button1 = create_button('Hello world!')
button1.on_clicked {
the_hello_world_button_was_clicked
}
# this is the verbose variant in a pseudo-DSL,
# I like things being explicit. In most code
# I may omit some parts e. g.
_ = button('Hello world!') { :the_hello_world_button_was_clicked }
I recently added the possibility to describe what kind of widgets are to be used via a yaml file, as an option. This may not sound like a huge win, but so far what I like here is that it becomes easier to modify individual widgets without having to sift through code; and it works for more programming languages too. Any customization for the widget, including method-invocations if necessary, can be done via a yaml file now. There is of course a trade off in that the yaml file can become a bit complex (if the GUI uses many widgets), so for the most part I use this for smaller widgets/components that do one specific functionality (or, few specific functionalities). For instance, a GUI over wget. Then if other larger programs need that, I make this small widget more useful and flexible.
The distant goal is to actually use a simple DSL that also would allow average Joe to customize everything in a very easy manner; and to have a widget set that can be used for as many different parts possible including wonky ideas such as having a whole operating system as a GUI available one day (a bit like webmin, but not limited to what webmin does; for instance, I'd also have games such as solitaire, reversi and so forth). I'd like to see how far that idea can go, but it is just a hobby so I can only invest little time into it.