# Feature Request: Livestream Delay Workaround **URL:** \ **Category:** Features\ **Created:** [January 31, 2022, 11:33pm UTC](https://community.crowdpurr.com/t/feature-request-livestream-delay-workaround/331 "2022-01-31T23:33:25Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![RossN](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.crowdpurr.com/rossn/32/74_2.png) [@RossN](https://community.crowdpurr.com/u/RossN)\ **Post date:** [February 1, 2022, 3:02pm UTC](https://community.crowdpurr.com/t/feature-request-livestream-delay-workaround/331/2 "2022-02-01T15:02:38Z")
This is a good idea and suggestion, and one we’ve had before, unfortunately it doesn’t work. The problem is even when you add a delay like this, the latency will still creep back into the “feedback loop” and affect the host. Here’s an example: Let’s say your YouTube latency is **5 SECONDS**. So pretend Crowdpurr has a **Latency Delay** setting that we can set to **5 SECONDS**. Let’s say a question is **15 SECONDS**. This is what will happen: Host says “Let’s start Question 1” and they trigger Question 1. Crowdpurr then delays the question from actually starting for **5 SECONDS**. The player than _hears_ the host say “Let’s start Question 1” and Crowdpurr updates at the exact same time due to the **Latency Delay**. So far so good. The _problem_ has already occurred because now, the host had to stream for _another_ **5 SECONDS** _waiting_ on the **Latency Delay** to kick off the question. This “waiting” of the host _then_ gets streamed and sent on to the player. The result, from the player’s perspective on the stream, is they see the host doing nothing for **5 SECONDS** , then when the **15 SECONDS** of the question is up, the host is now _behind_ by **5 SECONDS** , and they’ll see the host saying something like “Okay, the Question Timer is almost up, hurry up 5, 4, 3, 2, 1…” even though they already finished the question **5 SECONDS** ago. So the **Latency Delay** just moves the delay, it doesn’t solve it. Anytime the host is then _waiting_ on the players’ answers (i.e. their feedback) they’ll still be affected by the **5 SECONDS** latency delay. We’re thinking the solution to this will be likely rolling our own embedded real-time streaming WebRTC solution that is zero-latency (same technology as Zoom, WebEx, or Teams) and works right within Crowdpurr. More on this later in the year. Check out this thread post for a more detailed deep-dive into mitigating latency: > [@\[SOLVED\] Mitigating Streaming Latency When Using Crowdpurr](https://community.crowdpurr.com/t/mitigating-streaming-latency-when-using-crowdpurr/42): > > EDIT: This topic and it’s advice are now outdated as Crowdpurr has released its own built-in [real-time streaming solution](https://crowdpurr.zendesk.com/hc/en-us/articles/360052614212-Add-a-Live-Stream-to-Crowdpurr#:~:text=Add%20a%20Dashboard%20Stream&text=On%20the%20Experience%20Dashboard%20of,use%20your%20camera%20and%20microphone.) that uses WebRTC (the same technology behind Zoom) that allows near real-time streaming. If using Crowdpurr’s streaming, there is no longer a need to “mitigate” any latency because it’s negligible! Crowdpurr works great for adding fun trivia competitions to virtual and hybrid meetings where you may want to “stream” yourself as a live gameshow host while your crowd follows a… --- _[View the full topic](https://community.crowdpurr.com/t/feature-request-livestream-delay-workaround/331)._