How to mute tv while in Media mode (T2)

[Funjunkie6]

Hi guys,

I find it distracting hearing the tv while I’m scrolling thru the recorded media. Is there a setting on the T2 to auto mute the tv in Media mode?

(I know I could just press the mute button on the remote, but I get a large flashing sound bar on the screen when it’s muted)

Thanks in advance.

[prl]

Is there a setting on the T2 to auto mute the tv in EPG mode?

No.

[Funjunkie6]

Sorry, I meant scrolling through recorded media, not EPG

[IanSav]

Hi Funjunkie6,

Are you pressing MUTE on the TV or the Beyonwiz? With recent firmware on the Beyonwiz the MUTE function should flash up a MUTE icon and then it should go away and leave the screen clear.

Regards,
Ian.

[Gully]

Are you meaning that you don't want to see live TV in the background while you are in the movie list?

In that case you can go into settings in the movie list menu and set "Show live TV when movie stopped" to no.

[Funjunkie6]

Thanks Gully.
Appreciate it

[Funjunkie6]

Hey Gully
My T2 is running version 17.5, build 20180417.
I went into my Media list and selected menu/Settings. At the option “Show live TV when movie stopped", I selected No, as you suggested.
I also selected No for “play audio in background”. then restarted but tv sound continues when I’m in the Media/recordings list.
Any ideas?
Thanks

[prl]

It only changes what happens after a recording or media playback finishes.

[Gully]

Hey Gully
My T2 is running version 17.5, build 20180417.
I went into my Media list and selected menu/Settings. At the option “Show live TV when movie stopped", I selected No, as you suggested.
I also selected No for “play audio in background”. then restarted but tv sound continues when I’m in the Media/recordings list.
Any ideas?
Thanks

Have you played a media file? You have to play one first - as the setting says it is for when it stops playing?

EDIT beaten by prl

[MrQuade]

In summary, the feature doesn't do what you probably want it to do. The whole interface is more or less designed to have live tv going at all times with mostly see-through menus.

I believe that the overlayhd skin will let you set the menu background opacity so that you can hide the video from view, but that wont mute the sound.

[sub3R]

I believe that the overlayhd skin will let you set the menu background opacity so that you can hide the video from view, but that wont mute the sound.

Correct. The only thing it won’t stop is live TV showing through the large icons (the ones in Main Menu & sub menus etc.). If there is a way to do this I would love to know how.

Funjunkie6, I know how annoying the audio is, muting the audio is the first things I do when I switch on the T2 or U4. Live TV video & Live TV audio, except when I want to watch live TV, are at the top of my list for what I dislike about these boxes.

[Funjunkie6]

Thanks to everyone who posted. I appreciate your support.

[IanSav]

Hi Dennis,

Correct. The only thing it won’t stop is live TV showing through the large icons (the ones in Main Menu & sub menus etc.). If there is a way to do this I would love to know how.

Given that there were no offers for image/graphics assistance when I last asked I am now considering paying to have the graphical images in OverlayHD refreshed. The alternative could be for me to try and rework the images to remove the transparency components when I can find the time for the effort required. I haven't decided on which path as yet but I don't really want a hobby to start costing what could potentially become big dollars.

Regards,
Ian.

[sub3R]

Hi Ian,

Unfortunately I lack the programming & graphics skills for that, otherwise I would help you out. With all the various skills by T & U series Beyonwiz owners on this forum I would have thought someone would have those skills & the time to help. But that’s easy for me to say because I don’t know what is involved.

At least I know you haven’t hidden the option for icon transparency somewhere in OverlayHD Skin Manager.

[sub3R]

... Is there a setting on the T2 to auto mute the tv in Media mode?

One little trick I use is to shut our T2 to standby from the Movie Player screen. That way if a recording has previously been partially played, which will mute live TV audio, the next time the T2 is woken from standby it will open at the Movie Player screen with live TV audio muted.

Of course once you exit from the Movie Player screen you will get live TV audio again.

[adoxa]

Is there a setting on the T2 to auto mute the tv in Media mode?

Here's a quick proof-of-concept to do it (you'll need at least build 20180617). If mute is on then nothing changes; otherwise opening the movie list will turn on mute and leaving it will turn it off (even if you manually turn it off and on within). Todo: make it an option; should probably work with EPG and timer, too.

