Skip to content

Making Bounds in VideoSourceConfiguration adaptable #676

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ocampana-videotec wants to merge 2 commits into
base: development
Choose a base branch
from
Open

Making Bounds in VideoSourceConfiguration adaptable #676

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
44a6cc4
Making Bounds in VideoSourceConfiguration adaptable
ocampana-videotec Nov 13, 2025
d9ed54f
Including feedback from the F2F Meeting in Kuala Lumpur
ocampana-videotec Nov 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/Media2.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1251,7 +1251,7 @@
</variablelist>
<para>Note for the VideoEncoderConfiguration: if necessary the device may adapt parameter values for Quality and RateControl elements without returning an error. A device shall adapt an out of range BitrateLimit instead of returning a fault.</para>
<para>Note for the AudioSourceConfiguration: If the new settings invalidate any parameters already negotiated using RTSP, for example by changing codec type, the device must not apply these settings to existing streams. Instead it must either continue to stream using the old settings or stop sending data on the affected streams.</para>
<para>Note for the VideoSourceConfiguration: If a Device supports Rotation and the new settings do not contain Rotate element, a device shall keep current rotation state.</para>
<para>Note for the VideoSourceConfiguration: If a Device supports Rotation and the new settings do not contain Rotate element, a device shall keep current rotation state. Moreover, if necessary the device may adapt parameter values for the Bounds element without returning an error. In case of adaptation of the parameter values, the device shall return the adapted values upon the client's request.</para>
Copy link
Contributor

@bsriramprasad bsriramprasad Nov 17, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest to include 'parameter values for e.g. X'? for better understanding

Copy link
Contributor

@bsriramprasad bsriramprasad Nov 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<para>Note for the VideoSourceConfiguration: If a Device supports Rotation and the new settings do not contain Rotate element, a device shall keep current rotation state. Moreover, if necessary the device may adapt parameter values for the Bounds element without returning an error. In case of adaptation of the parameter values, the device shall return the adapted values upon the client's request.</para>
<para>Note for the VideoSourceConfiguration: If a Device supports Rotation and the new settings do not contain Rotate element, a device shall keep current rotation state. Moreover, if necessary the device may adapt parameter values for the Bounds element without returning an error. If certain parameters adapt, the device shall return the adapted values upon the client's request.</para>

</section>
<section>
<title>Get&lt;entity&gt;ConfigurationOptions</title>
Expand Down