aomenc 3.11.0-149-gd032a4f339 - partition debug

[Pablo De Chiaro R.]

I'm trying to debug the partitioning process in aomenc, specifically to gather information about partition modes, block sizes, and block positions within the frame. I believe the correct approach is to configure the build with:

-DCMAKE_BUILD_TYPE=Debug -DCONFIG_COLLECT_PARTITION_STATS=1

After compiling with these options, I understand that a file named part_timing.csv is generated, which should contain the relevant partitioning data.

However, I have a few questions:

• Is this the correct way to enable partition debugging in aomenc?
• What exactly does the part_timing.csv file contain? How can I interpret the values related to partition modes, block sizes, and block positions?
• Are there any additional build or runtime flags required to ensure that all the detailed partitioning information is captured?

Any guidance or additional documentation pointers would be greatly appreciated.

[James Zern]

Hi,

On Mon, Feb 3, 2025 at 8:49 AM Pablo De Chiaro R. <pablo.ch...@gmail.com> wrote:

I'm trying to debug the partitioning process in aomenc, specifically to gather information about partition modes, block sizes, and block positions within the frame. I believe the correct approach is to configure the build with:

Sorry for the slow response, this got marked as spam for some reason. Maybe others had this issue too.

 

-DCMAKE_BUILD_TYPE=Debug -DCONFIG_COLLECT_PARTITION_STATS=1

After compiling with these options, I understand that a file named part_timing.csv is generated, which should contain the relevant partitioning data.

However, I have a few questions:

• Is this the correct way to enable partition debugging in aomenc?

You can set `-DCONFIG_COLLECT_PARTITION_STATS=2` [1] to produce another csv which might be more what you're after. 

• What exactly does the part_timing.csv file contain? How can I interpret the values related to partition modes, block sizes, and block positions?

I'm not familiar with the code, but you can see where it's output in print_partition_timing_stats_with_rdcost() [2]. 

• Are there any additional build or runtime flags required to ensure that all the detailed partitioning information is captured?

There is a bitstream analyzer in the tree (`-DCONFIG_ANALYZER=1`), but I don't know how much attention this has seen since there are other options available like ViCueSoft's [3].

 

Any guidance or additional documentation pointers would be greatly appreciated.

[1]: https://aomedia.googlesource.com/aom/+/2454213a72f194522c98610ef17057c226ffe391/av1/encoder/encoder.h#4443

[2]: https://aomedia.googlesource.com/aom/+/2454213a72f194522c98610ef17057c226ffe391/av1/encoder/partition_search.c#3235 

[3]: https://vicuesoft.com/vq-analyzer/

--
You received this message because you are subscribed to the Google Groups "AV1 Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to av1-discuss...@aomedia.org.
To view this discussion visit https://groups.google.com/a/aomedia.org/d/msgid/av1-discuss/599c0abd-6189-4082-986e-9b6b377aed09n%40aomedia.org.

[Wan-Teh Chang]

On Fri, Feb 7, 2025 at 11:30 AM 'James Zern' via AV1 Discussion
<av1-d...@aomedia.org> wrote:
>
> Sorry for the slow response, this got marked as spam for some reason. Maybe others had this issue too.

Yes, Pablo's email was also marked as spam for me.

Wan-Teh