Skip to content

Ducking is not correctly handled in back and forth conversation when not using VACA media player #200

@msp1974

Description

@msp1974

From VACA issue 68 - msp1974/ViewAssist_Companion_App#68

@PengBG
VACA version 0.70
IF during setup of VA in View Assist integration you select non default player like MA player, ducking setting in VACA do not work. In this case ducking setting from Master Configuration is used. This results as a problem in continuous conversation since ducking happens every time when listening event is triggered and at the end we get wrong volume restore value.

What would be expected for VACA device is to use internal setting for ducking any set media player during VACA setup in View Assist integration and to take into account that ducking restores correct volume value after continuous conversation ends.

@msp1974
Notes for msp.

This is caused by lines 169 in entity_listeners.py not listing MA as a scenario whereby the device will handle ducking.

Also need to review how the integration handles ducking in a multi interaction conversation (ie continue conversation scenario) as looks like it keeps ducking more and more , which is incoreect.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions