Video Transcoding VS TiddlyWiki

I use this project by Don Melton to get a Blu-ray video down to an 8 - 10 GB file size: https://github.com/donmelton/video_transcoding

It uses HandBrake, FFmpeg, MKVToolNix, and MP4v2 with some custom tuned settings and has really good results from my experience.

I have primarily used Plex and pretty much everything you said is accurate for Plex as well. Limited transcoding based on the machine it is running on. As disc has become cheaper, I have pretty much stopped doing batch transcodes, which is great for the most part. But there are definitely negatives when you want to watch something offline, or remotely. Biggest pain point is subtitles though. Since they aren't ripped as text and then sent to a client, they have to be burned in to the video itself and transcoded on the fly. Which means losing out on 'forced' ones if it can't transcode fast enough.

Plex has definitely started to try and commercialize itself more and offer other stuff, when all I want is access to my own media. So I may look into Jellyfin more soon.

As for batch transcode jobs, I had a system that I was able to set up as essentially a black box. Drop a rip into a folder and out the other side comes a smaller one at a reasonable quality. With forced subs burned right into the actual video. Mostly based on https://github.com/donmelton/video_transcoding

I use Don Melton’s tools to transcode videos to mp4 files. His tools makes use of Handbrake but he has it tuned to produce very small video files of very high quality. You are unlikely to notice the difference when watching the videos.

Checkout https://github.com/donmelton/video_transcoding. In my experience produces higher quality and smaller files than handbrake alone.

When I was ripping my disc collection, I used Don Melton’s library. Don originally started the Safari and Webkit project at Apple but after he retired, he spent some significant time trying to create an easy way of compressing video but resting quality. Great collection of tools in my opinion that leverage handbrake for encoding. Good luck!

Check out https://github.com/donmelton/video_transcoding

I've been using Don Melton's Video Transcoding tool for my whole library. I upgraded my NAS to a Synology DS1019+ a few months ago, so now I have the space to store the untranscoded MakeMKV files. I've had issues with playback in my system, so I don't mind manually transcoding.

Check out https://github.com/donmelton/video_transcoding – I use it to turn raw Blu-ray tips from 30+ gigs down to 5-7 with no noticeable loss of quality.

> What does ownership mean here?

It means owning the code and the data. With webapps, the code and data are hosted and owned, the users do not own the code, cannot run it independently. This is a clear dileneation between owner and user, and the owners can use that clear line to create artificial scarcity of various kinds. (The most popular being the subscription SaaS model). It's also easier to defend your IP since end users never see your binaries.

I like to make my software single html files whenever possible. People can just save them and run them locally. Havent met anyone who cares yet though.

I like that idea a lot, and I care. I think others care, but yes, it's a niche interest. Take a look at https://tiddlywiki.com/ for an example of a fairly successful project that uses the single html format running locally. However it suffers from limitations on File|Save which often requires a separate runtime of some kind to support.

Another project that approaches this ideal is https://redbean.dev/, @jart's tiny, performant, featureful single-file webserver. In this case the "single file" is a server executable + zip whose state must be updated on the command-line, but I think hits a sweet spot in terms of practicality, and a global minima when it comes to minimizing dependencies. (Redbean bundles SQLite and Lua so it's also possible to do through-the-web state updates as in a traditional webapp.)

My own project, Simpatico, aspires to be something along these lines. Eventually your browser tab is both a client and server process, connecting via websockets to other connected browsers, storing all state locally. I call this pattern "monomorphism", a play on the "isomorphic" javascript SPA. The server[2] is currently written in ~1 node file, but eventually I would like to port to redbean (and greenbean, the websocket version of redbean, but it isn't quite ready yet). The server grew several features to support a fast, practical BTD loop using markdown[1], and safe, performant execution on the public internet[2], but ultimately I'd like to pare it down to serving a single html file and allow the connected clients to provide all diversity of experience. I've used it to explore all kinds of browser apis, from crypto[3] to svg[4] to writing my own libraries (combine[4] and stree[5]). And it's all running locally, and easily hosted on a $5 VPS, and its all open source.

1 - https://simpatico.io/lit.md

2 - https://simpatico.io/reflector

3 - https://simpatico.io/crypto

4 - https://simpatico.io/combine

5 - https://simpatico.io/stree

I use TiddlyWiki. It's a portable editable wiki that doesn't require a web server or web hosting. You open it from your computer, edit it, and save it. You get all of the linking that you'd expect to see in a wiki, and it's super readable and easy to use.

It is a single-HTML-file TiddlyWiki instance that runs in a web browser (offline as well as online), meant to be downloaded and stored wherever suits you best. Everything that you see when working in BASIC Anywhere Machine (everything that makes "BAM" work as an IDE and all BASIC programs) exist in the one HTML file.

TiddlyWiki still works as intended: https://tiddlywiki.com/#GettingStarted but there are so many different clients to run on. Mobile or Desktop ? What OS? What Browser?

This effort https://val.packett.cool/blog/tiddlypwa/ is remarkable as the mobile side of saving is not as robust as on the desktop side of things and there is a scaling limit on performance as the number of tiddlers grows. Also the syncing between tw documents between different desktop/mobile clients can be a challenge with diffing.

Since then I've moved back to plain vanilla vim for a wiki (map gf :tabe ) but tw.html is still good for data other than plain text and TiddlyPWA https://tiddly.packett.cool/ is a great effort to revisit TiddlyWiki again.

You should check out TiddlyWiki as it’s designed around the concept that small linkable notes are the best way to organize.

https://tiddlywiki.com/

It’s html based so you can access it in the same way you would access a website but it can be locally stored. Saving is a bit tricky but there are multiple solutions detailed on their site. https://tiddlywiki.com/

Hi, you can use tw on nodejs with npm package tiddlywiki....