How does IPTV work? Why does it need its own protocol?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • MrMaxwell
    Too lazy to set a custom title
    • Jul 2005
    • 10057

    #1

    How does IPTV work? Why does it need its own protocol?

    It doesn't make any sense to me
    I obviously cannot get it without a way out to the internet, right?
    Why don't they just use regular TCP IP ?
    What is this, like a VPN for television?
    Can I get channels and stations with Russian women? I am so curious about Russian women, these days. FFS





    PS: The board told me this and I think I posted a few days ago, maybe..

    Hello MrMaxwell it appears that you have not posted on our forums in several weeks, why not take a few moments to ask a question, help provide a solution or just engage in a conversation with another member in any one of our forums?
  • MrMaxwell
    Too lazy to set a custom title
    • Jul 2005
    • 10057

    #2
    Can I use a DVR with this bullshit? Also, cox recently capped our transfer so I guess I'm fucked on this for now. But it sure is interesting

    Comment

    • Ferus
      Bye - Left to do stuff
      • Feb 2013
      • 4108

      #3
      Just like ICA Protocol for Citrix. Sometimes the bare TCP cant hold enough info

      Comment

      • MrMaxwell
        Too lazy to set a custom title
        • Jul 2005
        • 10057

        #4
        I am still a little lost
        I have used up to 1 gigabit connections getting around 700 megabit speeds and was using TCP IP 4 (as far as I was aware, anyway... I didn't actually look, I suppose)
        I mean when you say information you mean data, right,

        I am confused
        Sorry if I sound ridiculous

        Comment

        • rowan
          Too lazy to set a custom title
          • Mar 2002
          • 17393

          #5
          An error correcting protocol (like TCP) isn't good for a time sensitive stream which can handle occasional corruption. As soon as TCP loses a packet the stream will stall as the source first detects the loss, then performs a retransmission.

          Better to have someone's head go blocky for the next half second due to a missed data packet, rather than have the whole picture freeze.

          Comment

          • Marshal
            Biz Dev and SEO
            • Jun 2005
            • 15219

            #6
            Originally posted by rowan
            An error correcting protocol (like TCP) isn't good for a time sensitive stream which can handle occasional corruption. As soon as TCP loses a packet the stream will stall as the source first detects the loss, then performs a retransmission.

            Better to have someone's head go blocky for the next half second due to a missed data packet, rather than have the whole picture freeze.
            Multicast: If you are referring to streams without long delay (short buffer times), usually IGMP is being used, due to an easy way to distribute streams to multiple users, using UDP broadcast (IGMP uses RTP over UDP). You can not use multicast on a WiFi connection, so you need some sort of a cable/fiber.

            Unicast: At the moment my ISP is using IPTV with HTTP streams (RTSP over TCP) and it works without any problems. I think they are using Wowza, and I see no problems broadcasting it over WiFi. It's not some internet service off of web, but a real regular ISP, which means HTTP streaming is very much possible with IPTV. Probably not the best solution for live event streams (basically any sports event), but the lag is definitely shorter than satellite streams.

            You can read more about IPTV protocols here: https://en.wikipedia.org/wiki/IPTV#Protocols
            ---
            Busy ranking websites on Google...

            Comment

            • MrMaxwell
              Too lazy to set a custom title
              • Jul 2005
              • 10057

              #7
              My router had an option for Multicast forwarding or some shit but I'm still a little lost
              It makes sense that the TCP protocol isn't good for the type of data video is I suppose
              You essentially are saying that tcp is inefficient and unreliable when you're sending compressed video over it?

              Comment

              • MrMaxwell
                Too lazy to set a custom title
                • Jul 2005
                • 10057

                #8
                So I guess TCP would be better for a bit for bit copy and this other shit would be good for video because it can live with not being 1000% correct data

                Comment

                • brandonstills
                  Confirmed User
                  • Dec 2007
                  • 1964

                  #9
                  I think there was some talk about when broadcasting a show it can be forwarded and sent to multiple addresses at once (multicast) without sending the entire stream to each person individually. That way if the stream is 1 Mbps and you have to send it to 100 people it isn't 100 Mbps.

                  Brandon Stills
                  Industry and programming veteran
                  [email protected] | skype: brandonstills | ICQ #495-171-318

                  Comment

                  • MrMaxwell
                    Too lazy to set a custom title
                    • Jul 2005
                    • 10057

                    #10
                    FFS - that must save a FUCKTON of BW!!! Wow. Multicast sounds awesome
                    What keeps all of it synced? I mean each moron isn't watching the same part of the film all at once... so how does that work? I know servers are making huge advancements in caching and all

                    Comment

                    Working...