Do you have adblock enabled?
If you can read this, either the style sheet didn't load or you have an older browser that doesn't support style sheets. Try clearing your browser cache and refreshing the page.

(Yahoo)   Amazon teams up BUFFERING...BUFFERING with RealPlayer, which contrary to popular belief apparently still exists, to BUFFERING...BUFFERING bring users cloud storage and access BUFFERING...BUFFERING solutions for their video collections   (ca.finance.yahoo.com) divider line 57
    More: Unlikely, Amazon, video collection, Fire TV, video cameras, REALNETWORKS, forward-looking statement, dry cask storage, PR Newswire  
•       •       •

684 clicks; posted to Geek » on 02 Apr 2014 at 7:30 PM (1 year ago)   |  Favorite    |   share:  Share on Twitter share via Email Share on Facebook   more»



57 Comments   (+0 »)
   
View Voting Results: Smartest and Funniest

Archived thread

First | « | 1 | 2 | » | Last | Show all
 
2014-04-02 06:32:13 PM  
RealPlayer is a good example of the free market going wrong

RealPlayer should be put out of its misery
 
2014-04-02 06:35:50 PM  
The buffering problem was before everyone had cable modems, cut Real Player some slack.
 
2014-04-02 06:53:24 PM  

EvilEgg: The buffering problem was before everyone had cable modems, cut Real Player some slack.


^ This.
 
2014-04-02 07:13:34 PM  

EvilEgg: The buffering problem was before everyone had cable modems, cut Real Player some slack.


I dunno, I've had cable internet since 1999 or 2000, and I still used get much, much more of that back in the day with RealPlayer video than with videos that opened in the other popular video players of the era (e.g., QuickTime and WMP).
 
2014-04-02 07:46:10 PM  

EvilEgg: The buffering problem was before everyone had cable modems, cut Real Player some slack.


People used it at work and on college campuses, where they had nice fat intertubes.

And it buffered there as well.

lordargent.com
 
2014-04-02 07:48:13 PM  
Buffering. Aggravating.

Auto-play pop-up ads. Annoying.

Buffering auto-play pop-up ads? WTF!!
 
2014-04-02 07:50:21 PM  
FireTV just isn't going to take off. Besides the name sucking the market is saturated already with proven hardware like Roku, AppleTV and Chromecast
 
hej
2014-04-02 07:50:30 PM  
What sites and/or products use RealPlayer?
 
2014-04-02 07:53:02 PM  

lordargent: EvilEgg: The buffering problem was before everyone had cable modems, cut Real Player some slack.

People used it at work and on college campuses, where they had nice fat intertubes.

And it buffered there as well.


Done in 5. Period.
 
2014-04-02 07:53:13 PM  
RealPlayer still exists?
 
2014-04-02 07:57:04 PM  
Subby is still on dialup?
 
2014-04-02 07:59:49 PM  

Cyberluddite: EvilEgg: The buffering problem was before everyone had cable modems, cut Real Player some slack.

I dunno, I've had cable internet since 1999 or 2000, and I still used get much, much more of that back in the day with RealPlayer video than with videos that opened in the other popular video players of the era (e.g., QuickTime and WMP).


I'm curious; were you actually streaming content with QT and WMP, or just playing partially downloaded files? Back in that day, I only had a 33.6 modem so it didn't make much difference to me. Although, I also didn't know what streaming actually meant until long after I'd left for college; so I was only using real player back then because some websites "needed" it. For example, for a few years back in the late 90's, Amazon had no option other than real player to sample songs on some CDs. I don't remember having issues with QT and WMP, but then again most of the stuff I played on them were mov, avi, or mp3 files; I don't think I ever actually streamed anything on them for comparison. Just curious.
 
2014-04-02 08:07:16 PM  

Flt209er: Cyberluddite: EvilEgg:
I'm curious; were you actually streaming content with QT and WMP, or just playing partially downloaded files?.


Makes no difference since realplayer wasn't technically streaming either.

The data from realplayer got cached, so it was technically downloading files as well

It allowed you to seek in a file, but so did the others.

It's kind of a wash really.
 
