Web Player 2.0b not working on my Mac :-\

Well the new beta doesn’t appear to be working for me.
Before installing I got a warning I needed the plug-in when I went to the announcement page (as expected).
No more warning after installing (so I suspect the plug-in is properly detected) but the are where the video should be is simply blank…

Mac Pro 4 x 3.0GHz
8GB RAM
MacOS X 10.6.1
Safari in 64 bit on this Mac.

Wrapping it up

Hey guys,

I'm wrapping up this thread for now. More work around 64-bit browsers will come later. There have indeed been a myriad of technology changes in this new version of DivX Plus Web Player and we've been primarily focusing around introducing support for DivX Plus (H.264/AAC/MKV) files as described in labs article.

This is the first release of the new stack only and of course there will be more to come including the broader support that you're looking for.

Keep the conversation positive and together we will make each release stronger :)

- Al

I made more tests… It

I made more tests… It works in FireFox (but the video is really really dark and borderline black and white).
I suspect that the plug-in is simply not 64-bit ready :-\

Corentin

=-=-=-=-=-=-=-=-=-=-=-=
Alea jacta Ouest

Snow Leopard isn't an

Snow Leopard isn't an officially supported OS yet. In our limited testing of Web Player on Snow Leopard it has worked well in 32-bit browsers. Safari can be launched in 32-bit mode, or you can use Firefox which is only 32-bit.

As for the dark video issue, can you tell me what graphics chip your Mac has? We have seen (and fixed) this issue that happened on ATI X1600 chips, but it may happen to others that we don't have test machines for.

You can check what graphics chip you have by clicking the Apple icon in the top left corner then About This Mac->More Info. This will launch the system profiler. On the left hand side go to Hardware->Graphics/Displays. You should see the your graphics "Chipset Model" on the right.

Here's my setup: Mac Pro 4 x

Here's my setup:
Mac Pro 4 x 3.0GHz
8GB RAM
MacOS X 10.6.1

The video card is a RadeonX1900
My default browser is OmniWeb anyway (and it's 32 bit), but I thought I had to report the issue with Safari.
It's sad that the current version of MacOS X is not supported :-\ but I guess it'll come later…

Corentin

=-=-=-=-=-=-=-=-=-=-=-=
Alea jacta Ouest

Yeah, unfortunately Apple

Yeah, unfortunately Apple likes to keep software partners on their toes with new releases. Architecturally there are a lot more changes between Leopard and Snow Leopard than between Windows Vista and 7.

Thanks for the info on your video card. The chip we had dark video issues with internally is an ATI X1600, so I imagine we can apply the same fix to the X1900 as well. If your issue issue is the same one we encountered you can work around it by putting the Web Player into Full Screen or Pop-out mode and then going back to embedded mode.

You do realize that Safari

You do realize that Safari even in 64 bit mode can load 32 bit plugins. Why?

Because the plug-in runs as a different process. The np plugin interface has been updated for 64 bit apps, apparently DivX hasn't gotten the memo. As for on your toes, Snow Leopard was in developer preview mode since at least WWDC 2008.

Very nice to see you here

Very nice to see you here LordRPI :-)

I can do nothing but agree with what you are saying.
Snow Leopard is hardly news for developpers…

Corentin

=-=-=-=-=-=-=-=-=-=-=-=
Alea jacta Ouest

Right, I've visited the

Right, I've visited the webpage that Apple posted about the new plugins. Here you can find the revision history: http://developer.apple.com/mac/library/documentation/InternetWeb/Conceptual/WebKit_PluginProgTopic/RevisionHistory/RevisionHistory.html#//apple_...

Since March 13 2009 Apple has documented the new conditions for plugins.

Paul, you might want to do some more research on the subject in the future before in order to maintain your aura of competence. Random conjecture presented using corporate buzzwords does not fool the vast majority of independent thinkers.

Even if DivX did find implementing the new plugins "confusing", the Apple Developer Connection Select Membership comes with two (2) Developer Technical Support Incidents in which you can use to get support from the source. This isn't rocket surgery.

We are planning on making

We are planning on making Web Player work in 64-bit Safari in Snow Leopard, it just isn't something that is done yet. It requires us to completely move all of our Carbon code to Cocoa (which we hadn't planned to do yet), and Apple only gave developers a six-month heads up from when they wrote that document to when Snow Leopard shipped.

You can still make Web Player work on 64-bit Snow Leopard by using Firefox or running Safari in 32-bit mode (Ctrl-Click Safari->Get Info, check "Open in 32-bit mode").

It looks like the Web Player is far from the only plugin to have issues with 64-bit Safari on Snow Leopard as well.

The phasing out of carbon

The phasing out of carbon for 64 bit environments is nothing new. In fact they told us of this starting at the Apple WWDC 2007. You can see a revision history for this document here: http://developer.apple.com/mac/library/documentation/Carbon/Conceptual/Carbon64BitGuide/RevisionHistory.html#//apple_ref/doc/uid/TP40004381-CH6-SW1

It looks like the total underpinnings of the DivX Web Player and DivX Player have changed - notably in the plugin architecture (that has also brought out embarrassing unintended consequences). Having the foresight to not write it using Carbon apparently slipped DivX's mind. Qt 5, for example, was recently re-written in Cocoa.

Pointing out that other plugins do not work does not suddenly make it OK to say "oh, just because other people are having problems, it gives us an excuse." DivX is a public company - it should produce public-company class products (I see Adobe had Flash ready, and we know Apple is not nice to them on the iPhone). DivX should not be blaming Apple for suddenly changing things when more than adequate notice was given, but it did fall on deaf ears. Instead, as an end user, I'd feel more confident if DivX could say, "We did not fully account for this and we are sorry for any inconvenience this has caused. The problems is being addressed and we hope to have a build to our wonderful customers out soon - because, we all know that DivX gives the best user experience out of all video player plug-ins and want our customers to be completely satisfied" - Yet, I see that "Snow Leopard is not supported because Apple likes to surprise us." That statement is un-DivX like. DivX is about making a better media future regardless of the roadblocks that inherently exist in the current marketplace.

I remember as a young(er) developer during the Intel transitions, I accidentally introduced a divide by zero error in certain malformed AVIs. It was a public beta release and as the report came in, I said, "This is a malformed AVI and caused a crash." I didn't realize that by saying "malformed" it implied I was not going to fix it - the users were livid because they thought I was implying this. I was horrified that the users would think I would ignore it and not fix it - it was the furthest thing from the truth. So in essence, maybe it is best to address the end goal rather than the impediments in the way by assigning blame to a 3rd party.

Maybe my expectations of DivX are a little high. I used to think that if any company on earth had life figured out, it was DivX - and seriously, I still want to believe this.

Carpe Visum.

You expectations are high.

You expectations are high. DivX is not that company.

:: sixsidedvideo.com ::