[bounty] [pipe] [developer program] loom generator

[m13v]

[please read the developer program description https://github.com//issues/1184]

• unique advantage: screenpipe allows users to create videos based on their desktop history. for instance, if a user encounters a bug they cannot recreate, they can still generate a video showcasing the issue. or sharing a time of your day with a coworker.
• inspiration: screen.studio provides excellent ux to draw from.
• use ai to narrate videos (voice and caption)

suggest other ideas, send us your plan, write comments, give feedback

[m13v]

/bounty 1000

[algora-pbc]

💎 $1,000 bounty • Screenpi.pe

Steps to solve:

1. Start working: Comment /attempt #1187 with your implementation plan
2. Submit work: Create a pull request including /claim #1187 in the PR body to claim the bounty
3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to mediar-ai/screenpipe!

Add a bounty • Share on socials

Attempt	Started (GMT+0)	Solution
🟢 @tribhuwan-kumar	Jan 22, 2025, 5:47:19 AM	WIP

[tribhuwan-kumar]

/attempt #1187

#804

Algora profile	Completed bounties	Tech	Active attempts	Options
@tribhuwan-kumar	20 mediar-ai bounties	TypeScript, JavaScript, Lua & more		Cancel attempt

[m13v]

hey @tribhuwan-kumar please first give us your plan, please read #1184

[tribhuwan-kumar]

Loom Generator

Unique Advantage: screenpipe allows users to create videos based on their desktop history. For instance, if a user encounters a
bug they cannot recreate, they can still generate a video showcasing the issue. Or sharing a time of your day with a coworker.
Inspiration: Screen.studio provides excellent UX to draw from.
Use AI to narrate videos (voice and caption)

loom pipe is half baked, i've to do ui improvements and a better ux to easily share videos over tg, whatsapp etc.
i've discussed about this pipe in #804

[m13v]

i see several discussion points, which one of the features do you want to work in this project, ui/ux or sharing or audio video integration first, pick one?
1.
Audio and Video Integration: Adding audio functionality to the "loom pipe" to enable recording and merging of audio with video. High-quality video recording (e.g., 30 fps) with audio sync is a priority.
2.
AI Enhancements:
Generating video descriptions with AI, including timestamps and voice narration.
AI chatbot integration for interacting with videos (e.g., asking for tweaks or insights).
Video Management: Implementing a history feature for users to manage, delete, and organize recorded videos.
3.
Sharing Features:
video sharing, including potential use of local solutions.
easy video sharing links or clipboard copies.
4.
Improved UX:
Adding a UI timeline with video frames and associated audio chunks for better navigation.
Prototyping a more intuitive user interface.

[tribhuwan-kumar]

audio video integration first, pick one?

I've talked about this here, we can't implement it until unless these is atleast 15 fps video & recording high fps videos 24*7 will take soo much space.

AI Enhancements:
Generating video descriptions with AI,
including timestamps and voice narration.
AI chatbot integration for interacting with > videos (e.g., asking for tweaks or insights).
Video Management: Implementing a
history feature for users to manage, delete, and organize recorded videos.

I've implemented in my branch, I just need to refactor a little bit

[m13v]

the first project could be just to make the pipe more stable, show more ui/ux elements, e.g. loading animation, progress bar when generating new videos, integrate it with timeline ui (now renamed to rewind) to select a specific snippet to export from your screen, rather than a 30 minutes chunk

[louis030195]

@tribhuwan-kumar

btw since we shifted to new pipe system, you can publish the pipe loom

https://docs.screenpi.pe/docs/plugins#developer-cli

i recommend you make it paid and later you can connect your stripe account to get payouts

making it paid make people more engaged and likely to give you feedback

check the doc how to publish, should be just about taking your dev api key in the settings and doing this:

eventually the pipe could be in your own repo if you want or here as you prefer @m13v wdyt matt?

# go to the pipe folder - i recommend you rename the folder to just "loom"
bun run build 
bunx @screenpipe/dev create --name loom --paid --price 20
bunx @screenpipe/dev publish --name loom 

this will publish for $20/m

when you need to update just bump the package.json version and do

bunx @screenpipe/dev publish --name loom 

any feedback on the DX appreciated ofc to make it better / document better