2014-04-02 08:22:11 PM  
A lot of NPR's online archives are in a RealPlayer format, which sucks.  I managed to find the last version of RealPlayer before they introduced whatever the heck RealOne is.  Even today, the real format blows.
 
2014-04-02 08:36:13 PM  
Everything was slow back then, what do you expect? But their clunky unwillingness to work with others really screwed them.
 
2014-04-02 08:37:48 PM  
RTSP's transport is RTP, which is UTP. Which means you don't any TCP window adjustments etc, so it was always shiatting for actual streaming. It did datagram sorting and management in the app layer which was the dumb. Flash video appeared at the dawn of ubiquitous broadband and didn't bother with the overhead, and just used x264 over tcp port 80. Done and done.

These days the HTML5 web codecs will eat everybody's lunch, and if TCP is too much overhead you have decent UDP based alternatives like RUDP, over DTSL if you need it.
 
2014-04-02 08:42:20 PM  

nonstopcrunchy: RTSP's transport is RTP, which is UTP. Which means you don't any TCP window adjustments etc, so it was always shiatting for actual streaming. It did datagram sorting and management in the app layer which was the dumb. Flash video appeared at the dawn of ubiquitous broadband and didn't bother with the overhead, and just used x264 over tcp port 80. Done and done.

These days the HTML5 web codecs will eat everybody's lunch, and if TCP is too much overhead you have decent UDP based alternatives like RUDP, over DTSL if you need it.


QED.
 
2014-04-02 08:51:54 PM  
there is RealPlayer on my Nokia phone.

i have yet to EVER be able to watch a video with it.
 
2014-04-02 08:54:05 PM  
Well YouTube appears to be trying to catch up in buffering technology and mimicing Real more and more... it's been getting so freaking slow to load now, and never appears to do a full load so trying to skip forward means that you have to wait for another buffering session before it starts playing...

I hate that.
 
2014-04-02 08:54:07 PM  

nonstopcrunchy: RTSP's transport is RTP, which is UTP. Which means you don't any TCP window adjustments etc, so it was always shiatting for actual streaming. It did datagram sorting and management in the app layer which was the dumb. Flash video appeared at the dawn of ubiquitous broadband and didn't bother with the overhead, and just used x264 over tcp port 80. Done and done.

These days the HTML5 web codecs will eat everybody's lunch, and if TCP is too much overhead you have decent UDP based alternatives like RUDP, over DTSL if you need it.


Translation for us n00bs?
 
2014-04-02 08:55:50 PM  
I recently installed Real Player because it seemed to be the only way to stream my own video files using Chromecast.  So it's not completely useless, but you still need to upload them to Real Player's cloud, which is kind of annoying.
 
2014-04-02 09:01:17 PM  
Arrgh. 'UDP' and 'DTLS'. I even previewed.
 
2014-04-02 09:02:05 PM  

lordargent: Flt209er: Cyberluddite: EvilEgg:
I'm curious; were you actually streaming content with QT and WMP, or just playing partially downloaded files?.

Makes no difference since realplayer wasn't technically streaming either.

The data from realplayer got cached, so it was technically downloading files as well

It allowed you to seek in a file, but so did the others.

It's kind of a wash really.


If you're talking about wav, mp3, etc files, sure. But was this the case for the .rm wrappers? The only thing I know about their proprietary formats is that they're proprietary, but I never used real player except when forced to; a.k.a. .rm. And from what I can find online, the .rm files were true streaming formats. Again, just curious.

Either way, count me in with the crowd that avoided RP when able.
 
2014-04-02 09:02:28 PM  

imfallen_angel: Well YouTube appears to be trying to catch up in buffering technology and mimicing Real more and more... it's been getting so freaking slow to load now, and never appears to do a full load so trying to skip forward means that you have to wait for another buffering session before it starts playing...


That's not the transport etc like RP, that's the CDN doing uncached transfers.
 
2014-04-02 09:04:15 PM  
Kittypie070:

Translation for us n00bs?

The old RealPlayer transport was a first generation solution to an unquantified problem glued together out of bits of internet by several committees then poorly commercialised. By it's basic design, it had severe limitations.
 
