First  Prev  61  62  63  64  65  66  67  68  69  70  71  72  73  74  75  76  77  Next  Last
Help with Video Playback Problems
jikap 
61475 cr points
Send Message: Send PM GB Post
24 / M / Norway
Offline
Posted 12/30/12 , edited 12/30/12

jikap wrote:





I'm afraid my streaming problems are on my end somewhere. Looking at other streaming services like youtube, and while it's by far less of a problem there, it does actually sometimes behave similarly there. With a buffer far larger than at crunchy, the moments where downloading works fine usually out-paces the stalls in the streaming though... With crunchy working fine on my Iphone, it's probably not an ISP issue either. :/

Geh, wish I knew what caused this, lol.
16 cr points
Send Message: Send PM GB Post
23 / M
Offline
Posted 12/30/12

Harkosion wrote:


hbk2818 wrote:

I also have a mac but I've been having problems with the video only playing on the top left hand corner when I fullscreen the video. I have tried updating adobe plugins for both safari and chrome but to no avail.


I'm also having the problem with both Safari and Chrome. I'm on a current gen Macbook Pro. Updating Flash plugins also didn't help. Everything else is fine in the window but it's just when it goes full screen it stays small and only takes up the top left corner of the screen while everything else is black.


It seems to be working now. Nevermind!
jikap 
61475 cr points
Send Message: Send PM GB Post
24 / M / Norway
Offline
Posted 12/30/12
Think I'm starting to get closer to the root of the problem... maybe. >_<;

In the security logs on my router, this have started appearing quite frequently:
Dec 31 01:18:15 Warn: The origin for route 239.255.255.250 changed from 192.168.2.x to 192.168.2.y
Dec 31 01:18:22 Warn: The origin for route 239.255.255.250 changed from 192.168.2.y to 192.168.2.x
Dec 31 01:18:23 Warn: MRT_DEL_MFC; Errno(2): No such file or directory

x being the ip for my computer, and y being the ip for the router.
239.255.255.250 seem to be generally used as a UPnP (Universal Plug and Play) broadcast channel...

going to my router's forum (belkin), and a quick search show other people getting the same problem within the last month or so, some people even getting disconnected because of it, though no solutions or definite cause have appeared yet. :/
39035 cr points
Send Message: Send PM GB Post
28 / M / Eastern Seaboard
Offline
Posted 12/30/12

Harkosion wrote:


Harkosion wrote:


hbk2818 wrote:

I also have a mac but I've been having problems with the video only playing on the top left hand corner when I fullscreen the video. I have tried updating adobe plugins for both safari and chrome but to no avail.


I'm also having the problem with both Safari and Chrome. I'm on a current gen Macbook Pro. Updating Flash plugins also didn't help. Everything else is fine in the window but it's just when it goes full screen it stays small and only takes up the top left corner of the screen while everything else is black.


It seems to be working now. Nevermind!


unfortunately my problems still continue...
Hynine 
15005 cr points
Send Message: Send PM GB Post
32 / M
Offline
Posted 12/30/12 , edited 12/31/12
Mine is a different issue with my internet service provider Verizon it does not seem to work at all with the apps iphone, xbox it is possible its all the apps. It works perfectly fine on the computers, i only get it working on the iphone or xbox using the cellular wifi have not tried other isp yet but any help getting it to work at home with Verizon would help.



Edit: Nevermind using google public DNS help fix the problem on my xbox and ipad.
64069 cr points
Send Message: Send PM GB Post
45 / M
Offline
Posted 1/6/13 , edited 1/6/13
Problems between 8pm and 12am on TWC NYC.

The videos start out playing fine with enough bandwidth stream to play properly, but then stream drops off to a trickle and eventually stops entirely. It does not start again unless the browser is reloaded, and unfortunately, when this happens it can take up to 10 reloads to finally get through a video.

I do not have this problem with any other streaming site, and I was able to watch a video this afternoon without a problem.

It appears that your CDN's servers on the TWC NYC network are getting overloaded during the evening hours.

I have seen this problem with the following servers, both last night when I was trying to watch Space Brothers and HunterXHunter, and tonight about 20 minutes ago when trying to watch Folktales from Japan (all with 1080p):

