Which part? The glass is an Epson BT-40 cut in half with some soldering to bypass needing both eyepieces; this cuts the weight & power consumption by ~40%. Mounted onto a printed carbon-fiber nylon frame similar to bone conduction headphones. The computer is a single-board computer I had lying around, but I will upgrade to 12-core 30W SBC next week. The battery is one made for video cameras, and I gave it a belt clip and strapped the SBC onto it. The SBC has camera & mic inputs as well as GPIO for whatever I want to add.
A custom, DIY smart monocle from off-the-shelf parts, 3d printing, and custom electronics: 1080p60hz, 8-11hrs of battery life on a belt-clip battery + computer combo, has wifi & lte/cellular, can run ML models on device. One third the weight of upcoming Apple AR/VR glasses and one-sixth the cost. Just having it working has increased my efficiency a ton without obstructing vision or requiring me to look at secondary monitors or phone.
Working on replacing my wireless keyboard and trackpad with some "gloves" so I can use it while on hikes or just generally outside. Then, gonna integrate some custom AR and ML/GPT.
Congrats on the launch Shah! I can tell you stayed up late giddy for this launch :D. As another peer building for video creators, I am delighted to see more efficiency features like this released.
This approach was the one I tried first also (I also tried the frequency one fwiw, which has its own, worse drawbacks). But using loudness runs into issues if the source loudness isn't (relatively) even across the entire source media. Using a single sensitivity setting like this would be a problem if:
* recording gain is set to automatic, and there are sudden changes in noise floor like wind (if recorded in 24-bit or lower)
* crew adjusts gain partway through recording (big no-no but happens)
* talent/host moves in and out of microphone sweet spot
* talent/host adjusts themselves in a squeaky chair during silence or transition-to-silence (or coughs, or breaths loudly, or ambulance goes by...)
If you apply the edit w/ a single sensitivity and something like the above is true, it would cut in the wrong place. Unfortunately, you would have to watch the entire show, skipping to boundaries with your full attention to know that ever got a cut wrong.
The black rectangles exist because the video is a different aspect ratio than your monitor. Not all displays have the same ratio, a monitor with a matching ratio will have no black bars on any side. So by nature, closed captioning has to be within the video bounds.
An offline-first web version of AE/Prem is what we're working on @ Vidbase. Internally, it works today better than the desktop apps imo. Others are working on similar tools as well.
I no longer see the warning on the readme, but, this relies on SharedArrayBuffer, so it is not currently supported on mobile
(except Firefox for android) and some other browsers: https://caniuse.com/sharedarraybuffer
While I was there, hapi.js was extensively used by the Global eCommerce department and was responsible for fronting the entire mobile API. You can check Eran's blog for stories of how it handled all of Walmart's mobile API traffic especially during the massive thundering herd of Black Friday traffic. It was used on many other projects including some "big name" projects, however, I don't know if hapi's involvement was made public for those so can't name them directly.
Most of the devs quit WalmartLabs a long time ago (including myself, Eran, etc). Sponsored in the sense that WalmartLabs paid us to use it to build their services and we developed hapi.js/joi to support our jobs.
I don’t know for certain, not op, but sounds like since they pushed the env file, it may have been accessible via URI and since it had all the credentials and host info to access the database, thats all the attacker messed with... and that is more than enough.
In some photos, you can see that from the camera's POV, the area around the actors is displayed on LED as green screen so the actors can be masked out. Then, a higher resolution background is composited in. Thus, the original LED serves to accurately light the scene to reflect the background but not always to actually be the background.
When I first saw Hasura, it was AGPL licensed which makes it unusable in a lot of use cases so we passed on it. Looks like they converted it to Apache license two months ago. I suppose it is worth another look, I'm glad they made the change.
Have you tried using Lerna for monorepo management? I see some projects using it, I haven't yet (no monorepos) but it claims to solve some of those problems. https://github.com/lerna/lerna
The latter should work but the former requires an extra step for now iirc: https://bun.sh/docs/cli/install#lifecycle-scripts