Do you know if the 1-second keyframe interval was also for reasons of compute time? (It allows each GOP to be encoded in parallel). It unfortunately seems a bit short for many streaming applications, and also prevents rate control from being tested.
At the moment, I run all codecs with rate control on in their constant quality mode. Perhaps this is not the right thing to do. On 03/02/2015 02:52 AM, Thomas Davies wrote: > The "Class A" JCT-VC sequences were originated at 4k or 8k and cropped > down for reasons of compute time. The 8k-originated ones (Nebuta and > SteamLocomotive) are very noisy and were shot with an early camera and > sensor. There wasn't much good 4k at the time HEVC started, and it would > certainly be good to get more. > > regards > > Thomas > > On 25/02/15 17:44, Thomas Daede wrote: >> The JCT-VC test set only includes three clips for video conferencing, >> which I don't think is sufficient. It also specifies a intra frame >> period of 1 second, which is not reasonable. It does not feature any >> 2160p test sequences either, which is a bit strange. >> _______________________________________________ video-codec mailing >> list [email protected] >> https://www.ietf.org/mailman/listinfo/video-codec > _______________________________________________ video-codec mailing list [email protected] https://www.ietf.org/mailman/listinfo/video-codec
