1368476 - FVP v3.2.3.135 web players like WWE Network load up in 32-Bit fine. Fails to load a video on 64-Bit altogether.

Status: RESOLVED WORKSFORME

(Core Graveyard :: Plug-ins, defect, P3)

Description

[wrestletube1]

Attachment: WWE Network Firefox 64 MPEG/TS/M2TS/JS Framework No Java Required As Works Fine In FireFox 32 and Chrome 64 Bug

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20170518000419

Steps to reproduce:

Updated my Flash 64 player did bugger all still says Media Server Error on WWE Network which uses that player. 

Downloaded both FireFox 32 and Chrome 64 for troubleshooting and both worked fine FVP v3.2.3.135 problem is on FireFox 64 only.

Chrome 64 no longer supports Java software and neither does FireFox 32 anymore so FireFox 64 should be the superior FireFox loading all these video players but it doesn't load stuff from this major Flash player which seems to be the only one it doesn't load.

Diognostics say that the player is done with ts mpeg format playing though flash player a certian js container which doesn't need a full java software installed to run and the FireFox 32 and Chrome 64 tests prove that yet FireFox 64 doesn't seem to play ball.

I watch it on the app for Windows 10 anyway but sometimes it has maintenence server downtimes when I want to watch something so I go onto the browser to watch my content in those cases as the browser version most of the time isn't having server maintenence at the same time so I wouldn't have to wait had it been working like it did when I was on FireFox 32 back when the installation of full jave software was an option now it isn't I'm on FireFox 64 as it's better other than having this issue with this non java flash player which does use minor browser only based javascript but not the program as FireFox 32 and Chrome 64 also non java supporting but minor js supporting proves.


Actual results:

The logo video and content warnings on WWE Network actually loads. After content messeges finished it does the swirly circles to put the loaded video content on just like when it is working.

Main content video loads up as a black screen with a messege in the middle saying Media Error: Video not available at the top of the video screen in white text.


Expected results:

After the swirly circles your Live or On Demand video from WWE Network using FVP v3.2.3.135 loads up instead of the black and white screen given.

By the way WWE Network issues out 30 day free trails so I'm sure you can get it running for you and us by then.

The 30 day free trials is a great thing for sorting this issue out as you can test your bug fixes yourself.

It might even only be a minor issue like FireFox 64 Flash within the flash loader in the browser having issues with loading js framework flash files whilst the FireFox 32 flash loader has no such issue with js framework even though none of them support real java software anymore.

If the problem with js and mpeg and both the versions of ts framework flash player videos is to do with no full software java support then surely FireFox 32 and Chrome 64 should be crashing out as well it's a really whacky video framework bug guys.

Yeah, FVP v3.2.3.135 is a whacky player to begin with as well it switches between mpeg, ts, m2ts on the fly dynamicly depending on if your connection is having a bad moment of speed slowdowns whilst you are watching something.

Comment 1

[wrestletube1]

Attachment: WWE Network Working In FireFox 32 & Chrome 64 Dispite Them Being Flash Only Browsers Now Loading Up The js Framework Fine And The ts/mt2s/mpeg Codecs Are Also Working Fine In It

Picturee of the working FireFox 32 and Chrome 64 version of a proof of bug in FireFox 64 vidoe frameworks loading consept.

Comment 2

[wrestletube1]

