Decouple Twitch VOD Track availability from hardcoded service checks (service == "Twitch")

[Soulhackzlol]

Right now, developers of third-party ingest tools and proxies are stuck in a Catch-22 because of how Enhanced Broadcasting (EB) and the Twitch VOD Track are gated.

If we look at OBSBasicSettings::UpdateVodTrackSetting():

void OBSBasicSettings::UpdateVodTrackSetting()
{
    bool enableForCustomServer = config_get_bool(App()->GetUserConfig(), "General", "EnableCustomServerVodTrack");
    bool enableVodTrack = ui->service->currentText() == "Twitch";
    
    if (enableForCustomServer && IsCustomService()) {
        enableVodTrack = true;
    }
    // ...
}

Because of recent PRs restricting custom EB configurations ( #13487 ), we run into a wall:

1. If we use a Custom Service (rtmp_custom), we can use the EnableCustomServerVodTrack flag in global.ini to get the VOD track back. BUT we lose Enhanced Broadcasting because EB relies on an auto-config URL that we can't easily inject into a pure custom service.
2. If we try to piggyback off a native service (or create a custom plugin) to keep EB working, we lose the VOD Track because enableVodTrack strictly requires ui->service->currentText() == "Twitch".

This hardcoded coupling means it is currently impossible to utilize both Enhanced Broadcasting and the VOD Track simultaneously on any proxy, relay, or custom setup.

Proposed Solution

The simplest and most non-intrusive fix would be to expand the existing config override so it isn't strictly gated behind IsCustomService().

If we added a global config flag (e.g., EnableForceVodTrack in global.ini) that enables the VOD track UI for any service, it would completely unblock third-party tools.

Alternatively, decoupling the VOD track from the "Twitch" string entirely and moving it to a service capability flag (OBS_SERVICE_CAP_VOD_TRACK) would allow custom service plugins to declare support for both EB and multitrack audio natively.

Impact

This minor change would allow advanced multi-streaming setups, local proxies, and third-party tools to retain full feature parity (EB + VOD Track) without relying on memory patching the OBS binary to bypass the UI string checks.

I've been trying to find workarounds for a while now to get both working together. It's entirely possible I might be missing an obvious solution. If there is already a proper way to achieve this, I'd love to learn about it!

[Fenrirthviti]

This sounds more likely to be a feature request, and we are not currently accepting feature requests on GitHub Discussions. Make sure you read any pinned posts on discussion boards before opening a new discussion. Please use our Ideas Page to submit your idea.

Additionally, we do not accept AI-generated output in our community. Future submissions should be human-written.

Thank you!

[Soulhackzlol]

Thanks for the clarification, but I think there's a misunderstanding here.

I opened a discussion instead of a feature request or a bug report specifically because I wasn't sure if this was intended, a side effect, a bug or if there was an existing workaround that I was missing.
My main goal was to ask if there's currently a way to achieve this after the latest update.

Also, I have to say it's quite disappointing to have my post called AI generated.
Taking the time to structure a post clearly for readability shouldn't be penalized, altho i understand your concern over AI stuff.

Anyways, I'm looking for guidence on this manner to correctly report or request this feature.

[Fenrirthviti]

Fair enough, I can reopen this.

The post followed a very standard AI-output paradigm/template of using the headers of "Proposed Solution" and "Impact", which is why it clocked AI-generated. We receive so much hallucinated nonsense that we're very sensitive to it at this point.

As for the question itself, it was my understanding that EB was able to denote a VOD track by itself, since it's mostly server-side processing anyway. I'll leave the technical details to those more familiar.

[Soulhackzlol]

Appreciate you reopening this and for the transparency!

Completely understand the headache with the AI spam, no worries at all. It just hit me hard because i overthink a lot this type of posts.

You actually nailed the exact wall I'm hitting.
While Enhanced Broadcasting handles things server-side, OBS itself restricts VOD track support at the API/service level using a hardcoded ServiceSupportsVodTrack() check, which literally only whitelists "Twitch".

inline bool ServiceSupportsVodTrack(const char *service)
{
	static const char *vodTrackServices[] = {"Twitch"};

	for (const char *vodTrackService : vodTrackServices) {
		if (astrcmpi(vodTrackService, service) == 0) {
			return true;
		}
	}

	return false;
}

If anyone sees a better way around this or if this could be escalated, I'm up to it!

Again, thanks for reconsidering, and any guidance on the VOD track matter is greatly appreciated!

Edit: I'm avoiding the use of rtmp_custom since that will break EB for me (since rtmp_custom requires a custom_config field, while other services use auto_config_url)
Because of that restriction, non-Twitch destinations won't expose or forward the secondary track through the standard pipeline.

As a temporary workaround, I had to write a Lua script to manually spin up an extra ffmpeg_aac audio encoder bound to the desired track index and attach it to the OBS audio source. For now It's crashing on me but I'll figure it out hehe.

edit2:
I managed to fix it with that script! Still, could be cool to give more freedom to nerdy users hehe