auto-editor VS procedural-gl-js

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.

Nice writeup, I always like it when the shaders are highlighted like this. I got started in a similar way 7 years ago and have been making 3D terrains with THREE.js & WebGL since.

The real fun begins when you need to implement some sort of Level-of-Detail system and streaming in data to give the illusion of high detail everywhere without sacrificing performance.

Last year I released an open-source framework (https://github.com/felixpalmer/procedural-gl-js) for creating 3D terrains for web applications, you can see Uluru here: https://www.procedural.eu/map/?longitude=131.036&latitude=-2... (unfortunately the aerial imagery from our default provider isn't as high resolution as other places in Europe)

Great visualization and approach with compressing the tile data. Do you have a comparison of how much smaller the payload ends up being compared to simply sending PNG files?

I use PNGs to encode elevation data in my 3D mapping library (https://github.com/felixpalmer/procedural-gl-js/) and this does a pretty good job of compressing the data, for example in the ocean the PNG files are also very small as the image is mostly black. Different use case I now as your data is much more sparse, but I wonder how close the PNG compression would be compared to your approach.

Yeah, the React parts of this are very minimal. I'm not really sure what using it gets you, since it just manages a single div.

The _actual_ library that does all the work is here: https://github.com/felixpalmer/procedural-gl-js

- Tiny filesize means library is parsed fast. Package size is less than THREE.js thanks to code stripping

Check it out on Github: https://github.com/felixpalmer/procedural-gl-js/

The imagery comes from the Orthofoto dataset on https://www.basemap.at/ - the actual texturing is done by the Procedural GL JS library https://github.com/felixpalmer/procedural-gl-js