How to film a wedding reception or first dance with both iPhone cameras

Split the night into takes around its own moments, not one running file

A dual-camera recording is one continuous file from record to stop, with no pause built in, and a reception is long enough that trying to hold one file open across the whole night is impractical before it is anything else — hours of storage and battery spent on a table full of small talk between the parts you actually wanted. The night already has its own structure to cut around: the entrance, the first dance, the toasts, the cake, the bouquet toss, a stretch of open dancing.

Starting a fresh recording for each of those, rather than one that runs the whole evening, also means you are not scrubbing through hours of footage afterwards to find the ninety seconds that mattered. Short, clearly timed clips in the app's own library are easy to tell apart later; one long file is not.

DJ lighting is the flicker problem other rooms show, just for hours instead of minutes

Moving coloured lights over a dance floor run on the same principle as an ordinary indoor bulb: many of them pulse on and off far faster than the eye can follow, fast enough to read as a steady colour to a guest but not fast enough to fool a camera sensor that reads the scene as a series of short, separate exposures. When a frame happens to land on a dimmer part of that pulse, it comes out darker than the frames around it, and strung together that reads as a flicker or a slow band moving through the shot.

Because the front and back cameras are separate hardware reading out at their own instant rather than one shared shutter, they can catch a different point in the same light's pulse — one half of a dual-camera frame flickering while the other looks steady, even pointed at fixtures a few feet apart. If that happens, repointing just the camera that is flickering toward a different light on the floor is worth trying before assuming the whole shot is affected; the two sides are not tied together. Steadier sources — a candle-lit table, warm uplighting along a wall — do not have this problem the way a moving strobe does, which is part of why footage from the tables often looks calmer than footage from the floor.

A spin or a dip on the dance floor is the same wobble as a fast pan

A phone camera sensor does not capture a whole frame at once; it reads the scene a strip at a time over a very short span, and anything moving quickly during that read shows up leaning, skewed or wobbling rather than sharp — the same effect a fast whip-pan produces anywhere else, not something specific to a reception. A dance floor is full of exactly the kind of fast movement that triggers it: a spin, a dip, someone twirling past close to the lens.

The two cameras read this independently, so a spin that skews badly on the camera pointed at the dancers may look completely normal on the camera pointed at your own face, and vice versa. There is no setting that removes this — it comes from how the sensor reads a frame, not from anything a dual-camera app is doing on top of that — so the more reliable fix is the same one that works for any fast pan: hold the phone steadier through the movement, or step back so the same spin covers fewer pixels crossing the frame, rather than following the couple in close with a moving phone.

The microphone struggles near the speakers specifically, not the room in general

A reception microphone problem is usually not the same one a quiet ceremony has. There, the issue is a voice too faint to reach the mic; here, right next to a DJ speaker during open dancing, the issue is a microphone with more sound arriving than it has room to represent, which comes out as a harsh, crackly distortion rather than quiet audio. That is clipping, and it happens right at the microphone before any setting in the app gets a chance to touch it — there is no volume dial in a dual-camera recorder that could have turned it down in advance, because the distortion has already happened by the time the sound becomes a recorded sample.

The practical fix is distance and timing rather than a setting: step back a few feet from the speaker stack if you want usable sound from the dance floor, and use the calmer moments — the toasts, the cake, dinner conversation at the table — for anything where the audio itself matters, rather than open dancing where the room is, on purpose, as loud as it gets. Once a clip is recorded distorted, boosting the volume afterwards brings up the distortion along with everything else; it does not undo it.

Picture-in-picture for the entrance and the floor, split for the first dance

The grand entrance and open dancing both have one clear subject that deserves the full frame — the room, the couple walking in, the crowd on the floor — with your own reaction sitting in the corner window. That is picture-in-picture's natural job: one thing is the point, and your face is a smaller layer alongside it.

The first dance is the one moment on a reception floor that plays more like the ceremony's kiss than like everything else that night: a couple's few unrepeatable minutes where a guest's own reaction is worth close to as much frame as the dance itself, not a small window tucked in a corner. Splitting the frame gives both cameras equal height rather than making one dominant, which is the layout built for a moment where both sides matter about the same amount. Switching back to picture-in-picture once open dancing starts keeps the room as the main subject again for the rest of the night.

What stays with you afterwards

A reception produces more short clips than a ceremony does, simply because there are more distinct moments to separate rather than one processional and one kiss. DualCam keeps every one of them in the app's own library with a thumbnail, with nothing uploaded or analysed while you are recording, so sorting through a night's worth of takes afterwards and saving or sharing only the ones worth keeping is something you do on your own schedule, not something the app decides for you in the moment.