The transport buttons do nothing
Play, pause and frame-step on the phone have no effect. Foreground focus, the Control Surface plugin, and what After Effects can and cannot do.
You tap play on the phone and Premiere Pro ignores it.
The transport bar has five buttons and they take two completely different routes to the host, so the first job is working out which route you are on.
Left to right: Go to In point, Step back one frame, Play/Pause, Step forward one frame, Go to Out point. Those five are the whole set — there are no shuttle or jog controls in the app, on any host.
The play glyph flips whether or not the command landed. The app switches the icon optimistically on your tap and only later reconciles it against what the host reports. A play icon becoming a pause icon is not evidence that Premiere Pro heard you.
1. Make sure you are actually streaming
The app drops every transport command unless the connection is in the streaming state. The buttons stay lit, they animate the press, and nothing is sent.
If the picture is black or frozen, you may be connected but not streaming — handle that first at The screen is black.
If the transport bar is not visible at all, the HUD has auto-hidden. Tap anywhere on the picture to bring it back.
2. Bring Premiere Pro to the foreground
This is the most common cause by a wide margin.
When the Control Surface plugin is not available, the plugin falls back to synthetic keystrokes — it injects Space, the arrow keys and so on into the operating system's input queue.
On Windows those keystrokes are not addressed to Premiere Pro. They go to whatever application is in the foreground. If you are in a browser when you tap play on the phone, the browser gets a Space and scrolls. The command is not lost — it is delivered to the wrong app.
Click Premiere Pro so it is the frontmost window, then try the phone again. If the buttons work now, you are on the fallback path and step 3 is the real fix.
On macOS the behavior is different: the keystrokes are posted inside Premiere Pro's own process rather than through the OS. Frame stepping and the In/Out jumps do not need focus, but play/pause does — it activates Premiere Pro first, so a phone tap can pull Premiere Pro to the front on you.
3. Check the Control Surface plugin
The proper path uses a second plugin — a Control Surface plugin that talks to Premiere Pro's real command API. With it loaded, transport works without Premiere Pro being in front and without touching your keyboard shortcuts.
Open Preferences → Control Surface in Premiere Pro and look for the device in the list.
The device is listed as PremiereLive, not "PreviewMonitor". That is the
old engineering name; the Control Surface plugin's display string was never
renamed. Everything else in the product — the Transmit device, the Setup
window, the installer — reads PreviewMonitor. Nothing is wrong.
If it is not listed at all, the file is not installed. The installers place it at:
| Platform | File | Location |
|---|---|---|
| Windows | PremiereLiveCtrl.acsrf | C:\Program Files\Adobe\Common\Plug-ins\ControlSurface |
| macOS | PremiereLiveCtrl.bundle | /Library/Application Support/Adobe/Common/Plug-ins/ControlSurface |
Note the folder is not under 7.0\MediaCore where the Transmit plugin
lives — Control Surface plugins have their own directory.
Reinstall PreviewMonitor if the file is missing, then restart Premiere Pro.
On macOS the bundle must be in /Library, not ~/Library. Premiere Pro scans
only the system-wide Control Surface folder and silently ignores the per-user
one, so a bundle copied to your home Library will never load.
There is nothing to configure — the plugin has no settings dialog by design.
4. Work out which route you are on
On Windows, the log settles it. Tap a transport button on the phone, then run:
findstr /C:"ctrl: bridge dispatch op=" "%LOCALAPPDATA%\PremiereLive\plugin.log"- A line per tap → the Control Surface route is working. If the button still does nothing, the command reached Premiere Pro and Premiere Pro declined it — check that the Program Monitor has a sequence, and that In and Out points exist if you are testing the outer two buttons.
- No lines → you are on the keystroke fallback. Go back to steps 2 and 3.
Two more lines worth knowing:
| Line | Meaning |
|---|---|
ctrl: bridge dispatch installed | The Control Surface plugin loaded and registered, once at startup |
Ctrl bridge unavailable — fallback to keyboard nudge | The bridge was missing when a phone connected. Logged once per connect, not per tap |
ctrl: play/pause: UI dispatcher not installed, can't post | Windows only, and the nastiest case — see below |
If you see ctrl: play/pause: UI dispatcher not installed, can't post, play and
pause are silently dead. The Control Surface plugin reports success to the
transport layer, so the keystroke fallback never runs, and the button does
nothing with no other symptom. Frame stepping and the In/Out jumps still work.
Restart Premiere Pro.
On macOS there is no log file. Use Console.app, or:
/usr/bin/log show --predicate 'subsystem == "com.premierelive.plugin"' --last 10m --info5. Know what the outer two buttons do
The buttons either side of the frame-step pair go to the sequence's In and Out points, not to the start and end of the timeline. On a sequence with no In or Out set, Premiere Pro's own behavior decides what happens — which can look like the button doing nothing.
After Effects
After Effects gets the same video through the same Transmit plugin, so the picture behaves identically. Transport is a different story, and it is worth being blunt about it.
The After Effects transport bridge ships in no installer. Neither the
Windows installer nor the MSI includes PremiereLiveAE.aex, because its
install path is specific to the After Effects version and After Effects may not
be present at all. It has to be placed by hand.
It does not exist on macOS. The bridge is built only on Windows. On macOS After Effects there is no bridge to install, and transport falls back to keystrokes with everything that implies.
Without the bridge, the step buttons edit your composition. The fallback sends → and ←, which in After Effects shift the selected layer one frame in time rather than moving the playhead. Nothing re-renders, so the picture on the phone is identical and there is no sign it happened; Undo is the only way back. If the step buttons appear to "do nothing" in After Effects, check whether a layer moved. Deselect all layers before using the transport bar, or install the bridge.
Where the bridge is installed, on Windows:
| Phone button | Mechanism | Needs After Effects in front? |
|---|---|---|
| Step forward / back one frame | Real AEGP API | No |
| Go to In point / Out point | Real AEGP API — seeks to the comp's first frame and its last whole frame | No |
| Play/Pause | Space posted straight to After Effects' panel window, with the app's active flag flipped first | No — it works even minimized |
Play and pause use a keystroke because After Effects exposes no preview API at
all. But the bridge does not inject it into the system input queue: it posts the
message to After Effects' own window, and when After Effects is backgrounded it
first flips the application's active flag (After Effects suspends its preview
engine when it loses activation) and sends the key a moment later. Nothing on
the bridge path requires After Effects to be the foreground application. The
foreground requirement belongs to the keystroke fallback — which, since no
installer ships the .aex, is what a stock After Effects install is running.
Audio never works in After Effects. There is no audio path on the After Effects side of the plugin at all. The speaker button on the phone does not turn orange to tell you, because the app assumes a host has audio until the plugin says otherwise and the After Effects side never says otherwise. See No audio.
There are no shuttle buttons anywhere in the app. The iPhone app declares exactly five transport commands, none of them a shuttle. The wire protocol reserves shuttle opcodes and the desktop plugin implements them against Premiere Pro's transport suite, but no shipping build can send one — to After Effects or to Premiere Pro. If you are looking for a shuttle control, it does not exist.
Full detail on both mechanisms is in Transport control and Transport.
Last updated on
The colors look wrong
What the phone can and cannot reproduce — transparency over black, untagged BT.709, no HDR, and a Windows-only downscaling difference.
Reset and reinstall
The escalation path when nothing else worked — forget a device, reset the app, clear the host's state, and reinstall on both platforms.