owncloud-archive / apps

Repo for ownCloud apps. Code here is work in progress and not intended for endusers
373 stars 337 forks source link

files_videoviewer - Safari BUG #1128

Open fsmeier opened 11 years ago

fsmeier commented 11 years ago

I have a Video that can be played in FF, but not in Safari (5.1.7) ... it's an mp4... the wmv-file can't be played by FF and Safari, but this seems like a normal codec-problem for me...

but when a video works for one browser and for another not.. it seems like a bug... :-/

MorrisJobke commented 11 years ago

cc @VicDeo

az0bcd commented 11 years ago

I'm also suffering the same problem. OC 5.0.7 (OSX 10.8.4) No video in Chrome or Safari but does work in FF.

D1reW0lf commented 11 years ago

Hi!

Just to let the devs know that this bug still exists under OC 5.0.11 (OS X 10.8.5).

Thanks! Pedro Fardilha

VicDeo commented 11 years ago

Here is what our upstream says (MediaElement.js) http://mediaelementjs.com/#devices

Adobe has pledged to support WebM in future versions of Flash (May 2010, again June 2011) which will enable playback in Safari (which may never support WebM) and older browsers. So far, it is only a promise :(

D1reW0lf commented 11 years ago

Hi.

I just tried with a "pure Apple style" mp4 file (H264/AAC) that according to the devices section of MediaElements.js should work, but still no luck. All that I'm getting is a never stopping loading icon. OC and Apache log doesn't show anything related to this.

ckujau commented 10 years ago

FWIW, this works for me with Safari 5.1.10 on MacOS 10.6.8 and also with Safari 5.1.9 on MacOS 10.6.8 Server. However, a friend of mine (who pointed me to this bug report) said it's not working with Safari 6.1.1 on MacOS 10.7.5. Unfortunately we have no further details so far.

codyxbell commented 10 years ago

Just curious, I have been trying to get apple native mp4 files to work in IOS devices and all I get is a play button with a line through it. If i navigate to the file manually, avoiding video viewer the file will play... is this related to this bug? Should I submit an issue separately from this bug?