Diagram: on the left, scene 1 with the camera full screen. In the middle, the Move transition with a timeline of roughly 400 to 700 milliseconds. On the right, scene 2 with a small camera in the corner above a GPS map. Below, a note that you still need a fallback scene for signal loss.

In this guide

1. Moving sources instead of just switching

Move Transition animates the position, size, and visibility of matching sources between two OBS scenes. A camera picture can travel from full screen into a corner while a GPS map or another overlay takes over the main area.

Additional Move filters can also move sources within a scene, change values, or be triggered by hotkeys and other events.

2. Where Move Transition helps in IRL streaming

The animation improves how things look, but it doesn't fix connection problems. In a real signal loss, the fallback scene still has to be quick and reliable to reach.

3. Installing Move Transition

  1. First note down your current OBS version and export a backup of your scene collection.
  2. On the official OBS resources page, pick the version that matches your operating system and OBS.
  3. Close OBS completely and, if possible, use the installer that is provided.
  4. Install the plugin, then restart OBS.
  5. Under Scene Transitions, check that Move or Move Transition is selectable.
Check versions: The current Move version 3.2 needs OBS 31.1 or newer. Requirements can change, so always read the release notes.

4. Setting up your first Move transition

  1. Create two test scenes, for example Camera Full Screen and Camera with Map.
  2. Use the same camera source in both scenes, or name the sources clearly so they match.
  3. In the second scene, shrink the camera and place it in the corner you want.
  4. Under Scene Transitions, create a Move transition with the plus sign.
  5. Set the duration to roughly 400 to 700 milliseconds at first.
  6. Switch several times in both directions and check position, aspect ratio, and audio.
Start simple: Move one camera between two positions first. Then add the map, text, alerts, and other sources one at a time.

5. Matching sources between scenes correctly

For Move Transition to recognize a source, the starting source and the target source have to match. The most reliable setup is the same existing source in both scenes. Alternatively, the plugin offers rules for similar names, stripped trailing numbers, or specific parts of a name.

Studio Mode: Certain combinations with duplicated sources can affect the matching. If you see unexpected jumps, check source names and duplicates first.

6. Move Source, Move Value, and action filters

The add-on covers more than the scene transition. Move Source filters can move a source within a scene between prepared positions. Value and audio filters can animate suitable settings. Depending on the filter, triggers such as show, hide, activate, deactivate, hotkey, or chained Move actions are available.

Move filters at a glance
FilterWhat it does
Move Sourceshifts a source back and forth between prepared positions within a scene
Move Value and Audioanimate suitable settings
Triggers (depending on the filter)show, hide, activate, deactivate, hotkey, or a chained Move action

For IRL, build complex sequences out of a few clear steps. Several animations started at the same time can overwrite each other.

7. Three useful IRL examples

Camera and GPS map

The camera starts full screen, shrinks when the map comes up, and moves into a safe corner. When the map closes, it returns to its original position.

BRB with a status window

The live picture shrinks briefly while a prepared status box appears. In a hard signal loss, you should still switch straight to a complete BRB or offline scene.

Alert or TTS notice

A notice slides briefly into a free area of the frame and disappears again. Test sound and animation separately so viewers don't hear the alert twice.

8. Common errors and performance

ProblemPossible causeCheck
Source jumps instead of glidingSources weren't matchedCompare names and source type
Picture is distorteddifferent bounding box or scalingCheck aspect ratio and Scale Type
Animation stuttersGPU/render load too highCheck OBS stats and cut back on effects
Wrong source movesnames too similargive sources unique names
Transition collidesseveral automations control the same sourcetest Scene Switcher and Streamer.bot one at a time

Before the real stream, run a private test with the camera, map, alerts, BRB, and the return to the live scene. Check again after OBS or plugin updates.

9. Privacy and safe design

Move Transition works locally in OBS. Visible sources can still contain GPS maps, location text, chats, browser sources, or other personal information, though. An animation does not protect that data.

10. Common questions

Do I need Move Transition for IRL streams?

No, the plugin is an optional add-on for OBS. Scene changes and overlay movements look smoother. It changes nothing about your connection, bitrate, or picture quality.

Why does the source jump instead of glide?

Most of the time, Move Transition doesn't recognize the source in the target scene. Check that both scenes use the same source, or that the sources have clearly matching names. And check for duplicates (see the table in section 8).

How long should a transition last?

Start with about 400 to 700 milliseconds. Then adjust the duration to the scene and your taste. Test the switch several times in both directions.

Can I move sources without a scene change?

Yes. Move Source filters do that: they move a source within a scene between prepared positions. More in section 6.

Does Move Transition help if the connection drops?

No. The animation only changes how things look. In a real signal loss, you still need a BRB or offline scene that you can reach fast. More in the emergency and outage plan.

Setup service & consulting

If you want to build a Move Transition workflow for your camera, GPS map, alerts, or BRB scenes, reach out in the IRL4YOU Discord.

Last technically reviewed: · Updated: · Published by IRL4YOU