You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the context of #759, I found it hard to navigate the spec around Mix Presentation OBU parameter definitions (element and output gains). IMHO, it could be simplified without changing the semantics or bitstreams, as follows:
The Mix Presentation OBU uses:
ElementMixConfig element_mix_config;
but ElementMixConfig is simply
class ElementMixConfig() {
MixGainParamDefinition mix_gain;
}
My suggestion would be to remove the use of ElementMixConfig and simply use the following in the MixPresentationOBU
MixGainParamDefinition element_mix_gain;
It means also moving the semantics of mix_gain from section 3.7.4 to section 3.7, merging it with the semantics of element_mix_config
Same for output_mix_config. The syntax in MixPresentationOBU should simply have:
MixGainParamDefinition output_mix_gain;
instead of
OutputMixConfig output_mix_config;
Section 3.7.5 can then be removed and merged with the semantics of output_mix_config (which would become output_mix_gain).
The text was updated successfully, but these errors were encountered:
In the context of #759, I found it hard to navigate the spec around Mix Presentation OBU parameter definitions (element and output gains). IMHO, it could be simplified without changing the semantics or bitstreams, as follows:
The Mix Presentation OBU uses:
but
ElementMixConfig
is simplyMy suggestion would be to remove the use of
ElementMixConfig
and simply use the following in the MixPresentationOBUIt means also moving the semantics of
mix_gain
from section 3.7.4 to section 3.7, merging it with the semantics ofelement_mix_config
Same for output_mix_config. The syntax in MixPresentationOBU should simply have:
instead of
Section 3.7.5 can then be removed and merged with the semantics of output_mix_config (which would become
output_mix_gain
).The text was updated successfully, but these errors were encountered: