obs-studio/obs/window-basic-main-outputs.hpp

#pragma once

class OBSBasic;

struct BasicOutputHandler {
	OBSOutput              fileOutput;
	OBSOutput              streamOutput;
	bool                   streamingActive = false;
	bool                   recordingActive = false;
	OBSBasic               *main;

	OBSSignal              startRecording;
	OBSSignal              stopRecording;
	OBSSignal              startStreaming;
	OBSSignal              stopStreaming;

	inline BasicOutputHandler(OBSBasic *main_) : main(main_) {}

	virtual ~BasicOutputHandler() {};

	virtual bool StartStreaming(obs_service_t *service) = 0;
	virtual bool StartRecording() = 0;
	virtual void StopStreaming() = 0;
	virtual void StopRecording() = 0;
	virtual bool StreamingActive() const = 0;
	virtual bool RecordingActive() const = 0;

	virtual void Update() = 0;

	inline bool Active() const
	{
		return streamingActive || recordingActive;
	}
};

BasicOutputHandler *CreateSimpleOutputHandler(OBSBasic *main);
BasicOutputHandler *CreateAdvancedOutputHandler(OBSBasic *main);
UI: Refactor output handling To accommodate multiple types of outputs, there has to be some level of abstraction. The BasicOutputHandler structure will give us a way that we can switch between different output configurations. 2015-02-06 11:17:33 +00:00			`#pragma once`

			`class OBSBasic;`

			`struct BasicOutputHandler {`
			`OBSOutput fileOutput;`
			`OBSOutput streamOutput;`
UI: Don't use activeRefs to determine if active Due to certain design changes for delay, it's better to simply determine whether outputs are active via booleans rather than an activeRefs variable, which could get decremented more than once if say, the signal for stopping the stream gets called more than once for whatever reason (which may happen in the case of delay due to the way delay works) 2015-09-06 23:07:45 +00:00			`bool streamingActive = false;`
			`bool recordingActive = false;`
UI: Refactor output handling To accommodate multiple types of outputs, there has to be some level of abstraction. The BasicOutputHandler structure will give us a way that we can switch between different output configurations. 2015-02-06 11:17:33 +00:00			`OBSBasic *main;`

UI: Release recording/streaming signals before outputs 2015-07-04 06:00:21 +00:00			`OBSSignal startRecording;`
			`OBSSignal stopRecording;`
			`OBSSignal startStreaming;`
			`OBSSignal stopStreaming;`

UI: Refactor output handling To accommodate multiple types of outputs, there has to be some level of abstraction. The BasicOutputHandler structure will give us a way that we can switch between different output configurations. 2015-02-06 11:17:33 +00:00			`inline BasicOutputHandler(OBSBasic *main_) : main(main_) {}`

			`virtual ~BasicOutputHandler() {};`

			`virtual bool StartStreaming(obs_service_t *service) = 0;`
			`virtual bool StartRecording() = 0;`
			`virtual void StopStreaming() = 0;`
			`virtual void StopRecording() = 0;`
			`virtual bool StreamingActive() const = 0;`
			`virtual bool RecordingActive() const = 0;`

			`virtual void Update() = 0;`

UI: Don't use activeRefs to determine if active Due to certain design changes for delay, it's better to simply determine whether outputs are active via booleans rather than an activeRefs variable, which could get decremented more than once if say, the signal for stopping the stream gets called more than once for whatever reason (which may happen in the case of delay due to the way delay works) 2015-09-06 23:07:45 +00:00			`inline bool Active() const`
			`{`
			`return streamingActive \|\| recordingActive;`
			`}`
UI: Refactor output handling To accommodate multiple types of outputs, there has to be some level of abstraction. The BasicOutputHandler structure will give us a way that we can switch between different output configurations. 2015-02-06 11:17:33 +00:00			`};`

			`BasicOutputHandler CreateSimpleOutputHandler(OBSBasic main);`
UI: Add advanced output settings Adds an 'advanced' mode to the output settings to allow more powerful and complex streaming and recording options: - Optionally use a different encoder for recording than for streaming to allow the recording to use a different encoder or encoder settings if desired (though at the cost if increased CPU usage depending on the encoders being used) - Use encoders other than x264 - Rescale the recording or streaming encoders in case the user wishes to stream and record at different resolutions - Select the specific mixer to use for recording and for streaming, allowing the stream and recording to use separate mixers (to for example allow a user to stream the game/mic audio but only record the game audio) - Use FFmpeg output for the recording button instead of only recording h264/aac to FLV, allowing the user to output to various different types of file formats or remote URLs, as well as allowing the user to select and use different encoders and encoder settings that are available in the FFmpeg library - Optionally allow the use of multiple audio tracks in a single output if the file formats or stream services support it 2015-01-26 21:41:22 +00:00			`BasicOutputHandler CreateAdvancedOutputHandler(OBSBasic main);`