The view stays until you run /camera clear or set another preset. Players can't move the free camera themselves.
The presets and ease curves come from Bedrock 1.26.52 itself: the six presets are the files in the game's behavior pack, and the 32 curves are the names the server accepts. Each form the generator can write was run on a Bedrock Dedicated Server against a simulated player, from a plain preset to a free camera facing an armor stand, and every one succeeded except easing into first person, which the generator no longer offers.
The free preset is the one for cutscenes, since it's the only one that takes a position and an angle. follow_orbit and fixed_boom take offsets instead, which shift the picture and the point the camera tracks. Building a Java cutscene instead? The camera path generator keyframes one into a data pack function.
No. /camera is a Bedrock command. On Java, cutscenes are built by riding a display entity or teleporting the player every tick, which the camera path generator does for you.
Chain several free-camera sets with ease, each in its own command block or function line, timed with delays of the same length as each ease. in_out_sine is the gentlest curve for a camera move; linear moves at a constant speed. End with /camera @s clear to hand the view back.
Bedrock won't ease into the first_person preset: the command succeeds for nobody when it has an ease. Set first_person without an ease and the view switches instantly; the generator leaves the ease off for that preset.
rot points the camera at a fixed angle, pitch then yaw. facing aims it at an entity or a spot instead, so you don't have to work the angle out yourself.
