Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[bannonb]

Hey all:

Just upgraded from MC 25 to 26.  Just updated to .39 today.

Moved my custom resources/resource.xml file during 25-26 upgrade as I've had issues before.

I use a USB DAC.  I always used internal volume along with the selected DAC device (Audioengine D1) in MC Audio settings.  Using exclusive access as always.

It appears that after the upgrade I can't use my keyboard vol up and vol down keys to affect the MC volume slider.  I can click on the slider with my mouse or use volume knob on the DAC, but the keyboard is most convenient...

At one time I had placed a MCC command into the resource.xml file which may have helped me use my keyboard keys.   

<Entry Global="1" Param="0" Command="10018" Key="Ctrl;+"/>

Now even the global setting only allows me to control volume with cmd + or cmd - .  I understood global to mean MC didn't need to be in focus for that to work...but it's not working when out of focus.

In the end, I really prefer to use the vol up and vol down keys on my Logitech K350 keyboard.

What am I missing?  Can you assist?

Thanks,

BannonB

[bannonb]

I reinstalled .39 from scratch.

Same result as far as volume control.  I am now relegated to using the knob on my USB DAC.

Keyboard vol control only controls mac speaker volume.  play/pause buttons launches Apple Music.  I also have no control of audio there, but play/pause works.

I have recently upgraded to MacOS 10.15.4.  Updated all keyboard firmware and drivers for new MacOS 10.15.

Love the Modern Card skins which put the window controls on the left side...consistent for Mac.

Any help is appreciated. 

[blgentry]

My guess is that your Logictech keyboard controls emulate the Mac native keyboard media controls for Volume, play, etc.  The fact that Play on the keyboard launches ITunes definitely supports this theory; that's how a native Mac keyboard works.

MC has a setting for how to handle media keys:

Tools > Options > General > Advanced > Media Key Mode

Try setting that to "all" or "keyboard only" and see if that helps.

Good luck.
Brian.

[bannonb]

@Brian

Thanks.  I never used that Media Key Mode before...It just worked I guess.

It has no effect on the behavior where play/pause launches Music (formerly itunes). 

I attribute this to MacOS 10.15 (Catalina) which I upgraded to about a week before installing Media Center 26.

I am surprised more Mac users haven't chimed in as I would guess it is the new default behavior for media keys.  There are various 3rd party keyboard mappers (Media Key Forwarder for example--not available for 10.15 yet) and some articles on disabling Music altogether to allow their use in Spotify.

--I'm using a USB DAC which may not be that common.  When I use Macbook pro speakers, the Logitech keys do control play/pause for MC when in focus--

Anyway, it looks like I'm relegated to using CMD + and CMD - for volume and CMD 2 for play/pause until someone smarter than me solves this.

[HaWi]

I am surprised more Mac users haven't chimed in ...

I have no issues using my Matias BT keyboard's media controls. Works exactly as I expect but I have no DAC. Also, I use JRemote most of the time.
cheers,
Hans

[blgentry]

I attribute this to MacOS 10.15 (Catalina) which I upgraded to about a week before installing Media Center 26.

Ah, interesting.  Doing a web search I see lots of forum posts (Roon, Spotify, Reddit, etc) where people are complaining about this.

--I'm using a USB DAC which may not be that common.  When I use Macbook pro speakers, the Logitech keys do control play/pause for MC when in focus--

Hmm.  If it works for one thing and not the other, it sounds like maybe changing the volume mode would fix it.  Maybe. 
Tools > Options > Audio > Volume > Volume Mode > (I suggest Internal Volume)

Restart MC after you make the change and see what happens.

Good luck.

Brian.

[bannonb]

I use internal volume so I can see the volume bar in MC.

If I use system volume and MacBook Pro speakers, it works fine.

Still in a quandary.  Using a company laptop and have to wait for MacOS updates until tested. So even If Apple has a fix, I’ll have to wait.