Framebuffer query for channels about anari-docs HOT 4 CLOSED

Framebuffer channels are parameters of type DATA_TYPE and will be enumerated via anariGetObjectInfo with parameterof type PARAMETER_LIST. This is not sufficient?

Actually there is currently no way to get the valid pixelType of Frame channels when requesting that channel (setting the parameter), for that we should extend the value info like below.

.Info of parameters for introspection.

from anari-docs.

Framebuffer channels are parameters of type DATA_TYPE and will be enumerated via anariGetObjectInfo with parameterof type PARAMETER_LIST. This is not sufficient?

Part of the problem is that there's no good way to distinguish parameters which are intended to be used as a FB channel. If an implementation provides extensions with additional FB channels, there isn't an obvious connection between a parameter and it being a valid channel.

We need the ability to discern how this connection to parameters and mappable channel names occurs, and there should be text stating the convention used to connect them.

I propose that we use a channel.[name] as the parameter name, where [name] is the matching name used to map it. There should at least be non-normative text that states that this is the convention and that extensions ought to strongly follow it.

from anari-docs.

Summary of consensus from today's WG call:

• We need to add the value info parameter for STRING_LIST/TYPE_LIST info queries as outlined by @johguenther (this was a gap that needs filled regardless).
• We want to add the channel query to ANARIFrame, providing a list of available channels by the implementation. These channels are the names which can be passed directly to anariMapFrame().
• ANARIFrame parameters for controlling various frame channels should all be prefixed with "channel." to both clearly state their relationship to mappable channels and prevent naming collisions with other parameters.
• We want language that states the [grouping].[name] naming convention is a rule for arrays/buffers (both input and output).

from anari-docs.

closed via #39

from anari-docs.