help with installation of avplayer 1.6 with videojs required

[dlen]

Hello,

as I read, the new AVPlayer is made to work with videojs, a javascript object that modifies the html5-<video>- and <audio>-tag in such a way that control elements can be formatted and there be a flash-fallback for browser, which cannot deal with those tags.

Now trying to install that...
I copied the module files into /modules/avplayer , went to -extensions -modules, there it was, and hit "install".
First, I noticed, that the -extensions -modules page did not change and I thought, that installation somehow had failed. Then I realized, that the module is actually installed. So it seems there is a little bug there.

Then defining a player-dataset. With the flash player it's easy - copy it to some place, give it a name and put in the proper path and all the options. With this videojs I am lost, as there isn't a player file.

Also I want just an audio player, but there isn't a hint on the videojs-website, how to achive that nor that it is even possible.

Some hints would be of great value...

Dominik

[Dr.CSS]

You did read the modules Help, right..?

[dlen]

@Dr.Css: Yes of course.

Actually I made a little progress by doing the following in analogy to the old flash player procedure:

• Copy the video.js into some directory and put the right path into the location field.
• Put a link to video-js-min.css into the header.
• Create a mediafile dataset with the created player dataset, an alias and a path to the mp3-file. (Which worked very nice with the file selector, eliminating possible typos.)
• Call the module like before with module name and track alias: {cms_module module="avplayer" alias="namaste"}

I set no player options as I have not found an options list for the time being.

Result is: The alias appears as h3. A big "play"-button appears. After clicking it a "loading" graph or - on mouseover - a bar-like player with some controls. The loading never ends.

In the output source a <video> - tag has been introduced.
Neither in the unchanged nor the js-changed source code (via bugzilla) the path to the track can be found.

[Dr.CSS]

Maybe a link to the page would help...