The Play+ is not recognized on macOS, neither as a MIDI nor as an audio device. The device should appear in the Audio MIDI settings as both a MIDI and audio device when connected.
Reproduction Steps
Connect Play+ to Mac using the factory USB cable.
Open Audio MIDI settings on macOS.
Observe that Play+ does not appear in the list of devices.
Occurrence
Bug is reproducible always
Found in
Version: 1.0.1
Build: 1405
Additional Context:
Mac: M2 Max
macOS: Sonoma 14.6.1
Ableton Live 12 Suite 12.0.25
No hubs, adapters or alternate cables used, direct connection to USB port
This issue follows a series of connection instabilities and audio dropouts. At one point, it was connecting but syncing with Ableton was so unstable that it brought my computer to a halt. It reached a point where I even had to restart my Mac. Whenever we do get it to connect again, I suspect I’ll face the same issues:
Frequent audio dropouts when used with Ableton Live.
Sample rate for Play+ appears locked at 44kHz, despite my system running at 48kHz.
Unstable connection - device briefly disappears and reappears in Audio MIDI Setup.
Issues persisted even when running system at 44kHz.
Experienced user, basic troubleshooting already attempted, including several restarts and trying different ports.
Again, factory USB cable. Are you sure it doesn’t do MIDI? It was appearing in Audio/MIDI Setup and Ableton as a MIDI device for a brief moment before going haywire….
I suppose I also must repeat — with emphasis — that right now it’s not showing up in macOS at all, anywhere. I don’t want to derail this thread, or make it too long by answering questions that were already answered I’m having trouble getting Polyend to respond as it is.
The best way is to check on some other computer, or better yet, with a friend. If there is no result, write to the company’s technical support. Maybe it’s a marriage.
I actually wrote to them a week ago, so I’m trying here. We’ll see!
I plugged it into an Intel Macbook Pro running Sonoma (good idea!), and it shows up. I can’t run more tests right now, but I guess I need to “reset” my main Mac somehow. I’ve restarted several times.
Also, I’m back in town and my Play no longer connects to my Macbook. It shows up as a MIDI device for a second while the Play boots, but disappears quickly. No action on the audio device front.
Let’s just wait to see what Polyend say. Although it’s been 8 days since I emailed them about this issue…
Edit: They emailed me back and said they’re aware of/working on it.
Hi @nathan.rightnour , have you managed to fix the problem? Did you get help from our customer support via email? I suspect it might be a faulty HW: cable, USB socket on Play or your laptop, or both. Have you tired using another computer or another cable? I cannot think of anything else at this point, please follow general guidelines (but I think you’re already doing so):
Avoid using USB hubs (we don’t support them) and instead connect the device directly to your computer USB port
To make sure the device i is correctly recognized as an audio device by your computer OS and DAW:
first connect the USB cable while your device is still switched off
then power on the device
launch the DAW
and finally select the device as your audio input and output device
If you are still experiencing issues then we suggest trying another buffer size setting or creating an aggregate device to use a different audio output device simultaneously with Play as your input device
Let us know if you had any progress with this critical issue please. Thanks for your patience.
Hi, support ended up getting back to me and they said they “haven’t found a solution”. In the meantime I sent it back for now, just because I personally won’t end up using it without DAW integration.
I swapped out every part: USB-C cable, miniSD card, (the miniSD adapter for what it’s worth), and tested 2 Macs on different OS’s and chips (Intel and Apple) and even updated one of the Mac’s OS post-issue.
If you’re able to use it with Sonoma or Sequoia, the issue could have been a manufacturing issue with the unit itself. Which would be strange indeed, but I’ve seen weirder.
Hi @nathan.rightnour , OK thanks for letting us know. I’m sorry you had a bad experience. I’ll close the report for now as we cannot reproduce it. Please let us know if you have any further issues in the future. Best regards