A scene collection in OBS saves the scenes and sources for your school channel; a profile saves most of the output settings, including recording configuration. You need to set up both, then select the matching pair and test the recording path before relying on it.
OBS can also be launched with a chosen collection and profile and instructed to start recording. Those launch options do not, by themselves, recover OBS after a crash, restart a computer, solve a full or disconnected drive, or protect a recording from power loss.
Plan the school channel’s scenes and sources
Start with what a pupil, parent or staff member should see during the recording. A small set of purposeful scenes is usually easier to check and maintain than a large collection of nearly identical ones. For example, you might use a holding slide, a programme scene, an announcements scene and a closing slide. These are planning examples, not a required OBS template.
A scene is a composition of sources. Depending on the material, sources might include a background image, text, a video file, a webcam or a capture device. Decide which elements belong on screen at the same time, and what should change when the operator switches scenes. If a channel is built around prerecorded lessons, for instance, a programme scene might show the lesson video with a small school identity graphic, while the announcement scene uses a still background and text.
Name each scene and source so another member of staff can recognise its purpose. Names such as Assembly – video or Announcements – date text are more helpful during a handover than Scene 2 or Media Source 4. Keep school assets distinct from equipment inputs, and remove unused sources rather than leaving a crowded scene list that can confuse an operator.
In the preview, check visibility and stacking order. A source placed above another may cover it; a hidden source may leave a blank area when you switch scenes. Confirm that text is readable at the intended output size and that images are not stretched. If the channel uses a playlist or a long looping video, verify the expected behaviour rather than assuming it will advance as planned. Our guide to fixing an OBS media-source playlist that does not advance covers a related failure point.
Audio needs its own check. Identify whether sound comes from the video file, a microphone, desktop audio or another input. Watch the OBS audio meters while playing a representative clip, and listen to a test recording with headphones. A meter moving is useful evidence that OBS detects a signal, but it does not establish that the sound is intelligible or that the right source is being recorded.
Create a dedicated scene collection
A scene collection stores scenes and their sources, including global audio sources. It is the part of the setup that describes what the channel can show and hear. OBS documents collections as a way to keep sets of scenes and sources separate for different situations; see the OBS Project’s Scene Collections guide.
Create a collection specifically for the recorded school channel, rather than editing a general-purpose collection used for meetings or another broadcast. In OBS, use the Scene Collection menu to create a new collection, then give it a name that is clear in the menu and in any launch procedure. School Channel – Recording is one possible label. The exact wording is your choice; consistency matters more than the example.
Build the planned scenes in that collection and add the sources each one requires. Open every scene in the preview and check that the correct files and devices are selected. A media source pointing to a file on a staff member’s desktop may work on that person’s machine but fail after a handover or when the file is moved. Keep source files in a location the recording computer can access, and document where they are kept for the staff who maintain the channel.
Do not treat a scene collection as a complete copy of the recording setup. Switching to it does not set the recording format, destination, encoder or output resolution. Those settings are controlled elsewhere. The distinction is important if a school already has OBS configured for another purpose: a carefully prepared collection can still be paired with unsuitable output settings.
Create a recording profile
Create or select a separate profile for the school channel’s recording settings. Profiles hold most output-related settings, while collections hold scenes and sources. OBS explains profiles in its Profiles guide. Think of the profile as the recording behaviour and the collection as the pictures, text, video and audio sources arranged for the programme.
Open the Output settings and choose a deliberate recording destination. The path should point to storage that is available to the recording computer and has enough room for the school’s planned retention. There is no universal capacity figure: space needed depends on the actual recording settings, duration and how long the school keeps files. Work this out from a representative test recording and the retention policy, then check available capacity routinely.
Choose a recording format with recovery in mind. OBS’s Standard Recording Output Guide recommends MKV because an ungraceful stop will not corrupt the whole file. That is a useful safeguard for the file already being written, not a guarantee that the full recording will be complete or usable after every failure. If another workflow needs MP4, OBS provides a remux function to convert a completed MKV recording. Remuxing does not restore missing footage or guarantee recovery from damaged storage.
Select an encoder and quality setting that the actual computer can handle. The best choice depends on the machine and the material; a school should not copy settings without checking performance. OBS notes that output choices other than “Same as stream” can require additional resources. A higher resolution or frame rate may also increase the work the computer has to do, so test the chosen configuration rather than assuming that a more demanding setting is necessary.
Set the canvas and output resolution, and choose a frame rate appropriate to the source material. A still announcement slide and a lecture video do not necessarily need the same motion detail as fast-moving footage. OBS’s overview explains these video controls and notes that 60 fps can be more taxing than 30 fps. Treat that as a reason to test on the intended computer, not as a promise that a particular value will work on every machine.
Pair the collection with the profile
The collection and profile are separate selections. Choose the school collection for the channel’s scenes and sources, then choose the recording profile for its output settings. Do not assume that creating or switching one automatically selects the other. Before any recording, check both names in OBS and confirm that the settings on screen match the school’s documented setup.
It helps to write down the intended pair in a short operating note: collection name, profile name, recording path, format and the person responsible for checking the files. That note is especially useful when several people share the computer or when a substitute operator needs to start a recording. Keep the note next to the machine or in the school’s normal handover system, but do not include a stream key or other secret in a broadly shared document.
A collection/profile pair also makes maintenance clearer. If a teacher changes a title slide, that is usually a collection change; if the recording destination or encoder changes, that is a profile change. After either kind of edit, test the whole setup again. A change that seems local can affect the recording path: a replacement video may have different audio, for example, while an output change may increase disk use or encoding load.
If the channel’s purpose includes a sequence of lessons or subjects, decide whether scene switching alone is enough or whether a media playlist is part of the design. For a YouTube education stream, planning how multiple subjects fit into a playlist can help clarify the programme structure before you make sources. Keep the actual playlist behaviour in OBS testing; a schedule written on paper does not confirm that files advance correctly.
Select them and test a recording
Make a short test recording before using the setup for a school programme. OBS’s Quick Start Guide encourages testing for a few minutes rather than beginning with a real recording. For this use, include representative scenes and audio, and save to the intended destination. A test that uses a different profile, drive or media file may miss the problem you need to find.
During the test, switch through each scene and check the preview. Listen to the resulting file from beginning to end, rather than relying only on the live meters. Confirm that dialogue is present and clear, the right video appears, titles are legible and transitions occur as expected. Then open the file from its saved location to confirm it was written where you intended and that a second staff member can find it.
Check storage before a long session and decide what happens when space runs low. The recording path setting does not monitor retention policy for you. A school should identify who checks available capacity, who moves or archives completed files and what to do if the destination becomes unavailable. Do not promise a continuous recording until those practical responsibilities and the machine’s capability have been considered.
Test the computer under realistic conditions, including the intended resolution, frame rate, encoder and source material. If OBS struggles, reduce the load and test again. A lower frame rate or output resolution may be a better trade-off than a recording that drops frames or stops, depending on the content. OBS’s guide on reducing CPU use during a 24/7 YouTube stream may help when the computer is under pressure, but your own test remains necessary.
Finally, rehearse the operating procedure: which collection and profile to select, where to check that recording has started, and how to confirm the saved file afterwards. If the computer is shared, have another authorised operator follow the note without coaching. That is a practical way to find ambiguous labels or missing steps before the setup is depended on.
Set up launch options and recovery checks
OBS documents launch parameters that can select a scene collection and profile and begin recording. The relevant options include --collection, --profile and --startrecording; see the OBS launch-parameters documentation. A Windows launch command may be arranged to open OBS with the intended names and start the recording, but quote collection and profile names appropriately if they contain spaces. Validate the exact command on the school’s computer before using it routinely.
For a scheduled Windows launch, OBS’s documentation says to set the working directory to the folder containing obs64.exe. This helps the application launch in the documented context. It does not mean that a scheduled task, shortcut or command-line argument detects a failure and brings recording back after OBS closes unexpectedly. Launching OBS at a planned time is different from supervising it while it is running.
Make the boundary explicit in the school’s operating plan. The launch options do not establish crash recovery, automatic restart, recovery after a full disk, reconnection after a disconnected drive, or recovery from power loss. They do not promise an uninterrupted recording. Any separate recovery or alerting process depends on the school’s operating system, permissions, automation, storage and staff response, and must be designed and tested independently.
Write down who checks that recording has begun, how often the output and available storage are reviewed, and whom to contact if OBS stops or a drive is unavailable. The school may choose manual checks, operating-system scheduling, or other administrative measures, but should verify what those measures actually do on the computer in use. Avoid describing an untested arrangement as automatic recovery. If the recording matters, arrange a realistic failure rehearsal and confirm what the operator will see and do.
A recorded OBS file is also distinct from a YouTube live broadcast. This guide concerns configuring OBS to record locally; a launch option to start recording does not start a YouTube stream. If the school later uses OBS to send a live feed, review the relevant YouTube setup and channel requirements separately, and test that workflow on its own.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
What does an OBS scene collection save?
A scene collection saves the scenes and sources used in them, including global audio sources. It does not save the recording output configuration. Pair it with the profile that holds the school channel’s recording settings.
What does an OBS profile save?
A profile saves most output-related settings, including settings used for recording. It is separate from the scene collection, so switching collections does not automatically configure the recording path, format or output choices.
Can launch parameters restart OBS if it crashes?
The documented launch parameters can select a collection and profile and tell OBS to start recording when launched. They do not, on their own, detect a crash or restart OBS. Any monitoring and recovery process needs to be configured and tested separately for the school’s computer.
Should the school record in MKV or MP4?
OBS recommends MKV because an ungraceful stop will not corrupt the whole file. If a downstream workflow needs MP4, OBS can remux a completed recording; remuxing does not guarantee recovery of missing or damaged data.