24.143.204.47
24.143.204.62
24.143.204.63
24.143.204.79
24.143.204.93
24.143.204.101

Again, I do not have this problem with any other streaming site. This was not a problem last week. I'm not sure when this started, because there weren't any new videos during the week so I was not watching during primetime. I was able to watch Fairy Tail yesterday morning, and DT this afternoon.

My own bandwidth is not a problem.




I also do not see any routing issues, latency or dropped packets when pinging or tracerouting:

bash-3.2$ traceroute 24.143.204.47
traceroute to 24.143.204.47 (24.143.204.47), 64 hops max, 52 byte packets
1 10.56.224.1 (10.56.224.1) 9.553 ms 7.377 ms 8.937 ms
2 gig-0-3-0-22-nycmnye-rtr01.nyc.rr.com (24.168.137.169) 6.711 ms 7.832 ms 13.102 ms
3 bun105.nycmnytg-rtr001.nyc.rr.com (184.152.112.114) 11.677 ms 13.804 ms 9.454 ms
4 bun6-nycmnytg-rtr002.nyc.rr.com (24.29.148.250) 12.084 ms 14.429 ms 15.867 ms
5 107.14.19.24 (107.14.19.24) 16.329 ms 15.380 ms 15.985 ms
6 107.14.19.153 (107.14.19.153) 8.451 ms
ae-1-0.pr0.nyc30.tbone.rr.com (66.109.6.161) 9.416 ms
107.14.19.153 (107.14.19.153) 9.870 ms
7 24.143.204.47 (24.143.204.47) 10.324 ms 8.941 ms 10.444 ms
bash-3.2$ traceroute 24.143.204.62
traceroute to 24.143.204.62 (24.143.204.62), 64 hops max, 52 byte packets
1 10.56.224.1 (10.56.224.1) 27.377 ms 7.023 ms 27.891 ms
2 gig-0-3-0-3-nycmnyte-rtr1.nyc.rr.com (24.29.97.106) 8.250 ms 9.049 ms 9.957 ms
3 bun105.nycmnytg-rtr001.nyc.rr.com (184.152.112.114) 13.348 ms 9.183 ms 14.983 ms
4 bun6-nycmnytg-rtr002.nyc.rr.com (24.29.148.250) 20.313 ms 15.729 ms 17.184 ms
5 107.14.19.24 (107.14.19.24) 18.320 ms 15.181 ms 22.625 ms
6 ae-1-0.pr0.nyc30.tbone.rr.com (66.109.6.161) 28.128 ms
107.14.19.153 (107.14.19.153) 9.436 ms 10.929 ms
7 24.143.204.62 (24.143.204.62) 10.840 ms 10.489 ms 9.575 ms
bash-3.2$ traceroute 24.143.204.63
traceroute to 24.143.204.63 (24.143.204.63), 64 hops max, 52 byte packets
1 10.56.224.1 (10.56.224.1) 10.473 ms 6.629 ms 30.996 ms
2 gig-0-3-0-22-nycmnye-rtr01.nyc.rr.com (24.168.137.169) 7.632 ms 7.422 ms 9.968 ms
3 bun105.nycmnytg-rtr001.nyc.rr.com (184.152.112.114) 14.519 ms 16.995 ms 14.058 ms
4 bun6-nycmnytg-rtr002.nyc.rr.com (24.29.148.250) 13.106 ms 15.475 ms 15.422 ms
5 ae-4-0.cr0.nyc30.tbone.rr.com (66.109.6.78) 10.936 ms 26.629 ms 16.558 ms
6 ae-1-0.pr0.nyc30.tbone.rr.com (66.109.6.161) 9.962 ms 9.550 ms 20.461 ms
7 24.143.204.63 (24.143.204.63) 9.177 ms 11.046 ms 11.474 ms
bash-3.2$ traceroute 24.143.204.79
traceroute to 24.143.204.79 (24.143.204.79), 64 hops max, 52 byte packets
1 10.56.224.1 (10.56.224.1) 17.668 ms 23.725 ms 7.321 ms
2 gig-0-3-0-3-nycmnyte-rtr1.nyc.rr.com (24.29.97.106) 8.685 ms 10.555 ms 14.797 ms
3 bun105.nycmnytg-rtr001.nyc.rr.com (184.152.112.114) 13.674 ms 15.996 ms 15.761 ms
4 bun6-nycmnytg-rtr002.nyc.rr.com (24.29.148.250) 8.280 ms 16.141 ms 15.313 ms
5 ae-4-0.cr0.nyc30.tbone.rr.com (66.109.6.78) 22.093 ms 15.586 ms 16.019 ms
6 ae-1-0.pr0.nyc30.tbone.rr.com (66.109.6.161) 43.229 ms
107.14.19.153 (107.14.19.153) 9.828 ms 12.105 ms
7 24.143.204.79 (24.143.204.79) 10.214 ms 8.455 ms 9.719 ms
bash-3.2$ traceroute 24.143.204.93
traceroute to 24.143.204.93 (24.143.204.93), 64 hops max, 52 byte packets
1 10.56.224.1 (10.56.224.1) 9.290 ms 7.858 ms 11.310 ms
2 gig-0-3-0-9-nycmnyte-rtr1.nyc.rr.com (24.168.139.233) 8.133 ms 6.935 ms 8.533 ms
3 bun105.nycmnytg-rtr001.nyc.rr.com (184.152.112.114) 11.202 ms 11.576 ms 11.960 ms
4 bun6-nycmnytg-rtr002.nyc.rr.com (24.29.148.250) 11.320 ms 25.131 ms 13.254 ms
5 107.14.19.24 (107.14.19.24) 13.938 ms 15.692 ms 24.347 ms
6 107.14.19.153 (107.14.19.153) 9.473 ms 18.584 ms
ae-1-0.pr0.nyc30.tbone.rr.com (66.109.6.161) 13.491 ms
7 24.143.204.93 (24.143.204.93) 9.053 ms 11.008 ms 14.801 ms
bash-3.2$ traceroute 24.143.204.101
traceroute to 24.143.204.101 (24.143.204.101), 64 hops max, 52 byte packets
1 10.56.224.1 (10.56.224.1) 10.676 ms 11.246 ms 9.312 ms
2 gig-0-3-0-9-nycmnyte-rtr1.nyc.rr.com (24.168.139.233) 12.180 ms 12.715 ms 8.687 ms
3 bun105.nycmnytg-rtr001.nyc.rr.com (184.152.112.114) 14.758 ms 16.874 ms 13.930 ms
4 bun6-nycmnytg-rtr002.nyc.rr.com (24.29.148.250) 15.082 ms 16.100 ms 16.723 ms
5 107.14.19.24 (107.14.19.24) 17.692 ms 15.413 ms 17.138 ms
6 107.14.19.153 (107.14.19.153) 16.467 ms
ae-1-0.pr0.nyc30.tbone.rr.com (66.109.6.161) 9.337 ms
107.14.19.153 (107.14.19.153) 8.809 ms
7 24.143.204.101 (24.143.204.101) 11.453 ms 10.419 ms 9.689 ms
bash-3.2$ ping 24.143.204.47
PING 24.143.204.47 (24.143.204.47): 56 data bytes
64 bytes from 24.143.204.47: icmp_seq=0 ttl=122 time=15.107 ms
64 bytes from 24.143.204.47: icmp_seq=1 ttl=122 time=9.706 ms
64 bytes from 24.143.204.47: icmp_seq=2 ttl=122 time=10.056 ms
64 bytes from 24.143.204.47: icmp_seq=3 ttl=122 time=9.522 ms
64 bytes from 24.143.204.47: icmp_seq=4 ttl=122 time=12.496 ms
^C
--- 24.143.204.47 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 9.522/11.377/15.107/2.151 ms
bash-3.2$ ping 24.143.204.62
PING 24.143.204.62 (24.143.204.62): 56 data bytes
64 bytes from 24.143.204.62: icmp_seq=0 ttl=122 time=18.252 ms
64 bytes from 24.143.204.62: icmp_seq=1 ttl=122 time=9.391 ms
64 bytes from 24.143.204.62: icmp_seq=2 ttl=122 time=8.514 ms
64 bytes from 24.143.204.62: icmp_seq=3 ttl=122 time=9.867 ms
64 bytes from 24.143.204.62: icmp_seq=4 ttl=122 time=16.822 ms
^C
--- 24.143.204.62 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 8.514/12.569/18.252/4.104 ms
bash-3.2$ ping 24.143.204.63
PING 24.143.204.63 (24.143.204.63): 56 data bytes
64 bytes from 24.143.204.63: icmp_seq=0 ttl=122 time=16.310 ms
64 bytes from 24.143.204.63: icmp_seq=1 ttl=122 time=10.000 ms
64 bytes from 24.143.204.63: icmp_seq=2 ttl=122 time=10.638 ms
64 bytes from 24.143.204.63: icmp_seq=3 ttl=122 time=9.220 ms
64 bytes from 24.143.204.63: icmp_seq=4 ttl=122 time=8.580 ms
^C
--- 24.143.204.63 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 8.580/10.950/16.310/2.769 ms
bash-3.2$ ping 24.143.204.79
PING 24.143.204.79 (24.143.204.79): 56 data bytes
64 bytes from 24.143.204.79: icmp_seq=0 ttl=122 time=9.009 ms
64 bytes from 24.143.204.79: icmp_seq=1 ttl=122 time=16.071 ms
64 bytes from 24.143.204.79: icmp_seq=2 ttl=122 time=9.181 ms
64 bytes from 24.143.204.79: icmp_seq=3 ttl=122 time=11.103 ms
64 bytes from 24.143.204.79: icmp_seq=4 ttl=122 time=10.146 ms
64 bytes from 24.143.204.79: icmp_seq=5 ttl=122 time=10.605 ms
^C
--- 24.143.204.79 ping statistics ---
6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 9.009/11.019/16.071/2.376 ms
bash-3.2$ ping 24.143.204.93
PING 24.143.204.93 (24.143.204.93): 56 data bytes
64 bytes from 24.143.204.93: icmp_seq=0 ttl=122 time=25.497 ms
64 bytes from 24.143.204.93: icmp_seq=1 ttl=122 time=9.078 ms
64 bytes from 24.143.204.93: icmp_seq=2 ttl=122 time=10.727 ms
64 bytes from 24.143.204.93: icmp_seq=3 ttl=122 time=9.625 ms
64 bytes from 24.143.204.93: icmp_seq=4 ttl=122 time=10.140 ms
64 bytes from 24.143.204.93: icmp_seq=5 ttl=122 time=10.332 ms
^C
--- 24.143.204.93 ping statistics ---
6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 9.078/12.566/25.497/5.806 ms
bash-3.2$ ping 24.143.204.103
PING 24.143.204.103 (24.143.204.103): 56 data bytes
64 bytes from 24.143.204.103: icmp_seq=0 ttl=122 time=10.209 ms
64 bytes from 24.143.204.103: icmp_seq=1 ttl=122 time=10.031 ms
64 bytes from 24.143.204.103: icmp_seq=2 ttl=122 time=15.985 ms
64 bytes from 24.143.204.103: icmp_seq=3 ttl=122 time=10.396 ms
64 bytes from 24.143.204.103: icmp_seq=4 ttl=122 time=17.070 ms
^C
--- 24.143.204.103 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 10.031/12.738/17.070/3.115 ms


bash-3.2$ ping 24.143.204.47
PING 24.143.204.47 (24.143.204.47): 56 data bytes
64 bytes from 24.143.204.47: icmp_seq=0 ttl=122 time=10.680 ms
64 bytes from 24.143.204.47: icmp_seq=1 ttl=122 time=12.420 ms
64 bytes from 24.143.204.47: icmp_seq=2 ttl=122 time=9.390 ms
64 bytes from 24.143.204.47: icmp_seq=3 ttl=122 time=18.230 ms
64 bytes from 24.143.204.47: icmp_seq=4 ttl=122 time=9.629 ms
64 bytes from 24.143.204.47: icmp_seq=5 ttl=122 time=10.275 ms
64 bytes from 24.143.204.47: icmp_seq=6 ttl=122 time=14.002 ms
64 bytes from 24.143.204.47: icmp_seq=7 ttl=122 time=18.519 ms
64 bytes from 24.143.204.47: icmp_seq=8 ttl=122 time=9.433 ms
64 bytes from 24.143.204.47: icmp_seq=9 ttl=122 time=8.694 ms
64 bytes from 24.143.204.47: icmp_seq=10 ttl=122 time=8.320 ms
64 bytes from 24.143.204.47: icmp_seq=11 ttl=122 time=10.462 ms
64 bytes from 24.143.204.47: icmp_seq=12 ttl=122 time=10.929 ms
64 bytes from 24.143.204.47: icmp_seq=13 ttl=122 time=11.417 ms
64 bytes from 24.143.204.47: icmp_seq=14 ttl=122 time=16.334 ms
64 bytes from 24.143.204.47: icmp_seq=15 ttl=122 time=9.017 ms
64 bytes from 24.143.204.47: icmp_seq=16 ttl=122 time=8.358 ms
64 bytes from 24.143.204.47: icmp_seq=17 ttl=122 time=11.209 ms
64 bytes from 24.143.204.47: icmp_seq=18 ttl=122 time=10.272 ms
64 bytes from 24.143.204.47: icmp_seq=19 ttl=122 time=19.681 ms
64 bytes from 24.143.204.47: icmp_seq=20 ttl=122 time=10.625 ms
64 bytes from 24.143.204.47: icmp_seq=21 ttl=122 time=9.314 ms
64 bytes from 24.143.204.47: icmp_seq=22 ttl=122 time=18.259 ms
64 bytes from 24.143.204.47: icmp_seq=23 ttl=122 time=9.727 ms
64 bytes from 24.143.204.47: icmp_seq=24 ttl=122 time=10.305 ms
64 bytes from 24.143.204.47: icmp_seq=25 ttl=122 time=11.469 ms
64 bytes from 24.143.204.47: icmp_seq=26 ttl=122 time=10.830 ms
64 bytes from 24.143.204.47: icmp_seq=27 ttl=122 time=10.746 ms
64 bytes from 24.143.204.47: icmp_seq=28 ttl=122 time=17.095 ms
64 bytes from 24.143.204.47: icmp_seq=29 ttl=122 time=15.303 ms
64 bytes from 24.143.204.47: icmp_seq=30 ttl=122 time=10.407 ms
64 bytes from 24.143.204.47: icmp_seq=31 ttl=122 time=17.362 ms
64 bytes from 24.143.204.47: icmp_seq=32 ttl=122 time=8.451 ms
64 bytes from 24.143.204.47: icmp_seq=33 ttl=122 time=9.997 ms
64 bytes from 24.143.204.47: icmp_seq=34 ttl=122 time=8.623 ms
64 bytes from 24.143.204.47: icmp_seq=35 ttl=122 time=9.189 ms
64 bytes from 24.143.204.47: icmp_seq=36 ttl=122 time=9.591 ms
64 bytes from 24.143.204.47: icmp_seq=37 ttl=122 time=9.268 ms
64 bytes from 24.143.204.47: icmp_seq=38 ttl=122 time=10.528 ms
64 bytes from 24.143.204.47: icmp_seq=39 ttl=122 time=10.148 ms
64 bytes from 24.143.204.47: icmp_seq=40 ttl=122 time=9.693 ms
64 bytes from 24.143.204.47: icmp_seq=41 ttl=122 time=11.116 ms
64 bytes from 24.143.204.47: icmp_seq=42 ttl=122 time=10.869 ms
64 bytes from 24.143.204.47: icmp_seq=43 ttl=122 time=10.022 ms
64 bytes from 24.143.204.47: icmp_seq=44 ttl=122 time=15.906 ms
64 bytes from 24.143.204.47: icmp_seq=45 ttl=122 time=10.608 ms
64 bytes from 24.143.204.47: icmp_seq=46 ttl=122 time=15.384 ms
64 bytes from 24.143.204.47: icmp_seq=47 ttl=122 time=9.033 ms
64 bytes from 24.143.204.47: icmp_seq=48 ttl=122 time=10.572 ms
64 bytes from 24.143.204.47: icmp_seq=49 ttl=122 time=9.753 ms
64 bytes from 24.143.204.47: icmp_seq=50 ttl=122 time=9.351 ms
^C
--- 24.143.204.47 ping statistics ---
51 packets transmitted, 51 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 8.320/11.506/19.681/3.049 ms

