• 1 Post
  • 245 Comments
Joined 1 year ago
cake
Cake day: August 30th, 2025

help-circle

  • That’s tight fit. If you really need the two capture cards then that’s the room you’ve got to work with. If you can bring it down to just one card at the top that would be a lot better. I personally use a capture card that’s connected using USB3, which works very well and doesn’t require room inside the computer (even though I would have room).

    Most videocards have two or three fans on the bottom these days, with such a tight fit one of the fans can easily collide with the capture card. And even when it doesn’t it will have a hard time sucking in air from there. You can try and find a blower type card, but that would be a bit harder to find.

    And you wouldn’t happen to have a GPU inside the CPU? Because the iGPUs from AMD are very solid if you don’t need much in terms of performance (easily faster than the 1030 you mentioned). Otherwise two capture cards and a GPU is a big ask in such a small case.


  • The A series is pretty limited, I would go for a B series if you can find it. But keep in mind drivers for Intel on Windows are terrible and on Linux even worse. So that would not be a good time.

    There’s plenty of cards that would fit in 40mm, but your airflow would be pretty bad. Do you have a pic of the inside of your system? There has to be a way to make something more fit.

    But most 6600, 7600 and 9060 cards should be able to fit in 40mm. And with AMD the drivers on Linux are very good.







  • Thanks for trying it out. I would model something up, but don’t have time right now. It would also depend on the slicer used, the printer and the settings etc.

    It probably doesn’t matter that much and not be worth the effort unless it’s really what you want. But for a quick prototype just having it solid is fine and not worth optimizing.


  • I think Roetz 4.0 has done some experiments with this iirc. It worked fine, but it was more like one of those multi-color filaments as there is no way to control the color coming out of the nozzle. He tried with 2 different colors I think, but his setup had 4 wires of filament being pushed through.

    There is actually a relative long time between filament being pushed into the nozzle and coming out at the bottom. In between is a reservoir of molted and partially molted plastic, which is essentially a chaotic system. When extruding or retracting the filament, this is actually controlling the pressure inside that reservoir. This makes it extremely hard to get any kind of controlled mix.

    You also have the issue of the number of filaments required. Remember CMYK only works when printing on white paper, the white is an important component to the end result. And those don’t actually mix those inkts. They just print little dots close enough together for our eyes to lack sufficient resolution and thus see them as one mixed color. For a lighter result less dots are printed, for a darker result more dots are printed and black dots added to go even darker.

    So you would need to have 5 filaments being pushed into a single reservoir, which is a challenge. Then you’d never get perfect mixing, even if you machine the combination inside perfectly (look at how nice the machining on Roetz his nozzle was). The pressure inside would vary leading to some filament being pushed less that others, it’s a very unstable situation which makes it very hard to perfectly predict or control. And being it’s mixing inside that reservoir, there is very little control of how the color comes out. It wouldn’t be the same color from all angles due to imperfect mixing and the changing of colors would be a slower gradual thing, not instant. And the way the color presents is also dependent on the direction the nozzle is moving.

    The amount of material being pushed in would vary a lot, where we’d want mostly the same continuous pressure on the nozzle side. And when moving reduce that pressure to prevent stringing. Controlling this with 5 filaments would be borderline impossible and would require a high flow large diameter nozzle. So only very large high speed printers would work. Or the filament would need to be thinner, so less material is pushed in, but then you run into compression strength issues in the filament.

    I think for practical results, people either just paint it after the fact. Use a multicolor filament for cool colored results. Or use a different technique that offers prints in precise colors.

    There is this super cool 3D printing technique from HP that is abandoned now, but does kinda work like you say with CYMK and a white material. It uses inktjet heads to eject a ceramic powder to 3D print. It can make high resolution 3D prints in full color and when baked the ceramic is very hard, so the objects can be practical to use. The big issue with this technology is the powder clogs up the nozzles on the inktjet heads. Just like with printers when the ink dries and the head clogs, it’s a nightmare. So those machines need constant cleaning and supervision. When they work they produce amazing results, but the technology is such a pain in the ass, they stopped making the machines. I think they still make the material and heads tho, for people who are already using the machines. I think they are often used in medical settings where they paid a lot for the machine and keep using them.


  • Just a question, but why is the large gear solid like that? It’s probably printed at some low infill, so it shouldn’t matter much. But I think you can massively reduce printing time and material needed, while at the same time increasing the strength of the gear, if you were to switch to a spoked design.



  • I’ve got some bad news for you. Even with AI you still can’t make a full web app in under a day.

    You can make a fun little demo for sure, but that’s a long way away from a full web app. Even without doing any coding or using the computer, simply describing a full web app using pen and paper would actually take more than a day. And when it comes to actually making such a thing, there’s so many things besides the coding and even with regards to the coding you haven’t considered.

    This is a big issue with AI. It provides a shortcut to some sort of end result. Since people get a result, they tend to think they have actually achieved the desired result. But in reality most things are much more complicated and people often have entire careers specializing in one aspect or the other. There’s so much that goes on, without people not in the know realizing. Without being an expert yourself, you wouldn’t even consider those things to be important.

    Let me explain using an example. I can write words on a page. I could even think of a story and give it some structure. Does that mean I can write a book? Technically yes. Would that book be any good and people want to read that book? Probably no. That’s because I know enough about writing books, that I know I don’t know shit about writing books and would not be able to without years of learning and failing. Now AI could help me vomit out words faster. More words more quickly means I can get a whole book worth of words out in no time at all. But does that mean I somehow gained the knowledge of how to write a good book? No, because I didn’t learn anything. In fact I would learn less from using the AI than I would have simply writing down the words myself. Using a tool doesn’t magically grant skills that weren’t there before.

    A lot of people don’t understand this and shit out shitty AI books anyways, which then nobody likes. They shit out apps, which then nobody likes and they get abandoned almost immediately. They shit out “art”, which then nobody likes. And since they got to some kind of a result, they glaze the AI tools and say it’s amazing, even though the results were shit.




  • This is cool, good to see you wanting to learn and experiment with stuff. I would recommend you study on the different aspects of current and past OSes. Especially simpler older OSes can give you a lot of insight into what an OS is, what components it has and how those tie together. What you currently have I would describe more as a cool little UEFI demo program and less of an OS. But it’s a great start to build out from.

    I would recommend trying to decouple software from hardware. Currently your code is heavily tied to hardware, which is fine in a test environment, but can easily break if the environment is different. Another aspect I would recommend you do a deep dive into is task schedulars. Especially looking at early types like the one from Windows 3.1 compared to the one from Windows 95. These are often used as case studies in schools, because they are easy to understand and offer similar but different approaches.

    Personally I can also recommend trying to develop your OS for a simpler chip. That puts constraints on the project, which both limits the scope and also gives you challenges because of those limits. But that might be my personal bias, as I once developed a full fledged OS for the Intel 8051 as part of my university studies. This was back in the olden days tho, these days I would probably use something like an ESP8266 or ESP32.

    Keep up the good work, keep being curious and keep learning!



  • Reminds me of the first time I saw Sin and Cos lookup tables being used in early 3D gaming. The computers could calculate those just fine, especially with a math co-processor. But for 3D gaming it would be too slow to get a good framerate. So lookup tables were used to greatly improve the speed.

    Back on those days all sort of neat tricks like that would be used. Often done as little demo programs that were very impressive. Before the internet it was hard to look up something like that and the latest and greatest tricks weren’t written in books yet. So often little code snippets and demo programs would be shared amongst programmers using the sneakernet, so we could all learn and get better.