Installation: Unzip to a USB drive and plug it into the Beyonwiz. Bring up the menu (from live TV) and select "Sources / Files". Navigate to the USB drive and press OK on the media-mute folder. Highlight setup.sh (press 4 if your USB isn't FAT/NTFS), press OK and select "Run script". Restart for it to take effect. Repeat to remove.

[sub3R]

I just tried that & it works well on the T2. Haven’t tried it yet on the U4.

I just copied the unzipped ‘media-mute’ directory to the T2’s HDD with FileZilla then changed ‘setup.sh’ permissions from 644 to 755. After running ‘setup.sh’ with File Commander I only had to restart the GUI for it to work.

Todo: make it an option; should probably work with EPG and timer, too.

If it worked with the various EPG screens, the Main MENU, Timer list & the Favourites screen it would be nice, but probably a fair bit of work to do that.

[sub3R]

... Haven’t tried it yet on the U4.

As expected, also works the same on the U4.

[adoxa]

Here's another approach, also muting during the timer list, AutoTimer overview, EPG (all but infobar types), channel selection and main menu. It also prevents the volume bar from showing when mute is automatically turned off (but the mute icon is still shown when automatically turned on). Remove the previous one, then install this one (which doesn't test for the build, anything from 2017 should be fine, possibly even earlier). Todo: make it optional; choose which screens should be muted.

[sub3R]

Here's another approach, ...

That works even better. Working fine on our T2 & U4 & doesn’t need removing & re-running after an on-line f/w beta update.

I was amused about your comment in screen.py about supporting screens without help.

I was tempted (for about 2 minutes) to try & modify your screen.py to get it to work in the AutoTimer overview screen & a couple of the non-default epg screens I use, but I thought; ‘no, I haven’t got a clue what I’m doing & I’ll probably break something, so be happy with what you’ve got’.

Thanks, it is something that has been on my wish list since I first bought the T2.

[MrQuade]

That works even better. Working fine on our T2 & U4 & doesn’t need removing & re-running after an on-line f/w beta update.

How do you figure that it doesn't need removing before an online update?

[prl]

That works even better. Working fine on our T2 & U4 & doesn’t need removing & re-running after an on-line f/w beta update.

How do you figure that it doesn't need removing before an online update?

You can be pretty sure that it does need to be removed. Any nasty effects may be delayed until you uninstall the package, because that will replace the Setup.pyo file with one from an earlier firmware version.

You should always remove hacks and patches before doing an online update. Keeping proper, but non-feed, plugins like OverlayHD or Series2Folder should be OK.

[MrQuade]

You can be pretty sure that it does need to be removed.

And in the exact reverse order in which it was applied along with any other patches.

(sorry, my previous comment was probably overly rhetorical)

[adoxa]

That works even better. Working fine on our T2 & U4 & doesn’t need removing & re-running after an on-line f/w beta update.

Updated the previous attachment, so it stays muted after selecting from the main menu.

I was amused about your comment in screen.py about supporting screens without help.

That's by "Paul In&In" (from 2005).

I was tempted (for about 2 minutes) to try & modify your screen.py to get it to work in the AutoTimer overview screen & a couple of the non-default epg screens I use, but I thought; ‘no, I haven’t got a clue what I’m doing & I’ll probably break something, so be happy with what you’ve got’.

Added them all (except the infobar-type EPGs).

[sub3R]

You can be pretty sure that it does need to be removed. Any nasty effects may be delayed until you uninstall the package, because that will replace the Setup.pyo file with one from an earlier firmware version.

You should always remove hacks and patches before doing an online update. Keeping proper, but non-feed, plugins like OverlayHD or Series2Folder should be OK.

Ok, Thanks for the explanation. In future I’ll uninstall before doing on-line beta updates.

And in the exact reverse order in which it was applied along with any other patches.

I wasn’t aware of that either. Thanks.

To help other users, it would be handy if all this information was in a sticky topic in the ’FAQs, Tips & How to Guides T2/T3/T4/U4’ sub-forum? I’m pretty certain I’m not the only user that didn’t know this.

[sub3R]

Added them all (except the infobar-type EPGs).

Many thanks.

[prl]

To help other users, it would be handy if all this information was in a sticky topic in the ’FAQs, Tips & How to Guides T2/T3/T4/U4’ sub-forum? I’m pretty certain I’m not the only user that didn’t know this.

When I post patches, the post page with the patch says to uninstall the patch before doing an online upgrade in bold red text. But it applies equally to adoxa's patches. I'm generally wary about installing more than one patch at a time (no matter what their sources are), and I don't install more than one without having a good look at their contents.

Adoxa's patches became popular when there was a long delay in getting his changes into the released firmware. I think that broadened the user base for patches in ways that mean that I think that the patches should come with more information about how to use them and also keep the firmware stable.

[sub3R]

Added them all (except the infobar-type EPGs).

Adoxa, that is excellent. Thanks again. Noise pollution gone.

[sub3R]