64069 cr points
Send Message: Send PM GB Post
45 / M
Offline
Posted 1/7/13
Happily, no problems this evening. I was able to watch all 3 premieres without any stalling or stopping.

Vegetable Support Manager
Bjaker 
35285 cr points
Send Message: Send PM GB Post
33 / M / San Francisco
Offline
Posted 1/8/13


Thank you for the follow up.

There have been some CDN Issues that we've been working to resolve.

Apologies for any inconvenience.
jikap 
61475 cr points
Send Message: Send PM GB Post
24 / M / Norway
Offline
Posted 1/8/13
All my streaming troubles seem to have mysteriously disappeared today, I got no idea why, lol.
Hope it'll still be cured tomorrow...
64069 cr points
Send Message: Send PM GB Post
45 / M
Offline
Posted 1/8/13 , edited 1/8/13

Bjaker wrote:



Thank you for the follow up.

There have been some CDN Issues that we've been working to resolve.

Apologies for any inconvenience.


Well, tonight while watching Love Live! School Idol Project (720p) and Shin Sekai Yori (1080p) - the video stopped once per video, and did not resume.

Fortunately, after reload pages in my browser, both videos continued to the end without interruption. It definitely wasn't as bad as it was the other day, when every video kept completely stopping multiple times.

The CDN servers that I was connected to tonight when the videos dropped were:

