Mhh, if I have evolved to a point where my experienced feelings and ideas are of such complexity that animal cues no longer suffice to broadcast them to the group self-awareness might have involved in tandem with the more complex nogging and not as a downstream feature.
We are working through what exactly that will look like at the moment.
First thing we think we want to add is comments to tracks.
Following this I want artists to meet other artists and to start sharing their fan base. Some kind of ‘connect’ feature that allows artists to chat and shows they support each other. Also if an artist shares a track they get mentioned on the home feed in some way.
Finally we want to add a full forum type thing like indie hackers as well as a blog for artist tips and advice.
This is great. Chapeau.
It's a little strange to select the muscle group one wants to target, what about a few primary and secondary dimensions such as explosiveness, endurance, strength, fat loss or aesthetics. Some way to more broadly describe what one is trying to accomplish.
The project is GPL licensed, if, however, you cannot use GPL licensed software do get in touch with support@img.ly and we'll make the package available to you under a different license.
There should be a table of contents at the beginning of the post. It's not very detailed, but expands as you scroll to each section.
I agree the reading time does not really convey too much useful info, the blogging platform is designed for simpler and shorter posts. Maybe a replacing it with a wordcount would be better.
FFmpeg is powerful technology, yet approaching it can be very daunting. So we decided to create an approachable guide for intermediate devs.
Feedback is very much appreciated.
Late 2020 I had the same thought, I was making screencasts and hated doing all the cutting to turn my 45 minutes of mistakes into a 3 minute video. So I made a similar script in Node, where it used ffmpeg’s silencedetect and instead of outputting a new video, it saved an EDL file that I could import into an editor like DaVinci Resolve, and then I could fine tune the edits.
As soon as that worked I wanted more - mostly just really wanted the process to be interactive and real-time, instead of the run-check-tweak-repeat cycle of using a script.
So I ended up down the rabbit hole of building a video editor instead of making screencasts, and now Recut exists (https://getrecut.com).
It’s basically an interactive silence remover. I still haven’t finished those screencasts but now I have an editor haha. While it’s pretty basic, it’s saving folks a bunch of time, and there’s lots more cool stuff I want to add between automations and basic manual editing features.
In my experience that approach will produce out of sync audio and video for long videos. Audio frames != video frames, so the cuts must be aligned to the video frames timestamps.
I hate the type of ‘instructional videos’ that have (likely programmatically) edited all and any short pause in the audio making the video appear as a 30+min continuous speak.
I mostly interpret this as ‘see me see me - I’m good!’ in stead of ‘let me try to educate you about this subject’.
All the natural pauses between sentences gives a much better and natural flow.
This also includes ‘oups I made a mistake .. and fixed it like this…’
Just like the line breaks in this comment serves a purpose;-)
I completely disagree. When I'm trying to learn something, I'd much rather sit through a short, efficient video than a 1 hour unedited video of someone including mistakes and rambling. Hell I generally don't even have the patience for videos in the first place and default to searching for text first unless I'm specifically looking for audio. But to each their own.
A bunch of non-breaking quick cuts is of course jarring and could be better, but what you describe with "mistakes and all" is too far down the other end in my mind. I would not want to sit through someone having to backpedal like that.
Agreed - I’ve been looking for a one liner to turn a series of stills into a gif for a while and buried in my todos is a note to read the documentation so thanks, I’ll read this when I’m done w/ a few other todos this morning.
Someone should do a gui for common tasks it can do line there used to be the Zenmap gui for nmap.
(Learning how to do those sorts of simple guis quickly in python of something is another holiday todo, if anyone has suggestions on that - all my tools thus far are gui based and I need to make sure as many folks as possible use them.)
A few years ago I went through exactly that kind of holiday todo list and created a few bash scripts for video-to-gif, gif-to-video, and image stabilization.
Here's the script I cobbled together from various internet searches for the video-to-gif one, it works well enough for that purpose and all you have to do is remove the video-to-PNG bits at the start.:
Thanks for the code! I'm going to pull down a copy and take a look and then later tweak it...
The goal is gonna be to have something where I can give it units of time as arguments and do clips. So for example, you could give it a dot mkv and say from 30 seconds in to 300 seconds in, take that into stills then create a GIF... or an aPNG but... I'll take a look, play around, I need to learn to read undocumented code better this will be a good exercise since it's not some possibly zero day malware that didn't get past noscript like the last time I did that...
(But to swing it back to graphics: there a reason people don't use apng more? The reason I got ages ago is PNG is more for line drawings, not raster images like what you'd normally use a JPEG format for, but it's my understanding you can play with settings and get a similar level of compression without the patent encumberment of things like GIF with aPNG, and that it's supported by pretty much every browser except for... [checks wikipedia] Internet Explorer[1]?)
Anyways TL;DR: sorry to wall of text you, I'm pounding caffeine and reading the news and jumping between several projects at once -- thanks for the code, I'm going to take a look later -- right now gotta switch locations in ~10 minutes like I'm a Tor circuit ;-)
Is it a popup. For example, as a text-only browser user, i.e., no Javascript engine, I generally never see cookie consent popups. (I also control whether cookies are sent via a localhost-bound forward proxy.) However I am starting to notice cookie consents placed in the HTML of the page. This is one example. The cookie consent is wrapped in <div> tags.
AMP actually looks great in a text-only browser such as links.
It may also be possible to remove a <div>-based cookie consent using a browser Add-On like uBlock Origin.
If it were up to me, cookie consents would be done via HTTP headers. The user could simply set their client to send an HTTP header indicating no consent. Something like
Cookie-consent: False
I use a localhost-bound forward proxy to selectively send cookies where they are actually needed. Thus it is not browser-specific. It works with any client, e.g., netcat.
I agree with this one. On mobile it's a full-screen capture, too. Totally overboard. Why would a reference guide even need cookies? If the author is worried about lawyers, I'd just ditch the cookie use altogether.
Never. If there's anything that browser developers hate, it's for their users to have fine control over what the sites they visit either save (or run) on their computers.
proof: they've had plenty of time, and even browsers that claim to be public services can't even keep the APIs stable for cookie/storage control.
Think you might have a editorial content left under the headline "Installing FFmpeg Check". There are instructions for installing FFmpeg (first I thought it was maybe some tool called "FFmpeg Check" to "check" the output of an FFmpeg command line, like in the above screenshot, but this turned out not to be the case :)
An example on how to seek and cut video exactly on it's "I-frames" would be nice. The few times I've searched, I've never really found what I'm looking for. Usually I just use avidemux to seek and cut to keyframes.
You shouldn't need to care about that; video formats should support clipping to non-keyframes by including the preceding GOP at negative playback times, so it skips to the frame you started the clip at.
(MOV in fact does support this, but ffmpeg doesn't play it back properly.)
I frames are full frames as far as I know - they are considered keyframes because you CAN physically jump to them. In between frames are going through temporal compression (all frames are going through image compression individually as well) which means they rely on the previous and next frame for information.
I'm learning ffmpeg to do some audio/visual manipulation for a backend service and was looking for the basics. This is perfect.
As far as feedback goes, I noticed when running through the guide that the following command is missing an -i flag:
ffplay -vf "drawtext=text='HELLO THERE':y=h-text_h-10:x=(w/2-text_w/2):fontsize=200:f
I've already learned a lot from the ffmpeg concepts section. Appreciate it.
I'd be interested how you arrived at this particular pricing. $20 per year seems crazy low to me, have you experimented at all with raising the price. Intuitively, I'd think that the next cut-off point is at $49, but that in the range below that the demand is fairly inelastic.
