/tech/ - Technology

Let me mention gallery-dl, which is an extremely useful tool for gathering large volumes of images and other media from most online art gallery places.  It even takes Nitter/Twitter URLs, although the default output file paths are weird.  You can find it easily with a search, either on Github or the Python file hosting community.

>shotcut
My copy of Vegas is getting kind of old, so I figured I'd give it a shot.  It's pretty lean and smooth, which I like, but every time I jump to a different frame in the timeline it plays the audio at that specific point.  Is there any way to disable this without disabling the audio from the timeline itself?  I'm on the wangblows version if that makes a difference.

>>128 (OP) 
>no Blender
unironically a good video editor, what other video editor allows you to render a spinning 3d cube on top of a video?

Also OBS decided to fug my shit up, might have to look into logs if it has any. So I had to fall back to the chad ffmpeg
[code]
ffmpeg \
	-f pulse -ac 2 -i default \
	-r 60 \
	-f x11grab $(slop -l -n 1 -f '-video_size %wx%h -i +%x,%y') \
	-b:v 4M \
	-b:a 80k \
	~/"$(date +%Y-%m-%d_%H-%M-%S)".mp4
[/code]
As long as you don't move the window around, it should be ok but isn't as good as Windows' gdigrab feature

I would also recommend Aegisub, absolute god tier subtitle editor - pretty sure most dedicated fansubbers use this program.

Is there an equivalent of WebM for Retards on Linux? It doesn't work under wine and I don't want to put in 100 different modifiers in a terminal just to make a file under 16MB or whatever the limit is for my Estonian bus enthusiast forums. A GUI is simpler for all the options it has. QWinFF doesn't have the features I want, most specifically how it dynamically changes commands to get it under a certain filesize.

>>143
HandBrake used to let you target file size in an earlier version but they removed it for some reason. You could maybe try using that version but it's quite old, it's 0.9.5. A more clean solution is probably some bash scripting, but that's out of my depth.
https://stackoverflow.com/questions/29082422/ffmpeg-video-compression-specific-file-size
The target file size feature in webm for retards never worked properly for me anyways. These days I just do the bitrate calculations manually. Target file size / duration. If you're using handbrake you might need to account for the audio bitrate as well. Hopefully some other anon has a better more retard proof solution up their sleeves. I have almost no clue what I'm talking about

>>143
> I don't want to put in 100 different modifiers in a terminal just to make a file under 16MB or whatever the limit is
It's 32MB here (literally read the post form, newfag), but are you really making videos that are so complex?  My default use case for encoding a webm or MP4 is like:
ffmpeg -i input.mp4 -b:v video_bitrate -b:a audio_bitrate -s resolution -fs 16MB -f webm output.webmwhich is hardly difficult to modify with a bit of trial and error, since the only things I ever really change are the video bitrate and the resolution.  I imagine you must be making something more complicated.

>>146
Unless I'm mistaken -fs just cuts off the video when it reaches the file size.

Is there a realistic replacement for GIMP at this point? Every update makes the UI worse and tools worse. It's become difficult to use these days.

>>223
Try Krita. It's targeted at mostly artfags, but it can also be used as an image manipulation program.

>>128 (OP) 
I have some txt files that i need to convert to mp4, any reliable program to do that?

How do you calculate estimated webm size, to help you pick bitrates without completely blind trial and error? I remember there was some method to do it.

1470505874679.webm
(194KB, 640x360, 00:05)

>too many packets buffered for output stream 0:1, conversion failed!
On my first day too.

>>238
I don't know that much about ffmpeg and conversion, but the only format that is reliably calculated is constant bitrate. As simple as taking the bitrate and multiplying it by seconds, just keep in mind that it's measured in bits. However, some sources say that constant rate factor is better, since it gives a less blocky picture during sudden movements as opposed to CBR. With CRF, there is no size estimation per se, you just specify a desired size and 2-pass encoding picks a CRF value to match that. I've seen a manual method mentioned, where it takes 5-10% of overall frames in the video and does a one pass encode with the value you specified. It's supposed to be fast enough to estimate size and play around with the settings, but I have no idea if it works.
On a side note, does anybody have that ffmpeg image guide that circulated around boards for video posting?