P3SA not functional during control mode?
Posted: Mon Aug 04, 2025 9:30 pm
Was curious if anyone had ran into this problem with the Push 3 Standalone in control mode. I recently purchased the standalone version and all of the instructions say that simply plugging it in via the provided USB C cable included. However, once plugged in the push remains unusable and stuck on "plug your device to your computer and start a live session". I have tried many troubleshooting steps listed below and nothing has worked so far.
- Ensure midi and audio reflects push when in control
- updated to latest Mac OS for M4 MacBook Pro
- Reset push to factory settings
- Updated push firmware and using live 12 suite
- Authorized live 12 suite
This is a weird issue as I am able to connect my push to live in standalone mode and I am able to transfer files and samples. When connected to control mode I am able to use the push as an audio interface. It is discoverable in audio input and output in live settings. The only thing I can think of is that the latest firmware is causing some issue however there is no option to rollback firmware updates (only software) in abletons website. I have contacted ableton and sent a status report so we will see but I figure I would post here to see if there have been similar experiences? If you have ran into this issue and have a fix I would greatly appreciate your help!
- Ensure midi and audio reflects push when in control
- updated to latest Mac OS for M4 MacBook Pro
- Reset push to factory settings
- Updated push firmware and using live 12 suite
- Authorized live 12 suite
This is a weird issue as I am able to connect my push to live in standalone mode and I am able to transfer files and samples. When connected to control mode I am able to use the push as an audio interface. It is discoverable in audio input and output in live settings. The only thing I can think of is that the latest firmware is causing some issue however there is no option to rollback firmware updates (only software) in abletons website. I have contacted ableton and sent a status report so we will see but I figure I would post here to see if there have been similar experiences? If you have ran into this issue and have a fix I would greatly appreciate your help!