2014-04-02 09:21:01 PM  

lordargent: Flt209er: Cyberluddite: EvilEgg:
I'm curious; were you actually streaming content with QT and WMP, or just playing partially downloaded files?.

Makes no difference since realplayer wasn't technically streaming either.

The data from realplayer got cached, so it was technically downloading files as well

It allowed you to seek in a file, but so did the others.

It's kind of a wash really.


With QuickTime, you would click on the link and then go do something else for a minute until the little grey bar had gone far enough that you reckoned you could start it without ever catching up.

With Real Player, you could let it sit there paused for three hours and it would still stop for buffering 10 seconds into it.

That was the difference.
 
2014-04-02 09:24:28 PM  

Kittypie070: nonstopcrunchy: RTSP's transport is RTP, which is UTP. Which means you don't any TCP window adjustments etc, so it was always shiatting for actual streaming. It did datagram sorting and management in the app layer which was the dumb. Flash video appeared at the dawn of ubiquitous broadband and didn't bother with the overhead, and just used x264 over tcp port 80. Done and done.

These days the HTML5 web codecs will eat everybody's lunch, and if TCP is too much overhead you have decent UDP based alternatives like RUDP, over DTSL if you need it.

Translation for us n00bs?


"I am a network admin, which makes me smarter than other people, which is good because I have a self esteem deficit due to not attending college"

My translation could be off.  I'm a bit rusty.
 
2014-04-02 09:30:59 PM  

nonstopcrunchy: These days the HTML5 web codecs will eat everybody's lunch


Flash is still 70% faster on .mp4 playback.
 
2014-04-02 09:56:31 PM  

styckx: FireTV just isn't going to take off. Besides the name sucking the market is saturated already with proven hardware like Roku, AppleTV and Chromecast


I own a Pivos Xios, a Boxee Box, a WD TV Live, a 2013-vintage Samsung Smart TV, an LG Smart TV Upgrader, a Popcorn Hour PCH200, a Roku 2, an Ouya, a Chromecast and there are a couple AppleTVs in my office.

None of them do everything I want a set top box to do, so my main entertainment device is an Intel NUC that's velcro'd to the back of my TV.

The Roku 3 is almost decent, but I think it's still too slow and has too clunky of a user interface. Roku did FINALLY add Youtube support, but it's barely capable for local media without interacting with a Plex Media Server.

The Xios has to run Linux (instead of the default Android ROM) to have fully functional XBMC and audio support, but it doesn't have the horsepower to manage high-bit rate videos. Plus, I have to screw with ROMs and everything outside XBMC sucks on it. It and the (obscure and long-discontinued) LG Smart TV upgrader are probably the best STBs I've tried, since they both talk to absolutely all the services I use, can read external disks, open arbitrary media files, connect directly to file servers and are still getting firmware updates to deal with changes in online services. The LG, unfortunately, has the worst UI of anything ever.

The Boxee Box is nice and fast with a great UI, but it doesn't talk to Plex and hasn't had a firmware update in 3 years, so it works with pretty much zero online services.

