Skip to content

Commit

Permalink
Merge remote-tracking branch 'origin/main'
Browse files Browse the repository at this point in the history
yes Please enter a commit message to explain why this merge is necessary,
  • Loading branch information
noahgsolomon committed Feb 20, 2024
2 parents 9dcc210 + cdd41f7 commit e32838e
Showing 1 changed file with 3 additions and 10 deletions.
13 changes: 3 additions & 10 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,6 @@
By Noah Solomon
Generate YouTube Shorts and short form content entirely automated. To run this locally, look into the generate/ folder. The build.mjs file is the one you must run to generate the videos.

The purpose of this project, [brainrot.js](https://brainrotjs.com) was to provide a seamless way to generate a short form video on any topic from multiple interesting personalities to extend my pursuit of making education more fun, intuitive, and absurd.
Below is a video demonstrating this project in use on [brainrotjs.com](https://brainrotjs.com).

We used various tools from the front to backend:
https://github.com/noahgsolomon/brainrot.js/assets/111200060/023c83f8-e88d-4d79-be10-346862f223e2

front end: Next.js, tailwind.css, tRPC, express.
backend: Docker, Express, PyTorch, Python, Flask, NodeJS, Remotion, OpenAI API, ElevenLabs API, Google Oauth, Google Custom Search Engine.
architecture: CloudFront, S3, Lambda, EC2, Vercel.

I ran into a ton of weird challenges. GLIBC incompatibility issues, rendering times of 8-15 mins (which is why I had to opt into using serverless parallelized computing, reducing it to 1 minute rendering!). Also, designing the whole rather complex architecture was quite the can of worms. Also, enforcing the google custom search engine to only return images which are publicly available was quite hard, but crucial as this is executed after much expensive laborious computation like transcript generation, audio subtitle inference generation, and more, so it is crucial it never becomes the bottleneck.

Public API's we used: Google Custom Search Engine API, OpenAI API, ElevelLabs API, AWS NodeJS SDK.

0 comments on commit e32838e

Please sign in to comment.