Two Hosts on One Machine
Running Premiere Pro and After Effects side by side — separate ports, names, logs and trust stores — plus what happens with two monitors live at once.
You can run Premiere Pro and After Effects at the same time with PreviewMonitor loaded in both. They do not collide: everything that could collide is kept separate per host. Your iPhone sees two devices in its list and pairs with each one independently.
The same plugin binary is loaded by both applications, but each runs in its own process, and the plugin asks which application it is in before it picks a port, a network identity, a log file and a trust store.
What is separate
| Premiere Pro | After Effects | |
|---|---|---|
| TCP control port | 47100 | 47110 |
| Network identity | The machine's Instance ID, unchanged | The Instance ID with -ae appended |
| Display name on the phone | <machine> — Premiere | <machine> — After Effects |
| Trusted iPhones | trusted.json | trusted-ae.json |
| Windows log file | plugin.log | plugin-ae.log |
| Audio | Works | None. There is no audio path in the After Effects side at all |
| Transport control | Control Surface plugin, ships in both installers | AEGP bridge, Windows-only, ships in no installer — otherwise synthetic keystrokes |
The separator in the display name is an em dash. A machine named STUDIO-PC
shows up as STUDIO-PC — Premiere and STUDIO-PC — After Effects.
The UDP video and audio ports, 47101 and 47102, are shared — they are ports on the iPhone, not on the host, so two host applications never contend for them.
Premiere Pro's identity is deliberately unsuffixed at the network level. Its Instance ID is the machine's raw ID, so an iPhone that paired before After Effects support existed keeps working with no re-pairing. Only the display name gained a suffix.
What is shared
One file, install.json, holds the machine's identity and the two Setup-window
toggles. Both hosts read and write it:
- Device name — rename it in one host's Setup window and both change. Each host still appends its own suffix.
- Discoverable on network — one switch for the whole machine.
- Use NVIDIA / Intel HW HEVC encoder — likewise, one switch for both.
There is no way to make one host discoverable and the other not.
Pairing both
Each host issues its own pairing token, so you pair twice. There is nothing special to do — connect to the first device, type the code, then connect to the second and type its code.

Both rows carry the same machine name and differ only by the suffix after the em dash.
Clicking Forget in one host's Setup window has no effect on the other. The two lists are genuinely independent files:

trusted.json and trusted-ae.json sit next to each other, alongside the shared install.json.
The full pairing model is in Trusted iPhones.
One phone, one host at a time
The phone connects to one device at a time. Switching from the Premiere Pro device to the After Effects device is a disconnect and a reconnect, and both happen automatically when you pick the other row.
Each host also accepts only one phone. A second iPhone connecting to the same host replaces the first.
Reading the right log
On Windows the two hosts write different files in the same folder, so make sure you are reading the one you mean:
%LOCALAPPDATA%\PremiereLive\plugin.log Premiere Pro
%LOCALAPPDATA%\PremiereLive\plugin-ae.log After EffectsmacOS writes no plugin log file at all — both hosts log to the unified system log under the same subsystem, separated by process. See Logs and diagnostics.
A known rough edge
The Setup window's Advanced info → NETWORK → Ports row is hard-coded to 47100 control · 47101 video · 47102 audio. Opened from After Effects it still says 47100, even though that host listens on 47110. The video and audio ports it lists are correct.
Discovery is unaffected — the port travels in the mDNS record, not in that label.
Program Monitor and Source Monitor
A second, smaller version of the same question comes up inside Premiere Pro alone. Premiere Pro creates one Transmit instance per open sequence and per monitor, and activates the ones that are on screen.
Both the Program Monitor and the Source Monitor can be active at once. When they are, both feed the same single connection to your phone — the plugin runs one network transport per process, and every active instance pushes into it.
There is no monitor picker. Not in the app, not in the Setup window, and not in the protocol: the plugin has no command for choosing a source. What you see is whichever monitor Premiere Pro most recently pushed a frame from.
If the phone keeps flicking between two different pictures, close or deactivate the monitor you do not want. Playing back in the monitor you do want is usually enough, because a monitor that is not producing frames stops pushing.
Instances that Premiere Pro has deactivated are silent. They keep their last frame cached, but they only replay it when no other instance is active — for example when Premiere Pro is minimized on a parked playhead — so a stale sequence cannot appear alongside the live one.
Last updated on
Transport Control
How the phone's play, step and jump buttons drive the host — the Control Surface plugin, the After Effects bridge, and the keystroke fallback.
Logs and Diagnostics
Where PreviewMonitor writes its logs, crash dumps and config files on Windows and macOS, the two debug switches, and what to send support.