FFmpeg is indeed a powerful video encoder/decoder tool¹. It operates in the command line, as opposed to using a GUI. Command line is that black window you find by clicking [windows+r] and typing cmd then hitting enter. This is also called "command prompt". Once setup you enter ffmpeg commands in one of these windows to use it.
Here are the basic steps to "...
As of December 2018, Adobe Creative Cloud aps, such as Premier, After Effects and Adobe Media Encoder give you the ability to encode in ProRes without any post-hoc conversion.
If you don't use Adobe CC aps or want a free, open source tool, ffmpeg can encode video using ProRes, and runs cross-platform.
This ffmpeg command:
ffmpeg -i input.avi -c:v ...
Your KAZAM video features YUV444P pixel format which WMP may not support without extra filters. Using ffmpeg, run
ffmpeg -i in.mp4 -pix_fmt yuv420p -c:a copy -movflags +faststart out.mp4
You can also use ffmpeg itself to capture screen and sound on linux. Basic syntax would be
ffmpeg -f v4l2 -i VIDEO -f alsa -i AUDIO -pix_fmt yuv420p -b:a 64k cap.mp4
You should be able to tell just by looking at it. When you watch for motion and see a comb-like horizontal pattern, the video is interlaced. You could also try pausing the video at several points and looking for this pattern, but not every frame will look interlaced. Pause the video at points where there is quick motion, and step forward one frame at a ...
It's because you're using Adaptive Resolution, where AE will attempt to let you scrub through quickly, by reducing the resolution it shows in the viewer. Higher powered computers will be able to show higher resolution in the viewer more quickly.
There's an explanation in Adobe's help here:
Here's a way to do it with the blackdetect and trim filters.
First, a better way to get the blackdetect output is via ffprobe because it is capable of writing structured data such as XML, JSON or one key=value per line.
You do this using metadata injection:
ffprobe -f lavfi -i "movie=/path/to/input.mp4,blackdetect[out0]" -show_entries tags=lavfi....
Windows won't help you with this. There are several file info programs available. I use MediaInfo, which I like especially for the context menu entry "MediaInfo" that allows you to quickly open video files and view their meta data in the program.
It shows mostly anything there is to know about the video file. The information you are looking for will be ...
I tried kdenlive, so I'll post my findings about it as an answer. It didn't quite do the job, so I'm not going to mark this as the accepted solution.
kdenlive easily imports my clips in mjpeg+pcm, and flac. And looks like it can export through ffmpeg, which is what I want.
It has a feature to "set audio reference", and for other tracks, "align audio to ...
I've not used it, but Microsoft makes Microsoft Movie Maker. It might meet your needs.
There are also some open source video editors you might have luck with:
ShotCut - http://www.shotcut.org - kind of new, might be buggy
Blender - http://www.blender.org - it's a 3D modelling app with video editing capabilities
Lightworks - http://www.lwks.com - there's ...
You can extract the file name directly from the for replacement parameter. No need to set a new variable at all.
for %f in (*.mp4) do ffmpeg -i "%f" -vn -ar 44100 -ac 1 -b:a 32k -f mp3 "%~nf.mp3"
If you want to do more complicated string munging, it's much more intuitive in Powershell:
ffmpeg -i $_ -vn -ar 44100 -ac 1 -b:a 32k -f mp3 ...
I've tried a bunch of front ends for ffmpeg and finally settled on Tencoder. Widows only. It has a preset for ProRes and is very easy to customize so you can crete setting for often used formats or settings.
It is multithreaded and allows you to do batch processing.
All anyone might be able to say is that there are no known holes in the various players. (I don't know if that's true, just that it's impossible to know that there are no undiscovered bugs in a complex piece of code.) H.264 streams are complex enough to have lots of corner cases. They're parsed with speed-optimized code written in C and assembly.
I would get as far away from EE as possible. Using the x264 tool, and mp4box, you can convert and segment out the files which are ready to be streamed to any dash compatible players. Especially since you mentioned using batch scripts, this is a great solution I think.
This is a good guide: http://www.dash-player.com/blog/2014/11/mpeg-dash-content-generation-...
Sure, you have to combine the field extraction with interleaving.
ffmpeg -i video.avi \
-filter_complex "field=top[t];field=bottom[b];[t][b]interleave" -r 50 fld%d.png
where the r value is double the original frame rate (or the same as the field rate).
@DigiVision media gives a very good answer that covers the default way of installing it, I'd like to propose another method that is good for noobs and pros alike:
Chocolatey is a package manager, it's a bit like the Microsoft Store, except that it's actually useful, it's all free, and it runs on the commandline. With chocolatey, installing ffmpeg—and ...
The concat protocol is the wrong choice for most file formats. Transport streams like MPEG-TS are one of the few formats which can be concatenated this way. All this method does is a crude appendation of each input to the previous input. So, any format which has a metadata element, can't be concatenated this way as the metadata of the other files will be in ...
I can recommend Adapter.
It is a Wrapper for the ffmpeg package and does its job pretty well. Because of its easy UI.
You could also use ffmpeg directly via macports, but I think that Adapter is far easier to control.
I use VLC Media Player. It will play most any format and will play DVD straight from the disc. Play the video and slow it way down during a motion sequence using the little double arrows next to the time line. It will clearly show the interlace if it is present.
This is the command line I have used to encode ProRes 4444. If you do not include -bits_per_mb you will get low res results in Windows 10. Many posts do not mention this little aspect.
ffmpeg -y -f mov -i input-file.mov -vcodec prores_ks -pix_fmt yuva444p10le -profile:v 4444 -bits_per_mb 8000 -s 1920x1080 output-file.mov
ffmpeg -i in.avi -r 50 -filter:v "setpts=0.5*PTS" out.avi
ffmpeg -i in.avi -r 50 -filter:v "setpts=N/50/TB" out.avi
If you want to interpolate new frames, use
ffmpeg -i in.avi -r 50 -filter:v "yadif,framerate=50" out.avi
yadif is a deinterlacing filter, which is needed since the framerate filter does not operate on interlaced media.
As far as I am aware, there isn't a way to disable Mercury Transmit if the viewer covers the UI, unless you set up a key binding. You can assign a keyboard shortcut to the "Enable Transmit" function in the keyboard preferences (I use ctrl+shift+' as it's similar to the maximise window shortcut). You can then use this key combination to toggle the full screen ...
I've created a thumbnail provider available from here https://github.com/tom-gangemi/braw-thumbnail-provider/releases/tag/v1.0.
All you need to do is extract to your desired install location and run register.cmd.
Driver type ASIO Audio device ASIO4ALL v2
Aha, there we go. ASIO is designed to give only one program at a time access to the audio hardware. As I said, this is in principle a good thing, because it ensures the DAW can run trouble-free and without overly long latency or crippled sound introduced when the OS tries to combine the audio from different programs ...