auto-editor VS io-ts

A few days ago I discovered a program that automatically trims the pauses from your video. This can decrease my raw footage duration by around 25%. I've used this for editing two videos so far, and this has been such a helpful tool.

Looking at the GitHub of auto-editor , I see it has a options page, and not being familiar with this app, I can see it has a pretty good display options.

auto-editor — removing silent portions from video recordings

auto-editor – Auto-Editor: Effort free video editing

Auto-Editor <--Is a command line application.

auto-editor can edit parts out based on motion and noise thresholds. I haven't found any settings I'm happy with though.

https://github.com/WyattBlue/auto-editor - to automatically remove silent portions of video recordings.

For those of us on Linux, check out https://github.com/WyattBlue/auto-editor: "Auto-Editor is a command line application for automatically editing video and audio by analyzing a variety of methods, most notably audio loudness."

However I have compiled it into a Windows binary which you can find here.Also a video I posted on using it is here.He also has a website for it here, from which you can also find a GUI version for Windows and Mac for a "donation" of $35 or more.

Qué rico. Si tenés chance meté un proceso de code review fuerte, y para el tema de I/O probá a usar https://github.com/Effect-TS/schema ó https://github.com/gcanti/io-ts que les da una solución obvia al tema de "tipos para lo que devuelva el backend", aunque es en realidad mucho más capaz que eso.

My fave is still io-ts (https://github.com/gcanti/io-ts/blob/master/docs/index.md) as I find it more flexible than zod at the ingress. The author is also working on the Effect ecosystem which also looks interesting.

I’ve been using io-ts for this and been very happy with it. [1] It’s similar to Swift’s Coding protocol in case you’re familiar.

[1] https://gcanti.github.io/io-ts/

Yeah, there are a few new concepts and it's not the easiest to pick up right away. The best introduction is here on the main documentation page.

We use https://github.com/gcanti/io-ts/blob/master/Decoder.md which has a very similar interface. It can even be used to mutate the data using https://github.com/gcanti/io-ts/blob/master/Decoder.md#the-parse-combinator.

A good way to significantly improve the reliability of your app is via improving type-safety by moving away from using any to unknown. One relevant example could be when you type your backend responses and when stringifying JSON to using unknown combined with some sort of runtime type checking. It can be done either by using built-in functionality like type guards or using an external library like io-ts, zod or yup.

Usage of TypeBox is similar with io-ts and zod, but it is much powerful and faster than them. Also, TypeBox can generate JSON schema very easily. Therefore, if you're looking for a validator library for new project and not suffering from legacy codes, I think TypeBox would be much better choice than io-ts and zod. TypeBox can totally replace them.

This check can be done with different libraries like: io-ts, typebox, or zod. These libraries allow you to create objects that represent your typescript definitions. Then, these objects can be used at runtime to validate the received data, in addition, you can also convert this object to a Typescript definition to have all the benefits of using typescript. These objects can be called schema validations because they are responsible for the data validation.