RVS_PersistentPrefs
player
| RVS_PersistentPrefs | player | |
|---|---|---|
| 1 | 2 | |
| 1 | 1,768 | |
| - | 8.0% | |
| 5.1 | 9.8 | |
| 2 months ago | 2 days ago | |
| Swift | TypeScript | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
RVS_PersistentPrefs
-
How to Write a Great Readme
I generally have a “What Problem Does This Solve?” section in my READMEs.
https://github.com/LittleGreenViper/LGV_TZ_Lookup#what-probl...
https://github.com/LittleGreenViper/LGV_MeetingServer#what-p...
https://github.com/RiftValleySoftware/RVS_Spinner#what-probl...
https://github.com/RiftValleySoftware/RVS_BlueThoth#what-pro...
https://github.com/RiftValleySoftware/RVS_PersistentPrefs#wh...
etc.
player
-
How to Write a Great Readme
vidstack is very light on technical details but starts with a concise intro and a screenshot, as well as relevant links: https://github.com/vidstack/player
payload is well-structured in general: https://github.com/payloadcms/payload
nanostores starts out with an intro and telling code examples, followed by lots of technical details: https://github.com/nanostores/nanostores
-
Show HN: Modern media captions parsing and rendering library (vtt/srt/ssa)
Hey everyone!
The motivation for this started with some initial exploration of how native captions are inconcistent and extremely limited with respect to positioning + styling across browsers. In addtion, existing captions work was glued inside player libs and all open-source parsers were ancient (e.g., mozilla/vtt)!
I wanted to modernize it all with newer web APIs such as `fetch` and `ReadableStream` and extend support out to multiple captions formats. I also noticed that a lot of popular players on the web in recent years started adding caption customization options. Turns out accessible captions can be legally enforced!
Do note that accessible captions not only includes sync/timing, but also an adequate set of controls to customize the style of the captions, ensuring they're readable for everyone. You can see an example of this on YouTube when you go to the captions and click customize.
It just seemed silly that probably every single company is internally building this type of lib which is insanely hard to get right. I built this to serve our accessiblity goals at Vidstack[1] where we're working on enabling you to build production-ready player quickly.
It took me about two weeks to build this and honestly there's still a lot of areas that need work but it's a great start. I hope you find it useful. You'll find a lot more helpful information in the repo.
I'll also leave you with this YouTube video where Dan Sparacio beautifully explains the complexities of building accessible media captions on the web at Paramount [2]. This is one of my favourite Demuxed talks. In there case, acessible enough to meet FCC guidelines _Highly_ recommend checking it out to learn more!
[1]: https://github.com/vidstack/player
What are some alternatives?
undb - 🚀 Private first, unified, self-hosted no code database.
mp4-muxer - MP4 multiplexer in pure TypeScript with support for WebCodecs API, video & audio.
LGV_TZ_Lookup - Server for Matching Long/Lat to Timezone
drop - File dropping made simple
LGV_MeetingServer - An aggregation server for meeting list servers.
earwurm - An easier way to use the Web Audio API for playback of UI sound effects.
novel - Notion-style WYSIWYG editor with AI-powered autocompletion.
revenut-web - SaaS metrics in a nutshell
analytics-next - Segment Analytics.js 2.0
nanostores - A tiny (286 bytes) state manager for React/RN/Preact/Vue/Svelte with many atomic tree-shakable stores
FPlayWeb - Experimental web audio player, including audio visualization and a graphic filter editor.