An Architecture for a hardware-software system

You are to design a single camera software, various client applications, and a communication model for a family of cameras. Each camera runs the Android OS, and will be crafted to make several variants; each of which takes up different forms. Each camera has various channels and interfaces to communicate with. Variables in the camera variants: headless or on-device display ie, the camera may be wireless only; it may have an LED as an indicator, or it may have an OLED or LCD perform on-device analytics not each camera is allowed to perform on-board analytics; some could do stabilization, some face detection, some motion detection, some may perform all. This is limited by what algorithms the customer buys. camera sensor resolution, fps, camera lens every variant has a different sensor and lens specification multiple camera sensors some cameras might have multiple sensors; thermal, near IR, or visible light motor-driven PTZ the camera might have a pan-tilt-zoom driven by motors

Lessons from drumming classes

Now, my drums teacher is quite a strict man. He's been teaching for over 10 years and has performed all over the country for another 10 years prior to that. Not everyone approves of his way of teaching, and he ensures he admits only those students fine with his strict ways. I've been attending two-hour classes once every Thursday, for the past 4 months now, and he has not yet let me play simple quarter note exercises. Most drum classes teach this during the first couple of weeks; some even start with these on their first day. He, on the other hand, has forced me to learn how to read notes, practice every exercise from the slowest 60 beats per minute to 240 beats per minute, and engraved in my mind that a great drummer is not one that can play a jazzy riff or perform a fancy dynamic, but one that understands drumming is all about timekeeping. Here's a list of parallels I've drawn from my life outside of drums. I ignored understanding Fourier transforms in my 1st yea

False coloring a video in real time using lookup tables

I've been working on OpenGLES very intensively for video rendering and applying real-time filters for months, and I haven't yet put up a blogpost on one of my favorite filters yet. I love it because it shows how fast and simple things can be in the GPU if you know how to use it well; What you have to do is given a greyscale image, false color it with a provided mapping from grayscale to RGB values; i.e., Grey [0,255] --> R [0,255], G [0,255], B [0,255] In a traditional CPU world, this is fairly simple. All you have to do is loop the image for each pixel, and use the mapping to convert the grey pixel to an RGB. But this is insanely slow, and cannot be done in real time. In comes the GPU! It's perfect for repetitive tasks, like this simple image processing problem where you have to apply the same function to every pixel of an image. Here's what the output looks like. The center image is the original greyscale image. My favorite color palette is the one o

Fully Duplex Multi Client Socket Communication

I’ve written a small, complete and reliable socket communication library. I wanted to avoid using the nio package and use the default ServerSocket and Socket classes provided in the package. Fully Duplex; Async This means the server and client can asynchronously send messages to each other whenever they’d like. This is different than most libraries where the server is only listening for messages and responds when a client requests for some information. Multi-Client The server can host as many clients as the internal sockets implementation allows. Java’s ServerSocket implementation sets the size to 50 connections . The server can also restrict the number of simultaneous clients it’d like to host at once. Any client can send a message to any other client. Server-Client symmetric API Effectively, it really doesn’t matter who the server is; each device in the network gets a callback when a device connects or disconnects, and each client is assigned IDs by the ser

WiFi Direct on Android | IT IS TERRIBLE

Wifi Direct ; a  wireless communication channel that runs in parallel with your Wifi connection, guaranteeing point-to-point communication at speeds much faster than BLE. It sounds perfect for a local multiplayer game, or a camera peer network. It works up to 20 meters in open space and penetrates a single wall given your antenna is strong. Sounds perfect? I really wish it was. I spent over a month trying to ensure it works on as many devices as possible. In principle, it works exactly the same as BLE. You make your device visible for a wifi direct connection, and another device upon discovering it connects to the former. If you're planning to use Wifi Direct, I'd suggest you don't and figure out another mechanism. Here's a list of problems I faced: The SDK: The heart of the issue is each phone functions differently. The Android Software Development Kit ensures all devices above API 19 provide the same set of APIs, but the lower layers manufacturer implemen

Java's Primitive Datatypes are Signed!

