Jump to content

Is Vessel a Buffery mess for anyone else?

Buffers 30 sec before starting, after that it's fine for me. Feels like overloaded servers.

Link to comment
Share on other sites

Link to post
Share on other sites

nope, 

 

its jus a total heap of crap, doesnt load vids at all

Cpu : AMD Ryzen 3 1200 (3.8Ghz), Motherboard : Gigabyte AB350 Gaming 3 - RAM : 8GB DDR4 2933 Team (Vulkan) memory, GPU : MSI GTX 980 4GB Case : Antec P50, Storage : 120GB Samsung SSD, 3TB WD Blue, PSU : 530w Thermaltake SPS-530MPC, Cooling : Artic freezer Pro 7, OS : Windows 10. 

 

Link to comment
Share on other sites

Link to post
Share on other sites

I have tried it for a day now. I have had no buffering problem what so ever. However I am a little bit disappointed about the image quality. The navigation is not as clear as on YouTube but I am new to the site.

I live in Sweden. Hopefully the buffering problem is just in some local areas.

I'm still running on my core i7-920

@Motherboard: GA-EX58-UD3R @GPU: GTX 560 @Memory: 16GB1600C9 @Storage: X25-M 80GB & 330 120GB * Caviar Green 2TB @Screen: Acer H223HQ

@Case: Antec P180B -EU * Jou Jye 480AUBA * 2x NF-S12A FLX @Peripherals: CM Storm QuickFire TK Blue - Rearranged Svorak * MX518 @Sound: Beresford TC-7520 DAC * ATH-M40 fs

Link to comment
Share on other sites

Link to post
Share on other sites

I'm also getting these buffering issues on Vessel unfortunately.

However, Linus is doing this to help bring some revenue guys. Surely if Vessel doesn't work for some of us then we can watch on Youtube. A little patience is all that is required.

Link to comment
Share on other sites

Link to post
Share on other sites

  • 2 months later...

Yeah Vessel is trash I just pinged www.vessel.com from here in Australia here are the results

 

Pinging ssl.so.vessel.com.c.footprint.net with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

As for Youtube

 

Pinging youtube-ui.l.google.com with 32 bytes of data:
Reply from youtube: bytes=32 time=20ms TTL=61
Reply from youtube: bytes=32 time=20ms TTL=61
Reply from youtube: bytes=32 time=19ms TTL=61
Reply from youtube: bytes=32 time=19ms TTL=61

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 20ms, Average = 19ms

 

This is enough evidence here to show that Vessel is inferior to youtube and I can't understand why LTT are using it.

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×