wosa, it supports encode h.265 and decode h.265, please check the profile.

Harney  –  5 years ago  –  Vond je deze reactie nuttig? ja | nee (+32)

Vertalen

Louis Van Gendt,
"users have reported that the site ahead may contain adult material on some pages."
It is possible that people put some files on Stack, that are adult or dangerous.
But I can assure you, that I don't do that.
Therefore I did create a separate Stack to use for GOTD-files.
So no EXE, no adult, no copyrighted material.
And there are some files, that I have downloaded from the internet, but from sites, I gave the link here.
And also I took some photo's from tree's to do some photo-examples. All taken by me with my phone.
Also possible that some people just say that the site is wrong. Just say it. No proof.
Some years ago someone said, that it was not sure, that the converted file was converted with the GOTD-program of that day. It could also be done with some other program. Why should I put a file, made by another program than the GOTD-program?
And also that the file could be found on the internet. Yes, of course I put it there.
The only thing I can give is my word, that I will not put any stupid material on the internet. Nothing else.

Ootje  –  5 years ago  –  Vond je deze reactie nuttig? ja | nee (+16)

Vertalen

Lilien,

"Does this Software support cut/trim without complete reencoding (smart rendering)?"

Short answer = no -- editing is an added feature & not what these converters are designed for. Cut editing is easier technically speaking, since cuts & joins are only performed at key frames, and while it's probably possible using the ffmpeg these converters are based on, it's difficult & iffy, using scripts written for the specific task. To perform so-called "Smart Rendering", the software used must fully understand & be able to duplicate the original encoding method & settings, which often means an app will only smart render video that it's encoded itself.

How it works... The video in between key frames must be generated -- a key frame has a complete image, while the in between frames only record what's changed since the key frame. Generating those in between frames isn't hard, but, if you're going to cut or join video segments anywhere besides at key frames, that small portion of the videos will have to be re-encoded, so the in between frames match the new video. That's not a big deal for a video converter, since everything will be re-encoded anyway, but to smart render, that small, re-encoded patch & all video segments Must have matching encoding methods and settings.

mike  –  5 years ago  –  Vond je deze reactie nuttig? ja | nee (+16)

Vertalen