Identify the controlling and receiving devices
When Kodi controls a remote UPnP player, keep the controller and the sound-producing device separate in the test. Write down which device should play and where volume is actually heard. A percentage shown on the controlling computer does not necessarily represent the same perceived level at a standalone receiver.
Begin with the receiving device at a modest known level and use a quiet familiar sample. Avoid a full-scale sound or an important live source while learning the control route. Keep a direct physical or ordinary remote control available for the receiving device so the test can be stopped promptly.
Inspect the documented UPnP settings
Kodi’s Services, UPnP/DLNA page distinguishes looking for remote players from synchronizing their volume. Inspect the enabled role and synchronization choice on the actual build. Record the original setting before changing it so the controlling arrangement remains recoverable.
The developer cautions that application and global system volume are independent. This can make a synchronized remote level unexpectedly loud compared with a computer whose system mixer is lower. Treat the displayed percentage as a control value, not as a measured sound-pressure level.
Compare one small level change
Start the known sample on the intended remote device and confirm its identity before adjusting anything. Make one small change through the chosen controller and observe the receiving device’s displayed value and audible result. Keep the source and output route fixed during the comparison.
If the wrong device responds or the level jumps unexpectedly, stop and preserve that observation. Do not continue raising the controller simply because the local computer appears quiet. The sound may be emerging elsewhere through a different volume chain, and a familiar-looking slider does not establish the target.
Retain an understood household setting
After the comparison, choose whether volume synchronization belongs in this setup and restore the intended ordinary levels. Check a normal start of remote playback once more at the conservative level. Keep the device names and chosen synchronization policy in the setup notes for other users.
The expected outcome is predictable control of the actual receiving player. It does not certify every UPnP implementation, equalize loudness between sources or make an application percentage comparable across different speakers. If the goal is simply browsing a server’s media, keep that client workflow separate from remote-player control.
Questions answered
Does 50 percent mean the same loudness on two devices?
No. Application values, system mixer levels and the receiving equipment’s own scale can differ. Test a small change on the actual route.
What should I confirm before adjusting remote volume?
Confirm the receiving device and audible output, keep its initial level modest and retain a direct way to stop playback.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.