AppleTVs are cute as long as you're doing Apple-approved things with them and fark you if you are not. They're bad at local media (unless it's in an Apple-approved format or playing on some other Apple device), so once again Plex is nearly a requirement to get around their intended limitations. Apple. Apple apple. Apple.

Chromecast has about three useful apps: Plex (finally), Youtube and Netflix - all things my TV does with or without the Chromecast part. Oh and you can play stuff that's in a Chrome window. EVERYTHING does those things, but the Chromecast uses a tablet or a laptop instead of a remote control. It can't be connected via ethernet and it doesn't have any kind of direct connectivity at all. I actually think it's overpriced for what it does.

Looking at the feature set for the Fire TV, I see something that supports all the online services I might use (Spotify and HBO Go aren't things I use, though I bet they show up sooner rather than later). It's supposed to be getting Miracast ("screencasting") support shortly after launch, which is particularly interesting to me since I'd like nothing more than to get those AppleTVs out of my office. The voice-based control could be a huge improvement over needing a bluetooth keyboard in the living room. It has basically twice the hardware specs as its closest competitors. I don't see any evidence that it directly supports DTS audio. That's a little lame, but it beats the hell out of having to transcode absolutely everything to two-channel AAC. Overall, it's an intriguing package and I'm willing to give it a try.
 
2014-04-02 09:59:21 PM  

EvilEgg: The buffering problem was before everyone had cable modems, cut Real Player some

<CARRIER LOST>
 
2014-04-02 10:09:42 PM  

Kittypie070: nonstopcrunchy: RTSP's transport is RTP, which is UTP. Which means you don't any TCP window adjustments etc, so it was always shiatting for actual streaming. It did datagram sorting and management in the app layer which was the dumb. Flash video appeared at the dawn of ubiquitous broadband and didn't bother with the overhead, and just used x264 over tcp port 80. Done and done.

These days the HTML5 web codecs will eat everybody's lunch, and if TCP is too much overhead you have decent UDP based alternatives like RUDP, over DTSL if you need it.

Translation for us n00bs?


Real Player is older technology that doesn't work as well as the new stuff.
 
2014-04-02 10:10:16 PM  

likefunbutnot: I own a Pivos Xios, a Boxee Box, a WD TV Live, a 2013-vintage Samsung Smart TV, an LG Smart TV Upgrader, a Popcorn Hour PCH200, a Roku 2, an Ouya, a Chromecast and there are a couple AppleTVs in my office.


Do you review tech for a living, or are you just a really dedicated early adapter?
 
2014-04-02 10:16:37 PM  
Back in the days of dial-up modems, RealPlayer was pretty much the only thing that worked..

Then along came Quicktime 4.0, and RealPlayer kind of lost its reason for existence (although Quicktime 4.0 also sucked, but it was quickly followed by things that worked better..)
 
2014-04-02 10:17:26 PM  

nonstopcrunchy: RTSP's transport is RTP, which is UTP. Which means you don't any TCP window adjustments etc, so it was always shiatting for actual streaming. It did datagram sorting and management in the app layer which was the dumb. Flash video appeared at the dawn of ubiquitous broadband and didn't bother with the overhead, and just used x264 over tcp port 80. Done and done.

These days the HTML5 web codecs will eat everybody's lunch, and if TCP is too much overhead you have decent UDP based alternatives like RUDP, over DTSL if you need it.


Can I buy a vowel?
 
2014-04-02 10:22:22 PM  

nonstopcrunchy:  It did datagram sorting and management in the app layer which was the dumb.


Granted, I have never developed a streaming network protocol, but what's so dumb about datagram resequencing at the application layer?  Isn't that pretty much standard for protocols that implement UDP that need datagram sequencing?
 
2014-04-02 10:23:19 PM  
Hollie Maea:
Translation for us n00bs?

"I am a network admin, which makes me smarter than other people, which is good because I have a self esteem deficit due to not attending college"

My translation could be off.  I'm a bit rusty.


Harsh but fair.
 
2014-04-02 10:26:30 PM  
I have never had any other media play that had to stop and buffer when playing videos from my hard drive.

It was, however, a better option for managing my ipod than itunes.
 
2014-04-02 10:26:48 PM  

Nightjars: nonstopcrunchy:  It did datagram sorting and management in the app layer which was the dumb.

Granted, I have never developed a streaming network protocol, but what's so dumb about datagram resequencing at the application layer?  Isn't that pretty much standard for protocols that implement UDP that need datagram sequencing?


Yeah, at the time you needed to do it then if you chose UDP, but it wasn't ideal and when TCP did all the heavy lifting for you I always thought it was an odd choice. It's even more clear cut today unless you need multicast or something.

All IMO only of course, someone with an actual brain will probably slap me down with some hard data and calculus to prove it.
 
2014-04-02 10:27:41 PM  
*media player
 
2014-04-02 10:29:33 PM  
I threw Rob Glaser out of a corporate party once.

I feel good about that.
 
2014-04-02 10:30:02 PM  

nonstopcrunchy: Nightjars: nonstopcrunchy:  It did datagram sorting and management in the app layer which was the dumb.

Granted, I have never developed a streaming network protocol, but what's so dumb about datagram resequencing at the application layer?  Isn't that pretty much standard for protocols that implement UDP that need datagram sequencing?

Yeah, at the time you needed to do it then if you chose UDP, but it wasn't ideal and when TCP did all the heavy lifting for you I always thought it was an odd choice. It's even more clear cut today unless you need multicast or something.

All IMO only of course, someone with an actual brain will probably slap me down with some hard data and calculus to prove it.


As a person who has a GED in network software development, I would assert that If you need datagram sequencing, but not retransmission, you're better off using UDP and developing your own sequencing mechanisms.  Retransmission is more or less useless for real-time applications, and TCP is just adding quite a bit of overhead if the service isn't actually useful.
 
2014-04-02 10:31:45 PM  

Nightjars: As a person who has a GED in network software development, I would assert that If you need datagram sequencing, but not retransmission, you're better off using UDP and developing your own sequencing mechanisms.  Retransmission is more or less useless for real-time applications, and TCP is just adding quite a bit of overhead if the service isn't actually useful.


I should add that you obviously would need to also include congestion detection so you don't accidentally mess things up in terrible ways.
 
2014-04-02 10:46:05 PM  
I like that it's a $99 gaming platform. I wonder if this will force Apple TV to follow suit.
 
2014-04-03 12:13:15 AM  

chionophile: I recently installed Real Player because it seemed to be the only way to stream my own video files using Chromecast.  So it's not completely useless, but you still need to upload them to Real Player's cloud, which is kind of annoying.


Pretty sure you can 'cast' your desktop to it if you have chrome and the extension. There might have been an issue with the audio playing only locally though. Can't really remember

/haven't used my Cc in months
 
2014-04-03 12:53:59 AM  
If Plex comes on the fire TV then I'm sold, I really love my Roku 2 XS but it's starting to show cracks, frequent crashes, playback chopiness here and then. I mean I use it to heck and probably wont upgrade for another year at the very least. In that time the Fire TV will hopefully mature as well.
 
2014-04-03 01:41:38 AM  
This must be an April 1 joke. Posted on the 2nd because buffering.

/or it's video Amazon started buffering in 1997 and it's just starting to play now
 
2014-04-03 02:08:58 AM  

imfallen_angel: Well YouTube appears to be trying to catch up in buffering technology and mimicing Real more and more... it's been getting so freaking slow to load now, and never appears to do a full load so trying to skip forward means that you have to wait for another buffering session before it starts playing...

I hate that.




It loads small chunks now and then stops. Probably saving a whole bunch of bandwidth because people often don't watch full videos because they have ADHD so instead of giving you the full thing they wait to see if they need to download more.
 
2014-04-03 05:56:35 AM  

Faddy: It loads small chunks now and then stops. Probably saving a whole bunch of bandwidth because people often don't watch full videos because they have ADHD so instead of giving you the full thing they wait to see if they need to download more.


I can atest that I enjoy that feature in the situations where someone posts "hey check out this really new funny thing!" in the video tab and within the first few seconds I recognize it from five years ago.

/and then smugly say so in its comment thread, like an asshole

/an asshole
//an asshole!
///he's a real asshole!
 
2014-04-03 08:03:31 AM  

Flt209er: I'm curious; were you actually streaming content with QT and WMP, or just playing partially downloaded files?


I'm curious: did you know that streaming is nothing more than playing partially downloaded files?
 
2014-04-03 09:27:44 AM  
Just when you thought cloud-based video collection platforms couldn't possibly suck any worse than Ultraviolet, in comes RealPlayer.
 
Displayed 50 of 57 comments

First | « | 1 | 2 | » | Last | Show all

View Voting Results: Smartest and Funniest


This thread is archived, and closed to new comments.

Continue Farking
Submit a Link »
Advertisement
On Twitter






In Other Media


  1. Links are submitted by members of the Fark community.

  2. When community members submit a link, they also write a custom headline for the story.

  3. Other Farkers comment on the links. This is the number of comments. Click here to read them.

  4. Click here to submit a link.

Report