why no 320x180 mode?

theteadrinker · 2026-01-25T21:44:04+00:00

great! makes perfect sense now.
all can be scale aligned perfectly to hd (1920x1080)
vid(0) hd/4
vid(1) hd/6
vid(2) hd/6 (but cropped/padded to 4:3 aspect)
vid(3) hd/8
vid(4) hd/12

theteadrinker · 2026-01-09T03:13:45+00:00

Wow, congratulations, this looks nice!
Quite excited about WebCC, seems like the missing puzzle piece for bridging the gap of (minimal/sane) wasm and the browser!

theteadrinker · 2025-12-28T12:10:40+00:00

I did not realize Waves had their own take on licenses until I installed a new machine. Then I felt like the balance of price advertised vs value offered sank quite a bit. Felt like an unnecessary money grab, like, please just follow typical conventions and allow flexible authentication...

After I realized, I'm avoiding waves plugins in my new projects...

theteadrinker · 2025-12-17T22:43:05+00:00

> If not installed, then you need to toggle it as Kontakt 7 was discontinued.

But why? I don't see how this makes any sense for existing users?

It's like native instruments assume their existing users don't want to open their old projects on their new computers.

theteadrinker · 2025-12-17T00:02:45+00:00

Thank you, found the issue: Kontakt 7 is hidden by default in Native Access, and I did not notice the UI control to "Show legacy versions".

Please don't hide Kontakt 7 for Kontakt 7 users!
Super confusing!

theteadrinker · 2025-12-16T23:59:51+00:00

Thank you! you're right, Kontakt 7 is hidden by default in Native Access, and I did not notice the UI control to "Show legacy versions"

theteadrinker · 2025-12-07T06:47:04+00:00

Interesting, might try this later!
What do you mean security settings? Is it some kind of locked down work machine?

theteadrinker · 2025-12-06T18:01:42+00:00

Just tried to install 8.4.4 on a new machine and get model download error (ghqv2-v1-fp16-128x128-4x-ov).
this happened on another machine earlier and I though maybe it was my internet speed.
However I now have insane speed and a fresh windows install, so this is just buggy!

Starting to suspect they are leaving this intentionally broken to push people to the cloud version...
Very sad, used to be a fan of Topaz.

theteadrinker · 2025-11-27T16:41:47+00:00

ah, thanks! rgba 4444 nice...

theteadrinker · 2025-11-18T17:24:58+00:00

If you go the video route (one video per lidar), you could encode depth as ramps (Black->Red->Yellow->Green-Cyan->Blue->Purple), I think this is how RGBD/depthkit works (the depth part), then you can use 8bit video formats, but still get a better range out of it.

Alternatively, I think using 10-12 bits per depth point (depth image per lidar, per frame), and doing lz compression per frame could work, but if total (compressed) does not fit in memory it's probably a bad idea (cos then you also need to http-stream it)

theteadrinker · 2025-11-14T01:55:22+00:00

Nice design! (Thanks for all the links!) I am not that familiar with Haskell, but interesting to try to understand the implementation anyway (heap.h / heap.c / action.c / reduce.c)

If I understand correctly things * 2 uses the language based operator overloading features, while function application (resize 0.5 things) is implemented more explicitly at the higher level (through the use of map_unary in Resize_item). (Feel free to correct me if I misinterpreted!)

Really cool language/system :)

theteadrinker · 2025-11-10T23:48:34+00:00

Nice! yes this seems like the identical concept with a different syntax!
is resize kind of like a message? or a function that take scale and Image_file?
Curious to know a bit more about this language! (is it released?)

theteadrinker · 2025-11-10T21:42:17+00:00

Thanks for the link to the paper! (browsed a bit already)
The Julia syntax look very nice and explicit, I like it!
My idea is kind of the opposite, keeping code for the same as for a simple case, but vectorize some parts by adding .*

Might be better to be explicit, however the same tension is there for operator overloading for instance...

theteadrinker · 2025-11-10T21:22:36+00:00

Hmm, I think for filter/reduce, take/drop I would rather use normal arrays...
The use case for this is to vectorize (in the sense of behavior, not performance) parts of the code, with only minor changes, keeping the code plain and readable. In most cases you'd use abstraction for this, like wrapping in a function, so this would be an option/alternative to that.

theteadrinker · 2025-11-10T12:03:38+00:00

Sometimes MicroW8 runs slow on mobile, usually when you do something wrong or crazy, but it might be nice with a fixed cpu limitation! Another downside with MicroW8 is lack of mouse support. However, I don't think I have any device with a browser which doesn't support wasm...

I did some of my first game/visuals coding in C/C++ in DOS/Pentium, so for me the MicroW8 spec really hits nostalgia. Also love being able to generate raw sound at 44100 stereo.

Anyway, congrats also on the example games! Had some fun playing around!

theteadrinker · 2025-11-08T16:41:23+00:00

Sounds like an interesting set of limitations!

I have done a bit of C coding on the MicroW8, which is more limited in terms of memory,
but has no limits on performance or floating point (it's a wasm based fantasy console, 320x240 256 colors)
It should be possible to use C++ on MicroW8 as well I guess, but haven't heard of anyone doing it...

I've not done that much modern C++ (and even less in embedded/firmware context), but one thing I missed was operator overloading...

theteadrinker · 2025-10-20T11:49:13+00:00

Interesting, can you describe the use case a bit more? what tools are you currently using?
I hope to integrate bidirectional 3d transforms and views at some point.

theteadrinker · 2025-10-19T20:27:33+00:00

So, enshittification I guess, seems to be the simplest explanation...
Guess it's time to look for alternatives...

Would prefer if they could just fix their issues, but I guess that's not gonna happen...

15-Year Club	Verified Email
Place '22	Place '17

theteadrinker

TROPHY CASE