What's your use case where you want more outputs than inputs? At home I run a Audiofuse 16Rig with a lot of ADAT expansion to get 32i/32o, but I only use like 6o, while every input is used.
The project just exposes everything the hardware can do, the audio codec chip used for the conversion is Burr-Brown PCM3168A 24-Bit, 96-kHz/192-kHz, 6-In/8-Out.
Some I can imagine are surround sound, multiple monitor pairs (including dedicated monitoring channels for different musicians or simply different outputs for mixing).
My partner has been playing with one and its truly incredible, the sequencer interfaces and enhancements make it go from a toy to an incredibly powerful machine. The felucca project has a web interface and you can try out the software on its own without the hardware: https://hugelton.github.io/Felucca/webapp/try/
This has opened the flood gates for great new stuff to be written for it, and oh what a ride it has been these past few weeks! Simply the hottest toy in music-tech, bar none!
I did some bits with gen-1 logue-sdk, the NTS-1 could have been a platform like the OP but the processor is severely underpowered for the price in today's standard and discontinued shortly after.
Oh, nice .. yeah the NTS-1 was a bit of a victim of its Bill of Materials, in my opinion - a lesson learned by the Monome and Zynthian communities, meanwhile.
There sure is, and folks are doing some crazy things with it ..
For example: the Bent[1] and Turbo[2] synths from Sinevibes[3] are incredible.
A perfect example of how the platform was embraced by user-developers and pushed into extremely creative and inspiring territory .. surely other manufacturers will start to take note, and maybe someone, some day, will start shipping their instruments with compilers-onboard, to .. you know .. make it easier for kids to keep the bending going on ..
Fair question. No. Nothing is hosted or restreamed. Every episode is a normal YouTube embed from the rights holder's own channel, so the views and ad revenue go to them. The site just puts those videos on TV style schedule.
I think an aging is going to be a non-linear (not in time, but in brightness application) fade to an off white and de-contrasting add addition of grains (not white noise, but bigger grains/dust). What's hard about this is there's some threshold of believability. Real photos age surprisingly well even when very sun bleached, staying pretty visible right till the end. You want slow degradation that does actually remove some of the photo each time, from what I can tell. You might be able to get away with a literal dust layer on top for that though.
half a grand for a tablet with a PI as the core running a weak LLM seems ... bad. Maybe I'm missing the point, but this doesn't seem like a useful product to me.
"Self healing" doesn't sound like a feature to me. It sounds like the product so regularly borks itself it needed nasty safegaurds put in to not, and it was done in a weird way that's annoying to diagnose and fix. Your most stand out feature being it doesn't break it self isn't great. Otherwise, it's what? Fancy on-prem Alexa? Why wouldn't I just setup Home Assistant Voice?
I suspect normal HN readers aren't your target market, but I don't really see who is?
> Models will become so fast that UI will be generated on the fly
Tells me this author is a bit, uh, disconnected from the real world. Your time to UI being populated and the UI's familiarity are the product.
I'm working on a huge vibe coded app in Rust rn, but it's entire purpose in existence is to be way, way faster to open and use than the software it competes with. The difference in feeling of something that opens and is usable within ~10ms (so under 1 frame at 60Hz) compared to one that's 100ms or 1s is HUGE. Getting it to be fast, good UI isn't a single prompt, it's a huge amount of refinement, over many weeks.
The difference between software with very straight forward keyboard shortcuts and intuitive UI, guided and crafted for a human, is huge.
Right now, models particularly struggle to make good UI, because it's a human problem. It doesn't care how big text is, because it's reading HTML, not visually looking at the page. Even if you feedback loop it image processing, it's a long ways from making good UI, especially good UI 1-shot. Even if you assume this makes leaps and bounds AND that "frameworks" that make the UI share common design language across on-the-fly prompts AND that it caches UI's that the user likes, etc. etc. I think this is incredibly far off base.
Then there's the missing points of software not being all basic tools that the end goal is to make a SAAS for. Embeded software exists. We're a long way from it being smart enough to figure out when something is a hardware issue. Hardware harness that connect it every test point are ungodly expensive, and so will continue to need a human in the loop for the foreseeable future.
Or, to pick on different points
> Code review will die. [...] Unit tests might die too
Alright, but then you're first up to use the AI vibe-coded pacemaker, or large machinery, or medical diagnostic hardware, or car.
To quote Doctorow,
> There are no cars, only computers we sit in. There are no hearing aids, only computers we put in our ears. There are no 3D printers, only computers that drive peripherals.
I do think AI will change software development, but not everything, not universally, and not without consequence to quality that we'll have to learn the hard way.
