I'm aware that I could batch convert the pngs beforehand to strip the alpha channel, but the sequence of images is produced by another program, and having to preprocess the images each time I make a video would be less than optimal.Įdit: After stripping the alpha channel from each frame using the command convert in.png -background white -flatten +matte out. Is there a way to get around this problem? Is there, for example, a way to get the encoder to ignore the alpha channel (my pngs don't actually have any transparent elements)? Import, Import an AviSynth script into the current script. My understanding is that there is an alpha channel in the pngs, which the x264 encoder cannot handle. This filter produces a video clip by reading in still images. I get the following warning message Incompatible pixel format 'bgra' for codec 'libx264', auto-selecting format 'yuv420p'
Using the command ffmpeg -y -r 30 -b 1800k -i _tmp%04d.png -vcodec libx264 out.mp4 I am using ffmpeg, and want to encode the video with the H.264 codec.
I only just managed to get raw video working reliably on my camera with ML, so you'll have to wait a bit, but I'm going to post some test footage on here some time soon with a breakdown of my workflow.I am trying to convert a series of pngs into an mp4 video.
Free tools and references: Post about ImageMagick, VirtualDub and friends. From what I've seen myself and all the research I've done so far, going with Nuke is the way to go. Or, if you already have the frame files, look into Avisynths ImageSource. I know it's not exactly a solution for everybody considering the prohibitive costs, but if you have access to it already like I do, then it is definitely the way to go IMO.
I still like to run it through After Effects and Camera Raw first in order to knock down the noise in the footage first, but it really looks nice when all is said and done. x264 M-0.160.3009-4c9b076-gcc11 Patman QSVEnc 4.04 VCEEnc 6.02 AVSMeter 3.0.2.0 2.1.3.4 Beta New setting to use AviSynth portable even. I've even managed to plug a second TVIScale node in to get 3840x2160 resolution and it still looks mighty fine.
It has a node called TVIScale which multiplies the dimensions by 2(the width gets doubled and the height gets doubled) so the result is that that all those 960x540 raw videos shot by the T3i are at the ideal resolution to get automatically turned into 1080p footage using TVIscale. I've gotten excellent results using Nuke. # If you want 4K, use 4048 X (4048 / YOUR_ASPECT_RATIO) # If your aspect ratio isn't 2.5:1 you may want to change the second number # That works only if your TIFF files are named like this: 1, 2, 3, 4,, 678 For that you need 'G:\wasu\04d.png' to indicate a name of 4 characters long with the proper number of zeroes in front.
Are your PNGs actually named 1.png, 2.png, etc You write '0001, 00086', which seems to imply your files might be named 0001.png, 0002.png, etc. ImageSource("PATH TO YOU TIFF FILES\%d.tif", FIRST_FRAME'S_NAME, LAST_FRAME'S_NAME, FRAME_RATE, false, false, "RGB24") I made some named PNGs and that line worked for me in AviSynth 2.57. LoadVirtualDubPlugin(ScriptDir()+".\VirtualDub\plugins\msu_sharpen.vdf", "MSUSmartSharpen", 0) LoadPlugin(ScriptDir()+".\Avisynth-plugins\nnedi3.dll")
Scout72: I got amazing results using this AviSynth script for upscaling my 600D footage to 1920 X 768 (2.5:1) and sharpen it: ImageSource bug Perhaps ImageSource does not support multiple png layers. Magic Lantern isn't processing the RAW files at all - Except from cropping the borders. Avisynth ImageSource screws up the loading, ie creates the BLACK surround not visible in Reel.Deel's color image, must be some kind of Layer Info. It skips lines & columns to reduce the resolution and saves the result directly to the memory card. Mkrjf: You've got an answer in that thread.