Especially the reference section gives a good glimpse into the basic building blocks: Site/Collection/Playlist/Video
Something that is not mentioned yet but is I think pretty cool, is that you can freely move all parts of a hyper8 site - within, but also across hyper 8 sites (!) - e.g. you can take a playlist (directory on the disk) with all its contained videos and copy or move it to another hyper8 site directory, at any point in its hierarchy, and it fits right in without adjustments, ready to deploy!
Today/yesterday I also implemented prototypical subtitle support, an adaptive theme option and language customization scaffolding. It's going nicely! \o/ #hyper8
Worked on #hyper8 all day today, doing iteration over iteration on the playlist pane mostly. In the last hour or so then started wildly moving elements around on the page and realizing all of the opportunities when you take away all the attention-desperate design choices from platforms such as youtube. Super excited to be working on this, it's slowly really coming together. ⸜(ˊᗜˋ)⸝
Laid the foundation for the custom video player in #hyper8 this weekend.
What is going to stand out from most other (mainstream) players is a more conscious design approach to communicating the underlying resource usage (third screenshot).
It's still research, and a fine line to walk between being too cryptic to the less technically interested or being too didactic to those that really just want to watch a video without a sustainability sermon, but in the end I believe technology has to do a better job giving people insights for informed choices, and ideally I want to find one or two good ways to do it with this video player. :)
@freebliss I am following with excitement #hyper8 and plan to test it soon.. looks great!
It's kind of confusing, that 136p got a bigger load than 270p. Is it about different aspect ratio?
Otherwise I could imagine that an onion rings like nesting from inside (small load) to outside (bigger load) maybe could give a nice visual representation on the expected amount of data and time.
Frequently mocked for its absence in (even mature) applications, but can't happen here anymore ^^ ... behold one of the most annoying dropdown menus I ever implemented: Interface language change at runtime in #hyper8. \\o///
Development of the Hyper 8 Video System is actually bootstrapped onto a video publishing project (we're getting a first version of the https://derive.at video archive online, independent from big tech \o/). This week I picked up the first batch of release-ready footage and started using #hyper8 itself for transcoding the final files, so I'm now also iterating on the usability of that whole workflow.
Most recent additions are a more useful dashboard for tracking the background encoding jobs, webm support and overall more robust video metadata handling, and just today I added frame rate parsing and encoding settings (because I needed to convert from 60 to 30 fps).
Next on that front I want to attempt a proof of concept for providing some kind of continuous feedback from the encoding jobs, i.e. just plain redirecting some of ffmpeg's stdout/stderr to the editor - no promises yet though, need to do some exploratory coding first. :D
Official beta release is coming up in ... checks notes ... less than four weeks now! ᕕ( ᐛ )ᕗ
I began versioning #hyper8 today so release procedures for the upcoming beta can be put in place. If you're on Debian or Ubuntu, a first alpha release package (0.12.0) is available now at https://simonrepp.com/hyper8/docs/installation.html
Before you go wild with it, mind the alpha version fine print: "Hyper 8's browser interface performs destructive file operations on your behalf and pending wider testing the program should be handled with caution, on a well back-upped system." With that in mind, have fun! :)