Trying not to get this topic too far off-topic, but as a follow up to what prl posted here, this morning on the T2 I got two timer conflicts reported when there wasn’t any conflicts.

I don’t know if that was because of what I did (or didn’t do) yesterday, but after a USB re-install of f/w 17.5 20180417 then an on-line update to 17.5 20180627 again, setting the same timers didn’t cause any reported conflicts. Patches were uninstalled before the updates & re-installed after. The U4 then got the same treatment.

[adoxa]

Trying not to get this topic too far off-topic, but as a follow up to what prl posted here, this morning on the T2 I got two timer conflicts reported when there wasn’t any conflicts.

Two or three timers? If three, it's possible the USB tuner wasn't recognised (check MENU>Setup>Information>Devices; restarting/rebooting fixes it); if two, idk, none of the patches should have any bearing on that.

[sub3R]

No it was only two, which even two tuners would have handled. When I deleted the timer it worked the second time, but it then did the same when I tried to set a different timer. I always check for the condition of the USB tuner after I shut the T2 to deep standby, reboot or restart the GUI. I normally leave the T2 in normal standby & not deep standby for that reason.

I just thought it may have been due to me not uninstalling the multiepg-icon patch & the first version of the auto-mute patch before updating the f/w on-line to the latest beta (I did uninstall OverlayHD-patch). The latest version of auto-mute patch I hadn’t put on the T2 at that stage, only on the U4.

I haven’t had this issue before I did that or after the above re-install. But it may have been something else that got screwed up.

[adoxa]

No it was only two, which even two tuners would have handled. When I deleted the timer it worked the second time, but it then did the same when I tried to set a different timer.

Hm, strange.

I just thought it may have been due to me not uninstalling the multiepg-icon patch [...]

Speaking of which, I just updated it to include the HDMI-IN fix.

[sub3R]

Speaking of which, I just updated it to include the HDMI-IN fix.

Thanks.

[sub3R]

Here's another approach, also muting during the timer list, AutoTimer overview, EPG (all but infobar types), channel selection and main menu. It also prevents the volume bar from showing when mute is automatically turned off (but the mute icon is still shown when automatically turned on). Remove the previous one, then install this one (which doesn't test for the build, anything from 2017 should be fine, possibly even earlier). Todo: make it optional; choose which screens should be muted.

This has been working brilliantly on the T2 & U4s (I just have to be aware what happens when trying to play music on the Wiz).

I haven’t noticed this before but when I did the last couple of updates to 19.3 series f/w I have been getting the following error on both U4s (haven’t checked the T2); “Could not import runpy module” after running the script to install auto-mute (see attachment). It may have happened prior to 19.3 series f/w but I hadn’t noticed it.

Auto-mute still works, so is this a problem? The script resides on the internal HDD & has the correct permissions (777).

I always run the script to uninstall auto-mute then do a UI restart before installing f/w updates, & run the script to install auto-mute followed by a GUI restart after the f/w update. This is the only script I am running.

auto-mute_enable-message_a.jpg (37.5 KiB) Viewed 5683 times

[adoxa]

I haven’t noticed this before but when I did the last couple of updates to 19.3 series f/w I have been getting the following error on both U4s (haven’t checked the T2); “Could not import runpy module” [...]

Auto-mute still works, so is this a problem? [...]

Apparently 19.3 no longer includes runpy by default, which is used to pre-compile the sources. There's no problem, as the sources will be compiled on the first run, anyway. I think you have three options: put up with it; modify the script to remove the py_files=... line; or install python-runpy (from the command line, don't think it can be done from the GUI).

[sub3R]

Thanks for the explanation. I had a look at deleting that line (I take it is the one below in red text).