24.143.204.62 and 24.143.204.47


Vegetable Support Manager
Bjaker 
35285 cr points
Send Message: Send PM GB Post
33 / M / San Francisco
Offline
Posted 1/9/13


Thank you for the follow up.
I'll look into this.

19189 cr points
Send Message: Send PM GB Post
28 / F / Oklahoma
Offline
Posted 1/12/13
For all of those who are having problems with buffering, like I was, and have tested their internet and it's fine:

Turn off your windows updates! And any other automatic updates that are not your spyware/adware/ that kind of thing software.

I now have no problems streaming at 720
64069 cr points
Send Message: Send PM GB Post
45 / M
Offline
Posted 1/12/13

skidnaus wrote:


Bjaker wrote:



Thank you for the follow up.

There have been some CDN Issues that we've been working to resolve.

Apologies for any inconvenience.


Well, tonight while watching Love Live! School Idol Project (720p) and Shin Sekai Yori (1080p) - the video stopped once per video, and did not resume.

Fortunately, after reload pages in my browser, both videos continued to the end without interruption. It definitely wasn't as bad as it was the other day, when every video kept completely stopping multiple times.

The CDN servers that I was connected to tonight when the videos dropped were:

24.143.204.62 and 24.143.204.47





It looks like the traffic on Saturday nights when Space Brothers and HunterXHunter are released is too much for the CDN servers on NYC Time Warner Cable to handle.