It took me a whole 6 hours to write a color conversion from the YUV420P color space to the RGB color space. I thought I had a fairly good understanding of the various color formats (YUV420P, SP, 422, etc etc) and how to access individual Y, U, and V components; but I spent the better half of the 6 hours reading and re-reading the conversions and theory. The converted output's colors were completely messed up, and the images looked something like this: The colors are all messed up; but notice you don't see the 4 quadrant ghosts as you'd usually see in YUV conversions that go wrong. This hinted that my conversions/element access wasn't wrong.* Note, you needn't know what each of these really is or the formula of the conversion behind this. The crux of the problem was converting the given byte[] array input, to an int[] array output . I struggled because of a very simple yet hair-pulling gotcha; but it took me hours to realize where I was going wrong. All pr

Bhutan | Fun Facts

I really enjoyed traveling Bhutan, but there were several things that stood out, felt very out of place, or were just surprising and I thought this would make an interesting read. Naming Things The Bhutanese aren't very creative while naming things. Everything is Druk-something;  they have the Druk Airport, Druk Beer, Druk Bank, Druk Hotel, and the list goes on. The other common name is Tashi. You'll find an equal number of Tashi-somethings there. Escaping materialism but still expensive? Being the Buddhist capital of the world, preaching to let go of the material world and all its enticements, ironically it's a very expensive nation to travel. The government sets the price to basic necessities - traveling from place A to B, the price of fruits and vegetables, etc, and it is far more expensive than you'd expect. For a foreigner it's even more so - a fixed rate of $200 USD applies to anyone visiting without an Indian passport. Killing animals isn't okay,

Bhutan | Monasteries & Impermanence

I visited a couple monasteries in Paro. The fun part was always getting to know more about these places from the monks living there. As an Indian, you are allowed to roam around where-ever you'd like; but for a foreigner, the Bhutanese government mandates every visitor to have a personal tour guide - this is probably done in an attempt to increase jobs. There are guides who know French, German and Spanish! If you're lucky, you could ask to tag along with one of these foreign visitors explaining things in English. You'll learn a lot more than just walking about on your own. Inside one of the monasteries in Paro. I asked a tour guide how the monastery decides whom to admit, and how a monk spends his day. The procedure to get into a monastery is like you'd apply to any school - there is a short interview, and if there are vacancies, you get a free pass to daily meals, a room to stay in, and the companionship of other monks studying along with you. Throughout their lif

Bhutan | Lango & Thimphu

My plan for Bhutan was fairly simple from the time I planned the trip. I wanted to reach there, figure things out as I go, and spend a good 2 weeks - to just be.  I wanted to spend some time in a remote village, and some time in a busy city. And I did exactly that. I did nothing more than read my books, sit outside in the sun, and walk for long hours on quiet roads, to  just be.  I spent 7 days in Lango, a small village 7km ahead of Paro, at a homestay. Lango, just as the rest of Bhutan, is surrounded by mountains. There is only one road that passes through Lango - the one that takes you to Paro, and the entire village is built around this road. There aren't further smaller roads inside. There is a narrow river parallel to the road, a small stretch of which is adopted by a school to clean and protect from further pollution. It is probably one of the cleanest rivers I've seen in a populated locality. The frequency of cars passing by is probably one per a minute, and to my

Backpacking Varanasi

Banaras. A city confused between the history of its mythical past, present day religion and religious ceremonies, and the influence of modernization and the West. In under ten minutes you can go from feeling as if you’ve stepped into history, to suddenly a dejavu resemblance to yet-another- modern -Indian-city. From sitting in an electric rickshaw to spotting cycle rickshaws and normal autos, Olas and Ubers, pass by a Domino’s surrounded by several small vegetable stores, handicraft stores and pharmacies, see a Pantaloons or a large city mall, and in no time reach super crowded streets queued up by people in hundreds to visit yet another mandir. And if you walk a little further, you’d find yourself by the Ganga at a funeral ghat. All in 10 minutes. The city is full of color, graffiti-ed with imagery of Shiva, life all around you is alive - busy streets and constant honking, people rushing about but stopping for a second to pray as they pass the dozens of temples on every street. I