rtmp-services: Add Nenufar.live - Multi-Streaming

[SpaceCrapaud]

Description

Add Nenufar.live - Multi-Streaming service with VOD Track support.

Service details:

• Name: Nenufar.live - Multi-Streaming
• Website: https://nenufar.live
• Application: https://app.nenufar.live
• Documentation: https://nenufar.live/docs
• Protocol: RTMP
• Supported codecs: H.264, HEVC (Plus subscribers)
• Max resolution: 4K (Plus subscribers), 1080p (standard)
• VOD audio track: Supported
• General availability: Reached
• Proof of being an official representative: dig TXT obs.nenufar.live

Motivation and Context

Nenufar.live Multi-Streaming is a French/European platform that allows creators to broadcast to multiple destinations simultaneously.
This PR adds native support in OBS, including VOD Track audio support for copyright-free VOD recordings.
We figured out how to support Twitch VOD Track, but until now we had to use Twitch as a destination with our ingest URL as Custom Twitch Server URL, which is quite confusing and leads to many misunderstandings for users.
The "Multi-Streaming" precision is here to avoid confusion with other services we provide such as Nenufar "Live IRL", "Relay" and "Dispatcher", which use different URLs and don't need a specific implementation in OBS like "Multi-Streaming".

The Multi-Streaming service is brand new, version 1.0 was officially released two weeks ago (the other services are almost a year old). Our public communication campaign is scheduled to begin on January 5th, but we already have active users who have been using it daily since pre-release.

This is our first contribution to OBS Studio. We're open to feedback and happy to discuss the VOD Track implementation approach if there's a preferred or cleaner way to integrate it.

How Has This Been Tested?

This was tested locally on OBS 32.0.4 on Fedora 43 and Windows 25H4 (dual boot).
AMD Ryzen 9 5950x - Nvidia RTX 3090 - 128Gb RAM

Types of changes

• New feature (non-breaking change which adds functionality)

Checklist:

• My code has been run through clang-format.
• I have read the contributing document.
• My code is not on the master branch.
• The code has been tested.
• All commit messages are properly formatted and commits squashed where appropriate.
• I have included updates to all appropriate documentation.

[Fenrirthviti]

While the change here to enable VOD track for your service likely works, this is not an acceptable approach.

The services.json schema should be updated to allow defining VOD track support and move away from a hard-coded allowance.

[SpaceCrapaud]

While the change here to enable VOD track for your service likely works, this is not an acceptable approach.

The services.json schema should be updated to allow defining VOD track support and move away from a hard-coded allowance.

That's what I thought.
Would it be acceptable to propose an approach in which VoD Track depends on service.json rather than the current hardcoded method (so for Twitch as well) ?

[Fenrirthviti]

A proposal (as a separate PR) would be welcome here, yes.