-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Play/Pause doesn't work with plugged in headphones #19
Comments
it should work now, can you please check it? |
@milgra I'm noticing the same problem. I've been using the app for a couple of weeks and thought I remembered my headphone jack working earlier. Now it's not. Just reinstalled 1.8 and still nothing. I have the exact same issue. Music plays for about 1 second and immediately pauses again. Button and the keyboard works perfectly though. Device: MacBook Air 2017 |
Im with the Version 1.8 build 3, it my beatsX pause button dont work. |
Play & Pause works fine but unfortunately next track (double press) and previous track (3x press) does not work anymore. 2 presses are interpreted as pause & play (the music stops and plays right again) |
I think we should revert the commit I made (d697595) since it's making more problems and it seems it doesn't fix the problem properly. |
hmm, I added an older version ( without the modification ) to the download page till I figure out what the problem is : http://milgra.com/high-sierra-media-key-enabler.html |
If it helps, I just used the v1.7 (build 1) you posted and the same headphone problem exists. |
hmm, thank you! |
1.9 (1) - still cant't pause/play with Apple Headphones. |
I've tried two ways but I failed.
Any idea? |
The main problem is that this issue its no consistent, I'm still on 1.8 build 3 (same build from my last comment) and noticed that right now it is working with my beatsX bluetooth headphones. And I cannot reproduce the non working state at the moment, but I'm sure that later it won't work. |
@joaodforce I think that the bluetooth headphones send |
Looks like this problem is actually extended to several Bluetooth headphones. In my particular setup (Motorola S305: https://www.amazon.com/Motorola-Bluetooth-Stereo-Headset-Microphone/dp/B002BH3I9U) it doesn't work with next/prev buttons. I tested it some weeks ago, so I'll try later, but I believe that only Play/Pause button works. |
After my last comment I noticed a pattern in the issue, It looks like if the headphones are connected before you first open HSMKE, they work as you would expect, if you connect it afterwards then it wond register. My guess would be that HSMKE is not registering some kinds of devices to its functionality. |
It also doesn't work with Bose QC 35 headphones |
Not working also with Fitbit Flyer (complete mute until i quit the app) |
Btw. same issue with the standard Apple EarPods. Volume regulation works, skipping rewind is very buggy and sometimes stops playing music or starts playing music. |
AirPods play/pause/next works fine, I will check out EarPods when I get back home. |
Stumbled upon this issue. I can confirm that it works out of the box as expected with Sony MDR-ZX770 (Bluetooth headphones) start/stop + skipping / rewind just fine. Was there a fix in the meantime? Or is this issue only related to some hardware? |
@krueschi this issue is only related to cable headphones (3.5mm headphone jack). The ones included with an iPhone for example. Bluetooth headphones work fine |
Any progress on that issue? |
Summary
When listening to music with classic headphones (3.5 mm headphone jack) a press on play/pause is executed twice. This means the music stops and immediately plays again. It is not possible to pause the sound with headphones
Steps to Reproduce
Open iTunes and start a song. Insert headphones and press the play/pause button
Actual Results
The music stops and immediately starts playing again
Expected Results
The music stops whenever triggered from keyboard or headphones
Note
Next (2x play) & previous (3x play) works but the music also stops for a moment
Device
iMac 5K Late 2015
macOS 10.13.2
The text was updated successfully, but these errors were encountered: