Broadcast Journey: From the Field to the Viewer’s Screen

The live broadcast of the match doesn't start from the play button in your app, nor does it end there. Behind every frame that reaches your screen is a long chain of technical and artistic work, involving multiple parties before the picture and sound reach your device's screen. A fault can occur at any stage of this chain.

#Stages of the Live Broadcast Journey

1. The entity producing the broadcast from the field covers the match on-site, including cameras, directing, sound, shot selection, audience shots, and replays. This entity creates the "original signal," the first version of the picture and sound as they come out of the stadium.

2. The original signal is transmitted to the producer's broadcast center, where it is checked for sound and picture quality, delay rate, and any color or sound issues before sharing the final signal version with the rights-holding channels, known as the carrier (such as Thamaniya).

3. The carrier (Thamaniya) receives the final signal from the broadcast producer, monitors it, and prepares it technically for broadcasting on different devices, then passes it to the Content Delivery Network (CDN) systems.

4. Content Delivery Network "CDN": A technical layer that comes after preparing the broadcast. It delivers the broadcast to viewers through multiple paths and servers, improving stability, increasing playback speed, and reducing pressure on the technical infrastructure.

The experience ultimately varies depending on the viewer's internet connection quality, device type, and app version.

ℹ️ Thamaniya's possession of broadcast and transmission rights does not include control over the stadium cameras, microphones, or the selection of shots appearing in the official match production.

#Where the Fault Might Begin

1. The original or final signal from the broadcast producer: crowd sound cut-off, weak stadium sound, a fault in a specific shot. This type of issue does not start from the app, distribution network, or your internet speed but from the original signal before reaching Thamaniya.
2. During the signal transfer between the three parties: the broadcast producer, the carrier, and the content distribution network.
3. The stage of preparing the broadcast for different platforms.
4. The distribution network and its infrastructure.
5. Internet connection to your device or the app version on it.

#"Crowd Sound Cut-off" as an Example:

Sometimes the viewer notices the absence of crowd sound despite the clear picture, thinking the fault is from the app. But in reality, the sound might be missing from the original signal issued from the stadium. Thamaniya does not have the ability to restore missing sound from the source; its role is limited to monitoring and coordinating with the signal source to minimize the issue's impact without direct control over the stadium microphones.

We are concerned with addressing the fault regardless of its source, as the viewer is not concerned with the multiplicity of chain parties. What falls within our systems, we address immediately, and what precedes it, we follow up with the concerned party to ensure improvement from the source.

#What Thamaniya Does When a Fault Appears

We do not confine broadcast issues to a single cause; instead, we examine the entire path: from the integrity of signal reception and fault source, to the scope of user, device, region, and service provider impact.

1. We review the signal quality: Did it reach us intact? Did the fault appear before or after receiving the signal?
2. We monitor the platform and operating systems' performance: Is the issue general or specific to a particular group of users?
3. We check the distribution network and its paths.
4. We compare the experience between devices, regions, and internet providers.
5. We coordinate with the signal producer if it is proven that the fault began before the signal reached us.
6. We update you with what can be clarified without technical complexity or inaccurate promises.

#What to Do If You Encounter a Broadcast Problem

1. Ensure that the app is updated to the latest version.
2. Ensure your internet connection is stable by checking it at speed.cloudflare.com.
3. Contact customer service if the issue persists.

#Information That Helps Us Quickly Identify the Problem Source

When contacting customer service, send us:

1. The time the issue appeared.
2. The name of the match.
3. Device type, operating system, and version.
4. Thamaniya app version.
5. Connection type (Wi-Fi or mobile data) and service provider.
6. A screenshot of the error message if it appears.

#Frequently Asked Questions

1. Is every broadcast problem from the Thamaniya app? Not necessarily. The fault might start from the original signal, preparation stage, distribution network, your connection, or your device. We review the entire path before identifying the cause.

2. What is meant by the broadcast signal? The original signal is the picture and sound as they come out of the stadium: camera shots, stadium sound, replays, and graphics before the broadcast reaches us.

3. Who produces the match signal? A specialized entity covering the match on-site produces the signal. It handles cameras, directing, sound, and replays before delivering the signal to the display entities.

4. Does owning broadcast rights mean full control over match production? Not necessarily. Broadcast rights grant the right to show the match to the audience, while signal production from the stadium might be with another specialized entity.

5. Why do some audience shots, including shots of women, appear during the match? Audience shots are part of the official match production, and their selection is made by the broadcast producer from the field. Thamaniya receives the final signal for broadcasting through its platforms and does not choose during the live broadcast the people appearing in these shots or their timing.

6. Why does the match work for one user and not another? The experience is affected by internet speed, service provider, device type, app version, and user location. Therefore, the fault might appear for a specific group without others.

7. If the crowd sound is cut off, does Thamaniya fix it directly? It depends on the fault's source. If the sound is missing from the original signal, we coordinate with the production entity. If the fault appears after the signal reaches us, we address it from our side.

8. What is the difference between buffering, poor picture quality, and sound cut-off? Buffering is often due to connection or distribution. Poor picture quality might result from internet speed or signal quality. Sound cut-off might come from the source, player, or your device.

9. Does changing the distribution network solve all broadcast problems? Not necessarily. Reconfiguring the network improves broadcast stability and reduces buffering in the distribution layer, but it does not address a fault that started from the original signal.

10. Does Thamaniya control the designs and information displayed on the screen during the match? No. The designs and "graphics" information appearing during the live match broadcast, such as the score board, match time, statistics, "VAR" information, or half-time stats, are within the original signal coming from the broadcast producer. Therefore, Thamaniya does not control them during the broadcast. However, designs appearing after the match within the app, or in highlights, clips, or posts, might be prepared by Thamaniya depending on the content type and platform.

11. When should I contact customer service? Contact us if you encounter a persistent issue that appears to you but not to other users.