|
|||||||||
|
Thread Tools | Search this Thread |
August 5th, 2016, 01:12 AM | #16 | |
Inner Circle
Join Date: Jun 2007
Location: Belgium
Posts: 9,510
|
Re: Beware: Vimeo's new default setting
Quote:
What does surprise me is when people seem to be fine with a very low resolution, as long as their films don't get stuck in constant buffering, and they seem to be ok to pay for that service even if the provider is making promises they cannot keep. There is one provider however that never has given me any playback or buffering issues and that is IMDB, their trailers always load very fast and have good playback quality, maybe they should start their own hosting service :) |
|
August 5th, 2016, 06:10 AM | #17 | |
Major Player
Join Date: Nov 2013
Location: Liverpool
Posts: 495
|
Re: Beware: Vimeo's new default setting
Quote:
I don't know if this is fairly known, but videos sent over the Internet are broken down and sent via packets to end users. Protocols state the way in which this information is delivered, and the end user's computer sends a message to the provider's server, explaining that they have received packet A, B, C, D etc. and that protocol continues to control the way in which packets are sent to ensure that video playback is as good as possible. Some protocols willingly accept that some packets will not be received, where as other protocols work based on all packets being received. Dropping packets of data to manageable levels seems to be the way that providers are working at this present moment, but IMDB seems to be able to retain at least a 480p image, whereas Vimeo stoops to all new lows. Vimeo's current structure is unacceptable for paying users. Vimeo should be able to match the quality of IMDB considering that this is their main forum of business and expertise, but I strongly believe that they are passing off 'user's internet speeds' as excuses for their poor servers that are unable to deliver content as well as IMDB, and - the most popular - YouTube, a website that receives much more traffic, and is able to deliver more hi-res footage for free users to the public. I know this to be true, because I am able to stream 1080p via YouTube without a hitch, whereas I can very rarely stream at 720p via Vimeo - via the same Internet connection. Therefore, that's not to do with my speeds, but to do with their servers. |
|
August 5th, 2016, 06:28 AM | #18 | ||
Inner Circle
Join Date: Jan 2013
Location: Austin, Texas
Posts: 2,006
|
Re: Beware: Vimeo's new default setting
It does not. The quality is really poor. There is no detail in the image and the codec breaks quite often for complicated scenes, resulting in moderate to severe macroblocking.
Quote:
Quote:
|
||
August 5th, 2016, 07:01 AM | #19 |
Inner Circle
Join Date: Jun 2007
Location: Belgium
Posts: 9,510
|
Re: Beware: Vimeo's new default setting
While it's not as detailed as footage shot with a 4K camera and played back on youtube at 4k I find IMDB has found a very good balance between avoiding buffering and having good enough IQ. Their films always load very fast no matter what time of day it is and the IQ looks to good enough to play on larger pc screens and certainly looks a lot better then vimeo's low rez playback at specific times.
While I do agree with Steve that a film that takes it time to load could have a bigger impact then films played on a very low resolution when it comes to loosing a client attention when they view your films on your website this shouldn't mean that we should just accept it like it is, especially not when it's a paying service. The problem is that there are not many better alternatives out there, I have tried Wistia but that one also had buffering issues, it's also not my internet connection because when I have playback issues on vimeo I don't have that on youtube, but even on youtube I sometimes do experience bad buffering issues but I can imagine their servers have to deal with a lot more users then vimeo so it's allready some achievement that we are even able to watch full hd, 4K viewing on youtube is more of a hit and miss, sometimes it's smooth as butter and other times it's like a slideshow. |
August 5th, 2016, 09:12 AM | #20 |
Trustee
Join Date: Jul 2012
Location: Romsey, UK
Posts: 1,261
|
Re: Beware: Vimeo's new default setting
Having a preference to minimalise buffering over higher resolution is by no means an endorsement that I either accept low resolution or even Vimeo itself. I have issues with Vimeo and why even though I could sometimes benefit from more than 5gbs a week upload, I don't upgrade to the next package with them. I have also complained myself over various issues.
As Vimeo is well established amongst video professionals, it feels almost like an obligation to have an account with them and it's true that as long as you have a good internet speed, playback can be quite good and professional looking. However I prefer to use YouTube more these days in part down to my own issues with Vimeo playback pre-fibre optic at my home. Whilst an option to force playback at higher resolution would be nice with Vimeo, it's not for me an essential requirement, despite Noa's suggestion it could lead to a loss of business. Partly because my website favours YouTube for Wedding work. |
August 5th, 2016, 04:36 PM | #21 | ||
Major Player
Join Date: Nov 2013
Location: Liverpool
Posts: 495
|
Re: Beware: Vimeo's new default setting
Quote:
I respectfully disagree from my own experiences. I guess you've never experienced the terrible quality Vimeo can happily output now unless you select your preferred frame rate, whilst I haven't experienced a struggle in IMDB's playback. Quote:
Good point. This I have considered, but this is where Vimeo triumphs in its sleek player. The only issue I have with Vimeo is playback, which was never a problem until they took away our control. It's easy when considering all of these varying opinions that our main issue is control. If we were able to decide how our clients stream our films, then I think we'd all be back to singing their praises, despite the content taking longer to stream in general in comparison to YouTube, which I do understand the reasoning behind as you have suggested. |
||
| ||||||
|
|