OBS Media Source lifecycle: restart, close and end-of-playback
An OBS Media Source can restart, unload or disappear according to its native scene-lifecycle settings without changing the movie on disk. Inspect the actual source path and properties, then test becoming active, ending and returning to the scene. A brief blank or repeated opening is not by itself evidence that the original recording changed or disappeared.
Open the relevant downloader · Platform tools and access limits
Identify the actual source and retained file
Select the intended Media Source and open Properties. Confirm the Local File path and recognize the movie by its actual content. Similar source names in different scenes can refer to different files. Preserve the authorized original and note which scene/source relationship you are testing rather than substituting another movie before the cause is known.
Keep required picture and sound separate in the observation. A source can be present but hidden behind another layer or routed differently for audio. Confirm the native source’s visibility and actual receiving context before interpreting a blank program view as damaged encoded media.
Review each lifecycle choice independently
Inspect Restart playback when source becomes active, Close file when inactive, Loop and Show nothing when playback ends in the documented Media Source interface. They answer different questions: returning to the source, freeing an inactive resource, repeating content and the presentation after its ending.
Unloading an inactive file can require a reload when it returns, so the transition needs an actual scene test. Do not assume a repeated first scene means the disk file was replaced. Choose the behavior required for the production and change one property at a time so the result can be attributed to that choice.
Verify the complete scene transition and recording
Make a short permitted local test: activate the scene, play a recognizable passage, switch away and return, then let the source reach its end. Observe the first wanted picture and sound after each step. Compare the behavior with the settings you chose rather than treating a source-properties preview as a completed receiving test.
Record a bounded sample where recording is authorized and reopen its actual output. Check the transition, later media content and ending. A successful source load is not proof that the program recording contains every intended frame or the right soundtrack. If a delay is unacceptable, revise the supported lifecycle or transition choice and verify a new sample.
Retain source identity and avoid false recovery claims
Keep the referenced movie available through its actual local path and preserve the accepted scene configuration. Moving a file can break that relationship independently of restart settings. Reconnect the intended authorized resource and check recognizable content instead of changing a reference to an unrelated similarly named clip.
SocialVidDownloader does not manage OBS scenes, private Media Source paths or scene-triggered playback. Its downloaded movie remains a file to retain and verify; it does not supply these native controls. Leave missing references or unverified recordings incomplete rather than reporting that a familiar source thumbnail proves the saved program movie contains the requested scene.
Worked example
Example: Close file when inactive unloads a local movie, and returning to the scene briefly shows no picture while it reloads. The reviewer tests the return and actual recording, keeps the parent file and changes the supported lifecycle choice if needed instead of claiming the movie was deleted.
Related guidance
Sources and verification
Reviewed 2026-10-13. Product behavior is limited to available source formats and provider access; it is not a promise that every public link works.