SopCast

Description

Before Twitch, YouTube Live or any of the streaming platforms that now dominate the distribution of live video, watching a live sports broadcast online meant dealing with official streams that either didn’t exist or went offline under load the moment a popular match started. SopCast solved that by distributing the load — rather than sending every viewer’s connection through a single server, it created a peer-to-peer network where the viewers shared bandwidth with one another, making the stream more stable as more people watched it.

The Chinese development team behind SopCast released the software in 2006, based on the same peer-to-peer principles that BitTorrent had applied to file sharing. SopCast adapted that approach to live streaming: each viewer downloading a channel at the same time uploaded stream data to other viewers, creating a self-sustaining distribution network with minimal central infrastructure.

BACKGROUND

SopCast’s peak usage period was in the late 2000s and early 2010s, when it became the main method of watching leagues and competitions by many European football fans that were not covered by local broadcasters. A user only needed SopCast and a channel address — known as an SOP link — to watch any broadcast another SopCast user was sharing. Websites aggregating SOP links for live sports emerged and cultivated large audiences around SopCast dependent viewing.

The platform was in a legal grey area throughout its active period. Channel operators broadcast copyrighted sports content, music concerts and television broadcasts without authorization and rights holders filed suit against the largest SOP link aggregation sites, not SopCast itself. SopCast the software was left available as it was neutral infrastructure that could stream any content and not just pirated content.

Official streaming services grew aggressively after 2012. Amazon, DAZN and rights holders themselves launched streaming platforms, which reduced the access gap that had driven fans to SopCast. Combined with the increased enforcement against SOP link sites, this hastened SopCast’s demise. Development slowed through the mid-2010s and came to a near standstill, with the last major release of Windows coming in the 3.x series. The software still works but gets no active maintenance.

KEY FEATURES

P2P Channel Streaming

SopCast channels are peer networked live video channels. A broadcaster uploads the stream once to the SopCast network and the viewers connecting to the channel receive video from each other instead of from a central server. This architecture means that a channel with 10,000 concurrent viewers puts no more load on the original broadcaster’s connection than a channel with 100 viewers. Stream quality is dependent on peer availability — channels with more active viewers generally provided more stable playback.

Channel Browser and SOP Links

The SopCast application has a built-in channel directory of publicly shared streams by category. Users can also enter SOP link addresses directly — a format that looks like sop://broker.sopcast.com:3912/channel_id — to access specific channels not listed in the main directory. Third-party websites used to aggregate the SOP links for sports events so that users could find streams for specific broadcasts.

Video Player Integration

SopCast’s inbuilt player is used to display streams within the application. Alternatively, SopCast can output the stream to an external media player like VLC or Media Player Classic using a local HTTP port, so that users can leverage the subtitle support, screen capture, and other functionality that SopCast’s player didn’t provide.

Broadcast Mode

Any SopCast user can create a channel and broadcast his or her own content to the network using broadcast mode. The broadcaster assigns a channel name, description, and category and then chooses a media file or live source to stream. The channel appears immediately in the public directory where the other SopCast users can find and watch it.

Buffering and Stream Quality

SopCast buffers incoming stream data to a local cache before playback is initiated, evening out the variation in peer delivery timing. The buffer size influences both the amount of time the viewer waits before playback begins and how well the stream handles temporary drops in peer connectivity. Users on slow connections could increase the buffer so that it would absorb longer gaps between peer deliveries, at the expense of greater delay between the moment of live broadcast and what the viewer sees. Stream quality differed significantly from channel to channel based on the original broadcast bitrate and the number of peers actively sharing the stream at a given time.