This message was deleted.

Hey @plain-nest-63832 yup, it's referring to average concurrent users that are receiving the livestream. we'll make that more clear in the calculator

@dry-elephant-14928 Got it, so for example, let's say we have a 3 hour stream where we an average 400 concurrent users from beginning to end with an average watch time of 1 hour per user i.e. at any moment, we got 400 people watching at once. Let's say for each hour, we get a new set of 400 users so that each group of 400 only watches for that average of 1 hour. This would mean 1200 total hours of content was streamed over the 3 hour stream by a total of 1200 unique users. When using the pricing calculator, we would plug in 400 for "Users receiving video"? The estimated monthly downstream would be: 400 users x 1 stream x 60 minutes x 600kbps x 1 sessions = 108.00GB instead of: 1200 users x 1 stream x 60 minutes x 600kbps x 1 sessions = 324.00GB ? Even if I change the publisher to stream for only 60 minutes and keep the "Users receiving video" set to 400 users for an average of 60 minutes, the usage still comes out to: 400 users x 1 stream x 60 minutes x 600kbps x 1 sessions = 108.00GB This makes me suspicious that the number represents average number of concurrent users throughout the entire stream. Am I misinterpreting what concurrent means in this context?

yes, I had confirmed that above as well. in your formula, you'd want to plug in the session length of 180 minutes instead of 60, correct? 400 users on average, and 3 hours total

in the initial example above with 400 users at a time over the 3 hours but any given user is only watching for 1 hour so 1200 unique users, are you saying i i plug in 180 minutes into "AVERAGE MINUTES PER SESSION" and keep "USERS RECEIVING VIDEO" as 400?

yeah.. average concurrent users * session length.

"AVERAGE MINUTES PER SESSION" = session length? so "AVERAGE MINUTES PER SESSION" isnt representing the average minutes per session of each unique user?

if you are doing it that way, then you'd also have to plug in the total number of users.. instead of average number of concurrent users.. the math would come out to be the same

got ya, that's what i figured. just needed further clarification. i think the label "AVERAGE MINUTES PER SESSION" misled me a bit into thinking the unique user route which still led to correct calculations but then i was being told the whole concurrent user thing by my teammate which then confused me lol, thanks for the help!

yeah, I hear you. we'll make that more clear. appreciate your feedback!

thought i'd share this summary here in addition to my team, the calculator could be used for downstream calculation in two different ways first, USERS RECEIVING VIDEO = concurrent users then, AVERAGE MINUTES PER SESSION = the average total length of each session second, USERS RECEIVING VIDEO = unique users then, AVERAGE MINUTES PER SESSION = the average minutes viewed per unique user per session