You have too much network bandwidth!!

Richard,

I do not use any online for primary or backup data, I don't trust the cloud.

I keep an external 2 TB SSD in the trunk of my car, I back up weekly, from the matching external 2tb SSD in my office with my primary data. I only use the hard drive inside my computer for operating system and programs, and recovery. usb 3.0 is so fast there is no sense it is an external drive when actively working.

Xfinity would store our temporary video recordings on their servers, up to 150 hrs, for $10/mo.

I haven't watched commercials since my 1st VCR was acquired. I purposely tape and watch later or eventually, then DELETE. Donna watches her crap upstairs, I watch my crap downstairs, we get together occasionally

Donna and her twin sister have a Pet/House sitting business, so they are often on someone else's TV. IF she can get the Xfinity APP on their TV, she can sign in and watch her crap there, otherwise she waits until she comes here.

I just tried, Verizon/Google Apps will not let me download Xfinity App. Presumably when using Xfinity TV Box, it will have their streamer built-in, thus no need to download it. 

Generally speaking, buffered audio/video uses TCP.  This means video streaming and audio streaming from a service like Netflix or Qobuz, Disney+, what have you. 

Real-time audio/video for things like live online meetings may use UDP instead.  

The difference is really in the buffering.  When you stream audio or video you can get several seconds of media in advance. This gives you the leisure of reconstructing a stream and requesting retransmissions if a packet is bad.  However with Zoom for instance, the service will just ignore the missing packets and keep going. 

Buffering is what really makes most of audiophile concerns about cables and switches irrelevant. 

Bandwidthis only part of the network. There are many more areas to look at. I used to install and maintain enterprise networks over 35 years ago.

A couple main things about networks: always use a wired connection, i always test/signature any ethernet cable whether i make it myself or buy a $1000 cable, and always use fiber over copper.

Audio has such low demands on network and computer resources that hardware manufacturers make it sound you need a 10G network or a 24 core mega server for hi res audio, which is simply not true.

If you are running a linux roon/audirvana/anything else server, do some system monitoring to really see how much memory/cpu/disk/network resources are used to play hi res music. Its lower than you think.

@erik_squires 

Generally speaking, buffered audio/video uses TCP.  This means video streaming and audio streaming from a service like Netflix or Qobuz, Disney+, what have you

It also means these services have to provide their own custom app at the client end to handle TCP!

Strictly, every TCP packet has to be acknowledged as received and correct in an individual message sent back to the server,

The practical maximum packet size is about 1500 Bytes, or 12,000 bits, if Ethernet is involved.  Given Netflix streams 4K video at 16 million bits per second, that’s well over 1000 acknowledgment messages per second.  CD quality streaming would need about 100!

@richardbrand 

I’d just add that TCP requires every client to send a message back to the server for every packet they have successfully received.  Not an efficient use of the Internet nor server resources and the planet is suffering as a result

My speculation on what their goals were:

1) Reducing video glitches through TCP and buffering content

2) Better control of content  (DRM) although on the internet you can easily find every bit of content that Netflix has, but for the average person that's probably good-enough DRM

I have to admit, I no longer subscribe to Netflix; I have plenty of content with what’s on my cable TV, and I have less patience with trying to navigate between various services;  my cable has roughly a 1,000 channels, and when combined with a Tivo satisfies my wife and me