- Rating
- 1
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
The authors reformulate AVS as an asymmetric entity-querying problem and propose AEQNet that separates visual entity construction from candidate-grounded acoustic verification through four complementary components.
Critical strengths
- The method seems feasible.
- The grammar and words are proper.
- The assumption is interesting.
Critical weaknesses
-
I find the motivation and contributions of this paper rather confusing. The abstract claims that “This overlooks a fundamental inductive bias: vision delineates entity locations, whereas audio merely verifies their acoustic activation.” However, the paper provides neither empirical observations nor experiments to support this claim. More importantly, I do not see a clear connection between this motivation and the proposed method. The method does not seem to explicitly exploit or investigate this inductive bias.
-
The novelty of the proposed method is also unclear to me. Although the abstract emphasizes the aforementioned inductive bias as the main motivation, the subsequent methodological discussion does not seem to be built around it. As a result, I find it difficult to identify the key technical contributions of this work.
-
The related work discussion is insufficient. Section 2.1 discusses only five related papers, despite AVS having been studied for approximately four years. I believe a more comprehensive discussion of existing methods is necessary to properly position the proposed approach within the literature.
-
The paper contains many equations, but I find most of them unnecessary. For example, Eq. 1, Eq. 2, and Eq. 3 mainly describe standard and widely adopted operations. At least from my understanding, the paper does not explain what is novel about these formulations. Some equations also appear to lack careful verification. For instance, (which is defined) appears without a proper definition of $ j $, and the superscript $ * $ seems to be used only in this particular instance. These issues give me the impression that some mathematical descriptions may have been automatically generated or summarized using AI without sufficient human verification of their correctness and relevance to the paper.
-
I have serious concerns about the qualitative results in Figure 4. In particular, I encourage the authors and reviewers to zoom in on the second, fourth, and fifth rows of the rightmost example. The masks produced by AVSegFormer, ICF, and SELM exhibit noticeable white outlines, whereas the masks from other methods do not. Upon closer inspection, some of these outlines are purely white, while others contain yellow, blue, or green pixels. At a minimum, this indicates a lack of consistency in the visualization process. More concerningly, these artifacts raise the possibility that some masks may have been manually edited or postprocessed, potentially using image editing tools such as the lasso tool in Photoshop. I cannot determine whether this is actually the case, but the unusual visual artifacts make me question the reliability of the presented results. Furthermore, apart from this example, the authors do not provide additional qualitative visualizations for AVSS. Overall, I have substantial concerns about the authenticity and reliability of the qualitative analysis.
-
The paper also appears to lack careful proofreading. For example, I do not understand what “Progressive loss weights” means in Figure 3. I searched through the paper but could not find a corresponding explanation. Similarly, Table 1 is first referenced at the bottom of page 8, even though the table itself appears near the top of page 7. This makes the paper unnecessarily difficult to follow.
-
The paper introduces too many abbreviations, including AEQNet, HVCC, CF-AQR, FSC, and PCQL. It is difficult for readers to remember all these abbreviations while following the technical discussion. I suggest reducing the number of abbreviations or using more descriptive terminology wherever possible to improve readability.
-
Line 377 states that all input frames are resized to . However, to my knowledge, although some methods in Table 1 use this resolution, others adopt different input resolutions. I believe the authors should explicitly report the input resolution of each compared method in Table 1, as these differences may affect the fairness and interpretation of the comparisons.
Overall, my main reason for assigning a score of 1 is my concern about the authenticity of the qualitative analysis, particularly the unusual mask boundaries in Figure 4. I believe these visual artifacts require a convincing explanation from the authors before the experimental results can be considered reliable. If I disregard the concerns regarding Figure 4, I would assign a score of 2.
Questions for authors
NA
3 comments
Feedback
Q5. Why were color replacement and pixel resampling necessary? Generating visualizations from an integer-valued mask tensor should be straightforward. What exactly does “color replacement” mean in this context, why is it needed for an integer-valued mask tensor, and how could it introduce artifacts at mask boundaries?
Furthermore, the visualizations in the previous version were inconsistent across rows, columns, and cases. I find these inconsistencies difficult to reconcile with the authors’ statement that “all reported metrics were computed directly from raw model outputs before any visualization processing.” I remain unconvinced that the reported results are reliable.
The manuscript also appears to have received insufficient proofreading, and parts of the text read as though they may have been AI-generated.
I therefore maintain that the manuscript does not meet the standard for acceptance.
I also encourage the AC to examine the visualization inconsistencies in the previous version of the manuscript when assessing the reliability of the reported results.
Thank you for the comment. Here, "colour replacement” refers to harmonising previously saved RGB visualisations from different export versions. The historical pipeline was RGB image → nearest VOC colour matching → HSV recolouring → enlargement for display. This processing operated on saved visualisation images, rather than the original integer-valued mask tensors.
Some source images already contained mixed boundary colours. During nearest-colour matching, these pixels could receive different inferred labels and consequently appear as coloured fringes after recolouring. For example, an ICF boundary pixel (93, 0, 0) was mapped to “boat” and displayed in blue. These reconstructed labels should not be interpreted as the model’s original predictions. Enlargement was a separate presentation step, not a requirement for palette mapping.
Using the archived pipeline, we reproduced all 20 audited historical visualisations exactly, pixel for pixel, providing a reproducible explanation for the verified coloured fringes. We respectfully ask that this evidence be considered when assessing the visualisation concern and welcome a careful comparison of the corresponding images.
Author Responses (continued)
We sincerely thank the reviewer for this helpful suggestion. We agree that frequent use of abbreviations can make the technical discussion less accessible. To improve readability, we have expanded the overview of AEQNet in Appendix A.1 (Methodology) to provide the full names and functional descriptions of its four components.
The revised overview explains their roles as follows:
We also explicitly clarify that PCQL is an optimization strategy used only during training and does not introduce an additional inference module. This distinction helps readers understand how the prediction components and training strategy fit into the overall framework.
These expanded explanations make each component's role explicit and provide a clearer reference for following the terminology throughout the technical discussion.
We sincerely thank the reviewer for highlighting this important aspect of experimental comparison. We agree that input resolutions should be explicitly reported to provide the necessary context for interpreting performance differences.
Reporting input resolutions in Table 1. We have added an "Input Size" column to Table 1 to specify the input resolution used by each compared method.
Clarifying the scope of Section 4.1. We have revised Section 4.1 to explicitly state that all AEQNet experiments use a fixed input resolution of 224×224. This statement refers specifically to AEQNet's experimental setup, while the input resolutions of the other compared methods are documented in Table 1.
These revisions make the experimental settings more transparent and allow readers to interpret the reported performance in light of each method's input resolution.