Age | Commit message (Collapse) | Author |
|
Use cq_level (which is identical) from VP9_CONFIG instead.
Change-Id: I1aaf2fcef3d2dbd4577f613d27693ff8a68989fd
|
|
|
|
This patch sets up a quad_tree structure (pc_tree) for holding all of
pick_mode_context data we use at any square block size during encoding
or picking modes. That includes contexts for 2 horizontal and 2 vertical
splits, one none, and pointers to 4 sub pc_tree nodes corresponding
to split. It also includes a pointer to the current chosen partitioning.
This replaces code that held an index for every level in the pick
modes array including: sb_index, mb_index,
b_index, ab_index.
These were used as stateful indexes that pointed to the current pick mode
contexts you had at each level stored in the following arrays
array ab4x4_context[][][],
sb8x4_context[][][], sb4x8_context[][][], sb8x8_context[][][],
sb8x16_context[][][], sb16x8_context[][][], mb_context[][], sb32x16[][],
sb16x32[], sb32_context[], sb32x64_context[], sb64x32_context[],
sb64_context
and the partitioning that had been stored in the following:
b_partitioning, mb_partitioning, sb_partitioning, and sb64_partitioning.
Prior to this patch before doing an encode you had to set the appropriate
index for your block size ( switch statement), update it ( up to 3
lookups for the index array value) and then make your call into a recursive
function at which point you'd have to call get_context which then
had to do a switch statement based on the blocksize, and then up to 3
lookups based upon the block size to find the context to use.
With the new code the context for the block size is passed around directly
avoiding the extraneous switch statements and multi dimensional array
look ups that were listed above. At any level in the search all of the
contexts are local to the pc_tree you are working on (in?).
In addition in most places code that used to call sub functions and
then check if the block size was 4x4 and index was > 0 and return
now don't preferring instead to call the right none function on the inside.
Change-Id: I06e39318269d9af2ce37961b3f95e181b57f5ed9
|
|
Change-Id: I86b85b5c11388e84a48f8936330c0d920df5d1f0
|
|
Change-Id: Ibf360fe0728e07de448e77e3841c49eb25d3ba2d
|
|
Just to be consistent with min_frame_bandwidth & max_frame_bandwidth names.
Change-Id: I36702c708cba9ad1a5c36393f37758a2edeadb90
|
|
|
|
|
|
Change-Id: I988eea8f78f71135b914661420c5c75674e5c010
|
|
|
|
|
|
Change-Id: Ibec06411c8cd843c2ca33b528a511a656e551983
|
|
Change-Id: Id81a76d18be6b2de69f81bb563d74c3bb356d434
|
|
Change-Id: Id755813fd5e78039bc9e76a046b33c8cafbc36dc
|
|
Change-Id: Ie144e9ece57f2d59c230704a2f166bda1042adeb
|
|
Change-Id: I0f4a5c50561a2653d22c366c214a937272ecfa2c
|
|
Change-Id: Ie5723690f7c0bfa29a7ccef5da0c6c6326600ee6
|
|
|
|
|
|
Change-Id: Ic68caec1bcb8a88f443c3e40ce9770eade5bd320
|
|
Change-Id: If1b0a2d6603ce24f5dd99855e8dfe459e7a2835a
|
|
Change-Id: Ib3886cb7cafc211581f4f9e7f76782d9d1984434
|
|
Reinstates this macro and truns it on in order to avoid issues
due to some frames at the end starving in harder videos.
A more acceptable solution is in the works.
Change-Id: I3c46148e86fa6114e3fed245246fb3686a9e6700
|
|
Turns off the DISABLE_RC_LONG_TERM_MEM macro and makes other changes
in the way the bits are updated, to make 2-pass rate control track
target bitrates closer.
Change-Id: I5f3be4b11c2908e6a9a9a1dd4fcf4e65531c44d8
|
|
|
|
Renames:
mi_8x8 -> mi
mode_info_stride -> mi_stride
Change-Id: I66f3e5fd1e7b7f46f108af5bb711c5fd9493c1be
|
|
Use a crude correction factor to correct for
lower compression efficiency at higher encode
speeds when estimating the max Q for the
clip.
Change-Id: I5ae377647f4adf5e91d700a8791fb3b8f70efc73
|
|
Change-Id: I366850015004644c4fc7feabe27a782fdd8d8718
|
|
Change-Id: If67ed8721f258883e41bab18f5c456505de68785
|
|
Change-Id: Id76a628495c822e23825b66a7589b4a3279680e2
|
|
|
|
|
|
1. Save stats for each spatial layer
2. Add frame buffer management for svc first pass rc
3. Set default spatial layer to 1
4. Flush encoder at the end of stream in test app
This only supports spatial svc.
Change-Id: Ia89cfa87bb6394e6c0405b921d86c426d0a0c9ae
|
|
Change-Id: I03049f89565ce19a297e65e2d53db127dc6f77d9
|
|
Change-Id: Ib9e27298c575afc02a98b593bc6ad60762064d9b
|
|
|
|
|
|
Change-Id: Ie68eefddf9b0120021668cf21dc2c6fc837c50ac
|
|
Change-Id: Id63e114a8f0615dbafd6a816019cdebffb983d2c
|
|
Change-Id: I612a5d2b3ab1f9202d5b0421a82a80849603c40d
|
|
|
|
Change-Id: Ia94d757de1d1b24609128cd40e68558078f50a38
|
|
Change-Id: I9717ef611ef9c39b109b2358c9771bf7fae2dd50
|
|
The core motion estimation fucntions all return sad now consistently.
The only exception is vp9_full_pixel_diamond(), however the core diamond
and refining search routines called from vp9_full_pixel_diamond() also
return SAD. If variance of pred error + mv cost is desired it must be
calculated explicitly outside these functions. For very fast encoding,
hopefully this will eliminate some redundant computations.
Also suggests reimplementing FAST_HEX with the vp9_pattern_search
framework. It is not exactly the same as the existing FAST_HEX, but
performance is slightly better and speed is very similar. Enables
removing a lot of duplicate code.
Change-Id: I152736393438c25bdf7e96b37cbb8ce330f4f94a
|
|
Change-Id: I916944950deb22f4c2301d83a803b732bf3ecd77
|
|
|
|
|
|
Change-Id: I111c5bd0dd47db7b1f6952c18056bee548bb42e9
|
|
Change-Id: I7255b3bc47d760333f58ac4878becbcc8ad30967
|
|
Change-Id: Iee4f8443971fe2b21762d87f0be5751329768b5a
|