Still, props to Bose for actively helping to keep their old devices usable.

[1] https://www.bose.com/soundtouch-end-of-life

Isn't it pretty bad for accuracy to accumulate large numbers of floats in this fashion? o.O In the example it's 640,000 numbers. log2(640,000) is ~19.3 but the significand of a float has only 23 bits plus an implicit one.

edit: Nice game, though. I wonder what it's made with. There seems to be a huge amount of generated shader code in the js. I wonder if that could be avoided.

  > Yes!
  > 80085 is 00000000000000000 in binary!

https://pastebin.com/5f1jwpkb

If anyone has ideas how to do this without root, get around the issue of calls being lower volume or remove the dependency on tinyalsa and termux, I'm all ears.

> It's for deep learning, not that much "for graphics".

No, while it is true that there is some overlap between the techniques and concepts used, gaussian splatting isn't necessarily "for deep learning". The library provides a differentiable rasterizer for gaussian splats. This basically means that you can ask it "if I want my output image to change in this and this direction, in what direction should I change the position / orientation / color / ... of my splats?". This enables users to plug it into other software (that is also commonly used for deep learning) and to optimize the parameters of the splats to represent a particular scene.

Since it's primarily a differentiable rasterizer for splats I think it's fair to say that it is "for graphics".

> The problem is "how do you do 3D deep learning 3D scene reconstruction" aka "how to make 3d equivalent of stable diffusion".

That it uses gradient descent doesn't mean that it is "deep learning". There are no neural networks or layers here.

It's not an "equivalent of stable diffusion". The way it's used now is to learn a representation of a single scene, not unlike photogrammetry. Sure, there may be other use cases for this library, but this is primarily what gaussian splatting is about.

  systemctl --user list-unit-files | grep -o "tracker-\S*\.service" | xargs systemctl --user mask

Only good phone I ever had. I wish things were as easy on Android devices, but somehow they almost never are.

At 1200 mm equivalent a picture is only about 1.15° high, so accuracy is important :)

> just measure it and then add a correction in your motor controller.

I think your first idea doesn't really work for tilting because there is little friction and the camera isn't going to be perfectly balanced (the center of gravity also changes with the focal length and even the focus). When gravity pulls the camera towards one direction backlash is less of a problem, but when it's near the tipping point it becomes really shaky and sensitive to disturbances. Past the tipping point it is biased towards the other direction.

Preloading might be an easy fix but at the cost of acceleration.

> Another way to do this is to always move back to endstop zero, and only move forward. THis is very limiting.

At least for panning in panoramas this isn't a bad solution at all. I think both your ideas are good for panning with planned paths.

> The biggest problem I had was all my PLA prints melted in the direct sun!

Was it white PLA? So far I've only had stuff bend out of shape in the car.

I've been trying to build something similar for tracking birds / panoramas / photogrammetry while avoiding using non-printed parts as much as possible but haven't been very successful so far. Because of that I'm particularly interested in the printed gears you are using. Maybe you could help me with some of my questions and concerns.

It looks like the whole thing is designed to be stiff, which means that the gears are pretty much at a fixed distance from each other. Doesn't that lead to backlash / play if the gears are a little bit too far apart or vibrations if there is too much pressure pushing them against each other? I've been worried about this and experimented with mounting the stepper motors on flexing parts to keep the pressure consistent and allow for more imprecision in the prints but I never really tried whether I can get away without that, so I'd be interested about how well this is working for you.

Pictures on the flexible motor mount idea: https://imgur.com/a/mM1Uql9

I would also like to know if there are any signs of wear after using the thing for a few days and what materials were used. I couldn't find anything on the type of filament on your website (did I overlook something?). I've only ever printed PLA so far and found that the gears would turn more smoothly after being used for a while. I imagine that the effect of wear might be different on the design without flexing parts.

Is it correct that the upper part is resting / sliding on "base-2"? Or is the bearing doing most of the work? Does it wobble at all? That was another one of the problems I had.

Anyway, I think this might be the submission you're looking for:

https://news.ycombinator.com/item?id=25357315

At least it's the one that came to my mind when I read your description. Being able to vividly remember posts from 86 days ago makes me feel a bit anxious about how much time I spend on HN and how much of my brain is allocated for storing what I read here.

  The second issue is that solving an overdetermined linear least squares problem is much more expensive than taking a few floating point reciprocals, and is also more prone to blowing up unexpectedly when you run out of precision.  There is some discussion in the paper about how to manage these issues, but it can become very tricky.  As a result, I did not get around to implementng this method in javascript (maybe later, once I find a good linear least squares solver…)

  initialize point at center
  for i = 1, 8 do
      project point onto each plane
      point := average of projected points
      constrain point to reasonable range
  end

https://i.imgur.com/utCcKYx.mp4

[1] https://github.com/SolidCode/SolidPython

Wikipedia on the human genome [1]:

> Protein-coding sequences account for only a very small fraction of the genome (approximately 1.5%), and the rest is associated with non-coding RNA genes, regulatory DNA sequences, LINEs, SINEs, introns, and sequences for which as yet no function has been determined.

Wikipedia cites [2].

[1] https://en.m.wikipedia.org/wiki/Human_genome

[2] https://www.nature.com/articles/35057062

Edit: Formatting

It gives an easy way to play with the coefficients and hopefully allows the player to gain some intuitions. For example how some combinations of frequencies lead to rotational symmetry and why negative frequencies are necessary.

It's not very polished, though. I made a mistake while writing the algorithm that checks whether the shape is matching. It causes some false negatives in certain situations. There might also be some issues with dragging the controls on Mac OS.

[1] https://coldiv.itch.io/fouriershaper