(In reply to wrestletube1 from comment #1)
> Created attachment 8872344 [details]
> WWE Network Working In FireFox 32 & Chrome 64 Dispite Them Being Flash Only
> Browsers Now Loading Up The js Framework Fine And The ts/mt2s/mpeg Codecs
> Are Also Working Fine In It
> 
> Picturee of the working FireFox 32 and Chrome 64 version of a proof of bug
> in the FireFox 64 video frameworks loading consept.

Comment 3

[wrestletube1]

(In reply to wrestletube1 from comment #2)
> (In reply to wrestletube1 from comment #1)
> > Created attachment 8872344 [details]
> > WWE Network Working In FireFox 32 & Chrome 64 Dispite Them Being Flash Only
> > Browsers Now Loading Up The js Framework Fine And The ts/mt2s/mpeg Codecs
> > Are Also Working Fine In It
> > 
> > Picture of the working FireFox 32 and Chrome 64 version of a proof of bug
> > in the FireFox 64 video frameworks loading consept keep in mind that flashes are updated and all bowsers only have flash no real java although the working ones are loading basic js video frameworks without it whilst FireFox 64 isn't which is a big bug in it's minor js loading framework even if it's to do with the loading instructions on FireFox's end of Flash FireFox 64.

I suggest giving a go at merging some framework instrutions from FireFox 32 into 64 but then converting it into proper 64 bit version framework code so that this minor js framework that loads in 32-Bit without a java required can load in 64-Bit as well.

Comment 4

[wrestletube1]

(In reply to wrestletube1 from comment #3)
> (In reply to wrestletube1 from comment #2)
> > (In reply to wrestletube1 from comment #1)
> > > Created attachment 8872344 [details]
> > > WWE Network Working In FireFox 32 & Chrome 64 Dispite Them Being Flash Only
> > > Browsers Now Loading Up The js Framework Fine And The ts/mt2s/mpeg Codecs
> > > Are Also Working Fine In It
> > > 
> > > Picture of the working FireFox 32 and Chrome 64 version of a proof of bug
> > > in the FireFox 64 video frameworks loading consept keep in mind that flashes are updated and all bowsers only have flash no real java although the working ones are loading basic js video frameworks without it whilst FireFox 64 isn't which is a big bug in it's minor js loading framework even if it's to do with the loading instructions on FireFox's end of Flash FireFox 64.
> 
> I suggest giving a go at merging some framework instrutions from FireFox 32
> into 64 but then converting it into proper 64 bit version framework code so
> that this minor js framework that loads in 32-Bit without a java required
> can load in 64-Bit as well to give us fully working WWE Network in both versions without a need to downgrade back to inferior versions as the need to downgrade should be thrown out in the new non java world of FireFox and Chrome.

Comment 5

[wrestletube1]

(In reply to wrestletube1 from comment #4)
> (In reply to wrestletube1 from comment #3)
> > (In reply to wrestletube1 from comment #2)
> > > (In reply to wrestletube1 from comment #1)
> > > > Created attachment 8872344 [details]
> > > > WWE Network Working In FireFox 32 & Chrome 64 Dispite Them Being Flash Only
> > > > Browsers Now Loading Up The js Framework Fine And The ts/mt2s/mpeg Codecs
> > > > Are Also Working Fine In It
> > > > 
> > > > Picture of the working FireFox 32 and Chrome 64 version of a proof of bug
> > > > in the FireFox 64 video frameworks loading consept keep in mind that flashes are updated and all bowsers only have flash no real java although the working ones are loading basic js video frameworks without it whilst FireFox 64 isn't which is a big bug in it's minor js loading framework even if it's to do with the loading instructions on FireFox's end of Flash FireFox 64.
> > 
> > I suggest giving a go at merging some framework instrutions from FireFox 32
> > into 64 but then converting it into proper 64 bit version framework code so
> > that this minor js framework that loads in 32-Bit without a java required
> > can load in 64-Bit as well to give us fully working WWE Network in both versions without a need to downgrade back to inferior versions as the need to downgrade should be thrown out in the new non java world of FireFox and Chrome.

Edit: Just realized my only edit button is a reply button so when I edited my text into more details I wanted to talk about it posted my updated messeges one after another oh well.

Comment 6

[Benjamin Smedberg]

Jim perhaps another RTMPS issue?

Comment 7

[Jim Mathies [:jimm]]

seems likely, thanks.

Comment 8

[wrestletube1]

(In reply to Benjamin Smedberg [:bsmedberg] from comment #6)
> Jim perhaps another RTMPS issue?

Definitely likely as it uses that as the main streaming protocol.

Comment 9

[wrestletube1]

(In reply to wrestletube1 from comment #8)
> (In reply to Benjamin Smedberg [:bsmedberg] from comment #6)
> > Jim perhaps another RTMPS issue?
> 
> Definitely likely as it uses that as the main streaming protocol.

In fact seems like it's been reported to Adobe too.

https://forums.adobe.com/thread/2252679

Comment 10

[Jim Mathies [:jimm]]

should be working now in 55.

Comment 11

[vdbsh]

Hello there,
Bug has been reproduced on version 61.0.1 (64-bit).