github-starred/MonitorControl

Fork 0

mirror of https://github.com/MonitorControl/MonitorControl.git synced 2026-05-15 14:15:55 -06:00

[GH-ISSUE #232] Compatibility with iTunes Volume Control #179

New issue

Closed

opened 2026-05-05 05:21:07 -06:00 by gitea-mirror · 7 comments

gitea-mirror commented

2026-05-05 05:21:07 -06:00

Owner

Originally created by @JonasGessner on GitHub (Jun 3, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/232

Originally assigned to: @waydabber on GitHub.

Hi Guillaume, I have been using this tool for a while and it is great!

I also use another app called iTunes Volume Control that I use to be able to control AirPlay volume. Sadly they both do not work well together. Basically it seems either tool overrides the actions of the other. If I launch MonitorControl after iTunes volume control then MonitorControl completely takes over and controlling AirPlay volume no longer works. Whereas the other way round the volume of the monitor is never changed.

I also opened an issue in the iTunes Volume Control project: https://github.com/alberti42/iTunes-Volume-Control/issues/26

I am hoping that there is some simple way to make these two apps compatible with each other. I'm willing to help, but I am first asking here since you surely know the involved APIs better than me.

Thanks,
Jonas

Originally created by @JonasGessner on GitHub (Jun 3, 2020). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/232 Originally assigned to: @waydabber on GitHub. Hi Guillaume, I have been using this tool for a while and it is great! I also use another app called [iTunes Volume Control](https://github.com/alberti42/iTunes-Volume-Control) that I use to be able to control AirPlay volume. Sadly they both do not work well together. Basically it seems either tool overrides the actions of the other. If I launch MonitorControl after iTunes volume control then MonitorControl completely takes over and controlling AirPlay volume no longer works. Whereas the other way round the volume of the monitor is never changed. I also opened an issue in the iTunes Volume Control project: https://github.com/alberti42/iTunes-Volume-Control/issues/26 I am hoping that there is some simple way to make these two apps compatible with each other. I'm willing to help, but I am first asking here since you surely know the involved APIs better than me. Thanks, Jonas

gitea-mirror

2026-05-05 05:21:07 -06:00

closed this issue
added the
enhancement
label

gitea-mirror commented

2026-05-05 05:21:13 -06:00

Author

Owner

@JoniVR commented on GitHub (Jun 10, 2020):

@JoniVR commented on GitHub (Jun 10, 2020): Related to this answer: https://github.com/MonitorControl/MonitorControl/issues/227#issuecomment-642090362

gitea-mirror commented

2026-05-05 05:21:15 -06:00

Author

Owner

@JonasGessner commented on GitHub (May 29, 2021):

Not really a fix, but In my fork I simply added the functionality of iTunes Volume Control into MonitorControl and no longer use iTunes Volume Control at all: https://github.com/JonasGessner/MonitorControl/tree/music-control

@JonasGessner commented on GitHub (May 29, 2021): Not really a fix, but In my fork I simply added the functionality of iTunes Volume Control into MonitorControl and no longer use iTunes Volume Control at all: https://github.com/JonasGessner/MonitorControl/tree/music-control

gitea-mirror commented

2026-05-05 05:21:18 -06:00

Author

Owner

@waydabber commented on GitHub (Aug 21, 2021):

Great! This issue seems to be resolved then, so I'll close it! Thank you!

@waydabber commented on GitHub (Aug 21, 2021): Great! This issue seems to be resolved then, so I'll close it! Thank you!

gitea-mirror commented

2026-05-05 05:21:22 -06:00

Author

Owner

@JonasGessner commented on GitHub (Aug 21, 2021):

No, I resolved this for myself in a way that isn't generally applicable. In general this problem still exists.

@JonasGessner commented on GitHub (Aug 21, 2021): No, I resolved this for myself in a way that isn't generally applicable. In general this problem still exists.

gitea-mirror commented

2026-05-05 05:21:24 -06:00

Author

Owner

@waydabber commented on GitHub (Aug 21, 2021):

Hi, maybe I did not understand the problem. We plan to add customization options to the keyboard in the following issue:

https://github.com/MonitorControl/MonitorControl/issues/118

Will that solve the problem? It means that you'll be able to remap the standard volume keys to something else.

@waydabber commented on GitHub (Aug 21, 2021): Hi, maybe I did not understand the problem. We plan to add customization options to the keyboard in the following issue: https://github.com/MonitorControl/MonitorControl/issues/118 Will that solve the problem? It means that you'll be able to remap the standard volume keys to something else.

gitea-mirror commented

2026-05-05 05:21:25 -06:00

Author

Owner

@JonasGessner commented on GitHub (Aug 21, 2021):

The issue is simply that this tool does not work when installed together with iTunes Volume Control. The exact key mapping is not the problem I believe.

Basically it seems either tool overrides the actions of the other. If I launch MonitorControl after iTunes volume control then MonitorControl completely takes over and controlling AirPlay volume no longer works. Whereas the other way round the volume of the monitor is never changed.

@JonasGessner commented on GitHub (Aug 21, 2021): The issue is simply that this tool does not work when installed together with iTunes Volume Control. The exact key mapping is not the problem I believe. > Basically it seems either tool overrides the actions of the other. If I launch MonitorControl after iTunes volume control then MonitorControl completely takes over and controlling AirPlay volume no longer works. Whereas the other way round the volume of the monitor is never changed.

gitea-mirror commented

2026-05-05 05:21:27 -06:00

Author

Owner

@waydabber commented on GitHub (Aug 21, 2021):

I see. How do you propose to solve the problem? What should be changed in MonitorControl in order to solve the issue? Does the issue persist if you turn set the keyboard to listen to the Brightness keys only?

@waydabber commented on GitHub (Aug 21, 2021): I see. How do you propose to solve the problem? What should be changed in MonitorControl in order to solve the issue? Does the issue persist if you turn set the keyboard to listen to the Brightness keys only?