…
if test ${f##*.} == py; then
py_files="$py_files $f"
if test -f /${f}o; then
old_files="$old_files ${f}o"
fi
…

I won't try to install python-runpy if it isn’t needed, so I think I’ll just put up with that message seeing it doesn’t cause any problems & it works as it should.

[adoxa]

Yep, that's the one - remove it and there won't be a list of files to be compiled, so runpy won't be invoked.

[sub3R]

You’ve convinced me. I don’t like error messages so I’ll remove it.

[adoxa]

Here's a plugin version. Uninstall the patch, restart, then install the plugin - it will take effect immediately.

To install: rename without .tgz (forum doesn't support .ipk) and copy to USB. Insert the USB, you should be prompted to install extensions, select it. Press OK to select the extension, GREEN to install. Done.

[stephenh]

Here's a plugin version. Uninstall the patch, restart, then install the plugin - it will take effect immediately.

To install: rename without .tgz (forum doesn't support .ipk) and copy to USB. Insert the USB, you should be prompted to install extensions, select it. Press OK to select the extension, GREEN to install. Done.

@adoxa
Thanks, works great!

* How do I uninstall and/or turn it off if I decide to not use it?

* if I keep it, do I need to uninstall it before doing firmware updates?

Cheers,

StephenH

[adoxa]

* How do I uninstall and/or turn it off if I decide to not use it?

I didn't do any config, so just remove the plugin itself (iirc PLUGIN>RED>Extensions>AutoMute) - that, too, will take effect immediately.

* if I keep it, do I need to uninstall it before doing firmware updates?

Nope, it'll continue to work even if IceTV updates (assuming the function I've patched hasn't changed, which I don't imagine will). You will need to reinstall after a USB update, of course.

[stephenh]

I didn't do any config, so just remove the plugin itself (iirc PLUGIN>RED>Extensions>AutoMute) - that, too, will take effect immediately.

@adoxa
Ok, thanks. Any chance of having it configurable so you can turn it On and Off without uninstalling/installing?

Nope, it'll continue to work even if IceTV updates (assuming the function I've patched hasn't changed, which I don't imagine will). You will need to reinstall after a USB update, of course.

Will continue to work across online firmware beta updates I'm hoping?
Confused by the reference to IceTV but figure you may be confusing the thread with the one for your IceTV Extended info IPK?

Thanks again,

StephenH

[adoxa]

Ok, thanks. Any chance of having it configurable so you can turn it On and Off without uninstalling/installing?

Sure.

Will continue to work across online firmware beta updates I'm hoping?

Yep.

Confused by the reference to IceTV but figure you may be confusing the thread with the one for your IceTV Extended info IPK?

Yes.

[stephenh]

Ok, thanks. Any chance of having it configurable so you can turn it On and Off without uninstalling/installing?

Sure.

Looking forward to it
I had another thought ... is it possible that "muting" be configurable?
So that if you want it just "dips" the audio to a preset like 50% rather than mutes it completely, and that the degree of "dip" is configurable?

[adoxa]

Ok, thanks. Any chance of having it configurable so you can turn it On and Off without uninstalling/installing?

You can now configure it from the main PLUGIN screen, as well as from BLUE. In addition to enable/disable, there's options to control the mute icon and the volume bar.

I had another thought ... is it possible that "muting" be configurable?

What happens when the volume is changed? Presumably decrease means lower it even more, but what about increase? Does it restore original volume first, or increase it as it is? What happens when the screen closes? Does it restore original, or keep current?

[stephenh]

You can now configure it from the main PLUGIN screen, as well as from BLUE. In addition to enable/disable, there's options to control the mute icon and the volume bar.

Nice one! Working well for me so far.

What happens when the volume is changed? Presumably decrease means lower it even more, but what about increase? Does it restore original volume first, or increase it as it is? What happens when the screen closes? Does it restore original, or keep current?

Hmmm ... not sure about this. I think for simplicity maybe if you are in a "muted or reduced" mode then any fiddling the volume should restore to original volume setting and then adjust as though the muting or reducing wasn't in operation and just leave it like that. Also gives you an override if you need it. You would then have to exit to live TV and then go into another "muted' screen for it to trigger again perhaps?

Note in my case I always have my Volume on 100% as the "actual" volume is controlled on my amplifier, so I would never be actually changing the Beyonwiz output setting, but others would be potentially I guess?

Is it also possible to have the "ramp" times into and out of mute or reduced volume mode as independently user adjustable?
For example I like a reasonably quick ramp down on volume reduction, but a slower ramp coming back to full volume ...

Sorry to be cheeky and keep asking for stuff

StephenH

[adoxa]

Hmmm ... not sure about this. I think for simplicity maybe if you are in a "muted or reduced" mode then any fiddling the volume should restore to original volume setting and then adjust as though the muting or reducing wasn't in operation and just leave it like that.

It doesn't sound right that if you automatically reduce the volume, then want to reduce it again, that it increases back to the original. Might just stick with mute.

Is it also possible to have the "ramp" times into and out of mute or reduced volume mode as independently user adjustable?

I'm not aware there are ramp times. I'd rather not add them.

[prl]

I'm not aware there are ramp times. I'd rather not add them.

There aren't. You'd have to do it in a similar way to the infobar fade. Given that I know you're familiar with that code, I suspect it's something you'd rather not go near

[stephenh]

I'm not aware there are ramp times. I'd rather not add them.

Fair enough, what I am hearing is a pretty abrupt almost "cut" when the mute cuts in, and a quickish fade up when you unmute. That must just be what is built into the Mute function anyway I guess?

Anyway, thanks for listening and many thanks for the configurable version, appreciate it!

StephenH