During the day, it was fine, but while watching these two shows, the streaming speed occasionally failed to keep with the video, and 3 to 4 times during each video, the stream just stopped entirely and I had to reload to get it to continue.

Similar list of servers as the last time:


24.143.204.62
24.143.204.79
24.143.204.93

3028 cr points
Send Message: Send PM GB Post
Offline
Posted 1/12/13
I've done everything I can think of, but it seems the problem with video stuttering/buffering/playback lies with CR. I have a 30 meg connection and this never happens on other streaming sites. They probably need a better video player/method or multiple methods of playback or I'm not going to pay. Very frustrating...
2033 cr points
Send Message: Send PM GB Post
Offline
Posted 1/14/13
I'm on free trial, and while streams are smooth as silk in 720p, I'm experiencing the dreaded "video player loads, but the show won't start at all"-problem. It's completely random too: streaming can work perfectly half a day, then it's not working for another whole day, then it can work for two days...without any reason. Not on my end, anyway. The first time it happened, I tried all the solutions offered by Crunchyroll, to no avail, and then it simply worked the next day. Right now I can't stream, it's been like this since late last night. Strangely, this only happens on my PC, as I've tried streaming from my iPad when it won't stream on my PC, and it works perfectly. Which makes the whole problem even more baffling. Maybe there's some buggy code that randomly makes it not work in computer browsers, who knows. Reading through this thread, it's quite obvious that the setup on Crunchyroll could be improved, maybe just throw out the old player, and in with a new one. I hope things get better in the future, as I love the concept of this site.
First  Prev  61  62  63  64  65  66  67  68  69  70  71  72  73  74  75  76  77  Next  Last
You must be logged in to post.