• 0 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle
  • For ntsc vhs players it wasnt a component in the vcr that was made for copy protection. They would add garbled color burst signals. This would desync the automatic color burst sync system on the vcr.

    CRT TVs didn’t need this component but some fancy tvs would also have the same problem with macrovission.

    The color burst system was actually a pretty cool invention from the time broadcast started to add color. They needed to be able stay compatible with existing black and white tv.

    The solution was to not change the black and white image being sent but add the color offset information on a higher frequency and color TVs would combine the signals.

    This was easy for CRT as the electron beam would sweep across the screen changing intensity as it hit each black and white pixel.

    To display color each black and white pixel was a RGB triangle of pixels. So you would add small offset to the beam up or down to make it more or less green and left or right to adjust the red and blue.

    Those adjustment knobs on old tvs were in part you manually targeting the beam adjustment to hit the pixels just right.

    VCRs didn’t usually have these adjustments so they needed a auto system to keep the color synced in the recording.


  • Pretty specific use case. A normal OS handleds time slicing and core assignment for processes and uses it’s judgement for that. So at any time your process can be suspended and you don’t know when you get your next time slice.

    Same with when you make wait calls. You might say wait 100ms but it may be much longer before your process gets to run again.

    In a real time OS if you have real time priority the OS will suspend anything else including it self to give you the time you request. It also won’t suspend you no matter how long you use the core.

    So if you need to control a process with extreme precision like a chemical manufacturing process, medical device, or flying a rocket where being 10ms late means failure they are required.

    However with great power comes great responsibility. You need to make sure your code calls sleep frequently enough that other tasks have time to run. Including things like file io or the gui.






  • It was something around 40 TB X2 . We were doing a terrain analysis of the entire Earth. Every morning for 25 days I would install two fresh drives in the cluster doing the data crunching and migrate the filled drives to our file server rack.

    The drives were about 80% full and our primary server was mirrored to two other 50 drive servers. At the end of the month the two servers were then shipped to customer locations.




  • I do use wireguard. Mostly because the proton app for linux is so bad.

    Look into how they have you setup port forwarding on linux using the official app. They want you to open a terminal and keep a looped script running as long as you are using it.

    Not only that but when I was testing it the script would start erroring out after about 5 min requiring a restart.





  • It’s a hot mess. Or it was 10 years when I was last forced to use it.

    I remember there was one setting I needed to adjust from time to time. However the menu tree it was in had been removed leaving it a orphaned tree. So you couldn’t get to it through the ui. The only way to get to the setting was to go to a unrelated page in the documentation and click on the goto link in it. That would launch the menu that otherwise didn’t exist. From there you could back up and get into the menu to adjust the setting.