Identify the model and connections
Confirm Vero V from the hardware or system information, then consult the Vero V specification page. List its television, receiver or soundbar route. A model-specific feature belongs to the complete supported combination of player, software, source and display rather than to the OSMC name in isolation.
For a planned equipment change, photograph only the necessary ports and write down which input currently works. Keep serial numbers private. This record can prevent a later support conversation from accidentally following instructions intended for Vero 4K or another member of the family.
Treat advanced video as a path
OSMC publishes a Vero V-specific Dolby Vision guide and explicitly distinguishes the older Vero and Raspberry Pi cases. Consult the current guide for the actual video profile and display arrangement. Do not turn that documentation into a blanket promise that every file carrying a Dolby label will produce the same result.
A useful illustrative comparison holds the media file steady while recording the display and connection route. If a title behaves differently after inserting a receiver, keep both route descriptions. A screen displaying a picture is useful evidence, but it is not by itself proof of every intended metadata or dynamic-range feature.
Build a precise support report
Include Vero model, OSMC release, source characteristics and television/receiver models when investigating an output problem. Describe whether the failure is no picture, a colour problem, a playback stop or a brief format switch. Those observations should not be merged into one generic buffering report.
Use only media you are entitled to play, and hide private paths or account tokens in logs. Vero hardware does not include every television service simply because a logo or player add-on can appear on screen. This reference is based on publisher documentation and does not claim physical-device or service-compatibility testing.